VERITAS FlashSnap Point-In-Time-Copy Solutions Administrator's Guide

Chapter 5, Decision Support
Creating an Off-Host Replica Database
55
◆ Sybase ASE from version 12.0 onward provides the Quiesce feature to allow temporary
suspension of writes to a database. As the Sybase database administrator, put the database
in quiesce mode by using a script such as that shown in “Script to Quiesce Sybase ASE
Database” on page 70.
If you are using Sybase ASE 12.5, you can specify the for external dump clause to
the quiesce command. This warm standby method allows you to update a replica
database using transaction logs dumped from the primary database. See “Updating a
Warm Standby Sybase ASE 12.5 Database” on page 59 for more information.
4. On the primary host, refresh the contents of the snapshot volumes from the original volume
using the following command:
# vxsnap -g volumedg refresh snapvol source=vol \
[snapvol2 source=vol2]... syncing=yes
The syncing=yes attribute starts a synchronization of the snapshot in the background.
For example, to refresh the snapshots svol1, svol2 and svol3:
# vxsnap -g dbasedg refresh svol1 source=vol1 svol2 source=vol2 \
svol3 source=vol3
5. If you temporarily suspended updates to volumes in step 2, release all the tablespaces or
databases from suspend, hot backup or quiesce mode:
◆ As the DB2 database administrator, use a script such as that shown in “Script to Resume
I/O for a DB2 Database” on page 74.
◆ As the Oracle database administrator, release all the tablespaces from hot backup mode
using a script such as that shown in “Script to End Oracle Database Hot Backup Mode” on
page 72.
◆ As the Sybase database administrator, release the database from quiesce mode using a
script such as that shown in “Script to Release Sybase ASE Database from Quiesce Mode”
on page 73.
6. Use the following command to wait for the contents of the snapshot to be fully synchronous
with the contents of the original volume:
# vxsnap -g volumedg syncwait snapvol