Installing and configuring secondary NetBackup master server
The following procedure provides guidelines for installing and configuring the secondary non-clustered master server with catalog replication.
To install and configure the secondary non-clustered master server with catalog replication
- Stop NetBackup on the primary master server.
- Map the DNS alias name to the secondary master server.
- Install the NetBackup master server on the secondary master server node, specifying the alias name for the master server. During installation, apply the same list of servers on the secondary master server.
- After the installation is complete, shut down NetBackup.
- To ensure NetBackup starts correctly when switching to the secondary master server, modify the server.conf and vxdbms.conf.
check the two files and ensure that the string is NB_<alias name>and not NB_<hostname> and modify the files if necessary.
On Windows master server these files are located at:
<install path>\VERITAS\netbackupdb\conf\server.conf
<install path>\VERITAS\netbackupdb\data\vxdmbs.conf
On UNIX or Linux master server these files are located at:
/usr/openv/var/global/server.conf
/usr/openv/db/data/vxdbms.conf
- 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 secondary master server and not the the disk volume.
- Move the catalog components to this disk volume.
For Windows installations, map the following paths to a common volume. Use symbolic links on Windows 2008, 2012, and 2016.
<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
- Configure NetBackup so that it can be manually started and stopped on the secondary master server. By default, NetBackup is started automatically when the master server is booted.
To prevent this automatic start, make the changes as per Steps 9 and 10 after the initial installation and after applying patches or upgrades.
Make the following changes on the NetBackup master server.
On UNIX and Linux master 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 Windows master server, go to the Services Manager and set the Startup type for all the NetBackup services to Manual.
- Start NetBackup on the secondary master server. Confirm that NetBackup comes up and then shut it down again. At this stage, you may run the NetBackup Configuration Wizard to 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 UNIX and Linux master 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 master server:
To start NetBackup, run the following command:
<install path>\VERITAS\NetBackup\bin\bpup
To stop NetBackup, run the following command:
<install path>\VERITAS\NetBackup\bin\bpdown
- After NetBackup shuts down, dismount the disk volume mounted on the primary server (refer step 6). Then reset the DNS alias name to the primary master server. Then restart NetBackup on the primary master server.