Configuring IBM Storage Protect Snapshot for Custom Applications for GPFS

Run the setup script to configure IBM® Storage Protect Snapshot for custom applications for a GPFS™ setup.

Before you begin

Before you run the setup script, and offload backups to the IBM Storage Protect server, you need to ensure IBM Storage Protect client is installed and configured on your system. When you are running the setup script, you must know the name of the IBM Storage Protect server that you will offload snapshots to. If dsm.sys or dsm.opt is not stored in the default path, you must specify the DSM_DIR during the setup configuration.

About this task

The configuration steps ask for the relevant information that is needed to configure IBM Storage Protect Snapshot for Custom Applications. During the configuration in advanced mode, you are asked specific GPFS questions to differentiate the configuration for a GPFS setup.

For some parameters, you can create multiple entries with different values. To create multiple entries of a particular parameter, when prompted if you want to add another instance of a parameter, choose yes. If you want to delete a parameter entry, enter !d.

Procedure

  1. When asked if your custom application is running on a GPFS file system, choose yes.
  2. Choose to configure an onsite production server with the option of a remote backup server configuration.
    This option configures IBM Storage Protect Snapshot on the production server. It also provides the option to remotely activate and synchronize the configuration of one or more backup servers by using the OpenSSH protocol.
  3. If you are going to run offloaded backups to the IBM Storage Protect server, choose to run offload backups.
    When you choose to offload backups to the IBM Storage Protect server, you proceed to configure support for offloaded tape backups. Alternatively, you can choose to configure support for running snapshot backups in a GPFS file system only.
  4. Choose if you want to start offloaded tape backups immediately after the snapshot completes.
    If you choose not to run offload operations immediately after the snapshot completes, you can schedule offload operations to run later by scheduling backups individually. Backups to IBM Storage Protect server can be delayed until the necessary server resources are available.
    To run the scheduled backup process manually enter the command fcmcli -f tape_backup.You can add a crontab entry to complete this action. The default value is to run tsm4acs as a daemon process on the production server.
  5. Choose one of the following options:
    • In a Linux™ environment, decide if you want the upstart jobs to be created and started.
    • In AIX® environments, decide if you want the inittab entries created.
    If you specify no, the executable files that include command line options are not added to the /etc/inittab, and the upstart jobs are not created. In this case, ensure that these items are started by your HA startup scripts, and that they are restarted whenever they are ended. If you choose yes, the daemon processes are entered in the /etc/inittab directory, or upstart jobs are created and started.

What to do next

After the configuration completes, you are asked if you want to deploy the configuration to a backup system. In a GPFS environment, a backup system is not required because all actions are carried out in the productive GPFS cluster. However, if you want to run offload backups to a IBM Storage Protect server you must configure a system where this operation is initiated. For example, the local node where IBM Storage Protect Snapshot is being installed, or any other management node in the GPFS cluster where the IBM Storage Protect client is set up and configured to cooperate with the GPFS command mmbackup. To configure such an offload system, choose to configure a new backup system.