IBM Tivoli Storage FlashCopy Manager for UNIX and Linux, Version 4.1

Post-installation and configuration

After you install and configure Tivoli® Storage FlashCopy® Manager, you can set up extra backup and clone servers.

You can use the setup script to update the profile and configure Tivoli Storage FlashCopy Manager on multiple backup servers from the production server. You can use one of the following methods:

Install Open Secure Shell (OpenSSH) to enable backup servers for remote installation and configuration from the production server.
Network file system (NFS) shares. An NFS file system allows information to be shared across multiple servers.

NFS shares between the production server and backup server are not required for this type of remote installation. OpenSSH is the preferred method for Tivoli Storage FlashCopy Manager, but NFS shares are supported.

When the database instance-specific installation directory (INSTANCE_DIR) is NFS-shared with other systems, you must configure Tivoli Storage FlashCopy Manager on one production server and on the backup server. In a physically partitioned DB2® environment, configuration is only required on one node of the production server and also on the backup server. In this case, it is only necessary to install Tivoli Storage FlashCopy Manager on the production server.

If both the configuration directory (ACS_DIR) and the INSTANCE_DIR directory are NFS-shared between the production server and backup server, Tivoli Storage FlashCopy Manager is best administered from the following location:

From the production server for Oracle or DB2 and custom applications.
From the master production server node for physically partitioned DB2 environments.

The master production server node is the production server on which Tivoli Storage FlashCopy Manager was installed. For the initial configuration, Tivoli Storage FlashCopy Manager must be installed, activated, and configured on the production server, and then configured on the backup server. The installation and activation steps on the backup server can be skipped. Upgrades and reconfiguration must be performed only on the master production server node. Typically, it is not necessary to start the setup script on the backup server after the initial configuration. However, you must edit the inittab entries on the backup server even though the installation and configuration directories are NFS shared. Exceptions to this rule might include:

The use of alternative storage hardware might require a reconfiguration of Tivoli Storage FlashCopy Manager on the backup server.
Changes to the scheduling policy for offloaded Tivoli Storage Manager backups might require you to reconfigure the backup server.

In these cases, stop Tivoli Storage FlashCopy Manager on the production server before reconfiguration of the backup server. Otherwise, you are prompted to stop Tivoli Storage FlashCopy Manager on the production server. For details about how to stop an activated Tivoli Storage FlashCopy Manager instance, see Tivoli Storage FlashCopy Manager commands and scripts.

Feedback