Sybase Database in a SAN Environment Using EVA Snapclone Technology (August 2007)

• Re-create or re-add any TEMPFILES used for temporary tablespaces on the target.

• Update DBID and GLOBAL_DBNAME using DBEWIND Utility provided by Oracle.

Hot backup

In a hot backup, the database is open and extensive transaction activities can occur. In this

case, the datafiles tend to be inconsistent with respect to the checkpoint SCN. Archived redo

logfiles are mandatory for cloning the database.

Cold Backup

In a cold backup, the database is shut down. There are no user transactions and

background processes that can change the system SCN. Therefore, the datafiles are

checkpointed to the same SCN, and the state of the database is consistent. Most database

administrators use cold backup for cloning.

Sample Script to Create the Initial Snapclones

The sample script to create the initial Snapclones is as follows:

!!!!!!!!!!!!!!!!!! Create initial snapclones (SC): copy OL to SC !

! create snapclone of VD_CEN

SET VDISK "\Virtual Disks\VD_CEN_01" writecache=WRITETHROUGH

SET VDISK "\Virtual Disks\VD_CEN_02" writecache=WRITETHROUGH

ADD COPY COPY_CEN_01 VDISK="\Virtual Disks\VD_CEN_01\ACTIVE" redundancy=vraid5

NOWAIT_FOR_COMPLETION

ADD COPY COPY_CEN_02 VDISK="\Virtual Disks\VD_CEN_02\ACTIVE" redundancy=vraid5

NOWAIT_FOR_COMPLETION

! wait with benchmark start till copy has finished

For more information on using SSSU scripts, contact your HP support representative.