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

ManualsBrandsHP ManualsSoftwareHP StorageWorks Business Copy EVA V3.2 Media Kit

Cloning an Oracle/DB2/Sybase Database in a SAN

Environment Using EVA Snapclone Technology

Executive Summary .............................................................................................................................. 3

Introduction......................................................................................................................................... 3

Terminologies...................................................................................................................................... 4

Requirements and Assumptions.............................................................................................................. 4

Cloning Process Overview .................................................................................................................... 5

Creating Production Database Components on EVA LUNs ........................................................................ 6

Cloning Oracle Database Using EVA Snapclone Technology .................................................................... 7

Cloning a Full Database Using Hot Backup ......................................................................................... 7

Cloning a Full Database Using Cold Backup ..................................................................................... 14

Validating the Cloned Database Using Oracle db_verify Script ........................................................... 15

Advantages of Cloning a Database Using the EVA Snapclone Technology Compared to Using the Oracle Recovery

Manager Feature ............................................................................................................................... 16

Advantages of Cloning a Database Using EVA Snapclone Technology .................................................... 17

Cloning a DB2 Database Using EVA Snapclone Technology................................................................... 17

Ensuring Consistency for a DB2 UDB Database (Suspended I/O)......................................................... 17

Initializing a Snapclone Copy of a Database Using the Db2inidb Command ........................................ 18

Changing the Location of a Database Using the db2relocatedb Command ........................................... 20

Advantages of Cloning a DB2 Database Using EVA Snapclone Technology.......................................... 20

Cloning a Sybase Database Using EVA Snapclone Technology............................................................... 21

Advantages of Cloning a Sybase Database Using EVA Snapclone Technology ......................................... 22

Conclusion........................................................................................................................................ 22

Related Information ............................................................................................................................ 23

Quick Reference Steps for Cloning an Oracle Database ..................................................................... 24

Hot backup ................................................................................................................................... 25

Cold Backup.................................................................................................................................. 25

Sample Script to Create the Initial Snapclones ................................................................................... 25

Summary of content (25 pages)

PAGE 1
Cloning an Oracle/DB2/Sybase Database in a SAN Environment Using EVA Snapclone Technology Executive Summary .............................................................................................................................. 3 Introduction ......................................................................................................................................... 3 Terminologies ...........................................................................................................
PAGE 2
© Copyright 2007 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
PAGE 3
Executive Summary EVA Snapclone is a feature that enables you to create copies of the existing data on EVA disk arrays. Using this feature, you can create a copy of original data, which can be restored whenever required. A Snapclone is an independent, point-in-time copy of a virtual disk. It is independent because the data from the source virtual disk is copied to the Snapclone.
PAGE 4
Note: The operating system on the clone and the operating system in the production environment must be the same. For example, the clone of the production database that is running on HPUX cannot run on Solaris. The cloning process must be carried out only when the traffic to the production environment is at its minimum. Hence, database administrators must schedule cloning and backup operations carefully.
PAGE 5
Proddata EVA LUNs to store the production database Sysdata log1 log2 archivedlog Proddataclone EVA LUNs to store the clone sysdataClone log1Clone log2Clone archClone /prod/DB1 Mount point of the production /prod/TEST Mount point of the clone Cloning Process Overview Figure 1 - Setup Details In Figure 1, the EVA is physically connected to the production server on which the original database resides. It is also connected to the test or development server on which the clone will reside.
PAGE 6
Creating Production Database Components on EVA LUNs To create the production database in the Oracle home directory, create the database using the following SQL script and name it as Prod: Note: If the production database already exists, you need not perform this step. connect / as SYSDBA set echo on spool /prod/OraHome1/assistants/dbca/logs/CreateDB.log startup nomount pfile="/prod/OraHome1/admin/DB1/pfile/initDB1.
PAGE 7
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.
PAGE 8
$ setenv ORACLE_BASE /prod/oracle9/clonebase $ setenv ORACLE_HOME /prod/oracle9/OraHome1 The environment variables set using these commands reflect the clone’s instance and the storage configuration. 2. Enter the following commands to create directories in the $ORACLE_BASE path: a. $ mkdir $ORACLE_BASE/TEST/admin b. $ mkdir $ORACLE_BASE/TEST/dbs c. $ mkdir $ORACLE_BASE/TEST/oradata d. $ mkdir $ORACLE_BASE/TEST/admin/bdump e. $ mkdir $ORACLE_BASE/TEST/admin/cdump f. $ mkdir $ORACLE_BASE/TEST/admin/pfile g.
PAGE 9
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.
PAGE 10
ALTER TABLESPACE XDB END BACKUP; ALTER TABLESPACE USERTS END BACKUP; Note: Duplicate the archived redo logfiles, because the archived redo logs are mandatory for the recovery of the cloned database TEST. 6.
PAGE 11
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.
PAGE 12
This command generates a trace file to be written to the destination where the production DB1 initialization parameter USER_DUMP_DEST is pointing to. In this case, the trace file is in $ORACLE_HOME/DB1/admin/udump directory. However, this trace file is unorganized and needs to be reshaped. The reshaped trace file is provided in the form of an SQL script controlClone.sql, as shown below: connect / as sysdba STARTUP NOMOUNT pfile=/prod/oracle9/clonebase/TEST/admin/pfile/initTEST.
PAGE 13
Total System Global Area 135352820 bytes Fixed Size 455156 bytes Variable Size 109051904 bytes Database Buffers 25165824 bytes Redo Buffers 679936 bytes Control file created. This command creates new control files for the clone. These files are stored on the directory specified by the clone’s initialization control_files parameter. In Step 7, the most recent online redo logfiles of the production database DB1 are archived. However, traffic to the database is still flowing.
PAGE 14
generated after the Snapclone is created, as a result of the volume clone, copy it to the archived logs directory. 9. Recover the clone TEST. Enter the following command on the clone instance: SQL> recover database using backup controlfile; You are prompted to enter the archived log file names one by one for recovery. You can select the AUTO option. When the archived logs are recovered, select the filename option and enter the names of the previously copied files, redo03a.log and redo3b.log.
PAGE 15
Important: Cloning a database using cold backup is faster and more consistent than using hot backup. Therefore, cloning database using a cold backup is highly recommended. Validating the Cloned Database Using Oracle db_verify Script To verify the Oracle database data files for integrity, save the following script in the db_verify.pl file and execute it: #!/usr/bin/perl ################################################################## #File:dbverify.
PAGE 16
Verify users01.dbf DBVERIFY: Release 9.2.0.1.0 - Production on Fri Aug 04 10:56:53 2006 Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved. DBVERIFY - Verification starting : FILE = /prod/clone/users/users01.
PAGE 17
Advantages of Cloning a Database Using EVA Snapclone Technology There are business needs that require production or near-production data. These needs can be satisfied by creating a clone of the production database. However, the added overhead and complexities associated with the traditional method of creating a clone database pose immense problems for database and storage administrators. The EVA Snapclone technology, on the contrary, has made the process of cloning a database c simple and easy.
PAGE 18
and later versions enable you to temporarily suspend writes to the database by executing the SET WRITE SUSPEND command. This command also suspends the transaction log files. However, read-only transactions continue to run on the database while it is in the writesuspended state. In addition, some transactions may be forced to wait if they require disk I/O; for example, to flush dirty pages from a buffer pool or to flush log records from the log buffer.
PAGE 19
DB_NAME=oldName,newName DB_PATH=oldPath,newPath INSTANCE=oldInst,newInst NODENUM=nodeNumber LOG_DIR=oldDirPath,newDirPath CONT_PATH=oldContPath1,newContPath1 CONT_PATH=oldContPath2,newContPath2 STORAGE_PATH= oldStoragePath1,newStoragePath1 STIRAGE_PATH= oldStoragePath2,newStoragePath2 The sample configuration file is similar to the following: DB_NAME=prod,clone DB_PATH=/mnt/proddata,/mnt/clonedata INSTANCE=db2inst1,db2inst2 NODENUM=0 LOG_DIR=/mnt/prodlogs/NODE0000,/mnt/clonelogs/NODE0000 CONT_PATH=/mnt/pro
PAGE 20
Important: The db2inidb command is never run on the production or the parent database. Instead, it must be executed only on the cloned database. After initializing a Snapclone copy of a database, change its location by performing the steps described in the following section.
PAGE 21
Cloning a Sybase Database Using EVA Snapclone Technology Assumption: Sybase Adaptive server 12.5.x is installed on Storage LUNs, and all the necessary Sybase devices and databases exist on these storage LUNs. To clone the Sybase database, complete the following steps: 1.
PAGE 22
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.
PAGE 23
Related Information For more information on EVA Snapclone technology and database administration, visit the following websites: http://www.hp.com/ http://www.oracle.com/ http://www.hp-oracle.com/ http://technet.oracle.com/ http://metalink.oracle.com/ (registration required) http://www.oraperf.com/ (registration required) http://www.oracle.hp.com (registration required) http://www.hporaclectc.com (registration required) Note Some of these links may not be accessible if you are outside the HP network.
PAGE 24
Appendix Quick Reference Steps for Cloning an Oracle Database The following section provides quick reference for the procedure used to clone an Oracle database. Assumption: The original database is run in archive log mode, because all production database instances must be available for recovery. However, the production system can remain online during the cloning process. • Back up Controlfile to trace on source database. o ALTER DATABASE BACKUP CONTROLFILE TO TRACE • Look up $ORACLE_HOME/admin/udump/*.
PAGE 25
• 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.