Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
What happens during a catalog backup @ end of media?
- Thread starter ronkr
- Start date
The retention is only as "GOOD" as the last regular netbackup image. The catalog should be backed up at a minimum of once a day. The tapes alternate and are reused. My catalog gets backed up about 3 to 4 times in a 24 hour period. I have enabled the catalog backup to run at the end of each session. So I guess the answer to your question is determined by the setting of the schedule for catalog backups.
Now you can also make catalog backups outside of the GUI configured catalog backup. Here is a technote:
How to configure and backup NetBackup catalogs from command line.
Details:
I. Configuration of the catalog backup from command line (usually performed on the Master server)
The configuration phase of this objective entails:
a) Specifying the media IDs to which the catalog backups are to be written. Configuring one media implies that catalog backup will be performed to that media each time; configuring two medias, however, will allow the catalog backups to be alternated from one tape to the other. The example below illustrates two medias A00000 and A00001 being used for a catalog backup. The UNIX command line for this is as follows:
#/usr/openv/netbackup/bin/admincmd/bpsyncinfo -server <master_server> -id1 A00000 -d1 <densitystr> -id2 A00001 -d2 <densitystr>
where <master_server> is the name of the Master server and <densitystr> is the media type (e.g. 4mm, dlt, etc)
b) Specifying when to perform the catalog backup. There are three options available: Never (must be manually initiated), After each successful Backup Schedule and After any successful Backup/Archive. From a command line perspective, this is has to be viewed as manual. The corresponding parameter for this option is "bw" (Backup When). Thus the UNIX command line is as follows:
#/usr/openv/netbackup/bin/admincmd/bpsyncinfo -bw never
c) Specifying the paths to be backed up. This should include NetBackup media databases of the Media servers as well as the databases of the Master server such as image and volume databases. The command to incorporate a typical example of a set of paths is as follows:
#/usr/openv/netbackup/bin/admincmd/bpsyncinfo -paths "<master_server>:/usr/openv/netbackup/db <master_server>:/usr/openv/volmgr/database <media_server>:/usr/openv/netbackup/db/media <media_server>:/usr/openv/volmgr/database"
where <master_server> is the name of the Master server and <media_server> is the name of the Media server.
Note: To ensure a list of multiple paths, the -paths option has to be used in conjunction with "" and a space between each path.
In order to confirm that all of the above configurations are successfully in place, run and verify the output of the command:
#/usr/openv/netbackup/bin/admincmd/bpsyncinfo -U
Additionally, the file which contains all of the above information is called the sync file which can be found under "/usr/openv/netbackup/db/config". This is the file which is referenced and called by the bpsyncinfo command.
II. Starting the catalog backup from command line
To start the catalog backup from the command line, use the command:
#/usr/openv/netbackup/bin/admincmd/bpsyncinfo -M <master_server> -doBackup
The above procedure is similar for Windows NT/WIN2K except for the paths and the backslashes (\) to replace the fowardslashes.
Bob Stump
Just because the Veritas documentation states a certain thing does not make it a fact
Now you can also make catalog backups outside of the GUI configured catalog backup. Here is a technote:
How to configure and backup NetBackup catalogs from command line.
Details:
I. Configuration of the catalog backup from command line (usually performed on the Master server)
The configuration phase of this objective entails:
a) Specifying the media IDs to which the catalog backups are to be written. Configuring one media implies that catalog backup will be performed to that media each time; configuring two medias, however, will allow the catalog backups to be alternated from one tape to the other. The example below illustrates two medias A00000 and A00001 being used for a catalog backup. The UNIX command line for this is as follows:
#/usr/openv/netbackup/bin/admincmd/bpsyncinfo -server <master_server> -id1 A00000 -d1 <densitystr> -id2 A00001 -d2 <densitystr>
where <master_server> is the name of the Master server and <densitystr> is the media type (e.g. 4mm, dlt, etc)
b) Specifying when to perform the catalog backup. There are three options available: Never (must be manually initiated), After each successful Backup Schedule and After any successful Backup/Archive. From a command line perspective, this is has to be viewed as manual. The corresponding parameter for this option is "bw" (Backup When). Thus the UNIX command line is as follows:
#/usr/openv/netbackup/bin/admincmd/bpsyncinfo -bw never
c) Specifying the paths to be backed up. This should include NetBackup media databases of the Media servers as well as the databases of the Master server such as image and volume databases. The command to incorporate a typical example of a set of paths is as follows:
#/usr/openv/netbackup/bin/admincmd/bpsyncinfo -paths "<master_server>:/usr/openv/netbackup/db <master_server>:/usr/openv/volmgr/database <media_server>:/usr/openv/netbackup/db/media <media_server>:/usr/openv/volmgr/database"
where <master_server> is the name of the Master server and <media_server> is the name of the Media server.
Note: To ensure a list of multiple paths, the -paths option has to be used in conjunction with "" and a space between each path.
In order to confirm that all of the above configurations are successfully in place, run and verify the output of the command:
#/usr/openv/netbackup/bin/admincmd/bpsyncinfo -U
Additionally, the file which contains all of the above information is called the sync file which can be found under "/usr/openv/netbackup/db/config". This is the file which is referenced and called by the bpsyncinfo command.
II. Starting the catalog backup from command line
To start the catalog backup from the command line, use the command:
#/usr/openv/netbackup/bin/admincmd/bpsyncinfo -M <master_server> -doBackup
The above procedure is similar for Windows NT/WIN2K except for the paths and the backslashes (\) to replace the fowardslashes.
Bob Stump
Just because the Veritas documentation states a certain thing does not make it a fact
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question