Veritas Storage Foundation for DB2 supports Database FlashSnap in the HA environment.
When using Database 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:
db2ed_vmchecksnap -D DB2DATABASE -f SNAPPLAN -o validate
The primary database must be down before you perform reverse resychronization (db2ed_vmsnap -D DB2DATABASE -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 repository is unmounted and the db2ed_vmsnap command is aborted.
To avoid the VCS failover process
As root, temporarily freeze the VCS resource group for the database:
# hagrp -freeze ResourceGroup
Run reverse resynchronization:
# db2ed_vmsnap -D DB2DATABASE -f SNAPPLAN \ -o reverse_resync_begin
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.
# hagrp -unfreeze ResourceGroup