Veritas NetBackup™ Appliance Administrator's Guide

To recover an appliance primary server using NetBackup catalog restore

1. Perform one of the following actions depending on the state of your primary server:

   • If you can log on to the primary server, perform a factory reset and retain the network settings. You can elect to delete all images and reset the storage configuration.

   • If you cannot log on to the primary server, perform a re-image of the server using the same network settings as before the disaster event.

2. Once you have completed the factory reset or re-image operation, log on to the NetBackup Appliance Shell Menu on the primary server and create an NetBackup CLI user.

   Main_Menu > Manage > NetBackupCLI > Create

3. Copy the NetBackup catalog files that were stored off-site onto the primary server.
4. Log out of the NetBackup Appliance Shell Menu, then log on as the NetBackup CLI user you created earlier.
5. Run bp.kill_all.
6. Run nbhostidentity -import -infile with the package file of the .drpkg
7. Run bp.start_all, then verify that the token, certifications, and security settings have been restored.
8. Configure the role on the factory state appliance as a primary server.

   Note:

   Make sure to keep the same host name, time zone, and storage settings of the primary as before the disaster.

9. Run bpsetconfig to add the line: MEDIA_SERVER=<media_server_name> and register media servers on the new primary server. Use Ctrl + D to exit and save this entry.
10. Run nbemmcmd to add the media server's record to the EEM database manually:

    nbemmcmd -addhost -machinename <media_server_name> -machinetype media -primarieserver <primary_server_name> -operatingsystem linux -netbackupversion <NetBackup_version>

11. Restart the NetBackup services on the media server.

    Note:

    To ensure proper communication between the primary and the media server, you must perform this step before you create the MSDP storage information on the media server as described in the following step.

12. Create the media server AdvancedDisk and MSDP storage information using the following commands:

    • AdvanvcedDisk

      nbdevconfig -creatests -storage_server <media_server_name> -stype AdvancedDisk -media_server <media_server_name> -st 5

      nbdevconfig -createdp -dp dp_adv_<media_server_name> -stype AdvancedDisk -storage_servers <media_server_name> -dvlist dvlist.txt

      bpstuadd -label stu_adv_<media_server_name> -dp dp_adv_<media_server_name> -cj 20 -odo 1 -okrt 0 -nodevhost -M <primary_server_name>

    • MSDP

      nbdevconfig -creatests -storage_server <media_server_name> -stype PureDisk -media_server <media_server_name> -st 9

      nbdevconfig -createdp -dp dp_disk_<media_server_name> -stype PureDisk -storage_servers <media_server_name> -dvlist dvlist.txt

      bpstuadd -label stu_disk_<media_server_name> -dp dp_disk_<media_server_name> -cj 20 -odo 1 -okrt 0 -nodevhost -M <primary_server_name>

13. Restore the NetBackup catalog by performing one of the following actions:

    • Run the bprecover -wizard command.

    • Use the NetBackup Catalog Recovery Wizard in the NetBackup Administrator's Console.

14. During the role configuration, the nbasecadmin user is recreated and its user ID may change which prevents that user from logging in to the NetBackup Web Console. Before attempting to log in to the web console as nbasecadmin, open an SSH session as a NetBackupCLI user and run the following command:

    bpnbaz -AddRBACPrincipal -User unixpwd:<appliancename>:nbasecadmin

    If the following message appears, the nbasecadmin user ID has not changed and you can log in to the web console:

    The user or user group provided already has Administrator privileges.

    If the above message does not appear, there are now two user IDs associated with the nbasecadmin username. To resolve this issue, perform the following tasks in the order as they appear:

    • Log in to the NetBackup Web Console as nbasecadmin.

    • Go to RBAC > Role > Adminstrator.

    • Remove the nbasecadmin user rows, which disables the nbasecadmin user from logging in.

    • Run the above bpnbaz command again to add nbasecadmin as an RBAC principal user. This step ensures that there is only one record for nbasecadmin in the NetBackup user database.

    No other OS users are created or recreated during the role configuration. The catalog recovery may show users with the Administrator, or other roles that were associated with OS users that no longer exist. Those users should be removed from the NetBackup Web Console, then recreated on the appliance and assigned their appropriate roles in the NetBackup Web Console.

15. Run bp.kill_all and bp.restart_all to finish recovering the primary server.
16. Synchronize the MSDP storage server password as follows:

    • For software versions 3.3.0.1 and later, log in to the appliance shell menu on the primary server and run the following command:

      Main_Menu > Appliance > ShowDeDupPassword

    • For software versions 3.1 through 3.2, log in to the appliance shell menu on the primary server and run the following command:

      Main_Menu > Appliance > ShowDeDupPassword

      Log in to the appliance primary server as a NetBackup CLI user and run the following command:

      tpconfig -update -storage_server <primary host name> -stype PureDisk -sts_user_id root -media_server <primary hostname>, then enter the dedupe password from the previous command output.