NetBackup™ in Highly Available Environments Administrator's Guide

To install and configure the alternate non-clustered primary server with catalog replication

1. Stop NetBackup on the main primary server.
2. Map the DNS alias name to the alternate primary server.
3. Install the NetBackup primary server on the alternate primary server node, specifying the alias name for the primary server. During installation, apply the same list of servers on the alternate primary server.
4. After the installation is complete, shut down NetBackup.
5. To ensure that NetBackup starts correctly when switching to the alternate primary server, verify the NB_<alias name> string in the vxdbms.conf file.

   Verify that the string is NB_<alias name> and not NB_<hostname> and modify as necessary.

   This file is located in the following directory:

   <install path>\VERITAS\netbackupdb\data\vxdmbs.conf

   /usr/openv/db/data/vxdbms.conf

6. Create a small disk volume (100 MB) and mount it to the same mount point used for the replicated volume on the primary server.

   Note:

   During a failover operation the replicated volume is mounted on the alternate primary server and not the disk volume.

7. Move the catalog components to this disk volume.

   For Windows installations, map the following paths to a common volume. Use symbolic links.

   • <install path>\VERITAS\netbackup\db

   • <install path>\VERITAS\netbackupdb\data

   • <install path>\VERITAS\netbackup\vault\sessions

   • <install path>\VERITAS\volmgr\misc

   • <install path>\VERITAS\netbackup\var

   • <install path>\VERITAS\kms

   For UNIX and Linux installations, soft-link the following paths to locations on a common volume:

   • /usr/openv/netbackup/db

   • /usr/openv/db/data

   • /usr/openv/netbackup/vault/sessions

   • /usr/openv/volmgr/database

   • /usr/openv/var

   • /usr/openv/kms

8. Configure NetBackup so that it can be manually started and stopped on the alternate primary server. By default, NetBackup is started automatically when the primary server is started.

   To prevent this automatic start, make the changes as per Steps 9 and 10 after the initial installation and after applying patches or upgrades.

9. Make the following changes on the NetBackup primary server.

   • On a Linux primary server, remove the links to /etc/init.d/netbackup created during the installation to enable automatic startup.

     Refer to the NetBackup Installation Guide for details of links for each operating system.

   • On a Windows primary server, go to the Services Manager and set the Startup type for all the NetBackup services to Manual.

10. Start NetBackup on the alternate primary server. Confirm that NetBackup comes up and then shut it down again. At this stage, you can configure media servers and storage devices.

    To start and stop NetBackup manually the run the following commands. It is recommended to document these commands in the failover procedure.

    On a Linux primary server:

    • To start NetBackup, run the following command:

      /etc/init.d/netbackup start command

    • To stop NetBackup, run the following command:

      /etc/init.d/netbackup stop

    On Windows primary server:

    • To start NetBackup, run the following command:

      <install path>\NetBackup\bin\bpup

    • To stop NetBackup, run the following command:

      <install path>\NetBackup\bin\bpdown

11. After NetBackup shuts down, dismount the disk volume that is mounted on the primary server (refer step 6). Then reset the DNS alias name to the main primary server. Then restart NetBackup on the main primary server.