Sponsored Content
Full Discussion: Veritas DataBase Backup
Operating Systems Solaris Veritas DataBase Backup Post 76155 by ppass on Saturday 25th of June 2005 08:29:42 AM
Old 06-25-2005
Quote:
Originally Posted by networkfre@k
Some things to know:

x) Do you have the master+media server on the same server ?
x) Do you have the Shared storage option enabled
(Tape Library in a SAN) ?
x) Do you have additional licenses installed (like Oracle extension,open file backup

networkfreak
yes we have all of the above except the additional license , for backups we are using RMAN .
actually we have a hot backup database scipt that comes with veritas and we are doing hotbackups almost daily .
veritas uses RMAN to do the backups . it connect to it and opens the chennels and takes backup .

only the shutdown /startup is done manually .

thanks u very much

cheers
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Backup of Product Database

HI, I know its scarey me asking this, but system is homegrown and I am just having fun, but at the same time dont want to have tooo much fun where the phrase "little knowledge is dangerous" perfectly fits my actions ;-). I have a couple of packages that are failing to be removed... #... (2 Replies)
Discussion started by: Student37
2 Replies

2. SuSE

SuSE Backup on Veritas

I am running SuSE 9.1 and want to backup my LVM vg00 on Veritas Backup Exec 10 Win2K server. My problem, I am unable to browse any of the folder/files of LVM vg00 in Veritas. He could find files on rooot but not in LVM. Any idea/help will be much appreciated. Thanks, Aa (1 Reply)
Discussion started by: aamirs
1 Replies

3. SCO

Veritas Backup Agent on SCO problem

Hello All, We have Veritas Backup Exec on a Windows 2003 OS and trying to setup the Ralus agent on SCO to perform regular backups of our Unixware system; but for some reason after "I believe" installing the agent on SCO; and launching it using the 'agent.be" command I receive a syntax error... (1 Reply)
Discussion started by: Yorgy
1 Replies

4. SCO

Veritas Unix Backup Agent won't start

I have 3 SCO 5.0.5 machines. Two are running the /etc/bkupexec/agent.be just fine but the 3rd fails with a NRL initialization error. It can't seem to find the backup server in the /etc/hosts file. The entry is in the /etc/hosts file. The perms are set correctly on /etc /etc/bkupexec... (0 Replies)
Discussion started by: cnpaul
0 Replies

5. UNIX and Linux Applications

Problem with Database backup

Hi! This is my first post and im not that familiar with UNIX but I'll try to explain my problem.. I have a server here at work running Open UNIX Release 8.0.0 It has a special application on it that I'm trying to run a database backup on. For the last 2 weeks this has failed.. Usually the... (2 Replies)
Discussion started by: TaZ
2 Replies

6. Solaris

How can i take private region backup in veritas

Hello experts, I am using Veritas Volume Manager 5.0. How can i take private region backup and restoration. thanks in advance... (3 Replies)
Discussion started by: younus_syed
3 Replies

7. AIX

AIX 5.3 & Veritas Backup with Tape Library

hello, I am facing this problem when trying to prepare AIX 5.3 for Veritas Backup: Veritas Software is not able to communicate properly with our tape library When we tried to run these commands here's the output # cfgmgr -l fscsi0 # cfgmgr -l fscsi2 # cfgmgr -l fscsi1 cfgmgr:... (3 Replies)
Discussion started by: filosophizer
3 Replies

8. AIX

Help me install Backup Exec (formerlly owned by Veritas) agent on AIX machine :(

Hi all. I hope someone could give me a hand on installing Backup Exec agent on AIX machine :( Agent: OS: AIX 5.3 Hostname: DB-HN-SRV02 IP: 10.1.4.64 Backup server: OS: Windows Server 2003 Hostname: backup-srv IP: 10.1.5.51 I download "Legacy Unix agent.tar", untar, then run file... (0 Replies)
Discussion started by: bsddaemon
0 Replies

9. Shell Programming and Scripting

script for backup database

Hello sir, i have used this for taking the database backup 5 * * * * \usr\bin\sh\mysqldump -h localhost -u username-ppassword cms> /home/dbbackup.sql. but it creates a zero size database and in mail it gives error like command not found. Please Help me (3 Replies)
Discussion started by: niva
3 Replies

10. Solaris

how to restore backup from veritas vm in ufs file system

Hi all I have a DLT tape in that tape backup is there is in veritas volume format and i want to restore it in ufs file system how can i do it? right now i don't have veritas file system setup. i have only ufs file sysytem please help some production data is to be restore. backup was taken... (0 Replies)
Discussion started by: nikhil kasar
0 Replies
nisbackup(1M)						  System Administration Commands					     nisbackup(1M)

NAME
nisbackup - backup NIS+ directories SYNOPSIS
nisbackup [-v] backup-dir directory... nisbackup [-v] -a backup-dir DESCRIPTION
nisbackup backs up a NIS+ directory object on a NIS+ master server. Updates to the NIS+ database will be temporarily disabled while nis- backup is running. The backup-dir is a UNIX directory that must exist prior to running nisbackup. The nisbackup command can be used to backup an individual NIS+ directory object or all ( -a) of the NIS+ directory objects served by a master server. The NIS+ directory objects being backed up will be placed into subdirectories under the backup-dir directory. These subdirectories are named according to the NIS+ directory object they contain. nisbackup operates on individual NIS+ directory objects (for example, org_dir.wiz.com). This allows an administrator to selectively backup specific directories. The rpc.nisd(1M) process must be running on the master server with a stable NIS+ database for nisbackup to complete. nisbackup will not attempt to correct any corruption in the NIS+ database, so it is important that backups be done regularly as part of the NIS+ administra- tion. The first synopsis is used to backup a single NIS+ directory object or a list of NIS+ directory objects. The objects can be partially qual- ified or fully qualified. The machine on which the command is executing must be the master for the NIS+ directory objects specified. The second synopsis will backup all of the NIS+ directory objects that are served by this master. The -a option is the recommended method of backing up a master server, since it will backup all NIS+ directory objects that are served by this master. If this server is a master server for more than one domain, the backup will include NIS+ directories that belong to all of the domains served. Individual NIS+ direc- tory objects can be selected for restoring from a backup-dir created with the -a option. See nisrestore(1M). The -a option only includes directory objects for which this server is the master. It is possible, but not recommended, to configure a master server as a replica for other domains. The objects belonging to those replicated domains will not be backed up with the -a option. The backup of replicated objects must be run on the master server for those objects. Do not use the same backup-dir to backup different master servers. Each master server must have its own backup-dir. nisbackup will set the rpc.nisd(1M) to read only mode, which will disable updates to the NIS+ database. This is neccessary to ensure the consistency of the backup. For this reason, nisbackup should not be run while large numbers of updates are being applied to the NIS+ data- base. Update utilities such as nisaddent(1M) should not be run simultaneously with nisbackup. OPTIONS
-a Creates a backup of all NIS+ directory objects for which this server is a master. -v Verbose option. Additional output will be produced and sent to syslog(3C) upon execution of the command (see syslog.conf(4)). OPERANDS
backup-dir The directory into which the subdirectories containing the backed up objects are placed. This must be created prior to running nisbackup. directory The NIS+ directory object(s) being backed up. EXAMPLES
Example 1: Backup of the org_dir NIS+ directory object of the domain foo.com on a master server to a directory named /backup To backup the org_dir NIS+ directory object of the domain foo.com on a master server to a directory named /backup: master_server# nisbackup /backup org_dir.foo.com. Example 2: Backup of the entire NIS+ domain foo.com to a directory named /backup To backup the entire NIS+ domain foo.com to a directory named /backup: master_server# nisbackup /backup foo.com. org_dir.foo.com. groups_dir.foo.com. ctx_dir.foo.com. Example 3: Backup of an entire NIS+ database to a backup directory named /backup To backup an entire NIS+ database to a backup directory named /backup: master_server# nisbackup -a /backup EXIT STATUS
0 Successful completion. 1 An error occurred. FILES
/backup-dir/backup_list This ascii file contains a list of all the objects contained in this backup-dir directory. /backup-dir/directory-object A subdirectory that is created in the backup-dir that contains the NIS+ directory-object backup. /backup-dir/directory-object/data A subdirectory that contains the data files that are part of the NIS+ directory-object backup. /backup-dir/directory-object/last.upd This data file contains timestamp information about the directory-object. /backup-dir/directory-object/data.dict A NIS+ data dictionary for all of the objects contained in the NIS+ directory-object backup. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWnisu | +-----------------------------+-----------------------------+ SEE ALSO
nis+(1), nisdefaults(1), nisrm(1), nisrestore(1M), rpc.nisd(1M), syslog(3C), nisfiles(4), syslog.conf(4), attributes(5) NOTES
NIS+ might not be supported in future releases of the SolarisTM Operating Environment. Tools to aid the migration from NIS+ to LDAP are available in the Solaris 9 operating environment. For more information, visit http://www.sun.com/directory/nisplus/transition.html. SunOS 5.10 12 Dec 2001 nisbackup(1M)
All times are GMT -4. The time now is 05:27 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy