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

Cloning Oracle Database Using EVA Snapclone Technology

This section describes how to create a non-Oracle Recovery Manager (non-RMAN) clone in

a SAN environment.

Cloning a Full Database Using Hot Backup

The EVA Snapclone feature offers an extremely convenient and efficient way to back up

databases.

Hot backup is performed when the database is open. It is generally employed when a

database cannot be shut down. However, you must ensure that the database is in archive

log mode.

Create a clone of the production database (DB1) and name it as TEST. The clone can reside

either on the same system as the source, or on a different system.

Note:

• During the cloning process, the EVA Snapclone feature duplicates only the production

datafiles and the archived redo logfiles.

• You need not duplicate the online redo logs and control files. These files are

recreated during the cloning process.

• The HP Storage System Scripting Utility (SSSU) can be used to create the Snapclones;

a script can be written to prepare the snapclones, and the Oracle SQL queries can be

included to bring the Oracle clone database up and ready. For more information on

creating the initial Snapclones, see Sample Script to Create the Initial Snapclones.

To clone the database, complete the following steps:

1. Set the environment variables, ORACLE_SID, ORACLE_HOME, and

ORACLE_BASE, appropriately.

Note:

If the clone and the source exist on the same system, $ORACLE_HOME must be

identical for both the systems.

Enter the following commands to set the environment variables:

$ setenv ORACLE_SID TEST