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

Locate the new mount point where you have mounted Snapclone, edit the interfaces file

located under the $SYBASE directory, and replace the original server name with the correct

server name of the new system.

The file output before the changes are made is as shown below:

ufive

master tcp ether hp987-lab03 4101

query tcp ether hp987-lab03 4101

The file output after the changes are made is as shown below:

ufive

master tcp ether hp987-lab04 4101

query tcp ether hp987-lab04 4101

Ensure that the shared memory parameters required for Sybase are set up on the new

system.

Note:

Work with the Sybase DBA for exact shared memory configuration parameters.

4. Start the new Sybase cloned instance.

Advantages of Cloning a Sybase Database Using EVA

Snapclone Technology

For information on the advantages of cloning a Sybase database using EVA Snapclone

technology, see Advantages of Cloning a Database Using EVA Snapclone.

Conclusion

The EVA Snapclone feature provides database administrators with a fast and robust method

to clone a production database. This feature and its associated Snapclone technology enable

you to save time and effort in performing database backup and recovery operations. The

EVA Storage enables users to create a distinct container for a distinct dataset. This greatly

simplifies backup and cloning of a partial database. The procedures described in this paper

provide you with a method to clone Oracle, DB2, and Sybase databases.