Running the setup script for IBM Storage Protect Snapshot for Custom Applications

Edit online

Run the setup script to configure IBM® Storage Protect Snapshot for Custom Applications.

Before you begin

In most cases, it is sufficient to configure IBM Storage Protect Snapshot in basic mode rather than advanced mode.
  • In basic mode, a subset of parameters is editable and can be modified. For all other parameters, default values are used. The daemons are started automatically.
  • In advanced mode, you can configure all parameters. You choose whether IBM Storage Protect Snapshot daemons are started automatically or not.

For more information about configuration files and different profile parameters, see Configuration files. To read about the profile contents and which parameters are editable in advanced mode, see Profile.

If this general information on the instance needs to be changed at a later point in time, the setup script must be called in advanced mode.

Depending on your environment and the functionality to be used, extra configuration files might be required when you are configuring the product. The setup script checks that these files exist, but does not verify the contents. They must be complete before you run any IBM Storage Protect Snapshot functions.

You can create multiple entries with different values for some parameters. To create multiple entries, when the script asks if you want to add another instance of a parameter, enter y. To delete a parameter entry, when prompted for a parameter value enter !d. To display help for a parameter, enter ? at the prompt for the parameter value. The help is best viewed in a window that is set for at least 130 characters.

Procedure

  1. From the production database instance on the production server, log on as the application owner, and go to the instance directory.

    <instance_owner_$HOME>/acs/

  2. Run the setup script by entering the following command

    ./setup_gen.sh [-advanced]

  3. Follow the setup script instructions.

    When you are configuring the production server, select On-Site Production System configuration with optional remote Backup System configuration. If OpenSSH is available, it is recommended to set up the backup server during the configuration process. To do this, select manage backup systems.

    For more information about configuring a backup server separately, see Setting up separately on backup servers.

Results

After you configured an instance, the following changes are made to the production server:
  • The ACS_DIR directory is created. The default location is <instance owner $HOME>/acs.
  • The IBM Storage Protect Snapshot profile is created in the ACS_DIR directory. Parameter values reflect values that you set during the configuration process.
  • An <ACS_DIR>/shared directory is created for shared information for the production and backup servers.
  • The IBM Storage Protect Snapshot repository for the metadata of each backup is created in the ACS_REPOSITORY directory. The ACS_REPOSITORY directory defaults to <ACS_DIR>/acsrepository
  • A logs directory for IBM Storage Protect Snapshot logs and traces is created at <ACS_DIR>/logs.
  • For secure communication with IBM Storage Protect Snapshot daemons, IBM Global Security Kit key database files fcmcert.* are created in the instance directory, with an fcmselfcert.arm file that contains a representation of the production server's self-signed public key. For more information about the secure communication, see Installing the GSKit.
  • IBM Storage Protect Snapshot daemons that are required for the configuration, start automatically unless you stated otherwise when you configured the product in advanced mode.
If a backup server is automatically set up during the configuration process, the following changes are applied to the backup server:
  • The ACS_DIR directory is created in the same path as on the production server.
  • The necessary IBM Storage Protect Snapshot are copied to the ACS_DIR directory on the backup server.
  • The IBM Storage Protect Snapshot profile for the backup instance is created in the ACS_DIR directory.
  • The <ACS_DIR>/shared directory is copied from the production system.
  • A directory for IBM Storage Protect Snapshot logs and traces is created at <ACS_DIR>/logs.
  • For secure communication with IBM Storage Protect Snapshot daemons, IBM Global Security Kit key database files fcmcert.* are created in the instance directory. Unless standard CA-signed certificates are used for server authentication, the fcmselfcert.arm file of the production system is imported in the keystore.
  • The mount agent daemon starts automatically unless you stated otherwise when you configured the product in advanced mode.