tivoli data protection for emc symmetrix for oracle...

Tivoli Data Protection for EMCSymmetrix for Oracle DatabasesInstallation and User’s GuideVersion 1 Release 1

NoteBefore using this information and the product it supports, read the generalinformation under “Notices” on page vii.

First Edition (July 2000)

This edition applies to Version 1 Release 1 of Tivoli Data Protection for EMC Symmetrix forOracle Databases, 5698–EMO, and to any subsequent releases until otherwise indicated innew editions or technical newsletters. Make sure you are using the correct edition for thelevel of the product.

Order publications through your Tivoli representative or the Tivoli branch office that servesyour locality.

Tivoli welcomes your comments. You can send us comments about this book electronically:

¶ Internet:[email protected]

Information sent grants Tivoli a nonexclusive right to use or distribute in any way Tivolibelieves appropriate without incurring any obligation to you.

© Copyright International Business Machines Corporation 2000. All rights reserved.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSAADP Schedule Contract with IBM Corp.

Contents

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiTrademarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Understanding TDP for Symmetrix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Operating Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Understanding the TSM Backup-Archive Client and Server. . . . . . . . . . . . . . 3

Understanding the TSM API. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Understanding TDP for Oracle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Chapter 2. Installing TDP for Symmetrix . . . . . . . . . . . . . . . . . 7Installation Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Hardware Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Software Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Environment Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Installation Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Installing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Editing the Options Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Option File Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Option File Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

TDP for Symmetrix Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . 12

Defining Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Environment Variable Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . 14

iiiTivoli Data Protection for EMC Symmetrix for Oracle Databases Installation and User’sGuide

Editing the TSM Server Script File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

TSM Server Script File Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Example TSM Server Script File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Creating a Backup Script. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Example Backup Script. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Establishing BCVs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Editing the User Setup File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Setup File Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Example Setup File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Specifying the TSM Management Class. . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Registering Your Workstations with the TSM Server. . . . . . . . . . . . . . . . . . 21

Chapter 3. Backup Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Performing a Backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Backup Method One. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Backup Method Two. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Backup Method Three. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Backup Strategy Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Chapter 4. Restore Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Performing a Restore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Restore Method One (Entire Database). . . . . . . . . . . . . . . . . . . . . . . . 27

Restore Method Two (Datafile Only). . . . . . . . . . . . . . . . . . . . . . . . . . 28

Restore Strategy Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Chapter 5. Using the TSM Central Scheduler . . . . . . . . . . . 31Example of Central Scheduler Service to Automate Backups. . . . . . . . . . . . 33

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

iv Version 1 Release 1

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

vTivoli Data Protection for EMC Symmetrix for Oracle Databases Installation and User’sGuide

vi Version 1 Release 1

Notices

This information was developed for products and services offered inthe U.S.A.

IBM may not offer the products, services, or features discussed inthis document in other countries. Consult your local IBMrepresentative for information on the products and services currentlyavailable in your area. Any reference to an IBM product, program,or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionallyequivalent product, program, or service that does not infringe anyIBM intellectual property right may be used instead. However, it isthe user’s responsibility to evaluate and verify the operation of anynon-IBM product, program, or service.

IBM may have patents or pending patent applications coveringsubject matter described in this document. The furnishing of thisdocument does not give you any license to these patents. You cansend license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.

The following paragraph does not apply to the United Kingdomor any other country where such provisions are inconsistent withlocal law: INTERNATIONAL BUSINESS MACHINESCORPORATION PROVIDES THIS PUBLICATION″AS IS″WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS ORIMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITYOR FITNESS FOR A PARTICULAR PURPOSE. Some states do notallow disclaimer of express or implied warranties in certaintransactions, therefore, this statement may not apply to you.

viiTivoli Data Protection for EMC Symmetrix for Oracle Databases Installation and User’sGuide

This information could include technical inaccuracies ortypographical errors. Changes are periodically made to theinformation herein; these changes will be incorporated in neweditions of the publication. IBM may make improvements and/orchanges in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites areprovided for convenience only and do not in any manner serve as anendorsement of those Web sites. The materials at those Web sites arenot part of the materials for this IBM product and use of those Websites is at your own risk.

IBM may use or distribute any of the information you supply in anyway it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it forthe purpose of enabling: (i) the exchange of information betweenindependently created programs and other programs (including thisone) and (ii) the mutual use of the information which has beenexchanged, should contact:

IBM CorporationInformation Enabling RequestsDept. M135600 Cottle RoadSan Jose CA 95193-0001U.S.A.

Such information may be available, subject to appropriate terms andconditions, including in some cases, payment of a fee.

The licensed program described in this document and all licensedmaterial available for it are provided by IBM under terms of theIBM Customer Agreement, IBM International Program LicenseAgreement or any equivalent agreement between us.

Information concerning non-IBM products was obtained from thesuppliers of those products, their published announcements or otherpublicly available sources. IBM has not tested those products and

viii Version 1 Release 1

cannot confirm the accuracy of performance, compatibility or anyother claims related to non-IBM products. Questions on thecapabilities of non-IBM products should be addressed to thesuppliers of those products.

This information is for planning purposes only. The informationherein is subject to change before the products described becomeavailable.

If you are viewing this information softcopy, the photographs andcolor illustrations may not appear.

ixTivoli Data Protection for EMC Symmetrix for Oracle Databases Installation and User’sGuide

TrademarksThe following terms are trademarks of the IBM Corporation in theUnited States, or other countries, or both:

IBM

Tivoli is a registered trademark of Tivoli Systems Inc. in the UnitedStates, or other countries, or both.

UNIX is a registered trademark of The Open Group in the UnitedStates and other countries.

Other company, product, and service names may be trademarks orservice marks of others.

x Version 1 Release 1

Customer Support

For support for this or any Tivoli product, you can contact TivoliCustomer Support in one of the following ways:

Contact Method Contact Information

Tivoli Storage Manager technicalsupport Web site

http://www.tivoli.com/support/storage_mgr/tivolimain.html

Submit a problem managementrecord (PMR) usingIBMSERV/IBMLINK

http://www2.ibmlink.ibm.com

Submit a problem managementrecord (PMR) using the Internet

http://www.tivoli.com/support

E-mail [email protected]

Telephone (United States) 1-800-TIVOLI8 (1-800-848-6548)

Telephone (international) Consult the Web site for customersupport telephone numbers

Telephone for product numbers5697-TS9, 5697-DRS or 5697-DPM

1-800-237-5511

You can review the Customer Support Handbook at the followingURL: http://www.tivoli.com/support/handbook/

When you contact Tivoli Customer Support, be prepared to provideidentification information for your company so that supportpersonnel can readily assist you. Company identification informationmay also be needed to access various online services available onthe Web site.

The support Web site offers extensive information, including:

Customer Support Handbook (a guide to support services).

Frequently Asked Questions (FAQs).

Documentation for all Tivoli products, including Release Notes,Redbooks, and Whitepapers.

xiTivoli Data Protection for EMC Symmetrix for Oracle Databases Installation and User’sGuide

The documentation for some product releases is available in bothPDF and HTML formats. Translated documents are also available forsome product releases. You can order documentation by e-mail [email protected]. Please provide the publication number, partnumber, or order number of the desired document. Alternatively, youcan provide the document title, version number, and date ofpublication.

We are very interested in hearing about your experience with Tivoliproducts and documentation. We also welcome your suggestions forimprovements. If you have comments or suggestions about ourdocumentation, please contact us in one of the following ways:

Send e-mail [email protected].

Complete our customer feedback survey at URL:http://www.tivoli.com/support/feedback

xii Version 1 Release 1

Before You Begin

This publication provides information to install, configure, andadministrate Tivoli Data Protection for EMC Symmetrix for OracleDatabases.

In this publication, it is assumed that you have an understanding ofthe following:

UNIX operating system

EMC Symmetrix subsystem

Sun Solaris operating system

Oracle database administration

Tivoli Data Protection for Oracle for Solaris

Tivoli Storage Manager Backup-Archive Client

Tivoli Storage Manager Application Program Interface

The following TSM publications provide additional information.

Table 1. Related PublicationsTitle Order Number

Tivoli Storage Manager for Sun SolarisAdministrator’s Guide

GC35-0407

Tivoli Storage Manager for Sun SolarisAdministrator’s Reference

GC35-0408

Tivoli Storage Manager Installing the Clients SH26-4119

Tivoli Storage Manager Messages GC35-0405

Tivoli Storage Manager Using the ApplicationProgram Interface

SH26-4123

Tivoli Storage Manager for UNIX Using theBackup-Archive Clients

SH26-4122

Tivoli Data Protection for Oracle for UNIXInstallation and User’s Guide

SH26-4112

xiiiTivoli Data Protection for EMC Symmetrix for Oracle Databases Installation and User’sGuide

Information about Tivoli Data Protection for EMC Symmetrixsupport, requirements, supported devices, Global Disaster Recovery,frequently asked questions, publications, Tivoli Storage Managerclients and PTFs can be found at the following URL:http://www.tivoli.com/support/storage_mgr/tivolimain.html

The following links to TSM and referenced products on the WorldWide Web also provide additional information.

Download TSM files from the Internetftp://ftp.software.ibm.com

Access the TSM Discussion Listhttp://vm.marist.edu:80/htbin/wlvindex?ADSM-L

TSM Redbookshttp://www.redbooks.ibm.com

xiv Version 1 Release 1

Introduction

Tivoli Data Protection for EMC Symmetrix for Oracle Databases(TDP for Symmetrix) minimizes the impact on Oracle databaseservers while performing Tivoli Storage Manager (TSM) automateddatabase backups. TDP for Symmetrix off-loads the transfer ofbackup data from the database server. The Oracle database mustreside on an EMC storage subsystem. TDP for Symmetrix providesoptions to implement high-efficiency backup and recovery ofbusiness-critical databases while virtually eliminating backup-relateddowntime or user disruption on the production host.

Understanding TDP for SymmetrixThis section describes the operating environment and functions ofTDP for Symmetrix.

Operating EnvironmentThe operating environment consists of the Oracle database executingon a Sun server attached to an EMC Symmetrix storage subsystem.This Sun server is the production system. Another Sun server, thebackup system, is also attached to the EMC Symmetrix storagesubsystem to back up copied data to the TSM server. In addition,TDP for Symmetrix uses the TSM Backup-Archive Client andServer, TSM Application Program Interface (API), and Tivoli DataProtection for Oracle (TDP for Oracle).

See “Software Requirements” on page 8 for a detailed list ofapplications required by TDP for Symmetrix.

1

1Tivoli Data Protection for EMC Symmetrix for Oracle Databases Installation and User’sGuide

1.Introduction

FunctionsThis section provides an overview of TDP for Symmetrix functions:

¶ High availability Oracle database backup using SymmetrixBusiness Continuance Volumes (BCV)

¶ Centrally administered and scheduled backup operations

¶ Integration with Tivoli Storage Manager Media Managementfunctions

High Availability Oracle Database Backup Using SymmetrixBCVs

TDP for Symmetrix accomplishes high availability backup of anOracle database on an EMC Symmetrix storage subsystem by usingTimeFinder BCV devices.

EMC TimeFinder is a licensed storage management softwarepackage available for Symmetrix systems. TimeFinder software mustreside on both the host and Symmetrix systems. This softwareprovides the ability to create independently addressed BCVs inbackground mode. BCVs are exact copies of active productionvolumes used to run simultaneous tasks. Once a mirror relationshiphas been established, the BCV can be split off to create a separatepoint-in-time copy of the primary data. As long as the BCV isconnected to the secondary host (backup side), this copy remainsindependently accessible and does not impact the productionenvironment (production side). BCVs can be established,re-established, split, or restored using the Symmetrix command-lineinterface (SYMCLI) or the Symmetrix TimeFinder API (SYMAPI).

TDP for Symmetrix integrates with TimeFinder BCVs to providehigh-performance, database-aware split-mirror backup of Oracledatabases from a secondary host machine while the productionapplication remains online and fully available to users. TDP forSymmetrix backs up a TimeFinder BCV on a secondary backup hostrunning TDP for Oracle. Because the backup operation is conductedon the split-mirror copy, most processing occurs on the secondarybackup host. As a result, the inaccessibility of the productiondatabase is minimized and the production host continues to dedicate

2 Version 1 Release 1

processor time to the production database. This greatly reduces anyperformance impact on the production database server.

TDP for Symmetrix uses the Oracle8 Recovery Manager (RMAN)utility in conjunction with TDP for Oracle to conduct backup andrestore procedures. After initiating a backup or restore with theOracle8 RMAN utility, TDP for Oracle interfaces with the TSMserver to transmit data. As a result, TDP for Symmetrix supportsmultiple parallel backup and restore procedures.

Centrally Administered and Scheduled Backup OperationsUnattended Oracle backups can be scheduled from the TSM server.You can select when the backups occur without waiting for off-peakhours or maintenance downtime.

Integration with TSM Media Management FunctionsAll TSM storage devices and media management capabilities areavailable to TDP for Symmetrix. You can share the devices used forother backups or give Oracle exclusive use of certain devices andmedia. Lifecycle management of the media and generation of tapecopies for off-site vaulting are supported.

Understanding the TSM Backup-Archive Client andServer

TSM is a client/server program that provides storage managementservices in a multivendor, multiplatform computer environment.

TSM provides the following functions:

Reduces Network Complexity

TSM reduces network complexity with interfaces and functionsthat span network environments. This provides consistency acrossdifferent operating systems and hardware.

Increases Administrator Productivity

TSM can reduce the cost of network administration by allowingadministrators to perform these actions:v Automate repetitive processesv Schedule unmanned processes


1.Introduction

v Administer TSM from anywhere in the network

Reduces the Risk of Data Loss

Many users do not back up their data. Other users applystand-alone backup techniques with diskettes and tapes as theonly protection for business data. These backup systems oftenproduce disappointing results during recovery operations. TSMschedules routine backups that enable users to recover fromaccidental data deletion without administrator involvement.

Optimizes Existing Storage Resources

TSM allows users to move files from client file systems to TSMstorage. This saves space on client file systems and can eliminatethe expense of upgrading client storage hardware.

TSM monitors client storage space and moves files from clientfile systems to TSM storage if an out-of-space conditionthreatens. This function can also eliminate the expense of clienthardware upgrades.

TSM provides these services:

Backup and Restore Services

Backup and restore services allow backup-archive clients togenerate backup copies of data at specified intervals and restorethe data from these copies when required. These services protectagainst workstation or file server media failure, accidental filedeletion, data corruption, data vandalism, or site-wide disasters.

Archive and Retrieve Services

Archive and retrieve services provide backup-archive clients withpoint-in-time copies of data for long-term storage.

Server Hierarchical Storage Management Services

Server hierarchical storage management services migrate clientfiles from expensive storage media to less expensive storagemedia (from disk to tape, for example). File migration isdetermined by administrator-defined thresholds for each storagepool. Migration applies to all backup and archive client files.


Automation Services

TSM administrators can increase productivity by automatingcommon storage administration tasks.

Administration Services

TSM administration services provide support for routinemonitoring, administration, and accounting. Administrators canmanage the server from another system or the same system. TheTSM utilities allow the administrator to perform these functions:v Define devicesv Label tape volumesv Add additional clientsv Format storage volumesv Set client and server options

TSM monitors scheduled operations and maintains statusinformation in the database. An administrator can export data toremovable media. This data can be imported by another server,making the export and import features a convenient utility formoving server data. The administrator can specify the accountingoption generated at the end of each client session.

Security Services

Security services control user access to TSM data, storage, policydefinitions, and administrative commands.

Disaster Recovery Services

Disaster recovery services help the administrator implement acomprehensive backup and recovery procedure for importantbusiness applications, data, and records.

Understanding the TSM APIThe TSM API enables an application client to use TSM functions.The TSM API includes function calls to perform the followingoperations:

Start or end a session.

Assign management classes to objects before storing them on aserver.


1.Introduction

Back up or archive objects to a server.

Restore or retrieve objects from a server.

Query the server for information about objects that are storedthere.

Manage filespaces.

For information about installing the TSM API, seeTSM Using theApplication Program InterfaceandTSM Installing the Clients.

Understanding TDP for OracleTDP for Oracle supports Oracle8 databases with the RMAN utility.Oracle8 RMAN backs up and restores Oracle databases in bothonline and offline settings. While Oracle8 RMAN initiates a backupor restore, TDP for Oracle acts as the interface to the TSM server.The TSM server then applies administrator-defined storagemanagement policies to the data.

TDP for Oracle operates with any Version 3 TSM server. TDP forOracle translates Oracle8 API commands into TSM API calls to theTSM server.


Installing TDP for Symmetrix

AttentionFor current information concerning installation of TDP forSymmetrix, refer to theREADME file shipped on the productinstallation media.

This section provides detailed instructions on installing andconfiguring TDP for Symmetrix. Installation of TDP for Symmetrixconsists of the following procedures:

¶ Installing TDP for Symmetrix

¶ Editing the options files

¶ Defining environment variables

¶ Editing the TSM server script file

¶ Creating a backup script

¶ Establishing BCVs

¶ Editing the setup file

¶ Registering your workstations with the TSM Server

2


2.Installing

TD

Pfor

Sym

metrix

Installation RequirementsThe following installation requirements must be met for TDP forSymmetrix to install successfully.

Hardware Requirements¶ 2 SPARCstations or compatible workstations (one for the

production side and one for the backup side)

¶ EMC Symmetrix storage subsystem with microcode level 5265(or higher)

¶ Disk space: 4 MB

¶ Memory: 96 MB

Software RequirementsThe following software must be installed and configured on both thebackup and production systems:

¶ TSM Backup-Archive Client and Serverv Client Version 3.7.2 (or higher)v Server Version 3.7.3 (or higher)

¶ TSM API Version 3.7.2 (or higher)v The TSM API is included in the Backup-Archive Client and

Server package.

¶ TDP for Oracle for Solaris Version 2.1.0.10

¶ Oracle Server Version 8.1.5 32-bit for Solaris

¶ EMC TimeFinder licensed interface

¶ Solaris 7

TDP for Symmetrix supports UNIX File System (UFS) and VeritasFile System 3.3.2 (VxFS).


Environment RequirementsTDP for Symmetrix requires specific configurations to exist prior toinstallation. The following environment requirements must be metbefore installing TDP for Symmetrix:¶ Both SPARCstations (or compatible workstations) are connected

to the EMC storage subsystem.¶ The EMC storage subsystem is configured so that the following

two conditions are met:

v EMC standard devices on the production database areaccessible to the production machine.

v The BCV devices targeted by the production database mustbe accessible to the backup machine.

¶ Oracle Server is installed on the production machine and backupmachine.

¶ The Oracle datafiles to be backed up reside completely on theEMC subsystem and are visible to the production machine. TheOracle databases can be located in raw logical volume or any ofthe following file systems:v UNIX file system (UFS)v Veritas File System 3.3.2 (VxFS)

Installation ProcedureThe following software must be installed on both the backupmachine and production machine prior to installation of TDP forSymmetrix:¶ TSM Backup-Archive Client and Server¶ TSM API¶ TDP for Oracle for Solaris

For information regarding installation procedures for these softwareapplications, seeTSM for UNIX Using the Backup-Archive Clients,TDP for Oracle for UNIX Installation and User’s Guide, TSMInstalling the Clients, andTSM Using the Application ProgramInterface.


2.Installing

TD

Pfor

Sym

metrix

InstallingImportant! TDP for Symmetrix must be installed on both the backupmachine and production machine.

Perform these instructions to install TDP for Symmetrix. Thisexample assumes that your CD-ROM drive is/cdrom.

1. Insert the CD-ROM containing the client package into theCD-ROM drive.

2. Log in as the root user.

3. Issue this command to install TDP for Symmetrix and the TDPfor Symmetrix license:$ pkgadd -d /cdrom/tdpemc/tsmcli/sol/tdpemc.sol32.pkg

TDP for Symmetrix is installed in the/opt/tivoli/tsm/client/tdpemc/oracle directory. This directory alsocontains:

¶ TSM server script

¶ Sample RMAN script

¶ Sample user setup file

¶ README file

The TDP for Symmetrix executable applications (emcorcb,emcorcp) are located in the/opt/tivoli/tsm/client/tdpemc/oracle/bindirectory.

Editing the Options FilesBy default, TDP for Symmetrix requires two separate user optionfiles (dsm.opt) and two separate system option files (dsm.sys) to beset up on both the production machine and backup machine. TDP forOracle uses, by default, thedsm.opt anddsm.sysfiles located in theTSM API directory:/opt/tivoli/tsm/client/api/bin . TDP forSymmetrix uses thedsm.opt anddsm.sysfiles located in the TSMbackup-archive client directory:/opt/tivoli/tsm/client/ba/bin . Allsystem option files must refer to the same server. See “TDP for


Symmetrix Environment Variables” on page 12 for information onhow to change these default locations.

The TDP for Oracle option file requires PASSWORDACCESS set toPROMPT. The TDP for Symmetrix option file requiresPASSWORDACCESS set to GENERATE and SCHEDMODE set toPROMPT.

SeeTSM for UNIX Using the Backup-Archive ClientsandTDP forOracle for UNIX Installation and User’s Guidefor more informationabout option file configuration.

Option File ExamplesThe following examples illustrate how system option files refer tothe same server. In these examples, the option files in the/opt/tivoli/tsm/client/ba/bin and /opt/tivoli/tsm/client/api/bindirectory are defined for a server with a TCP address ofarrow.sanjose.ibm.com.

ba/bin DirectoryExample: dsm.optservername arrow

Example: dsm.sysservername arrow

commmethod tcpiptcpport 1500tcpserveraddress arrow.sanjose.ibm.compasswordaccess generateschedmode prompted

api/bin DirectoryExample: dsm.optservername arrow2

Example: dsm.sysservername arrow2

commmethod tcpiptcpport 1500tcpserveraddress arrow.sanjose.ibm.com


2.Installing

TD

Pfor

Sym

metrix

Note: The SERVERNAME option in thedsm.opt anddsm.sysfilesdefine server stanza names only. The TCPSERVERADDRESSoption controls which server is actually contacted.

Option File ConsiderationsAn alternative method of configuring option files is to combine theTDP for Symmetrix option files and TDP for Oracle option files intoonedsm.sysfile located in the/opt/tivoli/tsm/client/ba/bindirectory:

1. Cut and paste the option settings from the TDP for Oracledsm.sysfile to the TDP for Symmetrixdsm.sysfile. Below is anexample of a combineddsm.sysfor a server with the namearrow:servername arrow

commmethod tcpiptcpport 1500tcpserveraddress arrow.sanjose.ibm.compasswordaccess generateschedmode prompted

servername arrow2commmethod tcpiptcpport 1500tcpserveraddress arrow.sanjose.ibm.com

2. Create a link from the TDP for Oracledsm.sysfile to the TDPfor Symmetrixdsm.sysfile:ln -s /opt/tivoli/tsm/client/ba/bin/dsm.sys/opt/tivoli/tsm/client/api/bin/dsm.sys

TDP for Symmetrix Environment VariablesTDP for Symmetrix backup and production executable files areimplemented as TSM API applications and use the TSMbackup-archive client and TDP for Oracle. TDP for Symmetrix usesthe same environment variables as the TSM backup-archive client.TDP for Oracle uses its own environment variables.


Defining Environment VariablesTDP for Symmetrix environment variables are defined as follows:

DSM_DIRThe DSM_DIR variable points to the directory where thedsm.sysfile and executable applications reside for TDP forSymmetrix and the TSM backup-archive client.

DSM_CONFIGThe DSM_CONFIG variable points to the client user optionsfile for TDP for Symmetrix and the TSM backup-archiveclient.

DSM_LOGThe DSM_LOG variable points to the directory where thelog files reside for TDP for Symmetrix and the TSMbackup-archive client.

DSMI_DIRThe DSMI_DIR variable points to the TSM API installedpath and the directory where the TDP for Oracledsm.sysfile resides.

DSMI_CONFIGThe DSMI_CONFIG variable points to the TDP for Oracleuser options file.

DSMI_LOGThe DSMI_LOG variable points to the directory thatcontains the TDP for Oracle API error log file.


2.Installing

TD

Pfor

Sym

metrix

Environment Variable ConsiderationsThe following information must be considered when settingenvironment variables:

It is recommended that you do not change DSM_DIR orDSMI_DIR since the variables are used to locate the resourcefiles and thedsm.sysfiles.

You can change DSM_LOG and DSMI_LOG if you want yourlog files in a different directory. Set DSMI_LOG to the directorywhere you want your TDP for Oracle API log (dsierror.log) togo. Set DSM_LOG to the directory where you want to place thebackup-archive client error log (dsmerror.log) and tdpemc.log.

Environment Variable Default BehaviorIt is only necessary to set environment variables if you want tochange the default behavior of TDP for Symmetrix. When no TDPfor Symmetrix environment variables are set, the following behavioroccurs:

¶ The dsmerror.log file (the TSM backup-archive client error log)is placed in the current working directory.

v If TDP for Symmetrix is run using the central scheduler, thedsmerror.log file is placed in the directory the centralscheduler is started from.

¶ The tdpemc.log file (log for all other TDP for Symmetrix errorsand RMAN output) is placed in the/opt/tivoli/tsm/client/ba/bindirectory.

¶ TDP for Oracle uses thedsm.opt anddsm.sysfiles located inthe /opt/tivoli/tsm/client/api/bin directory.

¶ TDP for Symmetrix uses thedsm.opt anddsm.sysfiles locatedin the /opt/tivoli/tsm/client/ba/bin directory.

Note: Important! These environment variables must be used on boththe production and backup systems.

For more information about environment variables, seeTSM forUNIX Using the Backup-Archive Clients, TDP for Oracle for UNIX


Installation and User’s Guide, TSM Installing the Clients, andTSMUsing the Application Program Interface.

Editing the TSM Server Script FileA sample TSM server script file (serverscript.smp) is located in theTDP for Symmetrix default installation directory(/opt/tivoli/tsm/client/tdpemc/oracle).

TSM Server Script File ParametersDefine the TSM server script file parameters with the followingappropriate values:

$1 The TSM node name for the production host.

$2 The name of the setup file. This name must be a fullyqualified pathname.

$3 The TSM node name for the backup host.

$4 The name of the temporary file that TSM will create. Thisname must be a fully qualified pathname.

$5 The Symmetrix database file name. If this parameter is notdefined, the default pathname for the Symmetrix databasefile is used.

The $1, $2, $3, and$4 parameters are required. The$5 parameter isoptional.

Example TSM Server Script FileBelow is an example of the TSM server script file provided by TDPfor Symmetrix. The$1, $2, $3, $4, and$5 represent parameters youmust define before performing a backup or restore:define clientaction $1 wait=yes action=commandobject="emcorcp $2 $3 $4 [$5]"if (error) goto endif (rc_ok) goto nextnext:define clientaction $3 wait=yes action=commandobject="emcorcb $1 $4 [$5]"end:exit


2.Installing

TD

Pfor

Sym

metrix

See “Backup Procedure” on page 23 for information on how todefine this script to the server and run the backup using this script.

Creating a Backup ScriptTDP for Symmetrix performs database backups using an Oraclecommand script. The command script is invoked by the TDP forSymmetrix application. Create a backup script and edit the setup fileas described in the next section to give the full path name of thebackup script. The backup script must contain the following:

¶ run , backup keywords

¶ Allocate and release at least one channel

¶ A DSMI_ORC_CONFIG and DSMO_NODE value

Example Backup ScriptBelow is an example of a backup script:run{allocate channel t1 type 'sbt_tape' parms'ENV=(DSMI_ORC_CONFIG=/opt/tivoli/tsm/client/api/bin/dsm.opt,DSMO_NODE=dewey)';

allocate channel t2 type 'sbt_tape' parms'ENV=(DSMI_ORC_CONFIG=/opt/tivoli/tsm/client/api/bin/dsm.opt,DSMO_NODE=dewey)';



backup(database);

release channel t1;release channel t2;release channel t3;release channel t4;}

Note: The allocate channel t1 typethru allocate channel t4 typeOracle commands in the above backup script example are


divided to accommodate page formatting. The actualcommands in the backup script are on one line.

Establishing BCVsIn order for TDP for Symmetrix to perform a backup, an associationmust first be established between the standard devices on which theOracle database resides and the BCV devices to which the Oracledatabase is copied. An administrator must use the Symmetrix userinterface to accomplish this association.

If a database is always mirrored to the same BCVs, this step needsto be done once before backing up a database for the first time.

If multiple Oracle database mirrors are desired (i.e., databases copiedto different BCVs on different days), the administrator stores thesedifferent associations in different Symmetrix databases (see “BackupProcedure” on page 23 for more information). The name of theSymmetrix database is then supplied as a parameter to TDP forSymmetrix (see “TSM Server Script File Parameters” on page 15 formore information).

Editing the User Setup FileThe setup file is defined by the user with all necessary databaseinformation to successfully perform a backup or restore procedure. Adifferent setup file is needed for each database that is backed up.The setup file is used only on the production machine and can beplaced in any directory location with any given name.

Setup File ParametersThe following setup file parameters must be defined beforeperforming a backup or restore procedure. You must use the samesyntax as provided in the sample setup file.

Target Database ParametersThe Target Database parameters define the Oracle database to bebacked up.


2.Installing

TD

Pfor

Sym

metrix

target_database_homeThis variable specifies the Oracle home directory. The Oraclehome directory is defined in the Oracle environment variableORACLE_HOME.

target_database_sidThis value specifies the Oracle system identifier (SID) forthe target database. TDP for Symmetrix performs actions onthe database resolved by the Oracle file initSID.ora.

target_database_usernameThis value specifies a username that has system databaseadministrator privileges on the target database.

target_database_passwordThis value specifies the password of the username defined inthe target_database_usernameparameter.

target_database_password_fileThis value specifies the fully resolved path of the targetdatabase password file (orapwSID by default).

target_database_parameter_fileThis value specifies the fully resolved path of the targetdatabase parameter file initSID.ora.

Recovery Catalog ParametersThe Recovery Catalog parameters define the Oracle RecoveryCatalog.

catalog_database_connect_stringThis value specifies the connect string of the RecoveryCatalog database to be used to catalog backup information.This value must correspond to the value defined in the$ORACLE_HOME/network/admin/tnsnames.ora file.

catalog_database_usernameThis value specifies a username that has system databaseadministrator privileges on the Recovery Catalog database.

catalog_database_passwordThis value specifies the password of the username defined inthe catalog_database_usernameparameter.


Other Database ParametersThese Database parameters define the type of backup to beperformed.

database_backup_script_fileEnter the name of the file that contains the TDP for Oracleenvironment variables. This file must contain commands thatare valid for the backup host database (applicable on adatabase with datafile copies). Important! This file must havethe TDP for Oracle DSMI_ORC_CONFIG andDSMO_NODE environment variables defined. IfDSMI_ORC_CONFIG is not defined, thedsm.opt file in theAPI default directory is used. In addition, DSMO_NODEmust reflect the TSM node name of the production system.SeeTDP for Oracle for UNIX Installation and User’s Guidefor more information.

database_backup_msglog_fileEnter the name of the file that contains output from allRMAN commands. Since the contents of this file isoverwritten after every RMAN command, output from allRMAN commands is also written to thetdpemc.log file.

database_backup_typeEnter the type of database backup to be performed. Enterone of the following values:offline or online.

reestablish_bcvsThis parameter determines if the BCVs are to bere-established after the database is backed up. Enter one ofthe following values:yes, y, no, or n.


2.Installing

TD

Pfor

Sym

metrix

Example Setup FileBelow is an example of the setup file you must define beforeperforming a backup procedure:#================================================================#

#=== Setup for the target database which will be backed up ===#

target_database_home: /orc8/app/oracle/product/8itarget_database_sid: t2target_database_username: tdptesttarget_database_password: tdptesttarget_database_password_file: /orc8/app/oracle/product/8i/dbs/orapwt1target_database_parameter_file: /orc8/app/oracle/product/8i/admin/t2/pfile/initt2.ora

#=== Setup for the catalog database ===#

catalog_database_connect_string: rman.worldcatalog_database_username: rmancatalog_database_password: rman

database_backup_script_file: /home/william/bkdb.scr.ks2database_backup_msglog_file: /orc8/app/oracle/product/8i/admin/rmanlog1database_backup_type: onlinereestablish_bcvs: n

Note: The target_database_parameter_filevariable in the abovesetup file example is divided to accommodate pageformatting. The actual variable in the setup file is on one line.

Specifying the TSM Management ClassWhen you back up a database, the default management class foryour node is used. You can override the default value by specifyinga different value in the Include option. This option is placed in theInclude-Exclude options file. The file name of theInclude-Excludeoptions file is placed in the client system’s option file. SeeTSMInstalling the Clients, for more information.

For example, to assign a management class nameorcbackup to allof the Oracle backups with a default file space name oftsmorc,perform the following steps:


1. Add this entry under the server stanza you use in thedsm.sysfile where the TSM API is installed:

inclexcl /u01/oracle/include.def2. Add this entry in/u01/oracle/include.def:

include /tsmorc/.../* orcbackup

All the files backed up with a default file space name oftsmorc areassigned to management classorcbackup.

If you do not want to use theinclexcl option, you can create a newdomain just for Oracle backups. You must then register your nodewith the new domain.

Rather than binding a different management class for Oraclebackups, it is recommended that you specify a different domain forOracle backups with a separate management class. Within thisseparate management class, define the backup copy group parametersasVERDELETED=0 andRETONLY=0

Registering Your Workstations with the TSM ServerTDP for Symmetrix requires both the backup workstation andproduction workstation to be registered as TSM clients. TSM uses anode name and a password (if one is required) to identify eachworkstation. TSM maintains a password for each node name.

Perform the following steps to register each workstation:

1. Register the client node with the TSM server.

If a TSM client already exists on the workstation, it isrecommended that a separate and unique node name for TDP forSymmetrix be used on the same workstation.

2. Define the policy domain for the client node.

It is recommended a unique policy domain be defined for TDPfor Symmetrix node names. Rather than binding a differentmanagement class for TDP for Symmetrix backups, it is alsorecommended a different domain for TDP for Symmetrixbackups with a separate management class be specified. Within


2.Installing

TD

Pfor

Sym

metrix

this separate management class, define the backup copy groupparameters asVERDELETED=0 andRETONLY=0 .

3. Increase the value of theidletimeoutoption on the TSM server to600 seconds.

This prevents a time-out from occurring during large databaseback ups.

SeeTSM Administrator’s GuideandTSM Administrator’s Referencefor more information about registering workstations to the TSMserver.


Backup Procedure

TDP for Symmetrix utilizes TDP for Oracle to interface with RMANto catalog and create database backups. A successful TDP forSymmetrix backup creates backup copies of each datafile that resideon the TSM server.

Performing a BackupThe TDP for Symmetrix production executable application backs upthe Oracle parameter file, Oracle backup script, and temp file to theTSM server and performs a″set access″ for the backup host to beable to restore them. TDP for Symmetrix does not remove thisaccess after the backup executable application has restored thesefiles.

Backup Method One1. Create a script file on the server machine using the sample script

file provided by TDP for Symmetrix.

This sample script file (serverscript.smp) is located in theTDP for Symmetrix default installation directory(/opt/tivoli/tsm/client/tdpemc/oracle).

$> cp <TSM sample script name> dbbackup$> vi dbbackup

You must edit the script file when values have changed. Forexample, if theemcorcp andemcorcb executableapplications are renamed, you must update the script file withthe appropriate values. Also, if the PATH environment

3


3.B

ackupP

rocedure

variable was exported without including the directorycontaining the appropriate executable application(s), theabsolute path must be specified. See “Editing the TSM ServerScript File” on page 15 for more information.

2. Define a TSM server script on the server for the script filecreated in Step 1.

Use the DEFINE SCRIPT command on the TSMadministrative client. SeeTSM Administrator’s GuideandTSM Administrator’s Referencefor more information aboutthe DEFINE SCRIPT command.

SERVER>define script dbbackup file=/opt/tivoli/tsm/server/bin/dbbackup

Note: The DEFINE SCRIPT command in the above example isdivided to accommodate page formatting. The actualcommand string is on one line.

3. Start the client scheduler on the production system and backupsystem by running the following command on both systems:# dsmc schedule

4. Run the server script defined in Step 2 with the necessaryarguments:

Use the RUN command on the TSM administrative client.

The input arguments provided during the RUN command mustcorrespond to the order of input arguments defined in the script:SERVER>run dbbackup <production host node name> <setup filename><backup host nodename> <temp filename> [<Symmetrix databasefilename, if required>]


Backup Method Two1. Log on to the production system:

# tn <production host name>

2. Run theemcorcp.exeapplication provided for the productionsystem with the necessary arguments:# <pathname to production application>/emcorcp <setup filename><backup host nodename> <temp filename> [<Symmetrix databasefilename,if required>]

3. If the application ran successfully to completion, log on to thebackup system:# tn <backup host name>

4. Run theemcorcb.exeapplication provided for the backup systemwith the necessary arguments:# <pathname to backup application>/emcorcb <production host nodename><temp filename> [<Symmetrix database filename, if required>]

Backup Method ThreeDefine an administrative schedule on the server to run the serverscript file. See “Using the TSM Central Scheduler” on page 31for information on how to perform this procedure.

Backup Strategy RequirementsThe following backup strategy requirements must be met in order forTDP for Symmetrix to function properly:

¶ The backup script file provided by the user must have at leastthe DSMI_ORC_CONFIG and DSMO_NODE environmentvariables defined. If the DSMI_ORC_CONFIG variable is notdefined, TDP for Symmetrix uses thedsm.opt file located in thedefault directory of the API.

¶ You must use the same syntax as provided in the sample setupfile.

¶ A delay of four to five minutes might occur between the start ofthe server schedule and the start of the schedule on the client.


3.B

ackupP

rocedure

¶ The Oracle parameter file must haveREMOTE_LOGIN_PASSWORDFILE set to EXCLUSIVE, sincethe TDP for Symmetrix application runs as root user. TheNO_ORACLE_PASSWORD_FILE error message is returned ifREMOTE_LOGIN_PASSWORDFILE is set to EXCLUSIVEandv a value fortarget_database_parameter_fileis not defined in

the setup filev the password file is not available in the default path.

¶ The production system and backup system need the TSM clientscheduler to be active in server prompted mode.

¶ The standard device that the database resides on must beassociated with BCV devices on the EMC storage subsystem.

¶ Oracle Server must be available on the production system andbackup system. The Oracle database to be backed up is createdon the production system only.

¶ The EMC storage subsystem must be configured so that theproper Logical Unit Numbers (LUN) are available on bothmachines.

¶ If two databases are backed up (especially at the same time),you must use different setup file names and temp file names.


Restore Procedure

Performing a RestoreTDP for Symmetrix backups are restored as an entire database(Restore Method One) or with a datafile granularity (Restore MethodTwo). RMAN must be used to perform restore procedures.

Restore Method One (Entire Database)Perform the following steps to restore an entire database backup:

1. Shut down the database (if necessary):shutdown;

2. Mount the database:startup mount;

3. Start RMAN and connect to the target database and the recoverycatalog:rman target username/password rcvcat username/password@connect_string

4. Perform an RMAN RUN command by specifying the allocationof channels and the restoration of the database:run {allocate channel ch1 type 'sbt_tape';allocate channel ch2 type 'sbt_tape';restore database;}

5. Recover the database (as needed) by connecting to the targetdatabase:recover database;

4


4.R

estoreP

rocedure

Restore Method Two (Datafile Only)Perform the following steps to restore a datafile only:

1. Shut down the database (if necessary):shutdown;

2. Mount the database:startup mount;

3. Start RMAN and connect to the target database and the recoverycatalog:rman target username/password rcvcat username/password@connect_string

Note: The RMAN command in the above example is divided toaccommodate page formatting. The actual RMANcommand string is on one line.

4. Perform an RMAN RUN command by specifying the allocationof channels and the restoration of the datafilen, wheren is thenumber of the datafile:run {allocate channel ch1 type 'sbt_tape';allocate channel ch2 type 'sbt_tape';restore datafile n;}

5. Bring the datafile online with the following SQL command,wheren is the number of the datafile:alter database datafile n online;

6. Recover the datafile as needed by connecting to the targetdatabase and issuing:recover datafile n;


Restore Strategy RequirementsThe most important issue for restore is the restore data path. Fromthe TSM server, the data can be sent to the following locations:

¶ A TSM client on the production system.

v The data can be sent over a local area network (LAN). Thisis the standard TSM restore.

v Data can be sent directly to the disk subsystem sourcevolumes.

¶ A TSM client on the backup system.

v Data can be sent to the disk subsystem target (or BCV)volumes, then copied to the source volumes.

v If the TSM server is located on the TDP backup machine, therestore can be done through shared memory.


4.R

estoreP

rocedure

Using the TSM Central Scheduler

This section describes how to use the TSM central scheduler servicewith TDP for Symmetrix to automate online backups of Oracledatabases.

To ensure this example works, it is recommended the latest TSMbackup–archive client be installed. The TSM backup-archive clientmust reside on the same machine as TDP for Symmetrix to use thecentral scheduler service. The latest TSM client PTFs (service packs)are available from the following URL:http://www.tivoli.com/tsm

After TDP for Symmetrix has been registered to a TSM server andinstalled on the production and backup systems, perform these steps:

1. On the production system where TDP for Symmetrix is installed:

a. Create a backup script for Oracle.

See thebkdb.scr example in the next section under Step1a.

b. Create a setup file with all the information required by TDPfor Symmetrix.

See thebkdbsetup example in the next section underStep 1b.

c. Start the scheduler.

5


5.U

singthe

TS

MC

entralS

cheduler

2. On the backup system where TDP for Symmetrix is installed:

Start the scheduler.

3. On the TSM server:

a. Create a script file on the server machine using the samplescript file (serverscript.smp) provided by TDP forSymmetrix. Theserverscript.smp file is located in the TDPfor Symmetrix default installation directory(/opt/tivoli/tsm/client/tdpemc/oracle).

See thedbbackup.txt example in the next section underStep 3a.

b. Define a TSM server script on the server for the script filecreated in Step 3a.

See thedbbackup example in the next section under Step3b.

c. Define an administrative command schedule (daily_orcbkup)on the server that will run the server script defined in Step3b.

See the DEFINE SCHEDULE command example in thenext section under Step 3b.


Example of Central Scheduler Service to AutomateBackups

This example assumes:

¶ TDP for Symmetrix on the production system is registered to aTSM server with a node name ofNodePSand a password ofPasswordPS.

¶ TDP for Symmetrix on the backup system is registered to aTSM server with a node name ofNodeBSand a password ofPasswordBS.

¶ The event to be scheduled is a daily backup of the onlinedatabase. The backups are to begin between 9:00 and 9:15 pm.

¶ The /tmp/dbbktemp file is generated by TDP to writetemporary information.

¶ The default Symmetrix database is used.

1. On the production system where TDP for Symmetrix is installed:

a. Create the database backup script (bkdb.scr) in the/home/william directory as shown:run{allocate channel t1 type 'sbt_tape' parms'ENV=(DSMI_ORC_CONFIG=/opt/tivoli/tsm/client/api/bin/dsm.opt,DSMO_NODE=NodePS)';allocate channel t2 type 'sbt_tape' parms'ENV=(DSMI_ORC_CONFIG=/opt/tivoli/tsm/client/api/bin/dsm.opt,DSMO_NODE=NodePS)';allocate channel t3 type 'sbt_tape' parms'ENV=(DSMI_ORC_CONFIG=/opt/tivoli/tsm/client/api/bin/dsm.opt,DSMO_NODE=NodePS)';allocate channel t4 type 'sbt_tape' parms'ENV=(DSMI_ORC_CONFIG=/opt/tivoli/tsm/client/api/bin/dsm.opt,DSMO_NODE=NodePS)';backup(database);release channel t1;release channel t2;release channel t3;release channel t4;}


5.U

singthe

TS

MC

entralS

cheduler

b. Create the setup file (bkdbsetup) in the /home/williamdirectory as shown:#============================================================#

#=== Setup for the target database which will be backed up =#

target_database_home: /orc8/app/oracle/product/8itarget_database_sid: t2target_database_username: tdptesttarget_database_password: tdptesttarget_database_password_file: /orc8/app/oracle/product/8i/dbs/orapwt1

target_database_parameter_file: /orc8/app/oracle/product/8i/admin/t2/pfile/initt2.ora

#=== Setup for the catalog database ===#

catalog_database_connect_string: rman.worldcatalog_database_username: rmancatalog_database_password: rman

database_backup_script_file: /home/william/bkdb.scr.ks2database_backup_msglog_file: /orc8/app/oracle/product/8i/admin/rmanlog1

database_backup_type: onlinereestablish_bcvs: n

Note: The target_database_password_file,target_database_parameter_file, anddatabase_backup_msglog_filevariables in the abovebkdbsetup file example are divided to accommodatepage formatting. The actual variables in thebkdbsetup file are on one line.

c. Start the scheduler, login as the root user, and issue thefollowing command:dsmc sched

Only the root user can restore backups performed by thescheduler.

2. On the backup system where TDP for Symmetrix is installed:

Start the scheduler, login as the root user, and issue thefollowing command:dsmc sched


Only the root user can restore backups performed by thescheduler.

3. On the TSM server:

a. Create thedbbackup.txt script file in the/opt/tivoli/tsm/server/bin directory on the server machineusing the sample script (serverscript.smp) provided by TDPfor Symmetrix.define clientaction $1 wait=yes action=commandobject="emcorcp $2 $3 $4 [$5]"if (error) goto endif (rc_ok) goto nextnext:define clientaction $3 wait=yes action=commandobject="emcorcb $1 $4 [$5]"end:exit

You must edit thedbbackup.txt script file when values havechanged. For example, if theemcorcp andemcorcbexecutable applications are renamed, you must update thescript file with the appropriate values. Also, if the PATHenvironment variable was exported without including thedirectory containing the appropriate executable application(s),the absolute path must be specified. See “Editing the TSMServer Script File” on page 15 for more information.

b. Define the TSM server script file (dbbackup) on the serverfor the script file created in Step 3a:SERVER>define script dbbackup file=/opt/tivoli/tsm/server/bin/dbbackup.txt

c. Enter the following command from an administrative client todefine the administrative schedule (daily_orcbkup) on theserver that will run the server script (dbbackup) defined inStep 3b:define schedule daily_orcbkup type=administrativedesc="Daily Online DB Backup"cmd="run dbbackup NodePS /home/william/bkdbsetupNodeBS /tmp/dbbktemp starttime=9:00duration=15 duru=minutes period=1 perunits=daydayofweek=any


5.U

singthe

TS

MC

entralS

cheduler

TSM displays this message:ANR2577I Schedule daily_orcbkup defined.

Note: The administrative client does not have to be runningon the same system as the TSM server.

A backup event (schedule) has now been defined on the TSM server.The schedule runs the TSM server scriptdbbackup. The backupstarts around 9:00 pm., is performed once a day, and can start onany day of the week.

This procedure is flexible because you can define a command filewith any set of commands you choose. This allows you to use thesame command file to define schedules on other TSM servers.

You can use the following TSM administrative commands to observescheduler behavior:

The query schedulecommand confirms that the schedule is setcorrectly.

The query event command checks the time a schedule isprojected to run and whether a schedule ran successfully.

You must specify the″type=administrative″ parameter with both ofthese commands since this is an administrative schedule. SeeTSMfor Sun Solaris Administrator’s Referencefor more information onthese commands.


Glossary

The terms in this glossary are defined as they pertain to the TSMlibrary. If you do not find a term you are looking for, you can referto the IBM Dictionary of Computingat URL:http://www.ibm.com/networking/nsg/nsgmain.htm

This glossary may include terms and definitions from:

¶ The American National Standard Dictionary for InformationSystems, ANSI X3.172-1990, copyright (ANSI). Copies can bepurchased from the American National Standards Institute, 11West 42nd Street, New York, New York 10036.

¶ The Information Technology Vocabulary, developed bySubcommittee 1, Joint Technical Committee 1, of theInternational Organization for Standardization and theInternational Electrotechnical Commission (ISO/IEC JTC2/SC1).

A

administrative clientA program that runs on a file server, workstation, or mainframe. This program letsadministrators monitor and control TSM servers using TSM administratorcommands. Contrast withbackup-archive client.

administratorA user who is registered to the server as an administrator. Administrators can beassigned one or more privilege classes. Administrators can use the administrativeclient to enter TSM server commands and queries according to their privileges.

B

backupA function permitting users to copy one or more files to a storage pool to protectagainst data loss. Contrast withrestore.

backup-archive clientA program that runs on a file server, PC, or workstation and provides a means forTSM users to back up, archive, restore, and retrieve files. Contrast withadministrative client.


Glossary

backup sideThe secondary server environment that performs backup procedures with TDP forOracle.

Business Continuance Volume (BCV)A mirrored copy of data derived from an online Symmetrix device.

C

central schedulingA function permitting an administrator to schedule backup and archive operationsfrom a central location. The operations can be scheduled on a periodic basis or onan explicit date.

clientA program running on a file server, PC, workstation, or terminal that requestsservices of another program called the server. There are two types of TSM clients:administrative and backup-archive. Seeadministrative clientandbackup-archiveclient.

client-serverA communications network architecture in which one or more programs (clients)request computing or data services from another program (the server).

H

hostA computer that is connected to a network and provides an access point to thatnetwork. The host can be a client, a server, or both a client and a serversimultaneously.

I

input/output (I/O)A device, process, or channel involved in data input, data output, or both.

L

local area network (LAN)A variable-sized communications network placed in one location. LAN connectsservers, PCs, workstations, a network operating system, access methods, andcommunications software and links.

logical unit number (LUN)A volume identifier number for a storage subsystem logical disk drive.


M

mirroringThe maintenance of more than one copy of stored data to prevent the loss of data.

N

node nameA unique name used to identify a workstation, file server, or PC to the server.

O

options fileA file that contains processing options.

P

production sideThe active production environment of the TSM server that remains online duringTDP for Symmetrix backup processing.

R

raw logical volumeA portion of a physical volume which is comprised of unallocated blocks and hasno Journaled File System (JFS) definition. A raw logical volume is read/writeaccessible only through low level I/O functions.

registrationThe process of identifying a client node or administrator to the server by specifyinga user ID, password, and contact information. For client nodes, a policy domain,compression status, and deletion privileges are also specified.

restoreA function that permits users to copy a version of a backup file from the storagepool to a workstation or file server. The backup copy in the storage pool is notaffected. Contrast withbackup.

S

serverA program running on a mainframe, workstation, or file server that provides sharedservices such as backup and archive to other various (often remote) programs(called clients).


Glossary

SYMAPI (Symmetrix Application Programming Interface)An application programming interface used to invoke operations on Symmetrixstorage subsystems.

SYMCLI (Symmetrix Command Line Interface)An open systems application that provides a set of commands to the host operatingsystem which can obtain data on attached Symmetrix storage subsystems.

T

TimeFinderEMC storage management software which uses Business Continuance Volumes (thatcontain copies of Symmetrix devices) while the standard devices are online forregular host operations.

Tivoli Data Protection (TDP)A storage management software application that performs backup and recoveryfunctions across a wide variety of client and server platforms.

Tivoli Storage Manager (TSM)A client/server program that provides storage management to customers in amultivendor computer environment.

U

UNIX File System (UFS)A type of file system organized as a hierarchy of directories beginning at a singleroot directory.

V

Veritas File System (VxFS)A high performance file system that provides transaction based journaling, fastrecovery, and online administrative operations.

W

workstationA programmable high-level workstation (usually on a network) with its ownprocessing hardware such as a high-performance personal computer. In a local areanetwork, a personal computer that acts as a single user or client. A workstation canalso be used as a server.


Index

Bbackup procedure 23

automating 31example 33

Backup Method One 23Backup Method Three 25Backup Method Two 25strategy requirements 25

backup scriptcentral scheduler

example 33creating 16example 16

BCVs 25, 29description 2establishing 17

Ccentral scheduler 31, 33considerations

environment variables 14option files 12

Ddsierror.log 14DSM_CONFIG

defining 13DSM_DIR

defining 13DSM_LOG

defining 13dsm.opt 14, 25

considerations 12

dsm.opt 14, 25 (continued)example 11

dsm.sys 14, 20considerations 12example 11

dsmerror.log 14DSMI_CONFIG

defining 13DSMI_DIR

defining 13DSMI_LOG

defining 13

Eenvironment

installation requirements 9environment variables 12

considerations 14default behavior 14defining 13DSM_CONFIG 13DSM_DIR 13DSM_LOG 13DSMI_CONFIG 13DSMI_DIR 13DSMI_LOG 13

examplesassign a management class 20backup script 16central scheduler 33

backup script 33server script 35setup file 34

option filesdsm.opt 11dsm.sys 11


Index

examples(continued)setup file 20TSM server script file 15

Hhardware

installation requirements 8

IInclude-Exclude 20installation requirements 8

environment 9hardware 8software 8

installing 10

LLAN 29

Mmanagement class

specifying 20

Ooption files

considerations 12dsm.opt 25dsm.sys 20editing 10

option files (continued)example

dsm.opt 11dsm.sys 11

OracleRMAN 2

Pparameters

setup file 17catalog_database_connect_string 18catalog_database_password 18catalog_database_username 18database_backup_msglog_file 19database_backup_script_file 19database_backup_type 19database parameters 19recovery catalog 18reestablish_bcvs 19target database 17target_database_home 18target_database_parameter_file 18, 26target_database_password 18target_database_password_file 18target_database_sid 18target_database_username 18

TSM server script file 15

Rregistration

workstation 21restore procedure 27

Restore Method One (Entire Database) 27Restore Method Two (Datafile Only) 28strategy requirements 29

RMAN 2and TDP for Oracle 6


Sserver script

central schedulerexample 35

setup filecentral scheduler

example 34database parameters 19editing 17example 20parameters 17

catalog_database_connect_string 18catalog_database_password 18catalog_database_username 18database_backup_msglog_file 19database_backup_script_file 19database_backup_type 19reestablish_bcvs 19target_database_home 18target_database_parameter_file 18target_database_password 18target_database_password_file 18target_database_sid 18target_database_username 18

recovery catalog parameters 18target database parameters 17

softwareinstallation requirements 8

TTDP for Oracle

and RMAN 6understanding 6

TDP for Symmetrixbackup procedure 23

Backup Method One 23Backup Method Three 25Backup Method Two 25strategy requirements 25

backup scriptcreating 16example 16

TDP for Symmetrix (continued)central scheduler

backup script 33server script 35setup file 34

environment variables 12considerations 14default behavior 14defining 13

functions 2, 3installation requirements 8

environment 9hardware 8software 8

installing 10operating environment 1option files 11

considerations 12editing 10examples 11

restore procedure 27Restore Method One (Entire

Database) 27Restore Method Two (Datafile Only) 28strategy requirements 29

setup filedatabase parameters 19editing 17example 20parameters 17recovery catalog parameters 18target database parameters 17

TSM server script file 15example 15parameters 15

understanding 1tdpemc.log 14TimeFinder 2TSM

APIunderstanding 5

backup-archive clientunderstanding 3

central scheduler 31example 33


Index

TSM (continued)management class

example 20specifying 20

server script file 15example 15parameters 15

workstation registration 21TSM server script file 15

example 15parameters 15


Program Number: 5698–EMO

Printed in the United States of Americaon recycled paper containing 10%recovered post-consumer fiber.

SH26-4114-00

Spine information:

Tivoli Data Protection for EMC Symmetrix for OracleDatabases Installation and User’s Guide,Version 1 Release 1

tivoli data protection for emc symmetrix for oracle...

Documents