About full catalog recovery
Full catalog recovery is primarily used to recover the catalog if the data is corrupted or storage is lost at the production site. Full catalog recovery is recommended for single domain configurations. Full catalog recovery is used if the DR site has the same number of media servers with the same names as those used at the production site.
Full catalog recovery has the following advantages over partial catalog recovery:
It restores the database components, which include the storage unit definitions, media assignment, and history.
It retains the tape information from the main site including the media pool and other assignment information.
It restores the NBDB, NBAZDB, and BMR (if configured) data.
It enables backups to be run at the DR site using the same policies and tapes that are used at the production site.
With full catalog recovery, there are the following limitations:
Catalog recovery does not recover host certificates. To recover the NetBackup primary server identity or host certificates and other information, the disaster recovery package must be recovered.
When you recover the database components, the device configuration and the server configuration set up at the DR site before recovery is lost. You must set it again after recovery. The information that exists in the database about production servers and devices may not exist at the DR site. To ensure smooth operation in the DR environment, these server entries must be disabled and the devices associated with them should be removed.
Full catalog recovery overwrites the device configuration and the server configuration in the database. You must rediscover the DR domain server and device configuration after the catalog is restored.