Assure MIMIX for AIX/PowerHA integration requirements - assure_mimix - 6.0

Keep in mind the following Assure MIMIX for AIX/PowerHA integration requirements:

Application Server—If there are multiple Resource Groups that can failover independently, there must be multiple Assure MIMIX for AIX Context IDs created, one for each Resource Group. Likewise, each of these Resource Groups requires scripts to manage the startup and shutdown of each Assure MIMIX for AIX ContextID. The Assure MIMIX for AIX start script needs to be placed at the beginning of the application server startup sequence, before applications are started. The Assure MIMIX for AIX stop script needs to be executed at the end of the application server shutdown sequence, after all applications have been stopped gracefully.

1. On the primary production server, use PowerHA to add or change Application Controller Scripts. For your convenience, sample start and stop scripts are provided in the /usr/scrt/samples directory.

   Copy the sample Assure MIMIX for AIX start and stop scripts to the location of your choice and change the values for CONTEXT_ID and FAILOVER_CONTEXT_ID and insert your application start and stop scripts where indicated.

   For example:

   Application Controller Name: App_Controller_C1Start Script: [/scripts/es_ha_start_script_C1.ksh]Stop Script: [/scripts/es_ha_stop_script_C1.ksh]Application Monitor Name(s)Application startup mode: [background]

   See the sample Assure MIMIX for AIX start and stop scripts below.

2. Configure a Service IP Label/Address if one does not already exist.

   • Configure HACMP Service IP Labels/Addresses.

     • Add a Service IP Label/Address

       • Configurable on Multiple Nodes

   Note: Use the IP Label/Address that was used by the Assure MIMIX for AIX Replication Group wizard.

3. Application Resource Group Changes

   • Enter the Service IP Labels/Addresses

   • Enter the names of all volume groups associated with the Assure MIMIX for AIX <Primary ContextID> to be varied on when the resource is initially acquired.

   Note: The Assure MIMIX for AIX drivers must be loaded before the Assure MIMIX for AIX protected file systems are mounted or written to. This is managed during the execution of the Assure MIMIX for AIX startup process. PowerHA determines which file systems to mount based on the information provided in the resource group configuration. If no file systems are specified, PowerHA will mount all file systems in all volume groups that are defined in the resource group. This scenario is not preferred for an Assure MIMIX for AIX environment. Assure MIMIX for AIX should start before the file systems are mounted.

   • Enter the file system mount points /usr/scrt/run/c<Primary Context ID>and /usr/scrt/run/c<Failover Context ID>. This will force only these file systems to be mounted when the resource group is acquired.

4. Run HACMP Extended Verification and Synchronization.

5. On the recovery server use rtstart to manually start the Assure MIMIX for AIX Primary Context ID.

   /usr/scrt/bin/rtstart -C<PrimaryContextID>.

6. Start Cluster Services on both production nodes:

   • Verify that the volume groups defined in the Resource Group are online in concurrent mode.

   • Verify that the /usr/scrt/run/c<Primary Context ID> and /usr/scrt/run/c<Failover Context ID> file systems are mounted.

   • Verify that all of the Assure MIMIX for AIX protected file systems are mounted.

   • Verify that the Service IP Address is aliased on the Ethernet Network Interface.

   • Verify that Assure MIMIX for AIX is replicating to the recovery server. View the log files: /var/log/EchoStream/scrt_lca-<Primary Context ID>.out on the production server and /var/log/EchoStream/scrt_aba-<Primary Context ID>.out on the recovery server.