Setup script values

Edit online

The following values are available for setup_type.sh.

The following values are available for action. The instance directory name -d option, is required for all explicit actions.

  • Use setup_gen.sh to configure IBM® Storage Protect Snapshot for Custom Applications.
disable

This call can be issued as the root or instance owner. It stops IBM Storage Protect Snapshot and removes all daemon jobs. To reactivate IBM Storage Protect Snapshot, call the script without parameters.

If IBM Storage Protect Snapshot cannot be stopped, stop IBM Storage Protect Snapshot on the production system before running setup_type.sh –a install -d <Instance owner $HOME directory>.

install
This call needs to be issued with the root user ID. When issued, the following actions are completed:
  1. Stops IBM Storage Protect Snapshot (setup_type.sh –a stop -d <Instance owner $HOME directory>) For DB2® databases, change <INSTANCE owner $HOME directory> to <INSTANCE owner $HOME directory>/sqllib.
  2. Copies all binary files from the IBM Storage Protect Snapshot installation directory to the instance-specific installation directory (<instance directory>)
  3. Sets the appropriate access rights for the binary files.
  4. Restarts IBM Storage Protect Snapshot (setup_type.sh –a start -d <Instance owner $HOME directory>).

The steps to start and stop IBM Storage Protect Snapshot are skipped if it is not configured.

If IBM Storage Protect Snapshot cannot be stopped, stop IBM Storage Protect Snapshot on the production system before running setup_type.sh –a install -d <Instance owner $HOME directory>.

start

This call can be issued as the root or instance owner. The call starts a previously installed and configured version of IBM Storage Protect Snapshot. This call starts the configured daemon jobs.

stop

This call can be issued as the root or instance owner. It stops the version of IBM Storage Protect Snapshot that is currently running. This call updates the configured daemon jobs and checks that IBM Storage Protect Snapshot is stopped successfully (a write lock can be acquired for the .lock file that is located in the instance-specific installation directory).

This call fails on the backup system in environments where the instance-specific installation directory is shared between the production and backup systems, if IBM Storage Protect Snapshot is running on the production system. To successfully stop IBM Storage Protect Snapshot in those environments, stop IBM Storage Protect Snapshot on the production system.

This option is not required for the default setup function.