Using Database FlashSnap in an HA Environment

VERITAS Storage Foundation 4.1 for Oracle supports FlashSnap in the HA environment.

When using FlashSnap in the HA environment, observe the following limitations:

• Modify the default snapplan to use the virtual host name defined for the database resource group for the PRIMARY_HOST and/or the SECONDARY_HOST parameters and validate the snapplan before creating a snapshot by running the following command:

• dbed_vmchecksnap - ORACLE_SID -H ORACLE_HOME \
  -f SNAPPLAN -o validate

• The primary database must be down before you perform reverse resychronization (dbed_vmsnap - ORACLE_SID -f SNAPPLAN -o reverse_resync_begin). When VERITAS Cluster Server (VCS) detects that the primary database is down, it starts the failover process and the VxDBA repository is unmounted and the dbed_vmsnap command is aborted.

To avoid the VCS failover process, perform the following steps:

1. As root, temporarily freeze the VCS resource group for the database:
     # hagrp -freeze ResourceGroup
2. Shut down the primary database.
3. Run reverse resynchronization:
   # dbed_vmsnap ORACLE_SID -f SNAPPLAN -o\
   reverse_resync_begin
4. After reverse reynchronization changes are committed (-o reverse_resync_commit), verify that the database has been started in ARCHIVELOG mode. This information is provided in the status messages that appear after running committing reverse resynchronization changes.
5. Unfreeze the resource group:
     # hagrp -unfreeze ResourceGroup