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

Configuring

After the installation and activation procedure is complete, configure Tivoli® Storage FlashCopy® Manager. To configure Tivoli Storage FlashCopy Manager, use the setup script. The information that you enter is used to create the profile configuration file.

Before you begin

Review the installation planning sheet that is associated with the Hardware and Software Requirements technote. This sheet contains the required parameters for each specific software application and custom application that are required during the configuration.

For the current requirements, review the Hardware and Software Requirements technote that is associated with the Tivoli Storage FlashCopy Manager release. This technote is available in the Tivoli Storage FlashCopy Manager - All Requirement Documents website at: https://www.ibm.com/support/docview.wss?uid=swg21427692. Follow the link to the requirements technote for your specific release or update level.

About this task

When you configure Tivoli Storage FlashCopy Manager, you are prompted to enter parameter values that are specific to your environment. Syntax and value ranges are checked during the setup. Also, you must enter password information that is used to create a password file. A separate Tivoli Storage FlashCopy Manager profile is created for each application.

Before you start a new configuration, review the following application-specific requirements:
DB2® pureScale® environment
In an IBM® DB2 pureScale environment, run the setup script from one DB2 pureScale member to configure the profile. The DB2 setup script setup_db2.sh, updates the instance shared file system that stores the instance shared data. This directory is accessible by all members. The setup script creates the following directories on the instance shared file system:
  • The sqllib/acs directory contains the Tivoli Storage FlashCopy Manager binary files.
  • The dbinstance_shared_directory-name/acs directory contains the profile configuration file and the Tivoli Storage FlashCopy Manager repository directory. This directory is the Tivoli Storage FlashCopy Manager configuration directory and corresponds to the ACS_DIR directory.
You can start a backup operation from any member of the DB2 pureScale instance. The Tivoli Storage FlashCopy Manager management agent acsd coordinates the backups and communicates between the application and device agents. The management agent is started automatically after the installation. If you are required to start the agent manually, this agent must not be started on more than one member. DB2 pureScale database is regarded as a single partitioned database.
DB2 only environment
For DB2 databases, the ACS_DIR directory can be exported from a Network file system (NFS) and the NFS shared on all DB2 Data Partitioning Feature (DPF) partitions.
When a profile exists and you run the setup script, the following options are displayed:
  1. Create a new profile
  2. Use the existing profile without updates
  3. Update and change parameters in an existing profile

The profile configuration file is stored in the ACS_DIR/profile directory. When the ACS_DIR directory is not identical to the INSTANCE_DIR directory, a symbolic link is created from the INSTANCE_DIR/profile that points to the ACS_DIR/profile. If the profile is not stored in the ACS_DIR directory, an error is reported. This profile directory must not be included in any snapshots when you back up data.

Procedure

Depending, on the environment you are configuring for example, DB2 pureScale or Oracle Automatic Storage Management (ASM) not all steps in the configuration procedure are mandatory. To complete the configuration process, complete the following steps:

  1. From the production server or member of the production database instance, log on with the appropriate ID. Use one of the following IDs:
    • (DB2): Log on as the database instance owner.
    • (Oracle or Oracle in an SAP environment): Log on as the database instance owner.
    • (Custom applications): Log on as the application backup user.
  2. Go to the database instance-specific or custom application-specific installation directory (INSTANCE_DIR):
    • (DB2): DB2 instance owner $HOME/sqllib/acs/
    • (Oracle or Oracle in an SAP environment): Oracle instance owner $HOME/acs/
    • (Custom application): $HOME/acs/
  3. Start the setup script by entering one of the following commands:
    • (DB2) ./setup_db2.sh
    • (Oracle or Oracle in an SAP environment) ./setup_ora.sh
    • (Custom applications) ./setup_gen.sh
    You can configure Tivoli Storage FlashCopy Manager in advanced mode by using the -advanced option with the appropriate setup script command. To display help for the parameters, enter the ? character. This help is best viewed in a terminal window that is set for at least 130 characters.

    For some parameters, you can create multiple entries with different values. To create these multiple entries, when prompted Do you want to add another instance of this parameter?, enter y. To delete a parameter entry, when prompted for the parameter value, enter !d.

  4. Follow the setup script instructions that display. Review the completed Tivoli Storage FlashCopy Manager installation sheet to ensure a successful installation. The prompts that are displayed might not be displayed exactly as described in these steps.
    1. Choose the type of configuration:
      • (1) On-site Production Server configuration with optional remote Backup Server configuration.

        This selection guides you through the configuration of Tivoli Storage FlashCopy Manager 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.

      • (2) On-site Backup Server configuration.

        This selection guides you through the configuration of Tivoli Storage FlashCopy Manager on the backup server as a separate installation.

    2. Select one of these configurations:

      Backup only

      Cloning only

      Backup and cloning

      Specify whether to configure the database instance for cloning, backup, or both:
      • Enter 1 to configure for backup only.
      • Enter 2 to configure for cloning only.
      • Enter 3 to configure for backup and cloning.
      Note: In an environment, where cloning is not supported by Tivoli Storage FlashCopy Manager enter 1.
    3. Are you going to perform offloaded backups to Tivoli Storage Manager? [Y|N]
      • Specify YES to configure support for offloaded tape backups.
        Note: For Oracle in an SAP environment, you must also manually update the IBM Tivoli Storage Manager for Enterprise Resource Planning profile initSID.utl file after the configuration completes.
      • Specify NO to configure support for disk-based snapshot backups only.
      Note: These values can be changed by running the setup script again.
    4. Do you want to start offloaded tape backups right after the snapshot? [Y/N]
      Offloaded backups to Tivoli Storage Manager are performed by the Tivoli Storage FlashCopy Manager offload agent tsm4acs. The following two options are available:
      • Start the offload immediately after the FlashCopy backup completes.
      • Start the offload later by scheduling backups on an individual basis. For example, schedule the FlashCopy backup to occur at midnight and the offloaded backup to Tivoli Storage Manager to occur at 4 am. The backup to Tivoli Storage Manager can also be delayed further until the necessary resources in Tivoli Storage Manager server are available.

      Specify YES to back up to Tivoli Storage Manager immediately after the FlashCopy backup completes.

      Specify NO to schedule offloaded backups individually. This answer requires the scheduled backup process to be started manually. For example, add a crontab entry. The default value is to run tsm4acs as a daemon process on the production server.

    5. Tivoli Storage FlashCopy Manager requires at least two daemon processes to be running at all times. Tivoli Storage FlashCopy Manager can add the necessary daemon process to the inittab. Alternatively, you can choose to start and stop the processes yourself, for example, if you want to include the processes in your HA policy.
    6. On Linux operating systems: Do you want IBM Tivoli Storage FlashCopy(R) Manager to create and start the upstart jobs for you? [y|n].
    7. On AIX®, Solaris, and HP-UX operating systems: Do you want FlashCopy Manager to create the inittab entries for you? [Y/N]

      Tivoli Storage FlashCopy Manager requires at least two daemon processes to be running always. Typically, the configuration wizard registers the Tivoli Storage FlashCopy Manager management daemon acsd and generic device agent acsgen in the /etc/inittab or creates and starts upstart jobs on the production server. These processes are started automatically even after a system restart.

      If you are installing Tivoli Storage FlashCopy Manager in an HA environment, these processes must be started from your HA environment. Add the processes to your HA startup scripts. In addition, you must ensure that these daemon processes are restarted if they are ended. In HA environments, nothing is added to /etc/inittab and no upstart jobs are created.

      • Specify NO for the executable files that include command-line options not to be added to the /etc/inittab and not to create upstart jobs. You must make sure that they are started by your HA startup scripts and that they are restarted whenever they are ended.
      • Specify YES to enter the daemon processes in the /etc/inittab or to create and start upstart jobs.
      Important: After this procedure completes, you are prompted whether to deploy the configuration to one or multiple backup or clone systems. This deployment associates the device classes that are specified in the profile with the backup or clone systems. The following section describes the configuration of a backup system. When you configure a clone system, similar options are displayed.
    8. Select the backup system to update or delete:

      n) To configure a new backup system

      b) Return to the previous menu

      q) To quit the configuration

      Tivoli Storage FlashCopy Manager requires a backup server to be available when the following conditions exist:
      • Offload backups to Tivoli Storage Manager are performed.
      • FlashCopy backup consistency must be verified during a forced mount operation.

      Select n to configure and activate Tivoli Storage FlashCopy Manager on a remote site by using OpenSSH. OpenSSH must already be available for remote connections from the production system to the backup system. You are prompted to specify the DEVICE_CLASS to be enabled on the backup system. Select one or more DEVICE_CLASS parameters from the list that is displayed on the console.

      Enter q to quit the configuration of the backup system and exit the setup script if one of the following conditions exist:
      • OpenSSH is not available.
      • The INSTANCE_HOME_DIR and ACS_DIR are shared between the production system and backup system by using NFS.
      • You want to configure the backup system in a separate step.

      When a backup system is configured, it is possible to run several actions on this backup system. For example, update, stop, start, delete FlashCopy Manager agents that are running on the backup system or you can set up SSH key authentication to the backup system.

      The following example illustrates these actions.
      Select the backup system to update or delete:
1) acsback1
2) acsback2
3) acsback5

n) to configure a new backup system
q) to quit configuration
1
selected backup system: acsback1

The backup system on acsback1 is configured with the device class DISK_ONLY3.
Select the action you want to take on the backup system acsback1:

1) update IBM Tivoli Storage FlashCopy Manager installation
2) start IBM Tivoli Storage FlashCopy Manager services
3) stop IBM Tivoli Storage FlashCopy Manager services
4) uninstall IBM Tivoli Storage FlashCopy Manager
5) setup the SSH key authentication

b) return to the backup system selection
q) quit the configuration

Select one of the options above.
      The same set of functions is provided for the configuration of the clone instances with SSH.
    9. If this DB2 instance is a DB2 standby server source or target, or is a source or target in a DB2 HADR configuration, you can also back up the database while it serves as the standby (or HADR) target.

      Do you want to configure Tivoli Storage FlashCopy Manager to also protect the database while it acts as a standby (or HADR) target? [Y/N]

      Specify YES to back up a DB2 standby server. An extra DB2STANDBY section is added to the profile. If you are using an offloaded backup configuration, an offload section OFFLOAD_DB2STANDBY is also added.

Parent topic: IBM Tivoli Storage FlashCopy Manager for UNIX and Linux

Feedback