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

ALTER TABLESPACE TOOLS BEGIN BACKUP;

ALTER TABLESPACE USERS BEGIN BACKUP;

ALTER TABLESPACE XDB BEGIN BACKUP;

ALTER TABLESPACE USERTS BEGIN BACKUP;

The BEGIN BACKUP commands freeze the checkpoint System Change Number (SCN)

in the datafile headers of the associated tablespaces. That is, even though user

transactions are in progress, the checkpoint SCN remains constant until the END

BACKUP command is issued.

To clone DB1 on EVA Storage and store it, ensure that there is enough disk space on

the EVA. The following figure illustrates the clone creation process on a Command

View EVA:

Figure 2 - Creation of clone

The cloning process must be carried out when the traffic to the EVA is low. The

average EVA Storage CPU usage is about 50 percent, and the cloning of 300GB of

data does not take more than a few minutes.

5. Once the volume cloning process is complete, terminate the tablespace backups using

the following SQL script:

ALTER TABLESPACE SYSTEM END BACKUP;

ALTER TABLESPACE UNDOTBS1 END BACKUP;

ALTER TABLESPACE DRYS END BACKUP;

ALTER TABLESPACE INDX END BACKUP;

ALTER TABLESPACE TOOLS END BACKUP;

ALTER TABLESPACE USERS END BACKUP;