Disaster recovery rehearsal in Continentalclusters

7. Move the recovery group sales_rac9i_recgp_1 and sales_rac9i_recgp_2 out of

maintenance mode.

#cmrecovercl -e -g sales_rac9i_recgp_1

#cmrecovercl -e -g sales_rac9i_recgp_2

Note: Using the cmviewconcl command, verify that the recovery group sales_rac9i_recgp_1 and

sales_rac9i_recgp_2 are not in maintenance mode.

Note: Restore the listener configuration on nodes HOUnode1 and HOUnode2 to use the original set up IP addresses

i.e., sales_rac9i_recpkg_1 and sales_rac9i_recpkg_2 respectively.

Primary site failure during rehearsal

This use case highlights the impact of a primary site failure during rehearsal. Unless explicitly

mentioned, the steps shown below can be executed from any node in the recovery cluster. It is

assumed that the primary packages sales_rac9i_primpkg_1 and sales_rac9i_primpkg_2 are up on

Atlanta cluster and rehearsal is in progress.

1. Using the cmviewconcl command, verify that the recovery groups sales_rac9i_recgp_1 and

sales_rac9i_recgp_2 are in maintenance mode

2. Use the “cmviewcl” command to verify to that the rehearsal package sales_rac9i_rhpkg_1 is

started on HOUnode1 and rehearsal package sales_rac9i_rhpkg_2 is started on HOUnode2.

3. Primary site fails (i.e., ATLnode1, ATLnode2, and the storage system at Atlanta cluster fail).

4. Recover the Atlanta cluster by running “cmrecovercl –c “Atlanta” on HOUnode1.

$) cmrecovercl –c “Atlanta”

Warning: This command will take over for the primary cluster <Atlanta> by starting the recovery package on the

recovery cluster <Houston>. You must follow your site disaster recovery procedure to ensure that the primary

packages on <Atlanta> are not running and that recovery on Atlanta is necessary.

Continuing with this command while the applications are running on the primary cluster may result

in data corruption.

Warning: The following recovery groups of the recovery pair are in Maintenance Mode and hence will not

be recovered.

<sales_rac9i_recgp_1>

<sales_rac9i_recgp_2>

Are you sure that the primary packages are not running and will not come back, and are you

certain that you want to start the recovery packages [y/n]? y

cmrecovercl: Attempting to recover Recovery Groups from cluster <Atlanta>

Note: The configuration file /etc/cmconcl/ccrac/ccrac.config for cluster shared storage recovery exists. Data

storage specified in the file for this cluster will be prepared for this recovery process. If you choose "n" - not to

prepare the storage for this recovery process, make sure that the required storage for this recovery process has

been properly prepared.

Is this what you intend to do [y/n]? y

cmrecovercl: Attempting to recover Recovery Group <inv_rac10g_recgp> from cluster <Atlanta>

Enabling recovery package inv_rac10g_recpkg on recovery cluster <Atlanta>

Running package inv_rac10g_recpkg

Thu Aug 31 05:40:23 2006

- Running package inv_rac10g_recpkg on node HOUnode1

Thu Aug 31 05:41:03 2006