best practices for oracle asm on xiv with tivoli flashcopy manager

Best Practices Guide for Oracle Databases with IBM XIV Storage System Snapshots XIV Snapshots for Backup/Restore using Tivoli Storage FlashCopy Manager

This document can be found in the IBM Techdocs library

Version 1.7 (2010-02-15) Hans-Guenther Hoerhammer ([email protected]) Markus Oscheka ([email protected]) IBM Systems and Technology Group (STG) IBM System Storage - Advanced Technical Support (ATS) European Storage Competence Center (ESCC), Mainz, Germany

A Best Practices Paper

Best Practices Guide for Oracle Applications with IBM XIV Storage System Snapshots

of 51 © COPYRIGHT IBM CORPORATION, 2010 Version: 1.7 (2010-02-15)

Abstract In today's IT world, where application servers are operational 24 hours a day, the data on these servers must be fully protected. With the rapid increase in the amount of data on these servers, their critical business needs, and the shrinking backup windows, traditional backup and restore methods may be reaching their limits in meeting these challenging requirements. Point-in-time copy operations can help minimize the impact caused by backups and provide near instant restore capabilities. Since a point-in-time copy operation typically takes much less time than the time for a tape backup, the window during which the data is being backed up can be reduced. This helps facilitate more frequent backups and increase the flexibility of backup scheduling and administration because the time spent for forward recovery through transaction logs after a restore is minimized. IBM/Tivoli offers a range of products for backup and restore of databases. Products that leverage storage system features like Snapshot help to reduce the backup window and to speed up the restore process.

The IBM XIV Storage System provides a volume level point-in-time copy function known as snapshot to help minimize the impact caused by backups and provide near instant restore capabilities These array-based snap-shot technologies provide copies of data that can be used to backup the database without impacting the production environment.

IBM Tivoli Storage FlashCopy Manager can help deliver the highest levels of protection for mission critical Oracle databases via integrated application-aware snapshot backup and restore capabilities. This is achieved through the exploitation of advanced IBM XIV Storage System snapshot technology to create a high performance, low impact application data protection solution. This paper covers the integrated solution of FlashCopy Manager for backup and restore of Oracle Databases in the XIV Storage System. It describes the installation and configuration of Tivoli Storage FlashCopy Manager for backup and restore of Oracle databases using XIV Storage System snapshots mechanism.



Table of Contents 1 Introduction........................................................................................................................... 4 2 Configuration and Setup ....................................................................................................... 5

2.1 Hardware Topology....................................................................................................... 5 2.2 Oracle Database servers .............................................................................................. 5 2.3 Configuration by example ............................................................................................. 5

2.3.1 Configuring the Oracle servers ............................................................................. 6 3 Installation and Configuration of FlashCopy Manager........................................................... 8

3.1 Tivoli Storage FCM Architecture ................................................................................... 8 3.2 FCM Pre-Installation Tasks........................................................................................... 9 3.3 TSM Client and Server................................................................................................ 10 3.4 FCM Installation.......................................................................................................... 10 3.5 FCM Configuration for disk-only backup ..................................................................... 10 3.6 Switching from disk-only to offloaded backup ............................................................. 12

4 Leveraging XIV Snapshots for Backup/Restore of Oracle databases with FCM ................. 14 4.1 Disk-only backup ........................................................................................................ 15 4.2 Offload to Tivoli Storage Manager .............................................................................. 16 4.3 Restore from snapshot................................................................................................ 17 4.4 Restore from TSM server............................................................................................ 17

5 Summary ............................................................................................................................ 19 References ............................................................................................................................ 20 Appendix A – XIV Storage configuration and Oracle Software installation............................. 21

Oracle Database servers .................................................................................................. 21 Storage hardware ............................................................................................................. 21 Configuration by example ................................................................................................. 21

Configuring the Oracle servers .................................................................................... 29 Appendix B – Commands and Output.................................................................................... 33 Trademarks and special notices ............................................................................................ 51



1 Introduction The IBM® XIV® Storage System is a revolutionary, easily manageable, enterprise class open disk system, designed to meet today’s ongoing IT challenges. Its design — a grid of standard Intel®/Linux® components are connected in a any-to-any topology using Gigabit Ethernet — represents the next generation of high-end SAN (Storage Area Networks) systems. This best practices paper focuses on benefits and business value of Backup and Recovery process for Oracle environments with XIV Storage System and Tivoli® Storage FlashCopy® Manager. It describes how to use Tivoli Storage FlashCopy Manager to backup and restore Oracle ASM applications taking advantage of XIV snapshot technology.

The key features covered in this paper for deploying IBM XIV Storage Systems are:

• XIV Snapshots - XIV snapshots produce very little performance impact based on a redirect-on-write concept. The snapshot capabilities within the XIV Storage System utilize a metadata, redirect-on-write design that allows snapshots to occur in the millisecond time range with little performance overhead. Up to 16,000 full or differential copies can be taken. Any of the snapshots can be made writable, and then snapshots can be taken of the newly writable snapshots. These snapshots can also be used for restore.

• XIV Consistency Groups - A XIV Consistency Group is a group of volumes of which a snapshot can be made at the same point in time, thus helping to ensure a consistent image of all volumes within the group at that time.

IBM Tivoli Storage FlashCopy Manager (FCM) uses the copy services capabilities of intelligent storage subsystems to create point-in-time copies. These are application-aware copies (FlashCopy or snapshot) of the production data. These copies are then retained on disk as backup allowing for a fast restore operation (Flashback). IBM Tivoli Storage FlashCopy Manager also allows mounting the copy on an auxiliary server (backup server) as a logical copy. This copy (instead of the original data on the production server) is made accessible for further processing including disk to tape backup by Tivoli Storage Manager. FCM highlights include:

- No load on production server by the backup process - Short database backup window - Supports disk and/or tape media - Balancing of tape workload - Snapshot/Flash Restore - Consistent process and user interface for tape/disk restore

When a tape backup is required, for long term archival for example, Tivoli Storage Manager (TSM), IBM/Tivoli’s central backup/restore facility should be used. TSM includes very powerful storage management functionality: all data are stored in storage pools, according to policies. Storage pools can be any type of disk, optical, or tape storage.

INTENDED AUDIENCE The intended audience of this paper is any Technical Lead, System Administrator, Storage Administrator, or Oracle DBA in a production environment that wants some guidance on the best practices for performing backups and restores of Oracle Database with IBM Tivoli FlashCopy Manager and IBM XIV Storage System.



2 Configuration and Setup The following section provides a rough overview of the topology, configuration, and software levels used for the test of the solution.

2.1 Hardware Topology Figure 1 depicts a generic hardware topology for the example in this white paper. The number of required FC ports per server depends on the workload of the application / database. For redundancy reasons, a minimum of 2 FC ports is recommended.

Figure 1 Hardware Topology

2.2 Oracle Database servers Two logical partitions (LPARs) on an IBM System p590 are configured as the Oracle database servers. One LPAR is used as the production database server and second as the backup/offload server. A detailed description of the lab setup is provided in the appendix.

2.3 Configuration by example This section provides an overview of the configuration scenario.

The easy-to-use graphical user interface is used for setting up XIV storage for the Oracle database.

XIV storage configuration by GUI For the Oracle production database setup, five volumes are created on the XIV storage system:



• One for the Oracle software (binaries)

• Four for the Oracle database

In order to meet the prerequisites of the FlashCopy Manager, the database control files and the logfiles are stored in a separate ASM disk group. Another ASM disk group is used for the Flash Recovery Area.

For the backup server, seven volumes are created on the XIV Storage System and three of them for Oracle:


• Two for the Oracle database

• The remaining LUNs contain the TSM software FlashCopy Manager installation and Oracle downloads etc.

In order to meet the prerequisites of the FlashCopy Manager, the backup server must have an ASM disk group for the logs with the same name as the disk group for the logs on the production server.

For storage pool setup and basic Oracle software installation, please refer to Appendix A – XIV Storage configuration and Oracle Software installation.

2.3.1 Configuring the Oracle servers Production server configuration

Set-up your production database using three disk groups according to FCM prerequisites:

• ORADB which is used for the data files of the database

• ORAFC which is used for the Flash Recovery Area

• ORALOGS which is used for the log files and the control

In our test scenario, a general purpose database is created with the instance name test. The database is configured according to the structure created previously in ASM. In the test setup, the DBCA utility is used to create a database with the following parameter:

• General Purpose or Transactional Processing database

• Global Database Name: test

• SID: test

• ASM Disk groups:

a. ORADB for the data files

b. ORAFC for the Flash Recovery Area

c. ORALOGS for Log and Control files

The use of FlashCopy Manager requires the use of Oracle RMAN. To be able to connect via RMAN from the recovery catalog database to the production database, the owner of the recovery catalog must exist as a user on the production database with sysdba privileges. In the example, this is the database user rcatowner. Use SQLPLUS to login to the production database and create the necessary user. After this you can start configuring the backup server.

Backup server configuration On the backup server, create two disk groups, one for the recovery catalog database and another one for the log and control files from the production database. The disk group on the backup server for the log and control files must have the same name as the equivalent disk group on the production server. After the ASM configuration is done on the backup server and the ASM instance is up and running, the catalog database have to be created using again the DBCA utility. For details, please check Appendix A.



After the successful configuration of the recovery catalog database and verification that every database is accessible, the production database has to be registered in the catalog. Once the production database is registered to the catalog, a RMAN backup script has to be created and placed on the backup server. Here is the sample script form the test scenario:

$ cat rman_backup_test run { allocate channel 'c1' type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)'; backup (database); release channel c1; }



3 Installation and Configuration of FlashCopy Manager IBM Tivoli Storage FlashCopy Manager uses the copy services capabilities of intelligent storage subsystems to create point-in-time copies. These are application-aware copies (FlashCopy or snapshot) of the production data. This copy is then retained on disk as backup allowing for a fast restore operation (Flashback).

IBM Tivoli FCM also allows mounting the copy on an auxiliary server (backup server) as a logical copy. This copy (instead of the original data on the production server) is made accessible for further processing, like backup to tape.

Tivoli Storage Manager should be implemented in cases where a tape backup is desired in addition to disk backup.

Tivoli Storage FCM supports databases on JFS, JFS2, raw logical volumes, and Oracle ASM running on raw physical volumes. This section focuses on Oracle ASM environments (for JFS and raw volumes configuration, please refer to the manual Tivoli Storage FlashCopy Manager Installation and User’s Guide for AIX.) Tivoli Storage FlashCopy Manager provides backup and recovery interface for Oracle database full backups and restores. The use of Oracle Recovery Manager and a recovery catalog database is mandatory. Optionally, the database control files can be backed up into the Tivoli Storage FlashCopy Manager backup repository.

Tivoli Storage FlashCopy Manager supports the following backup functions:

• Full database backups at a volume level

• Backup of database control files into the Tivoli Storage FlashCopy Manager repository after a full backup completes

• Database restores with or without restoring database control files

3.1 Tivoli Storage FCM Architecture Figure 2 depicts the three major components, namely, Application Agent, Management Daemon, and Device Agent of the Tivoli Storage FlashCopy Manager:

Figure 2 FCM Components

Application Agent The Application Agent provides the necessary support for implementing snapshot-based backup and



restore. For Oracle databases, the client functions are integrated in the application agent acsora.

Management Agent (acsd) The Management Agent (acsd) coordinates the backup operation. It controls the backup flow and mediates between the application and device agents. The Management Agent also provides access to the snapshot backup repository which contains information about the valid snapshot backups and their relationships to snapshot-capable storage devices.

Device Agent for Generic Devices (acsgen) The Device Agent for Generic Devices (acsgen) is an OS-independent and storage device-independent software layer that interacts with OS-specific and storage device-specific adapters. This agent is also used to send and request updates of the progress and usability information that is stored in the local snapshot backup repository.

CIM Adapter (fmcima) The CIM Adapter (fmcima) is used in conjunction with the Generic Device Agent (acsgen). It is the component that invokes a snapshot command on a FlashCopy device (such as DS8000 and SAN Volume Controller) using the CIM interface.

XIV Adapter Java Archive (XivAdapter.jar) The XIV Adapter (XivAdapter.jar) is used in conjunction with the Generic Device Agent (acsgen). It communicates with acsgen and issues commands to the XIV command line interface (xcli).

Offload Agent (tsm4acs) The primary role of the Offload Agent (tsm4acs) is to provide a single user interface for backing up an existing snapshot to Tivoli Storage Manager. Tivoli Storage FlashCopy Manager includes a license file that enables use of the enhanced functions of the Offload Agent. The Offload Agent also calls the generic device agent for mount and unmount operations on the backup systems.

3.2 FCM Pre-Installation Tasks The most recent pre-installation task checklist for FlashCopy Manager can be found at reference [5]. The checklist defines hardware and software requirements and describes the volume layout for the Oracle environment. To have a smooth installation of FlashCopy Manager, it is absolutely necessary that all requirements are fulfilled. For a list of considerations and decisions to be taken before installing IBM Tivoli Storage FlashCopy Manager Version 2.1 for AIX, refer to the Installation Planning Sheet at reference [6].

Additional Prerequisites for disk-only backup and restore A recovery catalog database on the production system or on another system and a RMAN backup script on the production system is needed. This backup script may be empty, but it is needed for the backup of the control files.

Additional Prerequisites for tape (offloaded) backup The additional prerequisites for the Backup System, which offloads the backup to the TSM server are listed below:

• TSM client must be installed and configured

• TSM for Databases, Data Protection for Oracle (TDPO) must be installed and configured on the backup server

• A RMAN backup script, which uses TSM for Databases to backup the mounted database on the backup server to the TSM server

• Create an ASM disk group for the control files with the same name as the disk group, where the control files on the production system resides

• The $ORACLE_SID of the production database must be defined on the backup server and set in the profile of the Oracle user

• The directory $ORACLE_BASE/admin/$ORACLE_SID and the following subdirectories must



be created on the backup system:

o adump o dpdump o pfile o scripts

• The init<SID>.ora file must be copied to the same directory as on production system

• Grant the recovery catalog owner connect and sysdba rights on the production database, if the recovery catalog is not on your production system

Additional Prerequisites for the restore of offloaded backups The following additional prerequisites are necessary for the restore of offloaded backups to the production system:

• TSM client must be installed and configured

• TSM for Databases, Data Protection for Oracle (TDPO) must be installed and configured on the production system

• A RMAN restore script, which uses TDPO to restore database on the production system from the TSM server

3.3 TSM Client and Server If an offloaded backup is planned, FlashCopy Manager requires a Tivoli Storage Manager (TSM) client installation on both the production and backup server.

The client configuration is performed on the production and backup server. In this setup, the TSM Server is running on the backup server. The basic Tivoli Storage Manager code has to be installed on the backup server or any other server and configured with an administrative ID, and the storage pools must be available. For more information about planning and installing a Tivoli Storage Manager server, refer to the product documentation, or to reference [7].

3.4 FCM Installation IBM Tivoli Storage FlashCopy Manager must be installed on the production system. Optionally, it can also be installed on the backup system to offload backup data to a TSM Server. The IBM Tivoli Storage FlashCopy Manager installation directory is /usr/tivoli/tsfcm/acs_2.1.x.x. To install FlashCopy Manager with a graphical wizard, an X server has to be installed on the production system. The installation package is using the following name format: <version>-TIV-TSFCM-<OS-platform>.bin.

The installation must be performed as root user.

1. Log on to the production server as root user

2. Using the console mode, enter “./2.1.0.0-TIV-TSFCM-AIX.bin –i console”

3. Follow the instruction that are displayed, a sample installation is shown in Appendix B – Commands and Output. After the installation has finished log into the server as the database owner and start the script setup_ora.sh. This configuration script requires a lot of setup information, which are described in the next section.

3.5 FCM Configuration for disk-only backup After the installation of FlashCopy Manager a profile is required to successfully run FlashCopy Manager. In the following example FlashCopy Manager is configured for executing a backup to disk only. To create the profile, login as the database instance owner and run the script setup_ora.sh on the production system. The script asks several questions for the content of the profile. The main questions along with the answers that describe the test setup for this paper are listed below:

• Configuration from Production System (PS) or Backup System (BS)?

1. FlashCopy Manager is configured from PS with subsequent remote deployment to BS



via SSH. This is the recommended configuration

2. This option is required if no SSH is available or no NFS share is possible

• Please enter the directory where the profile will be stored: /<home directory of database instance owner>/acs

• Are you going to perform off-loaded backups to Tivoli Storage Manager? NO: Sections and parameters related to offloaded backups are omitted

• Path of the IBM Tivoli Storage FlashCopy Manager directory {ACS_DIR} /<home directory of database instance owner>/acs

• Hostname and port of machine running Management Agent {ACSD} (<hostname> <port>) <hostname of the production server> 57328

• Path to the repository directory {ACS_REPOSITORY} /<home directory of database instance owner>/acs/acsrepository

• Suspend target database: YES, to perform an online snapshot backup without the need for a backup server

• Used volume manager ASM

• Recovery catalog connect string Specifies the name of the Recovery Catalog database, as defined in $ORACLE_HOME/network/admin/tnsnames.ora

• Catalog database user name Specifies a user name that has Oracle system database administrator privileges on the Recovery Catalog database

• Filename of the RMAN backup script Name of the RMAN backup script that contains the Data Protection for Oracle environment variables

• Filename of Oracle(R) parameter file Specifies the fully resolved path and file name of the Oracle parameter file (init<SID>.ora by default) for the target database.

• Type of Storage system XIV

• Storage system ID of referred cluster Serial No. of XIV

• Filepath to XCLI command line tool Specifies the fully resolved path to the XCLI

• Hostname of XIV system Either hostname or IP address of the XIV

• Username for storage device Username with storageadmin role on XIV

• Please enter the password for device section STANDARD: Password for the user above

The Appendix B – Commands and Output shows the complete setup_ora.sh protocols for XIV. The setup script creates the profile in the /<home directory of database instance owner>/acs directory and adds the CLIENT section for disk only backup to the profile. The profile for the test setup is shown below:

bash-3.00$ cat profile >>> GLOBAL # ACS_DIR /oracle/acs ACSD racnode3 57328 TRACE YES



<<< >>> ACSD ACS_REPOSITORY /oracle/acs/acsrepository # ADMIN_ASSISTANT NO # REPOSITORY_LABEL TSM <<< >>> CLIENT # BACKUPIDPREFIX ORCL__ APPLICATION_TYPE ORACLE TARGET_DATABASE_SUSPEND YES VOLUME_MGR ASM # MAX_VERSIONS ADAPTIVE # NEGATIVE_LIST NO_CHECK # TIMEOUT_FLASH 120 # GLOBAL_SYSTEM_IDENTIFIER # DEVICE_CLASS STANDARD <<< >>> ORACLE CATALOG_DATABASE_CONNECT_STRING rcat CATALOG_DATABASE_USERNAME rcatowner DATABASE_BACKUP_SCRIPT_FILE /orabin/orabase/db/rman_backup_scripts/rman_backup_test TARGET_DATABASE_PARAMETER_FILE /orabin/orabase/db/dbs/inittest.ora DATABASE_CONTROL_FILE_RESTORE YES ASM_INSTANCE_USER oracle # ASM_INSTANCE_ID +ASM # ASM_ROLE SYSDBA <<< >>> DEVICE_CLASS STANDARD COPYSERVICES_HARDWARE_TYPE XIV STORAGE_SYSTEM_ID 1300203 PATH_TO_XCLI /opt/xiv/XIVGUI/ COPYSERVICES_SERVERNAME 9.155.90.180 COPYSERVICES_USERNAME oracle # RECON_INTERVAL 12 # GRACE_PERIOD 24 # USE_WRITABLE_SNAPSHOTS AUTO # USE_CONSISTENCY_GROUPS YES # BACKUP_HOST_NAME <<<

3.6 Switching from disk-only to offloaded backup If FlashCopy Manager was already installed and configured on the production server without the offload backup option, you have to rerun the setup_sapora.sh script in order to modify the FlashCopy Manager profile instead of changing the configuration files manually. In addition to the changes on the production server setup_sapora.sh is also able to install and configure Tivoli Storage FlashCopy Manager on the backup server. Furthermore, you have to copy once the init<SID>.ora from the production system to the backup system.

The script asks several questions for the content of the profile. The main goal is to configure the offload option:

• Synchronize database configuration file on the BS with PS YES, to update the init<SID>.ora on the BS

• Level of backup 0, to perform the first time a full backup, may be changed later to a value greater than 0 to perform incremental backups to TSM server



• Create backup from snapshot YES

• Hostname of backup host Hostname of Backup server on XIV

• Do you want off-loaded tape backups to begin immediately after the snapshot NO, to perform the off-loaded backup manually or with crontab entries after the FlashCopy backup completes

• Do you want to install a new Backup System using the Open Secure Shell (OpenSSH) protocol YES, to install the FCM Software on the backup system

• Please enter the hostname of the backup system: Either hostname or IP address of the backup system

The Appendix B – Commands and Output shows also the complete modification with setup_ora.sh for the Offload Server.



4 Leveraging XIV Snapshots for Backup/Restore of Oracle databases with FCM The integration of FCM and XIV automates the backup and restore process of Oracle database. It minimizes the impact of the backup on the production environment and enables very fast restores. In addition, XIV’s space-efficient snapshots significantly reduce storage capacity required for disk-based backup.

After the configuration of FCM has completed as described in section Installation and Configuration of FlashCopy Manager, the backup and restore of the Oracle database may be started.

This chapter describes basic backup and restore scenarios that are supported by FlashCopy Manager. For the examples tested at the IBM lab, the following information is provided:

• the command line to invoke the backup or restore

• output information required for follow-on activities (e.g. backup IDs required for a potential restore)

Figure 3 and 4 show the backup and restore options of the FlashCopy Manager:

1. a disk-only backup of the production environment leveraging the FlashCopy or Snapshot feature of the storage system

2. a backup server unlocks the snapshots and offloads the database backup from the snapshot volumes to a TSM server.

3. a restore of the disk-only backup to the production environment reversing an existing Snapshot

4. a restore from the TSM server to the production environment

Notes:

• For a disk-only backup or restore, neither a backup server nor a TSM server is required (scenarios 1 and 3)

• A TSM restore writes directly to the production environment (scenario 4)

• The TSM server and the backup server can be installed on the same AIX host

• A standard online or offline backup of the production environment to the TSM server is still possible (but not shown in the figures)

Figure 3 FCM backup options



Figure 4 FCM restore options

4.1 Disk-only backup A disk-only backup leverages the snapshot feature of the XIV to create copies of the LUNs that host the database. A disk-only backup requires neither a backup server nor a TSM server. A disk-only backup is initiated with the acsora command, as shown in the following example:

# su - oracle $ . oraenv ORACLE_SID = [test] ? test The Oracle base for ORACLE_HOME=/orabin/orabase/db is /orabin/orabase $ cd acs $ ./acsora -f backup

The following steps are used for the FCM backup (refer to Appendix B for detailed examples):

1. Backup of the current control file via RMAN 2. Set the table spaces of the database in backup mode 3. Suspend the database 4. Flushing the buffers to disk 5. Create the Snapshot via XCLI 6. Resume the database 7. End the backup mode for the table spaces 8. Switch the database log files

FlashCopy Manager creates a BackupID that is displayed in the backup log file and can also be read out with the acsutil or acsora tools. This BackupID or an equivalent SnapshotID will be required to initiate a restore. The BackupID is a string of 10 alpha-numeric characters appended to the BACKUPIDPREFIX, as defined in the profile, e.g. A0G2OX8ILK.

Examples:

1. acsutil command line:

# su – oracle $ cd acs $ ./acsutil -p profile



2. acsora command line:

# su – oracle $ cd acs $ ./acsora -f inquire_detail

The complete output of the acsora commands are shown in Appendix B – Commands and Output.

Figure 5 depicts XIV snapshots created by FlashCopy Manager. XIV allocates snapshot space at the time it is required.

Figure 5 XIV snapshots created by FCM

Check that enough XIV snapshot space is available for the number of snapshot versions to keep. If snapshot space is not sufficient, XIV starts to delete older snapshot versions. These deletions are not immediately reflected in FlashCopy Manager’s repository. FlashCopy Manager’s interval for reconciliation is specified during FlashCopy Manager setup and can be checked and updated in the FlashCopy Manager profile. The current default value of the RECON_INTERVAL parameter is 12 hours.

4.2 Offload to Tivoli Storage Manager An existing disk-only backup can be offloaded to a TSM server. A backup server accesses the data on the FlashCopy target volumes and forwards the data to a TSM server which, in turn, stores it in one of its storage pools (tape or disk).

FlashCopy Manager supports multiple FlashCopy targets enabling the creation of several backup versions. Nevertheless a disk-only backup will usually be overwritten in shorter intervals than a TSM backup which will be usually kept for weeks.



To offload the backup, you will need to create an RMAN script, which specifies the configuration file tdpo.opt as an environment variable. An example for such an RMAN script is shown below:

bash-3.00# cat rman_backup_test run { allocate channel 'c1' type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)'; backup (database); release channel c1; }

To manually offload the last restorable snapshots initiate the tsm4acs command on the production system, as shown in the following example:

# su – oracle $ cd acs $ ./tsm4acs –f tape_backup

The complete output of the tsm4acs command is shown in Appendix B – Commands and Output.

The following steps are used for the FCM offload (refer to Appendix B for detailed examples):

1. Unlock the snapshots on XIV 2. Mount the snapshots 3. Start database instance 4. Write the control files to the ASM disk group for control files 5. Backup of the database via RMAN, TDPO and TSM client to the TSM server 6. Stop database instance 7. Unmount the snapshots

4.3 Restore from snapshot To restore a disk-only backup shutdown the target database and initiate the acsora command, as shown in the following example. The storage-based snapshot feature is not aware of the database structure and cannot perform restore operations on the file or table space level. The complete set of volumes belonging to the snapshot is reversed.

# su – oracle $ cd acs $ ./acsora -f restore

The complete output of the acsora command is shown in Appendix B – Commands and Output. After the restore a database recovery is necessary.

The following steps are used for the FCM restore (refer to Appendix B for detailed examples):

1. Check for the last restorable backup 2. Drop the ASM disk group 3. Restore the snapshot via XCLI 4. Bring the ASM disk group online 5. Start the database instance 6. Restore the control files via RMAN

4.4 Restore from TSM server Backup and restore to and from a TSM server are not specific to FlashCopy Manager; therefore you will need TDPO on the production system. The backup and restore options of TDPO are explained in chapter TSM for Databases, Data Protection for Oracle Overview. More details about TDPO may be found at reference [8].



To restore the production database from the offloaded backup, you will need to create an RMAN script, which contains the tdpo.opt file as an environment variable. An example for such an RMAN script is shown below:

bash-3.00$ cat rman_restore_test run { allocate channel t1 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)'; restore database; recover database; alter database open; } To restore the database, mount the database and initiate the rman command, as shown in the following example: bash-3.00$ rman target / catalog rcatowner/oracle@rcat cmdfile rman_restore_test msglog rman_restore.log

The complete output of the rman command is shown in Appendix B – Commands and Output.



5 Summary As demonstrated in this best practices guide, the snapshot and consistency group feature of the IBM XIV Storage System together with Tivoli Storage FlashCopy Manager completely automates backup process of Oracle databases, enables with very short backup windows, and provides almost instant restore capabilities.



References 1. Redbook: IBM XIV Storage System: Architecture, Implementation, and Usage

http://www.redbooks.ibm.com/abstracts/sg247659.html?Open

2. IBM XIV Storage System overview http://www-03.ibm.com/systems/storage/disk/xiv/index.html

3. IBM XIV Storage System Information Center http://publib.boulder.ibm.com/infocenter/ibmxiv/r2/index.jsp

4. IBM Tivoli Storage Manager Version 6.1 documentation

http://publib.boulder.ibm.com/infocenter/tsminfo/v6/index.jsp

5. IBM Tivoli Storage FlashCopy Manager Version 2.1 Hardware and Software Requirements http://www-01.ibm.com/support/docview.wss?&uid=swg21395564

6. Tivoli Storage FlashCopy Manager Installation Planning Sheet

http://www-01.ibm.com/support/docview.wss?uid=swg21395564&aid=3

7. Redbook: IBM Tivoli Storage Manager Implementation Guide, SG24-5416 http://www.redbooks.ibm.com/abstracts/sg245416.html?Open

8. IBM Tivoli Storage Manager for Databases: Data Protection for Oracle for UNIX and Linux

Installation and User’s Guide http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/index.jsp?topic=/com.ibm.itsmfd.doc/ab5u0004.htm



Appendix A – XIV Storage configuration and Oracle Software installation

The following section provides a rough overview of the topology, configuration, and software levels used for the test of the solution.

Oracle Database servers Two logical partitions (LPARs) on an IBM System p590 with were configured as the Oracle database servers. One LPAR was used as the production database server and one LPAR as the backup/offload server. The table below summarizes the hardware and software configuration for each AIX server in the test environment:

Features AIX 6.1/ Oracle Database 11g Release 1 Server model IBM System p595 Operating-system version

AIX 6.1 6100-03-01-0921

Oracle version

Oracle Database 11.1.0.7,0 Oracle ASM

Table 1. Oracle Database server

Storage hardware Table 2 shows the XIV Storage System that was used for the Oracle test environment.

Features Storage model IBM XIV Storage System Storage manager server level 10.2.0.a Storage manager GUI 2.4.1 XIV Host Attachment Kit 1.1.0.1

Table 2. Storage hardware

Configuration by example This section provides an example of the storage configuration scenario that is explained in this white paper. The easy-to-use graphical user interface is used for setting up XIV storage for the Oracle database. The section includes step-by-step examples to accomplish this task using the GUI.

XIV storage configuration by GUI For the Oracle production database setup, five volumes are created on the XIV storage system:


• Four for the Oracle database

In order to meet the prerequisites of the FlashCopy Manager the database control files and the logfiles are stored in a separate ASM disk group and for the Flash Recovery Area another ASM disk group is used.



Table 3 summarizes the storage infrastructure regarding the database production server

Description LUN size Number of LUNs Volume type

Oracle Database data files 96 GB 2 ASM

Oracle Database log and control files 16 GB 1 ASM

Oracle Database Flash Recovery Area 16 GB 1 ASM

Oracle Database SW 16 GB 1 JFS2 Table 3. Storage allocation for Oracle Database

For the Backup Server, seven volumes are created on the XIV storage system and three of them for Oracle:


• Two for the Oracle database

• The remaining LUNs containing the TSM software FCM installation and Oracle downloads etc.

In order to meet the prerequisites of the FlashCopy Manager, the Backup Sever must have an ASM disk group for the logs with the same name as the disk group for the logs on the production server, have to be created.

Table 4 summarizes the storage infrastructure on the backup server

Description LUN size Number of LUNs Volume type

Oracle Database recovery catalog 16 GB 1 ASM

Oracle Database log and control files 16 GB 1 ASM

Oracle Database SW 16 GB 1 JFS2 Table 4. Storage allocation for Oracle Database

Storage pool setup Use the XIV GUI for the storage configuration. Perform the following steps to create the storage pool:

1. Login to XIV Storage manager GUI

2. Select Storage Pools from navigation menu on the left hand side

3. Select Add Pool from the toolbar and create a new storage pool



Figure 6 Add Pool screen

a. From the drop down menu, select the type of pool you want to use. The scenario was tested on thin provisioned storage pool to demonstrate that this solution works well even if thin provisioning is used.

b. Enter the values for Pool Hard Size, Pool Soft Size, Snapshot Size, and the Pool Name

c. Click Add button to create the pool

LUN creation Perform the following steps to create the LUNs:

1. Select Volumes by Pools from navigation menu.

2. Select Add Volumes from the toolbar and create the desired volumes. Make sure that the correct pool is chosen.

3. List the storage pool and its volumes and review the volume list.



Figure 7 Storage Pools view

Figure 7 shows the storage pools view of the XIV storage system.

Figure 8 Storage Pools view details

The numbers shown in Figure 8 refers to the soft size and to the physical capacity. The used storage is marked green, while free storage is marked grey. In the example, the soft size of the pool is 2010 GB and the hard size or actual physical capacity is 1013 GB. These capacity numbers will be different in a real production system due to the fact that they depend on parameters like, available capacities (soft size / hard size) of the XIV system, the initial size of the production database and the data growth of the production database.

Create host connections and do LUN assignments to nodes The server is connected via SAN to four ports at the XIV Storage System. Perform the following steps to define the host connections on the XIV storage system:

1. Select Host Connectivity from the navigation menu

2. Select Add Host from the toolbar and enter the desired Host name

3. Add the WWPN of the server’s HBA ports. Select Host Connectivity from the navigation menu. A right mouse click on the previously added hosts opens a popup menu. Select Add Port from popup menu and choose the appropriate WWPN.

4. In the Hosts Connectivity screen, verify that all attached ports are configured correctly.

5. Select the previously created Host from the Hosts Connectivity list. Use a right mouse click on the host name to select Map Volumes to this host. Select from the left side the previously created volumes and map them to the host.



Figure 9 XIV LUN mapping

Host Configuration The following steps describe, in general terms, how to prepare the systems for the Oracle installation.

IMPORTANT:

For the latest requirements refer to Oracle Metalink Bulletin 282036.1 Minimum Software Versions and Patches Required to Support Oracle Products on IBM pSeries. This bulletin is available to Metalink users at: https://metalink.oracle.com/. Metalink Bulletin 282036.1 is regularly updated, and the information that the bulletin contains supersedes any information found in this paper.

1. Install the AIX operating system if AIX is not already installed. The example configuration uses AIX 6.1 Technology Level 3.

2. Install additional software packages required for Oracle.

a. bos.adt.base

b. bos.adt.lib

c. bos.adt.libm

d. bos.perf.libperfstat

e. bos.perf.perfstat

f. bos.perf.proctools

g. rsct.basic.rte

h. rsct.compat.clients.rte

i. xlC.aix61.rte:9.0.0.1 (See the previous important note)



j. xlC.rte:9.0.0.1 (See the previous important note)

3. Download and install the updates to the AIX operating system from IBM's website: http://www-933.ibm.com/support/fixcentral/ Example configuration uses AIX 6.1 Technology Level 3 (oslevel –s: 6100-03-01-0921).

4. Configure the network interfaces of the host.

5. Create operating system users and groups.

a. Create two groups, dba and oinstall.

b. Add a user, Oracle, with the oinstall primary group and with the dba group.

6. Set the shell soft limits for the Oracle and root users using the smitty chuser command.

a. Soft FILE size = -1

b. Soft CPU time = -1

c. Soft DATA segment = -1

d. Soft STACK size = -1

NOTE: The user Oracle has to be exactly the same on both servers including the UID and password. The same applies for the group dba and oinstall!!!

7. Use the smitty chgsys command to set the maximum number of processes for each user to at least 2048.

8. Use the /usr/sbin/no -a command to examine the minimum values for the following network tuning parameters.

a. ipqmaxlen = 512

b. rfc1323 = 1

c. sb_max = 1310720 (2*655360)

d. tcp_recvspace = 65536

e. tcp_sendspace = 65536

f. udp_recvspace = 655360 (10 * udp_sendspace, must be less than sb_max)

g. udp_sendspace = 65536

NOTE: If you modify these parameters, the method depends on whether the system is in compatibility mode. For specific instructions, refer to the AIX documentation for the no command. If you change the value of the ipqmaxlen parameter, you must restart the system for the change to take effect.

9. Change the .profile file in the Oracle user’s home directory to set the Oracle user's parameters.

Parameter to Add Description

umask 022

AIXTHREAD_SCOPE=S An environment variable that directs the system to place user threads within a system-wide scope rather than a process-wide contention scope. This placement provides better performance and more efficient memory use.

ASM_HOME Use this parameter if you want to install separate Oracle binaries for Oracle ASM. This method is preferred if more than one database instance is supported by Oracle ASM.

ORACLE_HOME A unique home for the database binaries.

LD_LIBRARY_PATH The complete pathway is $ORACLE_HOME/lib.



ORACLE_BASE Identifies the Oracle base directory.

ORACLE_SID Identifies the Oracle instance. DO NOT USE the ASM Instance on the backup server side!!!

PATH Include $ORACLE_HOME/bin.

CLASSPATH Include $ORACLE_HOME/jdbc/lib/<classes files>.

Table 5. Oracle User’s Parameters

10. Change the .profile file in the root user’s home directory to set the Oracle user's parameters. Add this entry to the .profile file: AIXTHREAD_SCOPE=S

11. During the test setup some Oracle utilities expected lsattr in the directory /etc. You might use the command ln -s /usr/sbin/ lsattr /etc/lsattr command to add a soft link.

Configuring the previously created XIV volumes on the host Analyze your implementation to determine the appropriate volume sizes and other parameters. The reference configuration uses the configuration of XIV volumes like described in table 3 or table 4.The number and the size of the logical drives created for Oracle storage varies based on the individual implementation. In the reference configuration, the Oracle binaries are installed on an XIV disk drive. This configuration uses the JFS2 file system and is mounted as /orabin/orabase/db In order to keep it simple use the same structure for production and backup server.

Before the XIV volumes can be discovered correctly on the host, the XIV Host Attachment Kit disk.fcp.2810.rte.1.1.0.1 (or later) has to be installed depending on the AIX level. Check the web (release notes) if a HAK-package is needed and download the appropriate package:

http://www-01.ibm.com/support/docview.wss?rs=1319&context=STJTAG&context=HW3E0&dc=D400&q1=ssg1*&uid=ssg1S4000802&loc=en_US&cs=utf-8&lang=en

http://www-01.ibm.com/support/docview.wss?uid=ssg1S4000802&rs=555

Follow the installation instructions shown in the XIV host attachment guide (release notes and packages are on the same web site)

1. Configure the XIV volumes in the operating system.

a. After you have created the volumes on the storage subsystem, and mapped them to the servers, the cfgmgr command rescans the AIX system for changes to the physical devices.

b. Check with xiv_devlist or lsdev –Cc disk for the XIV drives

c. The lspv command shows the physical devices that AIX has configured. lspv output (example production server):

# lspv hdisk0 00ce0c7b2fa12373 None hdisk1 00ce0c7bd1088fe1 rootvg active hdisk2 00ce0c7be2babb4f rootvg active hdisk3 none None hdisk4 none None hdisk5 none None hdisk6 none None hdisk7 00ce0c7bf20e1a02 vg00 active hdisk8 00ce0c7b455e431c backupvg active hdisk9 none None

d. Verify that the load balancing option on the XIV disks is round_robin and the queue depth is equal or larger than 32



e. The lscfg –vl <hdisk?> command, where ? is the number of the hdisk, displays the serial number of the disk drive. The bootinfo –s <hdisk?> command displays the size of the volume.

lsattr -El hdisk<?> PCM PCM/friend/2810xivpcm Path Control Module False PR_key_value Persistent Reserve Key Value True algorithm round_robin Algorithm True hcheck_cmd inquiry Health Check Command True hcheck_interval 60 Health Check Interval True hcheck_mode nonactive Health Check Mode True lun_id 0xb000000000000 Logical Unit Number ID False lun_reset_spt yes Support SCSI LUN reset True max_transfer 0x40000 Maximum TRANSFER Size True node_name 0x5001738001060000 FC Node Name False pvid 00c7ed64858db70a0000000000000000 Physical volume identifier False q_type simple Queuing TYPE True queue_depth 32 Queue DEPTH True reserve_policy no_reserve Reserve Policy True rw_timeout 30 READ/WRITE time out value True scsi_id 0x13b00 SCSI ID False unique_id 2611200173800010600C5072810XIV03IBMfcp Unique device identifier False ww_name 0x5001738001060150 FC World Wide Name False

If it is not, then execute the following command:

chdev -l hdisk<?> -a mode=round_robin –a queue_depth=64

2. Set ownership and permissions on hdisks for use by Oracle. Use these commands to set the ownership and the permission on disk drives:

chown oracle:dba /dev/<devnode> chmod 660 /dev/<devnode>

NOTE: Do not assign a physical volume identifier (PVID) to hdisks for use with Oracle ASM!!! A previously assigned PVID can be cleared using chdev -l hdisk? -a pv=clear (where ? represents the hard disk number)

Installing the Oracle database Software on both servers These are the basic steps for installing Oracle:

1. Create directories for Oracle database We recommend using a standard directory structure based on the Optimal Flexible Architecture (OFA) guidelines published by Oracle for ease of support. Follow these two important guidelines when creating directories for Oracle: If more than one database is serviced by Oracle ASM, create a separate home directory for Oracle ASM. An Oracle ASM home directory lets you modify the Oracle release for Oracle ASM while not changing the release of any of the databases on the same server. The directory tree must be owned by oracle.

2. Set up the Oracle user’s profile

a. Before you install the Oracle binaries, set up the Oracle user's .profile.

b. Add or modify entries for ORACLE_HOME, ORACLE_BASE, PATH, LD_LIBRARY_PATH, and similar environment variables to reflect the directories where the Oracle binaries are placed during the Oracle Database installation.

3. Install the Oracle database If you want a separate database home, use the Oracle Universal Installer to install another database home for a database instance. Select Install Database Software Only at the Create Database page.



4. Configure the listener names If your environment contains both an Oracle ASM instance and a database instance, supporting only one listener.ora configuration file for the Oracle ASM and database instances is easier. This environment variable lets the DBA maintain one set of tnsnames.ora, sqlnet.ora, and listener.ora files for the entire environment. Use Oracle’s netca utility to configure the Listener for Oracle.

5. Patch the Oracle Software. The Oracle Software has to be patched according to the required levels stated in the FlashCopy manager prerequisites.

Configuring the Oracle servers Production server configuration

Use Oracle’s DBCA utility to create ASM disk groups on production server. Create three disk groups for the production database. As Oracle user use asmcmd commandline utility and verify the created disk groups:

$ export ORACLE_SID=+ASM

$ asmcmd

ASMCMD> lsdg

State Type Rebal Sector Block AU Total_MB Free_MB Req_mir_free_MB Usable_file_MB Offline_disks Name

MOUNTED EXTERN N 512 4096 1048576 262144 260161 0 260161 0 ORADB/

MOUNTED EXTERN N 512 4096 1048576 16384 11632 0 11632 0 ORAFC/

MOUNTED EXTERN N 512 4096 1048576 16384 16141 0 16141 0 ORALOGS/

ASMCMD>

In our example, the lsdg output shows three disk groups: ORADB which is used for the data files of the database, ORAFC which is used for the Flash Recovery Area and the disk group ORALOGS which is used for the log files and the control files according to the FlashCopy Manager prerequisites.

After the ASM configuration is done the production database can be created using again the DBCA utility. In the test scenario a general purpose database was created with the instance name test. The database was configured according to the structure created previously in ASM. In the test setup the DBCA utility was used to create a database with the following parameter:


• Global Database Name: test

• SID: test

• ASM Disk groups:

• ORADB for the data files

• ORAFC for the Flash Recovery Area

• ORALOGS for Log and Control files

The use of FlashCopy Manager requires the use of Oracle’s RMAN. To be able to connect via RMAN from the recovery catalog database to the production database the owner of the recovery catalog must exist as a user on the production database with sysdba privileges. In the example, this is the database user rcatowner. Use SQLPLUS to login to the production database and create the necessary user:



$ export ORACLE_SID=test $ sqlplus / as sysdba SQL*Plus: Release 11.1.0.7.0 - Production on Tue Dec 15 07:35:57 2009 Copyright (c) 1982, 2008, Oracle. All rights reserved. Connected to: Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options SQL> create user rcatowner identified by oracle; User created. SQL> grant sysdba to rcatowner; Grant succeeded. SQL>exit

Now you can start configuring the backup server.

Backup server configuration Use Oracle’s DBCA utility to create an ASM Instance on the backup server. Create two disk groups, one for the recovery catalog database and another one for the log and control files from the production database. The disk group on the backup server for the log and control files must have the same name as the equivalent disk group on the production server. As Oracle user use asmcmd commandline utility and verify the created disk groups:

$ export ORACLE_SID=+ASM $ asmcmd ASMCMD> lsdg State Type Rebal Sector Block AU Total_MB Free_MB Req_mir_free_MB Usable_file_MB Offline_disks Name MOUNTED EXTERN N 512 4096 1048576 16384 16309 0 16309 0 ORALOGS/ MOUNTED EXTERN N 512 4096 1048576 16384 14349 0 14349 0 RCATDB/ ASMCMD>

After the ASM configuration is done at the backup server side and the ASM instance is up and running, the catalog database can be created using again the DBCA utility. In the test scenario, a general purpose database was created with SGA size=300MB and the instance name rcat.

Use DBCA utility to start the process of creating the recovery catalog database. Create a database with the following parameters:


• Global Database Name: rcat

• SID: rcat

• Use ASM Disk group: RCATDB for the entire ctalog database.

Once the database is created and started up, the catalog has to be created. Use the following steps:

• Login to the catalog database sqlplus sys/oracle@rcat as sysdba

• Create a tablespace (size=15MB) named rcat to hold the repository data create tablespace rcat datafile size 15M;

• Create the user who will own the recovery catalog data. Name the user rcatowner like the user on the production database. The default tabelspace should be the rcat tablespace and the user should have unlimited quto on that tablespace.



create user rcatowner identified by oracle default tablespace rcat quota unlimited on rcat;

• Grant the RECOVERY_CATALOG_OWNER role to the user rcatowner

grant recovery_catalog_owner to rcatowner;

• Exit from SQLPLUS

Now you can create the recovery catalog:

• Connect to the recovery catalog database using RMAN. Login as the recovery catalog owner rcatowner rman catalog rcatowner/oracle@rcat

• Now create the recovery catalog. This command may take a few minutes. Create catalog;

• Once the catalog is created exit from RMAN

Verify that tnsnames.ora and the Listener configuration have all the necessary entries to connect to the databases from each server. In the test setup the following configuration was used:

Production server: $ cat listener.ora # listener.ora Network Configuration File: /orabin/orabase/db/network/admin/listener.ora # Generated by Oracle configuration tools. LISTENER = (DESCRIPTION_LIST = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = racnode3)(PORT = 1521)) ) ) SID_LIST_LISTENER = (SID_LIST= (SID_DESC= (SID_NAME=test) (ORACLE_HOME=/orabin/orabase/db) ) ) $ cat tnsnames.ora # tnsnames.ora Network Configuration File: /orabin/orabase/db/network/admin/tnsnames.ora # Generated by Oracle configuration tools. RCAT = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = p6-570-lab-03v3.mainz.de.ibm.com)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = rcat) ) ) TEST = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = racnode3)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = test) ) ) $



Try to connect from each server to each database using sqlplus.

After the successful configuration of the recovery catalog database and verification that every database is accessible, the production database has to be registered in the catalog.

From the production server connect to the target database (production database to be registered) and to the recovery catalog database using RMAN:

• Verify the correct ORACLE_SID $ . oraenv ORACLE_SID = [test] ? test $ rman target / catalog rcatowner@rcat Recovery Manager: Release 11.1.0.7.0 - Production on Tue Dec 15 09:12:02 2009 Copyright (c) 1982, 2007, Oracle. All rights reserved. connected to target database: TEST (DBID=2000816864) recovery catalog database Password: connected to recovery catalog database RMAN>

• Now register the database RMAN> register database; database registered in recovery catalog starting full resync of recovery catalog full resync complete RMAN>exit

Now the production database is registered to the catalog database and a RMAN backup script have to be created and placed on the backup server. Here is the sample script form the test scenario: $ cat rman_backup_test run { allocate channel 'c1' type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)'; backup (database); release channel c1; }



Appendix B – Commands and Output This section provides the detailed output of commands invoked by 2.1.0.0-TIV-TSFCM-AIX.bin, setup_ora.sh, acsora, tsm4acs, and rman, as well as the flow of executable activities from the respective commands.

Installation of FCM

# ./2.1.0.0-TIV-TSFCM-AIX.bin -i console

Preparing to install...

WARNING: /tmp does not have enough disk space!

Attempting to use / for install base and tmp dir.

Extracting the JRE from the installer archive...

Unpacking the JRE...

Extracting the installation resources from the installer archive...

Configuring the installer for this system's environment...

Launching installer...

Preparing CONSOLE Mode Installation...

===============================================================================

Choose Locale...

----------------

1- Deutsch

->2- English

3- Español

4- Français

5- Italiano

6- Português (Brasil)

CHOOSE LOCALE BY NUMBER: 2

===============================================================================

IBM Tivoli Storage FlashCopy Manager (created with InstallAnywhere by Macrovision)

-------------------------------------------------------------------------------------

===============================================================================

Introduction

------------

InstallAnywhere will guide you through the installation of

IBM Tivoli Storage FlashCopy (R) Manager.

Respond to each prompt to proceed to the next step in the installation.

If you want to change something on a previous step, type 'back'.

You may cancel this installation at any time by typing 'quit'.

PRESS <ENTER> TO CONTINUE:



===============================================================================

International Program License Agreement

Part 1 - General Terms

BY DOWNLOADING, INSTALLING, COPYING, ACCESSING, CLICKING ON AN

"ACCEPT" BUTTON, OR OTHERWISE USING THE PROGRAM, LICENSEE AGREES TO

THE TERMS OF THIS AGREEMENT. IF YOU ARE ACCEPTING THESE TERMS ON

BEHALF OF LICENSEE, YOU REPRESENT AND WARRANT THAT YOU HAVE FULL

AUTHORITY TO BIND LICENSEE TO THESE TERMS. IF YOU DO NOT AGREE TO

THESE TERMS,

- DO NOT DOWNLOAD, INSTALL, COPY, ACCESS, CLICK ON AN "ACCEPT" BUTTON,

OR USE THE PROGRAM; AND

- PROMPTLY RETURN THE UNUSED MEDIA, DOCUMENTATION, AND PROOF OF

ENTITLEMENT TO THE PARTY FROM WHOM IT WAS OBTAINED FOR A REFUND OF THE

AMOUNT PAID. IF THE PROGRAM WAS DOWNLOADED, DESTROY ALL COPIES OF THE

PROGRAM.

Press Enter to continue viewing the license agreement, or enter "1" to

accept the agreement, "2" to decline it, "3" to print it, or "99" to go back

to the previous screen.: 1

===============================================================================

Choose Product

---------------

Please choose the Install Set to be installed by this installer.

->1- IBM Tivoli Storage FlashCopy (R) Manager (DB2 Advanced Copy Services)

2- IBM Tivoli Storage FlashCopy (R) Manager (Oracle)

3- IBM Tivoli Storage FlashCopy (R) Manager (SAP (R) with Oracle)

ENTER THE NUMBER FOR THE INSTALL SET, OR PRESS <ENTER> TO ACCEPT THE DEFAULT

: 2

===============================================================================

Choose Install Folder

---------------------

Please choose a destination folder for this installation.

Where Would You Like to Install?

Default Install Folder: /usr/tivoli/tsfcm/acs_2.1.0.0



ENTER AN ABSOLUTE PATH, OR PRESS <ENTER> TO ACCEPT THE DEFAULT

:

===============================================================================

HOME Directory of the instance owner

------------------------------------

Please enter the HOME Directory of the instance owner

Enter directory name (DEFAULT: ): /oracle

===============================================================================

===============================================================================

Pre-Installation Summary

------------------------

Please Review the Following Before Continuing:

Install Folder:

/usr/tivoli/tsfcm/acs_2.1.0.0

Product Components:

IBM Tivoli Storage FlashCopy (R) Manager (Oracle)

HOME Directory of the instance owner

"/oracle"

Disk Space Information (for Installation Target):

Required: 654,517,641 bytes

Available: 1,254,092,800 bytes

PRESS <ENTER> TO CONTINUE:

===============================================================================

Installing...

-------------

[==================|==================|==================|==================]

[------------------|------------------|------------------|------------------]

===============================================================================

Install Complete

----------------

Congratulations! IBM Tivoli Storage FlashCopy (R) Manager has been installed to:

/usr/tivoli/tsfcm/acs_2.1.0.0

Attention

You have to execute the script ./setup_ora.sh after the installation has finished once on each database instance to run IBM Tivoli Storage FlashCopy (R) Manager.



You will find the script setup_ora.sh in /oracle/acs and you need to run it as the database instance user.

PRESS <ENTER> TO EXIT THE INSTALLER:

Configuration of FCM for Oracle disk-only backup

$ ./setup_ora.sh

checking /oracle/acs/acsgen ...

OK

Select one of these configurations:

(1) On-Site Production System configuration with optional remote Backup System configuration

(2) On-Site Backup System configuration

Enter '1' to configure IBM Tivoli Storage FlashCopy(R) Manager on the production server with the option to remotely synchronize the configuration of one or multiple backup systems using Secure Shell.

Enter '2' to configure IBM Tivoli Storage FlashCopy(R) Manager on the backup system as a 'separate installation'.

1

Preparing to install on Production System

Please enter the directory where the profile will be stored: [/oracle/acs]

selected profile path: /oracle/acs

Deactivating FCM management daemon.

Are you going to perform off-loaded backups to Tivoli Storage Manager? [y|n]

n

Welcome to new wizard!

Special commands:

'?' -> Show help for current parameter

'!d' -> Delete current parameter instance (only applicable to multi-instance parameters)

FMM8422I Creating new profile '/oracle/acs/profile' for application 'ORACLE' ...

****** Profile parameters for section GLOBAL : ******

Path of the IBM Tivoli Storage FlashCopy(R) Manager directory {ACS_DIR} = [/oracle/acs]

Hostname and port of machine running Management Agent {ACSD} (<hostname> <port>) = [racnode3 57328]

Low level tracing {TRACE} (YES|NO) = [NO] YES

****** Profile parameters for section ACSD : ******

Path to the repository directory {ACS_REPOSITORY} = *input mandatory* /oracle/acs/acsrepository

Support for Administration Assistant {ADMIN_ASSISTANT} (<hostname> <port>|NO) = [NO]

Prefix for volume names {REPOSITORY_LABEL} = [TSM]



****** Profile parameters for section CLIENT : ******

Identifier for backups of this database instance in the repository {BACKUPIDPREFIX} (<string>) = [ORCL__]

Suspend target database {TARGET_DATABASE_SUSPEND} (NO|YES|OFFLINE) = *input mandatory* YES

Used volume manager {VOLUME_MGR} (LVM|ASM) = [LVM] ASM

Maximum number of snapshot versions {MAX_VERSIONS} (<number>|ADAPTIVE) = [ADAPTIVE]

Negative list {NEGATIVE_LIST} (<filename>|NO_CHECK|WARN|ERROR) = [NO_CHECK]

Timeout {TIMEOUT_FLASH} for phase 'flash' (<in seconds>) = [120]

Device class(es) {DEVICE_CLASS} (<list of dev classes> [USE_AT <weekdays>] [FROM <time> TO <time>]) = [STANDARD]

****** Profile parameters for section ORACLE : ******

Recovery catalog connect string {CATALOG_DATABASE_CONNECT_STRING} = *input mandatory* rcat

Username for Recovery Catalog database {CATALOG_DATABASE_USERNAME} = *input mandatory* rcatowner

Filename of the RMAN backup script {DATABASE_BACKUP_SCRIPT_FILE} = *input mandatory* /orabin/orabase/db/rman_backup_scripts/rman_backup_test

Filename of Oracle(R) parameter file {TARGET_DATABASE_PARAMETER_FILE} = [] /orabin/orabase/db/dbs/inittest.ora

Restore of Oracle control files {DATABASE_CONTROL_FILE_RESTORE} (YES|NO) = [NO] YES

User name of the ASM instance owner {ASM_INSTANCE_USER} (AUTO|<string>) = [AUTO] oracle

SID of the ASM instance {ASM_INSTANCE_ID} = [+ASM]

Role when connecting to ASM instance {ASM_ROLE} (SYSDBA|SYSASM) = [SYSDBA]

****** Profile parameters for section DEVICE_CLASS STANDARD: ******

Type of Storage system {COPYSERVICES_HARDWARE_TYPE} (DS8000|SVC|XIV) = *input mandatory* XIV

Storage system ID of referred cluster {STORAGE_SYSTEM_ID} = [] 1300203

Filepath to XCLI command line tool {PATH_TO_XCLI} = *input mandatory* /opt/xiv/XIVGUI/

Hostname of XIV system {COPYSERVICES_SERVERNAME} = *input mandatory* 9.155.90.180

Username for storage device {COPYSERVICES_USERNAME} = [superuser] oracle

Interval for reconciliation {RECON_INTERVAL} (<hours> ) = [12]

Grace period to retain snapshots {GRACE_PERIOD} (<hours> ) = [24]

Use writable snapshots USE_WRITABLE_SNAPSHOTS (YES|NO|AUTO) = [AUTO]

Use consistency groups USE_CONSISTENCY_GROUPS (YES|NO) = [YES]

Hostname of backup host {BACKUP_HOST_NAME} = []

FMM8426I Saving profile '/oracle/acs/profile' ...

FMM1555I Profile successfully created.

Please enter the password for authentication with the ACS daemon:



Please enter the password for device section STANDARD:

FMM8437I Verifying password...

FMM0005I Start of program at: Mon Nov 30 15:20:18 GMT+01:00 2009 .

FMM0020I End of program at: Mon Nov 30 15:20:33 GMT+01:00 2009 .

FMM0021I Elapsed time: 15 sec .

FMM6959I Script '/opt/XIV/XIVGUI/jre/bin/java -classpath /opt/XIV/XIVGUI/lib/*:/oracle/acs/XivAdapter.jar com.ibm.storage.xiv.XivAdapter -x /opt/XIV/XIVGUI/ -f checkpw' returned with code 0.

Please enter the password required for connecting to ORACLE catalog database:

FMM8437I Verifying password...

Recovery Manager: Release 11.1.0.7.0 - Production on Mon Nov 30 15:21:07 2009

Copyright (c) 1982, 2007, Oracle. All rights reserved.

connected to target database: TEST (DBID=2000816864)

connected to recovery catalog database

RMAN>

Recovery Manager complete.

Creating password file at /oracle/acs/shared/pwd.acsd.

A copy of this file needs to be available to all components that connect to acsd.

IBM Tivoli Storage FlashCopy(R) Manager requires at least two daemon processes to be running at all times.

The management daemon (acsd) and the generic device agent (acsgen) are typically registered in the /etc/inittab on the production server by the configuration wizard.

Both daemon processes restart after a system reboot.

If installing in a High Availability environment, both daemon processes must be started from the High Availability environment.

If you specify YES, these two daemon processes are not be added to the /etc/inittab and the required executable files and command-line options display.

Make sure these two daemon processes are started by the High Availability scripts. If you specify NO, /etc/inittab is used.

Do you want to install in a High Availability environment? [Y/N]

n

A backup system must be installed and configured when off-loaded backups to Tivoli Storage Manager are performed

or when FlashCopy backup consistency verification is needed during a forced mount.

Note that remote connections from the production system to the backup system must already exist to use Open SSH.

Specify YES to use OpenSSH. When prompted to specify which DEVICE_CLASS should be enabled on the backup system,

either select from the list of available DEVICE_CLASS parameters or press Enter to select all listed DEVICE_CLASS parameters.

Specify NO if OpenSSH is not available, the INST_DIR and ACS_DIR use NFS to share between the production



system and backup system,

or you want to configure the backup system in a separate step.

Do you want to install a new Backup System using the Open Secure Shell (OpenSSH) protocol? [Y/N]

N

Backup with acsora

bash-3.00$ ./acsora -f backup

IBM Tivoli Storage FlashCopy(R) Manager for Oracle

- Version 2, Release 1, Level 0.0 for AIX LF 64-bit -

Build: 427 generated on Sep 29 2009

(c) Copyright IBM Corporation, 2000, 2009, All Rights Reserved.

FMM0005I Start of program at: Wed Dec 9 15:35:18 GMT+01:00 2009 .

FMM8800I The command is: backup

FMM0461I Created tracefile '/oracle/acs/logs/client.test.ORCL__.0.20091209153518.trace' for process ID '946370'.

FMM6201I Checking status of database.

FMM6225I Create database parameter file '/orabin/orabase/db/dbs/inittest.ora_fromSPfile' from SPfile.

FMM6223I Detected control file: +ORALOGS/test/control01.ctl



FMM6224I Create control file copy: /orabin/orabase/diag/rdbms/test/test/trace/cntrl_copy_A0G307COMF

FMM1553I RMAN is logging to /oracle/acs/logs/rman.test.20091209153518.log

FMM8300I tsmACSInitialize() returned with code 0.

FMM8300I tsmACSBeginOperation() returned with code 0.


FMM1510I New connection received.

FMM1514I *****> Device client connected.

FMM6219I Backup to Tivoli Storage Manager: YES

FMM6901I Response to Init request.

FMM6902I Response to Partition request.

FMM0461I Created tracefile '/oracle/acs/logs/acsgen.racnode3.DEVICE_CLASS:STANDARD.0.20091209153545.trace' for process ID '676078'.

FMM6269I The diskgroup 'ORADB' with 'EXTERN' redundancy and '2' failure groups has been partitioned with failure groups 'ORADB_0000 ORADB_0001 '.

FMM8300I tsmACSPartition() returned with code 0.

FMM6903I Response to Prepare Flash request.

FMM8300I tsmACSPrepare() returned with code 0.

FMM6230I Set table space files in backup mode.

FMM6212I Suspend database.



FMM6905I Response to Flash request.

FMM0589I Flushing the buffers to disk...

FMM8300I tsmACSSnapshot() returned with code 0.

FMM6214I Resume database.

FMM6231I End backup mode for table space files.

FMM6906I Response to Verify request.

FMM6959I Script '/opt/xiv/XIVGUI/jre/bin/java -classpath /opt/xiv/XIVGUI/lib/*:/oracle/acs/XivAdapter.jar com.ibm.storage.xiv.XivAdapter -x /opt/xiv/XIVGUI/ -t -f backup' returned with code 0.

FMM8300I tsmACSVerify() returned with code 0.

FMM8300I tsmACSStoreMetaData() returned with code 0.

#SAVED ORCL__A0G307COMF +ORADB/test/sysaux01.dbf

#SAVED ORCL__A0G307COMF +ORADB/test/temp01.dbf

#SAVED ORCL__A0G307COMF +ORADB/test/undotbs01.dbf

#SAVED ORCL__A0G307COMF +ORADB/test/users01.dbf

#SAVED ORCL__A0G307COMF +ORADB/test/example01.dbf

#SAVED ORCL__A0G307COMF +ORADB/test/system01.dbf

FMM0020I End of program at: Wed Dec 9 15:37:26 GMT+01:00 2009 .

FMM0021I Elapsed time: 01 min 37 sec .

FMM8300I tsmACSEndOperation() returned with code 0.

FMM8300I tsmACSTerminate() returned with code 0.

FMM6217I Database switched to next logfile.



FMM0024I Return code is: 0.

List of available backups with acsora

bash-3.00$ ./acsora -f inquire_detail






FMM8800I The command is: inquire_detail





FMM8300I tsmACSBeginQuery() returned with code 0.

FMM8300I tsmACSGetNextObject() returned with code 21 (More data available).


FMM8300I tsmACSGetNextObject() returned with code 14 (End of data reached).

FMM8300I tsmACSEndQuery() returned with code 0.

#BACKUP ORCL__A0G307COMF SUCCESSFUL - REPETITIVELY_RESTORABLE ( 0 Bytes of 0 Bytes )

#BACKUP ORCL__A0G305MRHS SUCCESSFUL - REPETITIVELY_RESTORABLE ( 0 Bytes of 0 Bytes )





Restore with acsora

bash-3.00$ ./acsora -f restore






FMM8800I The command is: restore



FMM6232I Looking for the latest backup.








FMM8300I tsmACSRetrieveMetaData() returned with code 0.



FMM8300I tsmACSBeginOperation() returned with code 0.

FMM6233I Restoring backup with ID ORCL__A0G307COMF.


FMM1510I New connection received.

FMM1514I *****> Device client connected.

FMM6901I Response to Init request.

FMM6904I Response to Restore request.



FMM0461I Created tracefile '/oracle/acs/logs/acsgen.racnode3.0.20091209161611.trace' for process ID '950468'.

FMM0511I ====>Performing IBM Tivoli Storage FlashCopy(R) Manager PREPARE SNAP RESTORE command.

FMM6905I Response to Flash request.

FMM0511I ====>Performing IBM Tivoli Storage FlashCopy(R) Manager RESTORE command.

FMM0138I Time stamp: 12/09/09-16:17:07.

FMM0236I Disabling the volumes and filesystems ...

FMM0188I Trying to set the semaphore for the critical part of importing/exporting ...

#UNMOUNTING_FS

FMM2088I The diskgroup 'ORADB' and its online failure groups: 'ORADB_0000' 'ORADB_0001' are now dropped.

FMM0225I Enabling the volumes and filesystems ...

FMM0158I Start of listing of importing volume groups/mounting file systems ...

FMM0591I Bringing up the volume groups...

FMM0189I Semaphore released.

FMM0159I End of listing.

#FS_MOUNTED

FMM0138I Time stamp: 12/09/09-16:17:24.

FMM6907I Response to Complete Restore request.

FMM6959I Script '/opt/xiv/XIVGUI/jre/bin/java -classpath /opt/xiv/XIVGUI/lib/*:/oracle/acs/XivAdapter.jar com.ibm.storage.xiv.XivAdapter -x /opt/xiv/XIVGUI/ -t -f restore' returned with code 0.

FMM8300I tsmACSSnapshot() returned with code 0.

#RESTORED ORCL__A0G307COMF +ORADB/test/sysaux01.dbf

#RESTORED ORCL__A0G307COMF +ORADB/test/temp01.dbf

#RESTORED ORCL__A0G307COMF +ORADB/test/undotbs01.dbf

#RESTORED ORCL__A0G307COMF +ORADB/test/users01.dbf

#RESTORED ORCL__A0G307COMF +ORADB/test/example01.dbf

#RESTORED ORCL__A0G307COMF +ORADB/test/system01.dbf

FMM8300I tsmACSEndOperation() returned with code 0.




FMM6521I Database instance 'test' was started successfully.

FMM6229I Restoring control file +ORALOGS/test/control01.ctl









Configuration changes of FCM for Oracle offloaded backup

$ ./setup_ora.sh

checking /oracle/acs/acsgen ...

OK

Select one of these configurations:

(1) On-Site Production System configuration with optional remote Backup System configuration

(2) On-Site Backup System configuration

Enter '1' to configure IBM Tivoli Storage FlashCopy(R) Manager on the production server with the option to remotely synchronize the configuration of one or multiple backup systems using Secure Shell.

Enter '2' to configure IBM Tivoli Storage FlashCopy(R) Manager on the backup system as a 'separate installation'.

1

Preparing to install on Production System

Found profile /oracle/acs/profile

Do you want to:

(c)reate a new profile

(r)euse the profile unchanged

(m)odify the profile

Please enter one of the strings in parentheses:

m

The management daemon seems to be running.

Do you want me to stop it to proceed with the configuration? [Y/N]

y

Stopping FCM management daemon on your request.

Deactivating FCM management daemon.

Currently off-loaded backups are not configured. Do you want to configure off-loaded backups? [y|n]

y

Welcome to new wizard!

Special commands:

'?' -> Show help for current parameter

'!d' -> Delete current parameter instance (only applicable to multi-instance parameters)

FMM8421I Modifying existing profile '/oracle/acs/profile' for application 'ORACLE' ...

****** Profile parameters for section GLOBAL : ******

Path of the IBM Tivoli Storage FlashCopy(R) Manager directory {ACS_DIR} = [/oracle/acs]

Hostname and port of machine running Management Agent {ACSD} (<hostname> <port>) = [racnode3 57328]



Low level tracing {TRACE} (YES|NO) = [YES]

****** Profile parameters for section ACSD : ******

Path to the repository directory {ACS_REPOSITORY} = [/oracle/acs/acsrepository]

Support for Administration Assistant {ADMIN_ASSISTANT} (<hostname> <port>|NO) = [NO]

Prefix for volume names {REPOSITORY_LABEL} = [TSM]

****** Profile parameters for section OFFLOAD : ******

Synchronize database configuration file on the BS with PS {OVERWRITE_DATABASE_PARAMETER_FILE} (YES|NO) = [YES]

Level of backup {DATABASE_BACKUP_INCREMENTAL_LEVEL} (<number>) = [0]

****** Profile parameters for section CLIENT : ******

Identifier for backups of this database instance in the repository {BACKUPIDPREFIX} (<string>) = [ORCL__]

Suspend target database {TARGET_DATABASE_SUSPEND} (NO|YES|OFFLINE) = [YES]

Used volume manager {VOLUME_MGR} (LVM|ASM) = [ASM]

Create backup from snapshot {TSM_BACKUP} (NO|YES|TSM_ONLY|MANDATE|LATEST [USE_FOR <list of device classes>]) = [YES]

Do you want to add another instance of this parameter? [y, n] n

Maximum number of snapshot versions {MAX_VERSIONS} (<number>|ADAPTIVE) = [ADAPTIVE]

Negative list {NEGATIVE_LIST} (<filename>|NO_CHECK|WARN|ERROR) = [NO_CHECK]

Timeout {TIMEOUT_FLASH} for phase 'flash' (<in seconds>) = [120]

Device class(es) {DEVICE_CLASS} (<list of dev classes> [USE_AT <weekdays>] [FROM <time> TO <time>]) = [STANDARD]

****** Profile parameters for section ORACLE : ******

Recovery catalog connect string {CATALOG_DATABASE_CONNECT_STRING} = [rcat]

Username for Recovery Catalog database {CATALOG_DATABASE_USERNAME} = [rcatowner]

Filename of the RMAN backup script {DATABASE_BACKUP_SCRIPT_FILE} = [/orabin/orabase/db/rman_backup_scripts/rman_backup_test]

Filename of Oracle(R) parameter file {TARGET_DATABASE_PARAMETER_FILE} = [/orabin/orabase/db/dbs/inittest.ora]

Restore of Oracle control files {DATABASE_CONTROL_FILE_RESTORE} (YES|NO) = [YES]

User name of the ASM instance owner {ASM_INSTANCE_USER} (AUTO|<string>) = [oracle]

SID of the ASM instance {ASM_INSTANCE_ID} = [+ASM]

Role when connecting to ASM instance {ASM_ROLE} (SYSDBA|SYSASM) = [SYSDBA]

****** Profile parameters for section DEVICE_CLASS STANDARD: ******

Type of Storage system {COPYSERVICES_HARDWARE_TYPE} (DS8000|SVC|XIV) = [XIV]

Storage system ID of referred cluster {STORAGE_SYSTEM_ID} = [1300203]



Filepath to XCLI command line tool {PATH_TO_XCLI} = [/opt/xiv/XIVGUI/]

Hostname of XIV system {COPYSERVICES_SERVERNAME} = [9.155.90.180]

Username for storage device {COPYSERVICES_USERNAME} = [oracle]

Interval for reconciliation {RECON_INTERVAL} (<hours> ) = [12]

Grace period to retain snapshots {GRACE_PERIOD} (<hours> ) = [24]

Use writable snapshots USE_WRITABLE_SNAPSHOTS (YES|NO|AUTO) = [AUTO]

Use consistency groups USE_CONSISTENCY_GROUPS (YES|NO) = [YES]

Hostname of backup host {BACKUP_HOST_NAME} = [] p570_3_tsm

FMM8426I Saving profile '/oracle/acs/profile' ...

FMM1555I Profile successfully created.

Do you want to continue by specifying passwords for the defined sections? [Y/N]

n

IBM Tivoli Storage FlashCopy(R) Manager requires at least two daemon processes to be running at all times.

The management daemon (acsd) and the generic device agent (acsgen) are typically registered in the /etc/inittab on the production server by the configuration wizard.

Both daemon processes restart after a system reboot.

If installing in a High Availability environment, both daemon processes must be started from the High Availability environment.

If you specify YES, these two daemon processes are not be added to the /etc/inittab and the required executable files and command-line options display.

Make sure these two daemon processes are started by the High Availability scripts. If you specify NO, /etc/inittab is used.

Do you want to install in a High Availability environment? [Y/N]

n

The off-loaded backup to Tivoli Storage Manager will be performed by the IBM Tivoli Storage FlashCopy(R) Manager offload agent 'tsm4acs'.

Specify YES to perform the off-loaded backup immediately after the FlashCopy backup completes. This adds 'tsm4acs' to the /etc/inittab.

The default is to run 'tsm4acs' as a daemon process on the production server.

In High Availability environments, no entry is made to /etc/inittab since 'tsm4acs' must be added to the High Availability script.

Specify NO to schedule off-loaded backups individually with a crontab entry.

Do you want off-loaded tape backups to begin immediately after the snapshot? [Y/N]

n

A backup system must be installed and configured when off-loaded backups to Tivoli Storage Manager are performed

or when FlashCopy backup consistency verification is needed during a forced mount.

Note that remote connections from the production system to the backup system must already exist to use Open SSH.

Specify YES to use OpenSSH. When prompted to specify which DEVICE_CLASS should be enabled on the



backup system,

either select from the list of available DEVICE_CLASS parameters or press Enter to select all listed DEVICE_CLASS parameters.

Specify NO if OpenSSH is not available, the INST_DIR and ACS_DIR use NFS to share between the production system and backup system,

or you want to configure the backup system in a separate step.


y

Please enter the hostname of the backup system:

9.155.57.80

9.155.57.80 is reachable.

Enter the device classes to use for this Backup System. Make sure each device class is separated by a comma.

Here a list of device classes which are defined in the profile: STANDARD

To use all defined device classes just hit enter.

The authenticity of host '9.155.57.80 (9.155.57.80)' can't be established.

RSA key fingerprint is 11:c8:b6:34:66:13:35:d2:a6:d7:5f:28:04:8a:91:9f.

Are you sure you want to continue connecting (yes/no)?yes

Warning: Permanently added '9.155.57.80' (RSA) to the list of known hosts.

[email protected]'s password:

start copying...

copy completed.

start agents

Successfully installed the Backup System.


N

Offload with tsm4acs

bash-3.00$ ./tsm4acs -f tape_backup

IBM Tivoli Storage FlashCopy(R) Manager offload agent





FMM8800I The command is: tape_backup

IBM Tivoli Storage FlashCopy(R) Manager offload agent






FMM0005I Start of program at: Wed Dec 9 15:39:25 2009 .

FMM8800I The command is: tape_backup

FMM6501I Initializing 'mount' request.

FMM6502I Executing 'mount' request.

FMM6555I Selected snapshot backup with ID 'test,ORCL__,A0G307COMF'.

FMM6503I Terminating 'mount' request.

FMM6557I The 'mount' request for database 'ORCL__' processed successfully.

FMM6546I Write database parameter file /orabin/orabase/db/dbs/inittest.ora_fromSPfile

FMM6520I Starting database instance 'test'.

FMM6521I Database instance 'test' was started successfully.

FMM6545I Write control file +ORALOGS/test/control01.ctl




FMM6548I Start backup of database instance 'test'.


FMM6549I Finished backup of database instance 'test' successfully.

FMM6524I Stopping database instance 'test'.

FMM6525I Database instance 'test' was stopped successfully.

FMM6501I Initializing 'unmount' request.

FMM6502I Executing 'unmount' request.

FMM1554W The agent 'acsgen V. 2.1.0.0

' terminated with exit code 1.

FMM6555I Selected snapshot backup with ID 'test,ORCL__,A0G307COMF'.

FMM6503I Terminating 'unmount' request.

FMM6557I The 'unmount' request for database 'ORCL__' processed successfully.

FMM0020I End of program at: Wed Dec 9 15:43:16 2009 .





Logfile: Restore from TSM server with rman

bash-3.00$ cat rman_restore.log

Recovery Manager: Release 11.1.0.7.0 - Production on Thu Dec 10 11:35:52 2009

Copyright (c) 1982, 2007, Oracle. All rights reserved.



connected to target database: TEST (DBID=2000816864, not open)

connected to recovery catalog database

RMAN> run

2> {

3> allocate channel t1 type 'sbt_tape' parms

4> 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';

5> restore database;

6> recover database;

7> alter database open;

8> }

9>

new incarnation of database registered in recovery catalog

starting full resync of recovery catalog

full resync complete

allocated channel: t1

channel t1: SID=149 device type=SBT_TAPE

channel t1: Data Protection for Oracle: version 5.5.1.0

Starting restore at 10-DEC-09

channel t1: starting datafile backup set restore

channel t1: specifying datafile(s) to restore from backup set

channel t1: restoring datafile 00001 to +ORADB/test/system01.dbf

channel t1: restoring datafile 00002 to +ORADB/test/sysaux01.dbf

channel t1: restoring datafile 00003 to +ORADB/test/undotbs01.dbf

channel t1: restoring datafile 00004 to +ORADB/test/users01.dbf

channel t1: restoring datafile 00005 to +ORADB/test/example01.dbf

channel t1: reading from backup piece 1tl0fvhm_1_1

channel t1: piece handle=1tl0fvhm_1_1 tag=TAG20091209T154142

channel t1: restored backup piece 1

channel t1: restore complete, elapsed time: 00:00:45

Finished restore at 10-DEC-09

Starting recover at 10-DEC-09

starting media recovery

archived log for thread 1 with sequence 67 is already on disk as file +ORAFC/test/archivelog/2009_12_09/thread_1_seq_67.394.705169561





archived log file name=+ORAFC/test/archivelog/2009_12_09/thread_1_seq_67.394.705169561 thread=1 sequence=67

media recovery complete, elapsed time: 00:00:23

Finished recover at 10-DEC-09

database opened

released channel: t1

Recovery Manager complete.



Trademarks and special notices © Copyright IBM Corporation 2010. All rights Reserved.

References in this document to IBM products or services do not imply that IBM intends to make them available in every country.

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol (® or ™), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at

www.ibm.com/legal/copytrade.shtml.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

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

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

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

Information is provided "AS IS" without warranty of any kind.

All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics may vary by customer.

Information concerning non-IBM products was obtained from a supplier of these products, published announcement material, or other publicly available sources and does not constitute an endorsement of such products by IBM. Sources for non-IBM list prices and performance numbers are taken from publicly available information, including vendor announcements and vendor worldwide homepages. IBM has not tested these products and cannot confirm the accuracy of performance, capability, or any other claims related to non-IBM products. Questions on the capability of non-IBM products should be addressed to the supplier of those products.

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

best practices for oracle asm on xiv with tivoli flashcopy manager

Documents