Recovering the entire catalog using the Catalog Recovery Wizard on UNIX/Linux

This procedure shows you how to recover the entire catalog using the Catalog Recovery Wizard. You must have root (administrative) privileges. The Catalog Recovery Wizard panels that appear when you are performing these procedures are very similar for UNIX, Linux, and Windows platforms. Only the Windows panels are shown in text in the following procedures. Note: The Catalog Recovery Wizard does not work after you perform a change server operation. You must be logged on locally to the master server that being recovered. Note: During the catalog recovery process, services may be shut down and restarted. If NetBackup is configured as a highly available application (cluster or global cluster), freeze the cluster before starting the recovery process to prevent a failover. Then unfreeze the cluster after the recovery process is complete. To recover the entire catalog 1. Your configuration may include an Enterprise Media Manager (EMM) server that is separate from the master server. If so, start NetBackup on the EMM server before starting NetBackup on the master server. 2. Start NetBackup by entering the following: On UNIX and Linux:
/usr/openv/netbackup/bin/bp.start_all

On Windows:
install_path\NetBackup\bin\bpup

The NetBackup Administration Console appears. 3. If the necessary devices are not already configured, configure them in NetBackup. 4. Make available to NetBackup the media that contains the catalog backup. 5. Click Recover the Catalogs on the NetBackup Administration Console to start the Catalog Recovery Wizard.

The Welcome panel appears. 6. Click Next on the Welcome panel to display the Catalog Disaster Recovery File panel.

This wizard relies on the disaster recovery information that is generated during the online catalog backup. Part of the online catalog backup configuration indicates where the disaster recovery information file was to be stored and-or sent. In most cases, you specify the most recent disaster recovery information file available. If some form of corruption has occurred, then you may want to restore to an earlier state of the catalog. If the most recent catalog backup was an incremental backup, use the disaster recovery file from the incremental backup. (There is no need to first restore the full backup and then follow with the incremental backup.) Indicate where the disaster recovery file is stored by entering the fully qualified path to the disaster recovery file. More information is available on the email that is sent and the attached disaster recovery file. See Recovering the catalog without the disaster recovery file on UNIX/Linux 7. The wizard waits while NetBackup searches for the necessary media sources. The wizard then informs you if the necessary backup ID of the disaster recovery image is located.

Or, if the media is not located, the wizard lists which media is needed to update the database. Follow the wizard instructions to insert the media that is indicated and run an inventory to update the NetBackup database. The information that is displayed on this panel depends on whether the recovery is from a full backup or an incremental backup. If an online catalog backup policy includes both full backups and incremental backups, the disaster recovery email may indicate either a full backup or an incremental backup for recovery. An incremental backup recovery completely recovers the entire catalog because it references information from the last full backup. You don't need to first recover the last full catalog backup, then follow with subsequent incremental backups. 8. When the required media sources are all found, click Next to display the Disaster Recovery Method panel. The Recover entire NetBackup catalog radio option is selected.

9. With the Recover entire NetBackup catalog radio option selected, click Next to initiate the recovery of the entire NetBackup catalog. NetBackup restores the entire NetBackup relational database, which includes the following:

NBDB database (including the EMM database) BMR database (if applicable) NetBackup policy files Backup image files Other configuration files

If the EMM server is located on a remote computer, the NBDB database is recovered on the remote computer. 10. The wizard displays the recovery progress.

If the recovery is not successful, consult the log file messages for an indication of the problem. 11. The final panel announces that the full recovery is complete. Each image file is restored to the proper image directory, and the NetBackup relational databases (NBDB and optionally BMRDB) have been restored and recovered. If this step is part of a server recovery procedure, complete the remaining steps in the appropriate Server Disk Recovery procedure. 12. NetBackup does not run scheduled backup jobs until NetBackup is stopped and restarted. Before you restart NetBackup, protect the media that contains the backups that were successfully performed after the catalog backup that was used to recover the catalog. This recovery can include the following: Importing the backups from the backup media into the catalog. Write protecting the media. Ejecting the media and setting it aside. Freezing the media. 13. You can manually submit backup jobs before you stop and restart NetBackup. Be aware that if you have not protected the media containing the backups done after the catalog backup, the media may be overwritten.

14. Stop and restart NetBackup on all the servers. On UNIX and Linux:
/usr/openv/netbackup/bin/bp.kill_all /usr/openv/netbackup/bin/bp.start_all

On Windows:
install_path\NetBackup\bin\bpdown install_path\NetBackup\bin\bpup

If a remote EMM server is used, start NetBackup on it before you start NetBackup on the master server. If you have recovered from removable media, that media is now frozen.