Hello
You should be also receiving emails after hot catalog backup. Here is an example one for NBU 10.0.0.1, after replacing some fragile data - not sure which version you are using:
Server
mastername
NetBackup Version
10.0.0.1
Date
Mon 17 Jul 2023 12:00:04 PM
Policy
HOT_CATALOG
Catalog Backup Status
the requested operation was successfully completed (status 0).
DR image file: /HOT_CATALOG/HOT_CATALOG_1689588076_FULL
To ensure that the NetBackup catalog data is protected through Mon 17 Jul 2023 12:00:04 PM SAST, retain a copy of the attached file, and the media or files listed below:
Catalog Recovery Media
Media Server Media ID Image File Required
* mastername tape001 HOT_CATALOG_1689588005_FULL
* mastername tape001 HOT_CATALOG_1689588076_FULL
DR file written to
/HOT_CATALOG/HOT_CATALOG_1689588076_FULL
DR Package file written to
/HOT_CATALOG/HOT_CATALOG_1689588076_FULL.drpkg
The CA configuration at the time of catalog backup is as follows:
The master server mastername is configured to use NetBackup certificates.
ECA_CRL_PATH_SYNC_HOURS = 1
ECA_CRL_REFRESH_HOURS = 24
ECA_CRL_CHECK = LEAF
The master server is configured to use service account: nbsvcusr
* - Primary Media
Catalog Recovery Procedure for the Loss of an Entire Catalog
You should create a detailed disaster recovery plan to follow should it become necessary to restore your organization's data in the event of a disaster. A checklist of required tasks can be a tremendous tool in assisting associates in triage. For example, after the facility is safe for data to be restored, the power and data infrastructure need to be verified. When these tasks are completed, the following scenarios will help to quickly restore the NetBackup environment, and in turn, restore applications and data.
Disaster Recovery Procedure using the DR Package file and DR Image File
In the event of a catastrophic failure, use the following procedure to rebuild the previous NetBackup environment.
Important Notes:
- If new hardware is required, make sure that the devices contain drives capable of reading the media and that the drive controllers are capable of mounting the drives.
- Keep the passphrase associated with the DR Package file handy. This passphrase is set before the catalog backup policy configuration using the NetBackup Administration Console or the nbseccmd command.
- If the catalog backup is encrypted using keys from an External KMS, configure the External KMS in NetBackup after the installation completes and before starting recovery. See the NetBackup Security and Encryption Guide for information on how to configure an external KMS.
https://www.veritas.com/content/support/en_US/article.100040135- If the catalog backup is encrypted using keys from the NetBackup KMS, configure the NetBackup KMS and restore the required keys after the installation completes and before starting recovery. See the NetBackup Security and Encryption Guide for information on how to backup and restore keys from the NetBackup KMS.
1. Install NetBackup.
a. The installation procedure prompts you to confirm if this is a DR scenario.
i. On the UNIX installer, you can see a prompt as "Are you currently performing a disaster recovery
of a master server? [y,n] (y)". Select "y"
ii. On the Windows installer click the "Disaster Recovery Master Server" button.
b. The installation procedure prompts you for the master server’s DR Package (refer to the /HOT_CATALOG/HOT_CATALOG_1689588076_FULL.drpkg mentioned earlier).
Make sure that the master server can access the attached DR package file.
c. Type the passphrase associated with the DR package, when prompted.
i. The installer validates the DR package using the passphrase.
ii. In case of errors in validation, the installer aborts the operation.
To work around the issue, refer to the following article:
iii. If the external CA-signed certificates could not be backed up, configure the certificates on the host.
2. Configure the devices necessary to read the media listed above.
3. Inventory the media.
4. Make sure that the master server can access the attached DR image file.
5. Start the NetBackup Recovery Wizard from the NetBackup Administration
Console. Or, start the wizard from a command line by entering
bprecover -wizard.
Disaster Recovery Procedure without the DR Image File
NOTE: ONLY ATTEMPT THIS AS A LAST RESORT If you do not have the attachment included with this email, use the following instructions to recover your catalog (If using OpenStorage disk pools, refer to the Shared Storage Guide to configure the disk pools instead of step 2 and 3 below :(
1. Install NetBackup.
2. Configure the devices necessary to read the media listed above.
3. Inventory the media.
4. Run
To recover from copy 1:
bpimport -create_db_info [-server name] -id tape001
5. Run:
cat_export -client mastername
6. Go to the following directory to find the DR image file
HOT_CATALOG_1689588076_FULL:
/usr/openv/netbackup/db.export/images/mastername/1689000000
7. Open HOT_CATALOG_1689588076_FULL file and find the BACKUP_ID
(for example: mastername_1689588076).
8. Run:
bpimport [-server name] -backupid mastername_1689588076
9. Run:
bprestore -T -w [-L progress_log] -C mastername -t 35 -p HOT_CATALOG -X -s 1689588076 -e 1689588076 /
10. Run the BAR user interface to restore the remaining image database
if the DR image is a result of an incremental backup.
11. To recover the NetBackup relational database, run:
bprecover -r -nbdb
12. Stop and Start NetBackup.
13. Configure the devices if any device has changed since the last
backup.
14. To make sure the volume information is updated, inventory the media
to update the NetBackup database.
