Recovering the primary server when root is intact
The following procedure recovers the primary server by reloading the operating system, restoring NetBackup, and then restoring all other files.
To recover the primary server when root is intact
- Verify that the operating system works, that any require patches are installed, and that specific configuration settings are made. Take corrective action as needed.
- Reinstall NetBackup software on the server you want to recover.
See the NetBackup Installation Guide for instructions.
Note:
For the NetBackup Web Services, you must use the same user account and credentials that were used when you backed up the NetBackup catalog. More information is available:
https://support.cohesity.com/s/article/article-100023872
If you used a custom nbsvcuser or nbwebgrp you must populate the NetBackup installation answer file with the custom names before you begin the installation. Refer to the NetBackup Installation Guide for additional details. See the web services requirement in the NetBackup requirements for UNIX and Linux table. This table is located in the Installation requirements for UNIX and Linux section.
Note:
You must use the same service user account that was used when you backed up the NetBackup catalog.
For more information on the service user account, refer to the NetBackup Security and Encryption Guide.
- Install any NetBackup patches that had been previously installed. See the documentation that was included with the patch software.
Note:
Cohesity does not support the recovery of a catalog image that was backed up using an earlier version of NetBackup.
- If the catalog directories differ from those in the NetBackup catalog backups, recreate that directory structure on the disk before you recover the catalog. For example, if you used symbolic links as part of the NetBackup catalog directory structure.
If the recovery scenario involves restoring policy or catalog backups, the appropriate recovery devices must be configured, which may involve the following tasks:
Install and configure the robotic software for the devices that read backups of the NetBackup catalog and regular backups of the disk being restored. If a non-robotic drive is available that can read these backups, then no robot is required. Although manual intervention is required if multiple pieces of media are required.
See the NetBackup Device Configuration Guide.
Discover and configure the recovery device in NetBackup.
Use the NetBackup tpautoconf command to discover and configure the recovery device in NetBackup.
See the NetBackup Commands Reference Guide.
Update the device mapping files.
- If you must restore from the policy backups or catalog backups that were done to media, the appropriate media may have to be configured in NetBackup
See the NetBackup Administrator's Guide, Volume I.
Configuring the media may require some or all of the following tasks:
Manually load the required media into a standalone recovery device.
Use the NetBackup utilities such as robtest or vendor-specific robotic control software to load media into the required recovery device or devices.
Inventory the media contents of a robotic device.
Use the vendor-specific robotic control software to load the media into the required recovery devices.
- Recover the NetBackup catalogs.
The NetBackup catalogs can be recovered only to the same directory structure from which they were backed up (alternate path recovery is not allowed).
- Stop and restart all NetBackup daemons.
/usr/openv/netbackup/bin/bp.kill_all /usr/openv/netbackup/bin/bp.start_all
- Restore other files to the server as desired.
You can use the NetBackup web UI, the NetBackup Backup, Archive, and Restore interface, or the bp command. When the files are restored, you are done.