Configuring the secondary node

After you configure the primary node, you must configure the secondary node so that System Automation for Multiplatforms can move the IBM Storage Protect server components to the secondary node if the server fails on the primary node.

Procedure

To create the directories and the user ID for the server instance manually, follow the instructions in Creating the user ID and directories for the server instance. Ensure that the same directory names are used on the primary and secondary nodes.
Define the mount points by adding entries in the /etc/fstab file.

When you add mount points on the cluster nodes, use the noauto option. This option prevents the mount points from being automatically mounted on more than one node in the cluster.

Ensure that the disk UIDs for each mount correspond to the disk UIDs on the primary node.
Set the following permissions on each of the mount points:
- The 755 permission. For example, the following command sets the 755 permission on the /tsminst1 mount point:
```
chmod -R 755 /tsminst1
```
- IBM Storage Protect server instance owner. For example, the following command sets the permissions for the instance owner:
```
chown -R  tsminst1  /tsminst1
```
- IBM Storage Protect server group that the instance owner belongs to. For example, the following command sets the permissions for the instance owner's group:
```
chgrp tsmsrv_1_group /tsminst1 
```
Mount the shared drives.
Create the IBM Storage Protect server instance by issuing the db2icrt command. For instructions, see Creating the server instance.

Remember: You do not have to create a new server options file because the secondary node uses the dsmserv.opt file from the primary node.
Log on to the secondary node by using the instance user ID. Catalog the database by issuing the catalog db command.
For example, the following command catalogs the tsmdb1 database:
```
db2 catalog db tsmdb1 
```
Prepare the database for backup. For instructions, see Preparing the database manager for database backup.
Change to the instance directory and start the IBM Storage Protect server by using the DSMSERV utility.
For example, the following command starts the server for normal operation:
```
/opt/tivoli/tsm/server/bin/dsmserv
```
Verify that the IBM Storage Protect components are starting without any errors.
Halt the IBM Storage Protect server and unmount the shared directories.