During the activation process, the necessary files are copied from the
installation directory to an instance-specific directory. The installer does not activate the
instance. In order to activate an instance, follow the procedure.
Procedure
-
Log in to the production server and use the root user ID. Change to the global installation
directory.
-
To activate any additional custom applications, complete the following steps:
To activate a custom application, complete the following steps:
- Run one of the following commands to activate the custom application instance:
- Environments other than GPFS™
- The default installation directory is
$HOME/acs. The home directory of the
application backup user is $HOME. The following command creates the
$HOME/acs directory:
./setup_gen.sh -a install
-d <Application_owner_$HOME_directory>
- GPFS environments
-
./setup_gen.sh -a install
-d <Application_owner_$HOME_directory>
-t <directory_in_shared_file_system>
The
-t parameter specifies a target directory in a shared file system to
ensure that
IBM® Storage Protect
Snapshot binary files are
copied to the shared file system. These files are then available on all nodes of the GPFS cluster. Use a directory in an independent file set or a GPFS file system that does not contain other application data that
you intend to protect with
IBM Storage Protect
Snapshot. A
link that is named
$HOME/acs is created that targets the specified directory.
$HOME is the home directory of the application backup user. The link is only
created on the local node and on the node that is used as a backup server. You must manually create
that link on other GPFS cluster nodes to operate
IBM Storage Protect
Snapshot from other nodes.
What to do next
After the installation you must activate the instance for the applications. When the
activation process completes, you must configure each application instance to finalize the
installation process.