Configuring Oracle RAC for daemon high availability

You can configure IBM® Storage Protect Snapshot in an Oracle RAC environment so that the IBM Storage Protect Snapshot daemons are highly available. When you choose this configuration, IBM Storage Protect Snapshot remains operable even if the RAC node that is hosting the daemons fails. The Configuration Wizard stops and starts daemons as required.

Before you begin

Ensure that a shared file system exists for the IBM Storage Protect Snapshot repository, configuration, and binary files. For more information about this prerequisite, see Preparing Oracle RAC.

When you choose to configure IBM Storage Protect Snapshot for Oracle RAC, the product defines Oracle RAC node names. Each node is made available to the mount agent that is running on the backup or clone server. The mount agent then attempts to connect to the management daemon for each node name. When you complete the configuration and exit the Configuration Wizard, choose to start the daemons automatically. The local node where RAC is running is configured when the process completes.

Procedure

  1. Choose Protecting a new database with the Configuration Wizard, and step through each of the panels.

    Running the Configuration Wizard configures the local node where RAC is running, and stops and starts the daemons automatically. To ensure that the daemons are available on all other RAC nodes, you must manually add them to /etc/inittab, or create the upstart jobs. Alternatively, use systemd on all other RAC nodes. A locking mechanism that uses the shared file system, ensures that only one daemon is active at a time.

    The Configuration Wizard creates a link from Oracle_instance_owner_$HOME_directory/acs to the target directory in the shared file system on the local node where you ran the configuration. You must manually create that link on all other RAC nodes to operate IBM Storage Protect Snapshot from other nodes.

  2. After you configured the daemons on all RAC nodes, login as the Oracle instance owner and go to the <Oracle_instance_owner_$HOME_directory>/acscall directory.
  3. Enter the start or stop command as follows,
    ./setup_ora.sh -a stop -d 
    <Oracle_instance_owner_$HOME_directory>
    or,
    ./setup_ora.sh -a start -d 
    <Oracle_instance_owner_$HOME_directory>