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

minutes by simply clicking the Command View EVA twice. The efficiency and

simplicity of EVA Snapclone technology offers DBA a robust and fast backup

mechanism. In addition, the EVA LUNs enable users to create a distinct container for

a distinct dataset. This is extremely useful for the partial backup of a database. For

instance, you can create database datasets, such as the Oracle binary files, datafiles,

multiplexed online redo logfiles, or the archived redo logfiles, and store them in

separate containers. Each dataset has its own container, and the size of the container

depends on the dataset space requirements. If you want to back up a particular

dataset -- for example, the archived redo logfiles - you need to back up only the

associated container. No other datasets are involved. This method saves time and

effort required for performing backups in database administration.

7. Mount the previously cloned volumes, sysdataClone and archClone, on the Oracle

server, which can be on the same system as the source database DB1, or on a

different system by entering the following commands:

mkdir /dev/<vgsnapclonename>

mknod /dev/<vgsnapclonename>/group c 64 0xNn0000

vgchgid /dev/rdsk/vgsnap_dev_file

vgchange -c n <vgsnapclonename>

vgchange -a y <vgsnapclonename>

fsck -F vxfs /dev/<vgsnapclonename>/lvol1

mount -F vxfs /dev/<vgsnapclonename>/lvol1 /mount_point_dir

At this point, the file backups are complete and the clone TEST is ready for recovery.

Caution:

These steps may vary depending on the operating system; the steps described here

are tested only on the HP-UX operating system.

Note:

Do not duplicate the online redo log files and control files of the production DB1,

because they may corrupt your clone if not used carefully. Instead, create new

volumes, log1Clone and log1Clone, to store the online redo logfiles for the clone.

8. Recreate the clone’s control files on the production server by entering the following

SQL command:

SQL> alter database backup controlfile to trace; Database altered.