Disaster recovery rehearsal in Continentalclusters

22
PACKAGE RECOVERY GROUP inv_rac10g_recgp
Maintenance Mode no
PACKAGE ROLE STATUS
Atlanta/inv_rac10g_primpkg primary up
Houston/inv_rac10g_recpkg recovery down
Houston/inv_rac10g_rhpkg rehearsal down
PACKAGE RECOVERY GROUP sales_rac9i_recgp_1
Maintenance Mode no
PACKAGE ROLE STATUS
Atlanta/sales_rac9i_primpkg_1 primary up
Houston/sales_rac9i_recpkg_1 recovery down
Houston/sales_rac9i_recpkg_1 rehearsal down
PACKAGE RECOVERY GROUP sales_rac9i_recgp_2
Maintenance Mode no
PACKAGE ROLE STATUS
Atlanta/sales_rac9i_primpkg_2 primary up
Houston/sales_rac9i_recpkg_2 recovery down
Houston/sales_rac9i_recpkg_2 rehearsal down
PACKAGE RECOVERY GROUP billing_recgp
Maintenance Mode yes
PACKAGE ROLE STATUS
Atlanta/billing_primpkg primary up
Houston/billing_recpkg recovery down
Houston/billing_rhpkg rehearsal down
PACKAGE RECOVERY GROUP mkt_recgp
Maintenance Mode no
PACKAGE ROLE STATUS
Atlanta/mkt_primpkg primary up
Houston/mkt_recpkg recovery down
PACKAGE RECOVERY GROUP payroll_recgp
Maintenance Mode no
PACKAGE ROLE STATUS
Atlanta/payroll_primpkg primary up
Houston/payroll_recpkg recovery down
4. Prepare the replication environment for DR rehearsal.
Manually suspend the replication and enable write access to secondary mirror copy configured for
the package.
$) pairsplit –g billing_dg -rw
For each volume group configured for the package change the cluster id by running the following
command from any of the recovery cluster nodes.
#vgchange -c n billing_vg
#vgchange -c y billing_vg