NetBackup™ in Highly Available Environments Administrator's Guide
- About in this guide
- NetBackup protection against single points of failure
- About site disaster recovery with catalog backup and recovery
- About site loss protection with auto image and catalog replication
- About NetBackup catalog replication
- Deploying NetBackup primary servers with full catalog replication
- About non-clustered NetBackup primary server with catalog replication
- About globally clustered NetBackup primary servers with catalog replication
- Installing and configuring a globally clustered NetBackup primary server with catalog replication
- Using NetBackup to perform backups and restores in a cluster
Performing a partial catalog restore
With partial catalog approach, it is assumed that restore operations do not need tapes to be assigned or located in specific media pools. It is also assumed that a tape exists in EMM and NetBackup can mount and read the tape for restoring. The following steps must be carried out before restores can be started:
To prepare for partial catalog restore
- Run the nbgetconfig command and save the output. This output can be used after the catalog recovery to recover the host-specific information that is overwritten during the catalog recovery.
For example:
./nbgetconfig > sample.txt
- Recover only the NetBackup catalog image and configuration files.
Select the Partial catalog recovery option when prompted.
Or run the bprecover -wizard command. When you are prompted
"Do you want to recover the entire NetBackup catalog? (Y/N)"
, enter N.
Note:
The DR primary server must have the same name as the production primary server.
Note:
If a catalog backup that was created on a separate media server is used, a media server with the same name is required for the catalog recovery.
- If you want to recover the image header information without recovering the entire NetBackup database, perform the following steps:
Step a - Back up the target database. Run the following command.
nbdb_backup -online directory
Make sure that you do not specify the staging folder as the output directory. (The staging folder contains the schema data and configuration data for the NetBackup database from the catalog backup. Image
.f
and configuration files are recovered to their final destinations.)Step b - Recover the NetBackup database from the staging directory.
nbdb_restore -recover -staging
Step c - Export the image header data that you want to import from the backup.
For example, the following command exports export all image header data. The data is exported to the
netbackup/db.export
directory.cat_export -all
Step d- Recover the NetBackup database with the following command.
nbdb_restore -recover directory
Make sure that you specify the same directory as in step a.
Step e- Run the cat_import command to import the image header data that you extracted in step c.
cat_import -all -replace_destination -delete_source
The command does the following:
Imports all of the image header data in the
netbackup/db.export
directory.Replaces any image header data that was exported that already exists in the target database.
Removes the image header data that resides in the
netbackup/db.export
directory.
Step f- If you recovered the catalog from a disk device, you may have to fix the disk media ID references. Run the following command:
nbcatsync -sync_dr_file DR file path -dryrun
Replace DR file path with the path to the catalog DR file.
Step g - If the result of the dry run is satisfactory, run the following command:
nbcatsync -sync_dr_file DR file path
- Deactivate all the backup policies to prevent backups from starting automatically, in one of the following ways.
In the NetBackup web UI.
Run the bpplinfo <policy> -modify -inactive CLI.
- Shut down NetBackup.
- Recover the host settings that you backed up in step 1. Run the following command.
./nbsetconfig sample.txt
- Start NetBackup.
- Inventory all the tape libraries to ensure that the tapes are added to the non-scratch media pool. This pool prevents tapes from being accidentally overwritten by active backup policies at a later time.
You can now start restore and recovery operations of client data that is backed up at the production datacenter.