HP OpenView Storage Data Protector Integration Guide for Oracle SAP Manual Edition: July 2006 Manufacturing Part Number: B6960-96008 Release A.06.00 © Copyright 2006 Hewlett-Packard Development Company, L.P.
Legal Notices ©Copyright 2006 Hewlett-Packard Development Company, L.P. Hewlett-Packard Company makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.
Contents 1. Integrating Oracle and Data Protector In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Integration Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Configuring the Integration . . . . . . . . . . . . . . . . . . .
Contents Using Oracle After Removing the Data Protector Oracle Integration on UNIX and OpenVMS Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Removing the Data Protector Oracle Integration Link on HP-UX Systems . . . . . . 112 Removing the Data Protector Oracle Integration Link on Solaris and other UNIX Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Backing Up Using Recovery Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Manual Balancing of Files into Subsets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating an SAP /R3 Backup Specification for Manual Balancing . . . . . . . . . . . . . Testing the Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backing Up an SAP R/3 Database . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Setting, Retrieving, and Listing Data Protector SAP DB/MaxDB Configuration File Parameters Using the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260 Configuring the Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263 Configuring Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263 Configuring an SAP DB/MaxDB Backup . . . . . . . . . . .
Printing History Manual updates may be issued between editions to correct errors or document product changes. To ensure that you receive updated or new editions, subscribe to the appropriate product support service. See your HP sales representative for details. Table 1 Edition History Part Number Manual Edition Product B6960-90109 October 2004 Data Protector Release A.05.50 B6960-96008 July 2006 Data Protector Release A.06.
viii
Conventions The following typographical conventions are used in this manual. Table 2 Convention Meaning Example Book or manual titles, and manual page names Refer to the HP OpenView Storage Data Protector Integration Guide for more information. Provides emphasis You must follow these steps. Specifies a variable that you must supply when entering a command At the prompt type: rlogin your_name where you supply your login name. Bold New terms The Data Protector Cell Manager is the main ...
Data Protector provides a cross-platform (Windows and UNIX) graphical user interface. Refer to the online Help for information about the Data Protector graphical user interface.
Contact Information General Information General information about Data Protector can be found at http://www.hp.com/go/dataprotector Technical Support Technical support information can be found at the HP Electronic Support Centers at http://www.itrc.hp.com Information about the latest Data Protector patches can be found at http://www.itrc.hp.com HP does not support third-party hardware and software. Contact the respective vendor for support.
xii
Data Protector Documentation Data Protector documentation comes in the form of manuals and online Help. Manuals Data Protector manuals are available in printed format and in PDF format. Install the PDF files during the Data Protector setup procedure by selecting the User Interface component on Windows or the OB2-DOCS component on UNIX. Once installed, the manuals reside in the \docs directory on Windows and in the /opt/omni/doc/C/ directory on UNIX.
HP OpenView Storage Data Protector Integration Guide This manual describes how to configure and use Data Protector to back up and restore various databases and applications. It is intended for backup administrators or operators.
HP OpenView Storage Data Protector Integration Guide for HP OpenView Operations for UNIX This manual describes how to monitor and manage the health and performance of the Data Protector environment with HP OpenView Operations (OVO), HP OpenView Service Navigator, and HP OpenView Performance (OVP) on UNIX.
SQL Server 2000 databases. The manual also describes how to configure and use Data Protector to perform backup and restore using the Microsoft Volume Shadow Copy Service. HP OpenView Storage Data Protector MPE/iX System User Guide This manual describes how to configure MPE/iX clients and how to back up and restore MPE/iX data. HP OpenView Storage Data Protector Media Operations User's Guide This manual provides tracking and management of offline storage media.
Documentation Map Abbreviations Abbreviations in the documentation map that follows are explained below.
Abbreviation Manual PA Product Announcements, Software Notes, and References Trouble Troubleshooting Guide ZDB Admin ZDB Administrator's Guide ZDB Concpt ZDB Concepts Guide ZDB IG ZDB Integration Guide Map The following table shows where to find information of different kinds. Shaded squares are a good place to look first.
Integrations Look in these manuals for details of the following integrations: Integration Guide HP OpenView Operations (OVO) IG-OVOU, IG-OVOW HP OpenView Reporter (OVR) IG-OV HP OpenView Reporter Light IG-OVOW HP OpenView Service Information Portal (OVSIP) IG-OV HP StorageWorks Disk Array XP all ZDB HP StorageWorks Enterprise Virtual Array (EVA) all ZDB HP StorageWorks Virtual Array (VA) all ZDB IBM DB2 UDB IG-IBM Informix IG-IBM Lotus Notes/Domino IG-IBM Media Operations MO User MPE
xx
In This Book This guide describes how to configure and use Data Protector with Oracle and SAP applications. Audience It is intended for backup administrators responsible for planning, setting up, and maintaining network backups. It assumes you are familiar with: • Basic Data Protector functionality • Database administration Conceptual information can be found in the HP OpenView Storage Data Protector Concepts Guide, which is recommended to fully understand the fundamentals and the model of Data Protector.
Organization The manual is organized as follows: Chapter 1 “Integrating Oracle and Data Protector” on page 1. Chapter 2 “Integrating SAP R/3 and Data Protector” on page 143. Chapter 3 “Integrating SAP DB/MaxDB and Data Protector” on page 249. Glossary Definition of terms used in this manual.
1 Integrating Oracle and Data Protector Chapter 1 1
Integrating Oracle and Data Protector In This Chapter In This Chapter This chapter explains how to configure and use the Data Protector Oracle integration.
Integrating Oracle and Data Protector Introduction Introduction Data Protector offers offline as well as online backup of the Oracle Server instances. To enable recovery from an online backup, the respective Oracle Server instance must operate in the ARCHIVELOG mode. The online backup concept is widely accepted. It addresses the business requirements for high application availability, as opposed to the offline concept.
Integrating Oracle and Data Protector Introduction Restore Types Using the Data Protector Oracle integration, you can restore the following: • The whole database or parts of it • The database to a specific point in time • From incremental backup • To a host other than the one where the database originally resided • A datafile to a location other than its original one • A catalog before restoring the database • From a chain of incremental backups Duplicating a Database Using the Data Protector Oracle inte
Integrating Oracle and Data Protector Integration Concept Integration Concept The Data Protector Oracle integration links the Oracle database management software with Data Protector. From the Oracle point of view, Data Protector represents a media management software. On the other hand, the Oracle database management system can be seen as a data source for backup, using media controlled by Data Protector.
Integrating Oracle and Data Protector Integration Concept The interface from the Oracle server processes to Data Protector is provided by the Data Protector Oracle integration Media Management Library (MML), which is a set of routines that allows the reading and writing of data to General Media Agents. Besides handling direct interaction with the media devices, Data Protector provides scheduling, media management, network backups, monitoring, and interactive backup.
Integrating Oracle and Data Protector Integration Concept These features can be used for online or offline backup of the Oracle target database. However, you must ensure that the backup objects (such as tablespaces) are switched into the appropriate state before and after a backup session. For online backup, the database instance must operate in the ARCHIVELOG mode; whereas for offline backup, objects need to be prepared for backup using the Pre-exec and Post-exec options in the backup specification.
Integrating Oracle and Data Protector Integration Concept Messages from the backup session are sent to the Backup Session Manager, which writes messages and information regarding the backup session to the IDB. The Data Protector General Media Agent writes data to the backup devices. Restore Flow A restore session can be started using: • Data Protector GUI • RMAN CLI • Oracle Enterprise Manager GUI You must specify which objects are to be restored.
Integrating Oracle and Data Protector Integration Concept Figure 1-1 Data Protector Oracle Integration Concept Oracle 10g database files can also be part of ASM configuration. They can reside in the flash recovery area. Legend: SM The Data Protector Session Manager, which can be the Data Protector Backup Session Manager during a backup session and the Data Protector Restore Session Manager during a restore session. RMAN The Oracle Recovery Manager.
Integrating Oracle and Data Protector Integration Concept IDB The IDB where all the information about Data Protector sessions, including session messages, objects, data, used devices, and media is written. MA The Data Protector General Media Agent, which reads and writes data from and to media devices.
Integrating Oracle and Data Protector Configuring the Integration Configuring the Integration Prerequisites • It is assumed that you are familiar with the Oracle database administration and the basic Data Protector functionality. • You need a license to use the Data Protector Oracle integration. See the HP OpenView Storage Data Protector Installation and Licensing Guide for information about licensing.
Integrating Oracle and Data Protector Configuring the Integration See the Oracle Recovery Manager User’s Guide and References for more information about different connection options. See “Troubleshooting” on page 116 for details about how to check the prerequisites listed above. Note that the Data Protector Oracle integration uses RMAN for backup and restore. RMAN connection to a target database requires a dedicated server process.
Integrating Oracle and Data Protector Configuring the Integration • The Data Protector Oracle integration does not support the RMAN disk backup of a target database to the flash recovery area. The Data Protector Oracle integration supports only backups from the flash recovery area to a backup device. However, you can create an RMAN script that backs up the target database to the flash recovery area before or after the Data Protector backs up files from the flash recovery area to a backup device.
Integrating Oracle and Data Protector Configuring the Integration Cluster-Aware Clients If you intend to use the Data Protector CLI, set the Data Protector environment variable OB2BARHOSTNAME to the virtual server name. Set the variable on the Oracle Server system as follows: Windows: set OB2BARHOSTNAME= UNIX: export OB2BARHOSTNAME= RAC: Configure an Oracle database on every node from where you want to run backups and restores.
Integrating Oracle and Data Protector Configuring the Integration The filename for MML depends on the platform: Table 1-1 Filenames for the MML on Different Platforms Platforms 32-bit 64-bit HP-UX libob2oracle8.sl libob2oracle8_64bit.sl HP-UX on IA-64 libob2oracle8.so libob2oracle8_64bit.so Solaris libob2oracle8.so libob2oracle8_64bit.so AIX libob2oracle8.a libob2oracle8_64bit.a Other UNIX libob2oracle8.so libob2oracle8_64bit.so Proceed as follows: 1.
Integrating Oracle and Data Protector Configuring the Integration • 64-bit: ln -s /opt/omni/lib/libob2oracle8_64bit.sl libobk.sl Solaris: • 32-bit: ln -s /optS/omni/lib/libob2oracle8.so libobk.so • 64-bit: ln -s /opt/omni/lib/libob2oracle8_64bit.so libobk.so Other UNIX: • 32-bit: ln -s /opt/omni/lib/libob2oracle8.so libobk.so • 64-bit: ln -s /opt/omni/lib/libob2oracle8_64bit.so libobk.
Integrating Oracle and Data Protector Configuring the Integration ora_olb:libcommon8/lib generic8/libgeneric8/lib • ORA_RDBMS:LORACLE_64.COM Example ora_olb:libclient8_64/lib/incl=(kgu),‘rdbmslib$$’‘plsqllib$$’‘rdbmslib$$’!ora_rman_mml_64/lib,- COMMENT OUT THIS LINE ora_olb:libnro8_64/lib,‘network$$’ora_olb:libtrace8_64/lib,‘oracoreSS’‘cart64$$’ora_olb:libslax8_64/lib,‘utl$$’‘oracore$$’sys$input/options SYS$SHARE:LIBOBK2SHR32_8I.EXE/SHARE,- ADD THIS LINE • ORA_UTIL:LOUTL.
Integrating Oracle and Data Protector Configuring the Integration ‘oracore$$’‘network$$’‘rdbmslib_noshare$$’‘otracelib$$’‘oracore$$’‘rdbmslib_noshare$$’‘oracore$$’‘useroption$$’sys$input/opt SYS$SHARE:LIBOBK2SHR32_8I.EXE/SHARE,- ADD THIS LINE sys$share:decc$shr/share !Temporary: fixup readonly attributes between compiler versions psect_attr = $readonly$,pic,shr 3. Shut down the Oracle database instance on the Oracle Server system. 4.
Integrating Oracle and Data Protector Configuring the Integration When you are prompted for the root directory, enter DISK$ORADISK_ODS5:[ORACLE8.HOME1]. NOTE If loading products from savesets, enter the drive or directory where savesets are located. If loading from a remote device, do not include username and password. For more information, see the Oracle documentation for OpenVMS. When you are back at the main menu, select the option Software Installation and Upgrade Menu.
Integrating Oracle and Data Protector Configuring the Integration 9. Include Java Aurora external option? [Y/N] N The options marked by Y will be selected. Exit the menu to return to Select Configuration Options. Enter the number of the product you want to configure (18 corresponds to RDBMS). In Software Installation and Upgrade Menu, enter 4 to build the selected licensed products (RDBMS). That will initiate the relinking process.
Integrating Oracle and Data Protector Configuring the Integration 2. Check the presence of the MML LIBOBK2SHR32.EXE in the SYS$SHARE: directory. NOTE The logical definition for SYS$SHARE:LIBOBK2SHR32.EXE is $DEFINE/SYSTEM DP_SBT SYS$SHARE:LIBOBK2SHR32.EXE. You are now ready to use the MML with RMAN to perform backups. For information on how to use RMAN, see the Oracle documentation.
Integrating Oracle and Data Protector Configuring the Integration Figure 1-2 Finding the Oracle User The example above states that the user ora has sufficient privileges within the Oracle database to back up and restore the database. Therefore, this user must be added to the corresponding Data Protector user group (admin or operator) and must also become the owner of the backup specification to be able to back up the Oracle database using Data Protector.
Integrating Oracle and Data Protector Configuring the Integration $PIPE@DKC0:[ORACLE9i]ORAUSER.COM > NLA0: • ORATAB Depending on the current location of ORATAB, modify $DEFINE/NOLOG/JOB ORATAB_LOC DKA0:[ORACLE]ORATAB accordingly. For example, if ORATAB is located in DKC0:[ORACLE9i], the changes will be: $DEFINE/NOLOG/JOB ORATAB_LOC DKCF0:[ORACLE9i]ORATAB Oracle 8i Execute the OMNI$ROOT:[BIN]DP_ORA8I_RENAME.COM command. This will update the required Oracle8i executables. 2.
Integrating Oracle and Data Protector Configuring the Integration 4. Oracle 8i/9i If you use CLI commands for Oracle integration agents, execute OMNI$ROOT:[LOG]LOGIN.COM. 5. Oracle 8i/9i Verify that the -key Oracle8 entry is present in OMNI$ROOT:[CONFIG.CLIENT]ONMI_INFO, for example: -key oracle8 -desc "Oracle Integration" -nlsset 159 -nlsId 12172 -flags 0x7 -ntpath "" -uxpath "" -version A.06.00 If the entry is not present, copy it from OMNI$ROOT:[CONFIG.CLIENT]OMNI_FORMAT.
Integrating Oracle and Data Protector Configuring the Integration Using the Data Protector GUI Configure an Oracle database when you create first backup specification for the database. Start with the procedure “Creating a Data Protector Oracle Backup Specification” on page 37 and at step 5 proceed as follows: 1. In the Configure Oracle dialog box and in the General page, specify the pathname of the Oracle Server home directory.
Integrating Oracle and Data Protector Configuring the Integration Figure 1-4 Configuring Oracle - General (UNIX) 2. In the Primary page, specify the login information to the primary database. Note that the user must have the SYSDBA privilege granted. In Services, type the net service name for the primary database instance. The backup will be performed on the system where this database instance resides.
Integrating Oracle and Data Protector Configuring the Integration Figure 1-5 Configuring Oracle - Primary 3. In the Catalog page, select Use target database control file instead of recovery catalog to use the primary database control file. To use the recovery database catalog as an RMAN repository for backup history, select Use recovery catalog and specify the login information to the recovery catalog. Oracle Data Guard: If you intend to back up a standby database, you must use the recovery catalog.
Integrating Oracle and Data Protector Configuring the Integration Figure 1-6 Configuring Oracle - Catalog 4. Oracle Data Guard: If you intend to back up a standby database, configure also the standby database: In the Standby page, select Configure standby database and specify the login information to the standby database. In Services, type the net service name for the standby database instance.
Integrating Oracle and Data Protector Configuring the Integration Figure 1-7 Configuring Oracle - Standby 5. Click OK. The Oracle database is configured. Exit the GUI or proceed with creating the backup specification at step 6 on page 1-40. Using the Data Protector CLI NOTE On OpenVMS, to invoke the Data Protector CLI, run: $@OMNI$ROOT:[BIN]OMNI$CLI_SETUP.COM 1.
Integrating Oracle and Data Protector Configuring the Integration On Windows: perl -I..\lib\perl util_oracle8.pl -config -dbname -orahome [] [][-client ] On UNIX and OpenVMS: util_oracle8.
Integrating Oracle and Data Protector Configuring the Integration Parameter Description Name of the Oracle Server system with the database to be configured. It needs to be specified only in a cluster environment. RAC: Name of the node or the virtual server of the Oracle resource group. The latter can only be used on HP-UX. Oracle Data Guard: Name of either a primary system or secondary (standby) system. Name of the database to be configured.
Integrating Oracle and Data Protector Configuring the Integration Example The following example represents configuration on HP-UX or Solaris of an Oracle database and its recovery catalog in Oracle Data Guard environment.
Integrating Oracle and Data Protector Configuring the Integration If the recovery catalog was selected, util_oracle8.pl starts the Oracle RMAN command, which registers the target database in the recovery catalog. Information about the Oracle database’s structure is transferred to the recovery catalog from the Oracle database’s control files. Checking the Configuration You can check the configuration of an Oracle database after you have created at least one backup specification for the database.
Integrating Oracle and Data Protector Configuring the Integration On Windows: perl -I..\lib\perl util_oracle8.pl -CHKCONF -dbname On UNIX and OpenVMS: util_oracle8.pl -CHKCONF -dbname Handling Errors If an error occurs, the error number is displayed in the form *RETVAL*. To get the error description: Windows: On the Cell Manager, see the file \help\enu\Trouble.
Integrating Oracle and Data Protector Configuring the Integration IMPORTANT On UNIX, it is possible that although the GUI check returns a successful result, you may still receive the error 12:8300 when trying to start a backup session. Such a backup session will not start. For more information, see “Troubleshooting” on page 116.
Integrating Oracle and Data Protector Configuring an Oracle Backup Configuring an Oracle Backup To configure an Oracle backup, perform the following steps: 1. Configure the devices you plan to use for a backup. See the online Help index: “configuring devices” for instructions. 2. Configure media pools and media for a backup. See the online Help index: “creating media pools” for instructions. 3. Create a Data Protector Oracle backup specification.
Integrating Oracle and Data Protector Configuring an Oracle Backup To create a new backup template, proceed as follows: 1. In the Data Protector Manager, switch to the Backup context. 2. In the Scoping Pane, expand Backup and then Templates, and then right-click Oracle Server. 3. Click Add Template. Follow the wizard to define the appropriate backup options in your template. Creating a Data Protector Oracle Backup Specification To create an Oracle backup specification, proceed as follows: 1.
Integrating Oracle and Data Protector Configuring an Oracle Backup Database_Switch_ArchiveDel Backs up the database instance, switches the Online Redo Logs, backs up the Archived Redo Logs and then deletes the Archived Redo Logs. Direct_Database Backs up the database instance and controlfile. SMB_Proxy_Database Backs up the database instance and control file in the ZDB (split mirror or snapshot) mode using the proxy-copy method.
Integrating Oracle and Data Protector Configuring an Oracle Backup UNIX only: Type the username and user group of the Oracle user. See “Configuring Oracle Users on UNIX and OpenVMS” on page 21 for information on how to identify that user.
Integrating Oracle and Data Protector Configuring an Oracle Backup Figure 1-9 Specifying an Oracle Server System (UNIX) Click Next. 5. If the Oracle database is not configured yet for use with Data Protector, the Configure Oracle dialog box is displayed. Configure the Oracle database for use with Data Protector as described in “Configuring Oracle Databases” on page 24. 6. Select the Oracle database objects to be backed up.
Integrating Oracle and Data Protector Configuring an Oracle Backup NOTE If your database uses a recovery catalog, it is backed up by default after each database backup, unless otherwise specified in the backup specification. Figure 1-10 Selecting Backup Objects Click Next. 7. Select the device(s) you want to use for the backup. Click Properties to set the device concurrency, media pool, and preallocation policy. For more information on these options, click Help.
Integrating Oracle and Data Protector Configuring an Oracle Backup 8. Set the backup options. For information on the Backup Specification Options and Common Application Options, see the online Help. Oracle Data Guard: To back up a standby database, you must select Back up standby database in the Application Specific Options dialog box. For information on the Application Specific Options (Figure 1-11), see Table 1-2 on page 44 or online Help.
Integrating Oracle and Data Protector Configuring an Oracle Backup Figure 1-11 Oracle Specific Options Click Next. 9. Optionally, schedule the backup. For more details, see “Scheduling a Backup” on page 58. Click Next. 10. Save the backup specification. It is recommended that you save all Oracle backup specifications in the Oracle group. IMPORTANT The word DEFAULT is a reserved word and therefore must not be used for backup specification names or labels of any kind.
Integrating Oracle and Data Protector Configuring an Oracle Backup Figure 1-12 Saving the Backup Specification Click OK. To start the backup, see “Backing Up an Oracle Database” on page 55. 11. On UNIX, after the backup specification is saved, verify that the owner of the backup specification is the specified Oracle user. See “Configuring Oracle Users on UNIX and OpenVMS” on page 21 for details about this user. 12.
Integrating Oracle and Data Protector Configuring an Oracle Backup Table 1-2 Oracle Backup Options Disable Data Protector managed control file backup By default, Data Protector backs up the Data Protector managed control file in every backup session. Select this option to disable backup of the Data Protector managed control file. Back up standby database Oracle Data Guard: This option is applicable if the database is configured with the standby connection.
Integrating Oracle and Data Protector Configuring an Oracle Backup Examples of Pre-Exec and Post-Exec Scripts on UNIX Pre-Exec Example The following is an example of a script that shuts down an Oracle instance: #!/bin/sh export ORACLE_HOME=$2 export ORACLE_SQLNET_NAME=$1 if [ -f $ORACLE_HOME/bin/sqlplus ]; then $ORACLE_HOME/bin/sqlplus << EOF connect sys/manager@$ORACLE_SQLNET_NAME as sysdba shutdown EOF echo "Oracle database \"$DB_NAME\" shut down.
Integrating Oracle and Data Protector Configuring an Oracle Backup ($ORACLE_HOME/bin/sqlplus)." exit 1 fi Editing the Oracle RMAN Script The RMAN script is used when the Data Protector backup specification is started to perform a backup of the Oracle objects. The RMAN script section is not written to the backup specification until the backup specification is either saved or manually edited by clicking the Edit button.
Integrating Oracle and Data Protector Configuring an Oracle Backup If the RMAN script contains additional manually entered backup commands, for example a second backup command for backing up a database that is already listed in the first backup command, the object selection is disabled and it is only possible to browse the Source tab.
Integrating Oracle and Data Protector Configuring an Oracle Backup • Depending on the backup objects selection, an RMAN backup statement for the backup of the whole database instance, and/or for any combination of RMAN commands to back up tablespaces, datafile, or the flash recovery area. The backup statement consists of the following: — The Oracle format of the backup file in the following format: format '<_%s:%t:%p>.
Integrating Oracle and Data Protector Configuring an Oracle Backup If an appropriate template was selected, or if the statement was manually added, the RMAN statement to delete the Archived Redo Logs after they are backed up: archivelog all delete input; • If the control file was selected for a backup, an RMAN backup statement for the backup of Oracle control files.
Integrating Oracle and Data Protector Configuring an Oracle Backup backup format 'New1.dbf' current controlfile ; } Creating Copies of Backed Up Objects Oracle Duplex Mode Oracle support the duplex mode, which allows you to create copies of every backed up object to a separate backup device. To enable the duplex feature, perform the following steps: 1. Add the following command to the RMAN script before any allocate channel command: set duplex=
Integrating Oracle and Data Protector Configuring an Oracle Backup Testing the Integration Once you have created and saved a backup specification, you should test it before running a backup. The test verifies both parts of the integration, the Oracle side and the Data Protector side. In addition, the configuration is tested as well.
Integrating Oracle and Data Protector Configuring an Oracle Backup Figure 1-13 Previewing a Backup Testing Using the CLI A test can be executed from the command line on the Oracle Server system or on any Data Protector client system within the same Data Protector cell, provided that the system has the Data Protector User Interface installed. NOTE On OpenVMS, to invoke the Data Protector CLI, execute: $@OMNI$ROOT:[BIN]OMNI$CLI_SETUP.
Integrating Oracle and Data Protector Configuring an Oracle Backup • On HP-UX and Solaris: /opt/omni/bin/omnib -oracle8_list \ -test_bar • On other UNIX systems: /usr/omni/bin/omnib -oracle8_list \ -test_bar • On OpenVMS: $omnib -oracle8_l qist -test_bar The ob2rman.pl command is started, which then starts the BACKUP VALIDATE DATABASE RMAN command.
Integrating Oracle and Data Protector Backing Up an Oracle Database Backing Up an Oracle Database There are two strategies for backing up a database. These are an offline or consistent database backup, and an online or inconsistent database backup. The latter is also known as a hot backup. Special attention is required to reach a consistent state with an online backup. A decision about your database backup strategy depends on a number of factors.
Integrating Oracle and Data Protector Backing Up an Oracle Database Oracle Online As opposed to an offline backup, an online backup is performed when a database is open. The backup of an open database is inconsistent, because portions of the database are being modified and written to disk while the backup is progressing. Such changes to the database are entered into the online redo logs as well. A database running in the ARCHIVELOG mode enables the archiving of the online redo logs.
Integrating Oracle and Data Protector Backing Up an Oracle Database 3. Start SQL*Plus and type: alter database archivelog; alter database open; alter system archive log start SCOPE=SPFILE; If PFILE is used: 1. Shut down the database. 2. Change PFILE to enable log archiving by setting: log_archive_start = true 3. Mount the database. 4.
Integrating Oracle and Data Protector Backing Up an Oracle Database • Start a backup on the Oracle server using either Oracle Recovery Manager or Oracle Enterprise Manager. See “Starting Oracle Backup Using RMAN” on page 62. Backup Procedure The following happens when you start a backup using the Data Protector user interface: 1. Data Protector executes ob2rman.pl on the client. This command starts RMAN and sends the Oracle RMAN Backup Command Script to the standard input of the RMAN command. 2.
Integrating Oracle and Data Protector Backing Up an Oracle Database For example, you may decide to perform daily backups and make multiple copies of the online redo logs and the Archived Redo Logs to several different locations. An example of scheduling backups of production databases: • Weekly full backup • Daily incremental backup • Archived Log backups as needed To schedule an Oracle backup specification, proceed as follows: 1.
Integrating Oracle and Data Protector Backing Up an Oracle Database Figure 1-14 Scheduling Backups Click OK and then Apply to save the changes. Running an Interactive Backup An interactive backup can be performed any time after a backup specification has been created and saved. You can use the Data Protector GUI or CLI. Starting a Backup Using the GUI To start an interactive backup of an Oracle database using the Data Protector GUI, proceed as follows: 1.
Integrating Oracle and Data Protector Backing Up an Oracle Database Note that the backup type can be full or incremental, with the incremental level as high as Incr 4. See Figure 1-14 on page 60. See the RMAN documentation for details on incremental backup levels. Click OK. Figure 1-15 Starting an Interactive Backup Starting a Backup Using the CLI 1.
Integrating Oracle and Data Protector Backing Up an Oracle Database You can select among the following list_options: -protect {none | weeks n | days n | until date | permanent} -load {low | medium | high} -crc -no_monitor Oracle8Mode = {-full | -incr1 | -incr2 | -incr3 | -incr4} See the omnib man page for details.
Integrating Oracle and Data Protector Backing Up an Oracle Database b. Execute $rman target catalog . Oracle 8i: Use rcvcat instead of catalog in the above syntax. If you do not use the recovery catalog: • On Windows: \bin\rman target nocatalog • On UNIX: /bin/rman target nocatalog • On OpenVMS: a. Run ORAUSER.COM using $@OMNI$ROOT:[LOG]LOGIN.COM. b.
Integrating Oracle and Data Protector Backing Up an Oracle Database 2. Allocate the Oracle channels. Allocating a channel tells RMAN to initiate an Oracle Server process for backup, restore, or recovery on the Oracle target database. For example: allocate channel 'dev_0' type 'disk'; or allocate channel 'dev_1' type 'sbt_tape'; where you specify the backup directly to disk in the first case and directly to tape in the second case.
Integrating Oracle and Data Protector Backing Up an Oracle Database For example, if you have created and saved a backup specification named bspec1 for backing up an Oracle database identified by the Oracle instance called inst1, you would enter the following string: format 'bspec1.dbf' See the Oracle Recovery Manager User’s Guide and References for information on substitution variables. The Oracle channel format specifies which Oracle backup specification to use for the backup. 5.
Integrating Oracle and Data Protector Backing Up an Oracle Database Examples of the RMAN Scripts Some examples of RMAN scripts that must be executed from the RMAN> prompt are listed below: Backing Up a Single Channel To back up the Oracle instance ORACL, using a backup specification named ora1, enter the following command sequence: run { allocate channel 'dev_0' type 'sbt_tape' parms'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=ORACL,OB2BARLIST=ora1)'; backup incremental level 0 format 'oracl1.
Integrating Oracle and Data Protector Backing Up an Oracle Database allocate channel 'dev_2' type 'sbt_tape' parms'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=ORACL,OB2BARLIST=ora1)'; backup incremental level 0 format 'ora1.dbf' tablespace SYSTEM, RONA sql 'alter system archive log current' format 'ora1.
Integrating Oracle and Data Protector Backing Up an Oracle Database parms'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=ORACL,OB2BARLIST=ora1)'; backup format 'ora1.dbf' recovery area; } Including Control File in a Backup Specification The current control file is automatically backed up when the first datafile of the system tablespace is backed up. The current control file can also be explicitly included in a backup, or backed up individually.
Integrating Oracle and Data Protector Backing Up an Oracle Database parms'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=ORACL,OB2BARLIST=ora1)'; allocate channel 'dev_2' type 'sbt_tape' parms'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=ORACL,OB2BARLIST=ora1)'; backup incremental level 0 format 'ora1.dbf' database; } On Windows run { set maxcorrupt for datafile 'C:\oracle\data1.
Integrating Oracle and Data Protector Restoring an Oracle Database Restoring an Oracle Database You can restore the database objects using: • Data Protector GUI. See “Restoring Oracle Using the Data Protector GUI” on page 72. • RMAN. See “Restoring Oracle Using RMAN” on page 93.
Integrating Oracle and Data Protector Restoring an Oracle Database Figure 1-16 Taking the Oracle Resource Group Offline Verify that you have set the Prevent Failback option for the Oracle resource group and Do not restart for the .world resource, which is an Oracle Database resource. Figure 1-17 Checking Properties MC/ServiceGuard Clients When restoring the database from a backup performed on a virtual host, you should set OB2BARHOSTNAME environment variable in the RMAN script.
Integrating Oracle and Data Protector Restoring an Oracle Database allocate channel dev1 type 'sbt_tape' parms'ENV=(OB2BARHOSTNAME=virtual.domain.com)'; restore datafile '/opt/ora9i/oradata/MAKI/example02.dbf'; release channel dev1; } Prerequisites • An instance of Oracle must be created on the system to which you want to restore or duplicate the database.
Integrating Oracle and Data Protector Restoring an Oracle Database • Oracle 9i/10g: 1. Restore the control file from automatic backup. If no automatic backup of the control file is available, see problem “The Recovery Catalog was lost and the control file cannot be restored from Data Protector managed backup” on page 139. 2. Restore the database or data items.
Integrating Oracle and Data Protector Restoring an Oracle Database Restoring the Recovery Catalog Database The Oracle recovery catalog database is exported using the Oracle export utility to a binary file and backed up by Data Protector. This file has to be restored back to the disk and then imported into the Oracle database using the Oracle import utility. Data Protector provides a facility to do this automatically using the Oracle integration. To restore the recovery catalog database: 1.
Integrating Oracle and Data Protector Restoring an Oracle Database Figure 1-18 Recovery Catalog Settings Dialog 5. In the Options page: In User name and User group, specify the user name and password to the recovery catalog database. From the Session ID drop-down list, select the Session ID. For further information, see “Restore, Recovery, and Duplicate Options” on page 88. 6. Click Restore. Proceed to restore the control file.
Integrating Oracle and Data Protector Restoring an Oracle Database Restoring the Control File The control file contains all the information about the database structure. If the control file has been lost, you must restore it before you restore any other part of the database. The database should be in the NoMount state.
Integrating Oracle and Data Protector Restoring an Oracle Database IMPORTANT Ensure that you have properly configured the RMAN autobackup and that the correct backup version is available. If the RMAN autobackup session is not found during the restore, the procedure is aborted. See the Oracle 9i/10g documentation on how to set up RMAN AUTOBACKUP. • Restoring from RMAN backup set (CONTROLFILE FROM RMAN BACKUPSET) The recovery catalog is required.
Integrating Oracle and Data Protector Restoring an Oracle Database Set the other restore options. See “Restore, Recovery, and Duplicate Options” on page 88 for information. 6. Click Restore. Proceed with restoring the Oracle database objects. Restoring Oracle Database Objects Before you restore Oracle database objects, ensure that you have an up-to-date version of the recovery catalog database and the control file. They contain the database structure information.
Integrating Oracle and Data Protector Restoring an Oracle Database Figure 1-19 Source Page 6. In the Results Area, select objects for restore. If you are restoring datafiles, you can restore the files to a new location. Right-click the database object, click Restore As, and in the Restore As dialog box, specify the new datafile location.
Integrating Oracle and Data Protector Restoring an Oracle Database TIP The same can be done if you set the DB_FILE_NAME_CONVERT initialization parameter. This parameter captures all the target datafiles and converts them appropriately. 7. In the Options page, from the Client drop-down list, select the client on which the Data Protector Oracle integration agent will be started.
Integrating Oracle and Data Protector Restoring an Oracle Database Figure 1-20 Options Page 8. In the Devices page, select the devices to be used for the restore. You can restore using a device other than that used for backup, although Data Protector defaults to the original device on which the backup was made. To change the device from which an item is restored, select your desired device and click Change. For more information on the Devices page, press F1.
Integrating Oracle and Data Protector Restoring an Oracle Database Figure 1-21 Devices Page 9. Click Restore. After the restore: 1. Put the database in the correct state. If you selected Perform Restore and Recovery or Perform Recovery Only in the Source page, then the database is automatically put into Open state by Data Protector. 2.
Integrating Oracle and Data Protector Restoring an Oracle Database Oracle 8i: Use rcvcat instead of catalog in the above syntax. 3. If you did not choose to use Data Protector to recover the database objects and if you have all archived redo logs on disk, perform the following after the database is restored: Open a command line window and enter the following commands: sqlplus /nolog SQL>recover database; SQL>connect /@ as sysdba; SQL>alter database open; 4.
Integrating Oracle and Data Protector Restoring an Oracle Database If you are restoring a tablespace enter: SQL>alter tablespace online; Restoring and Recovering an Oracle Database in Oracle Data Guard Environment Restoring and Recovering a Primary Database You can restore and recover a primary database from backups done on either a primary or standby database. The restore and recover is almost the same as restore and recover of a database in a standalone configuration.
Integrating Oracle and Data Protector Restoring an Oracle Database • Failover of database roles occurred. Duplicating an Oracle Database Perform a production database duplication to create: • A standby database which has the same DBID as the production (primary) database. With this, you can: — Create a new standby database.
Integrating Oracle and Data Protector Restoring an Oracle Database databases when the duplicate database resides in the same Oracle home directory as the target database. Note also that if the duplicate database resides in a different Oracle home directory than the target database, then the duplicate database name has to differ from other database names in that same Oracle home directory. To duplicate a production database: 1.
Integrating Oracle and Data Protector Restoring an Oracle Database Figure 1-22 Oracle Duplicate Options 6. Click Restore. When the standby database is created, it is left mounted. Start the managed recovery process (log apply services) manually. For information on how to use the RMAN commands to duplicate a database, see Oracle documentation.
Integrating Oracle and Data Protector Restoring an Oracle Database Restore, Recovery, and Duplicate Options Restore Action Options The following describes each of the options in the Source page. This page is used to define the combination of restore and recovery you would like to perform using the GUI. In the context of Data Protector “restore” means to restore the datafiles.
Integrating Oracle and Data Protector Restoring an Oracle Database General Options Client This option specifies the client on which the Data Protector Oracle integration agent (ob2rman.pl) will be started. Settings Click Settings to specify the login information (user name, password, and net service name) for the target database (in case of restore and recovery) or auxiliary database (in case of duplication) where you want the selected database objects to be restored or duplicated.
Integrating Oracle and Data Protector Restoring an Oracle Database restore you would like perform. The options are: • Normal This option should be used when a conventional backup or ZDB using the backup set method was performed with version of Data Protector older than A.05.00. • Proxy copy This option should be used when the original Oracle backup was made using the Oracle RMAN proxy-copy method, such as ZDB of Oracle 8i/9i using Data Protector version A.05.10.
Integrating Oracle and Data Protector Restoring an Oracle Database Select this option if you want RMAN to recover the database after creating it. To database name Select this option to create a new database copy. In the text box, specify its name. The name should match the name in the initialization parameter file that was used to start the auxiliary database instance. By default, the database name is set to the database name of the currently selected target database.
Integrating Oracle and Data Protector Restoring an Oracle Database limit of redo logs to restore. Data Protector restores the backup that can be used in recovery to the specified log sequence number. • Selected SCN number Use this option to specify the SCN number to which you wish the database to be restored. Data Protector restores the backup that can be used in recovery to the specified SCN number.
Integrating Oracle and Data Protector Restoring an Oracle Database RMAN> RESET DATABASE; RMAN> exit Oracle 8i: Use rcvcat instead of catalog in the above syntax. Open database after recovery Opens the database after a recovery is performed. Reset logs Resets the archive logs after the database is opened. Always reset the logs: • After an incomplete recovery. • If a backup of a control file is used in recovery or restore and recovery.
Integrating Oracle and Data Protector Restoring an Oracle Database This section only describes examples of how you can perform a restore. The examples provided do not apply to all situations where a restore is needed. See the Oracle Recovery Manager User’s Guide and References for detailed information on how to perform: • Restore and recovery of the database, tablespace, control file, and datafile. • Duplication of a database.
Integrating Oracle and Data Protector Restoring an Oracle Database • Control files must be available. If the control files are not available, you must restore them. See the Oracle Recovery Manager User’s Guide and References for more details. If you have to perform a restore of the recovery catalog databaseor control files, you must perform this restore first. Only then can you perform a restore of other parts of the Oracle database.
Integrating Oracle and Data Protector Restoring an Oracle Database NLS_DATE_FORMAT='Mon DD YYYY HH24:MI:SS' OpenVMS Example ORACLE_HOME=DKA400:[ORACLE9I] ORACLE_TERM=hp DB_NAME=PROD • Check that the /etc/oratab file has the following line: Windows: PROD:\product\10.1.0:N UNIX: PROD:/opt/oracle/product/10.1.0:N OpenVMS: — Oracle 9i: /oratab TEST:/DKA400/ORACLE9I:N CAT:/DKA400/ORACLE9I:N — Oracle 8i: /rdbms/ORA_RDBMS_SIDS.
Integrating Oracle and Data Protector Restoring an Oracle Database Example of Full Database Restore and Recovery To perform a full database restore and recovery, you also need to restore and apply all the archive logs. To perform a full database restore and recovery: 1.
Integrating Oracle and Data Protector Restoring an Oracle Database You can also save the script into a file and perform a full database restore using the saved files. The procedure in such cases is as follows: 1. Create a file restore_database in the /var/opt/omni/tmp (UNIX systems) or \tmp directory. 2.
Integrating Oracle and Data Protector Restoring an Oracle Database • On OpenVMS: rman target sys/manager@PROD sys/manager@PROD catalog rman/rman@CAT Oracle 8i: Use rcvcat instead of catalog in the above syntax. If you do not use the recovery catalog, run: • On Windows: \bin\rman target sys/manager@PROD nocatalog • On UNIX: /bin/rman target sys/manager@PROD nocatalog • On OpenVMS: rman target sys/manager@PROD nocatalog 2.
Integrating Oracle and Data Protector Restoring an Oracle Database • On Windows: \bin\rman target sys/manager@PROD catalog rman/rman@CATAL cmdfile=\tmp\restore_PIT • On UNIX: /bin/rman target sys/manager@PROD catalog rman/rman@CATAL cmdfile=/var/opt/omni/tmp/restore_PIT Oracle 8i: Use rcvcat instead of catalog in the above syntax.
Integrating Oracle and Data Protector Restoring an Oracle Database • On Windows: \bin\rman target sys/manager@PROD nocatalog • On UNIX: /bin/rman target sys/manager@PROD nocatalog • On OpenVMS: rman target sys/manager@PROD nocatalog 2. Start the tablespace restore and recovery.
Integrating Oracle and Data Protector Restoring an Oracle Database 2. Start the tablespace restore. If you use the recovery catalog database, run: Oracle 9i/10g: • On Windows: \bin\rman target sys/manager@PROD catalog rman/rman@CATAL cmdfile=\tmp\restore_TAB • On UNIX: /bin/rman target sys/manager@PROD catalog rman/rman@CATAL cmdfile=/var/opt/omni/tmp/restore_TAB Oracle 8i: Use rcvcat instead of catalog in the above syntax.
Integrating Oracle and Data Protector Restoring an Oracle Database Use rcvcat instead of catalog in the above syntax. If you do not use the recovery catalog database, run: • On Windows: \bin\rman target sys/manager@PROD nocatalog • On UNIX: /bin/rman target sys/manager@PROD nocatalog • On OpenVMS: rman target sys/manager@PROD nocatalog 2.
Integrating Oracle and Data Protector Restoring an Oracle Database ''C:\oracle\data\oradata\DATA\temp01.dbf'' online"; release channel dev1; } • If the database is in a mount state, the script to restore and recover the datafile should have the following format: UNIX run{ allocate channel dev1 type 'sbt_tape' parms 'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=)'; restore datafile '/opt/oracle/data/oradata/DATA/temp01.dbf'; recover datafile '/opt/oracle/data/oradata/DATA/temp01.
Integrating Oracle and Data Protector Restoring an Oracle Database • On Windows: /bin/rman target sys/manager@PROD catalog rman/rman@CATAL cmdfile=/var/opt/omni/tmp/restore_dbf • On UNIX: \bin\rman target sys/manager@PROD catalog rman/rman@CATAL cmdfile=\tmp\restore_dbf Oracle 8i: Use rcvcat instead of catalog in the above syntax.
Integrating Oracle and Data Protector Restoring an Oracle Database • On UNIX: /bin/rman target sys/manager@PROD nocatalog • On OpenVMS: rman target sys/manager@PROD nocatalog 2. Start the archive log restore: run{ allocate channel dev1 type 'sbt_tape' parms 'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=)'; restore archivelog all; release channel dev1; } You can also save the script into a file and perform an archive log restore using the saved files: 1.
Integrating Oracle and Data Protector Restoring an Oracle Database Restoring Oracle Using CLI Restoring the Recovery Catalog Data Protector can restore the binary file which contains the logical backups of the Oracle recovery catalog. This file is made using the Oracle Export utility, which creates it by reading the Oracle database and writing the output to the binary file, which is then backed up by Data Protector.
Integrating Oracle and Data Protector Restoring an Oracle Database 3. Run: Windows: From the \bin directory: perl -I..\lib\perl ob2rman.pl -restore_catalog -session [-apphost ] HP-UX and Solaris: /opt/omni/lbin/ob2rman.pl -restore_catalog -session [-apphost ] Other UNIX: /usr/omni/bin/ob2rman.pl -restore_catalog -session [-apphost ] OpenVMS: $@OMNI$ROOT:[BIN]OMNI$CLI_SETUP.
Integrating Oracle and Data Protector Restoring an Oracle Database Example Suppose you have Oracle objects backed up on a device called DAT1. To restore them from a device named DAT2, specify the following in the restoredev file: "DAT1" "DAT2" Disaster Recovery Disaster recovery is a very complex process that involves products from several vendors. As such, successful disaster recovery depends on all the vendors involved. The information provided here is intended to be used as a guideline.
Integrating Oracle and Data Protector Monitoring an Oracle Backup and Restore Monitoring an Oracle Backup and Restore During a backup, system messages are sent to the Data Protector monitor. You can monitor the backup session from any Data Protector client on the network where the Data Protector User Interface is installed. Monitoring Current Sessions To monitor a currently running session using the Data Protector GUI, proceed as follows: 1. In the Context List, click Monitor.
Integrating Oracle and Data Protector Monitoring an Oracle Backup and Restore Viewing Previous Sessions To view a previous session using the Data Protector GUI, proceed as follows: 1. In the Context List, click Internal Database. 2. In the Scoping Pane, expand Sessions to display all the sessions stored in the IDB. The sessions are sorted by date. Each session is identified by a session ID consisting of a date in the YY/MM/DD format and a unique number. 3.
Integrating Oracle and Data Protector Using Oracle After Removing the Data Protector Oracle Integration on UNIX and OpenVMS Systems Using Oracle After Removing the Data Protector Oracle Integration on UNIX and OpenVMS Systems After uninstalling the Data Protector Oracle integration on an Oracle server system, the Oracle server software is still linked to MML. You must re-link the Oracle binary to remove this link.
Integrating Oracle and Data Protector Using Oracle After Removing the Data Protector Oracle Integration on UNIX and OpenVMS Systems Removing the Data Protector Oracle Integration Link on Solaris and other UNIX Systems To remove the Data Protector Oracle integration link on Solaris and other UNIX systems: 1. Change to the /lib directory: cd /lib (32-bit Oracle), cd /lib64 (64-bit Oracle 8i) or cd /lib (64-bit Oracle 9i/10g). 2. If the libobk.so.
Integrating Oracle and Data Protector Oracle RMAN Metadata and Data Protector Media Management Database Synchronization Oracle RMAN Metadata and Data Protector Media Management Database Synchronization This section describes how to synchronize the Oracle RMAN metadata with the Data Protector Media Management Database. The RMAN metadata contains information about the target database. RMAN uses this information for all backup, restore and maintenance operations.
Integrating Oracle and Data Protector Oracle RMAN Metadata and Data Protector Media Management Database Synchronization TIP It is recommended that synchronization be performed in the following cases: • after a Data Protector import or export of media with Oracle objects and • whenever protection for media with Oracle objects has expired.
Integrating Oracle and Data Protector Troubleshooting Troubleshooting This section lists general checks and verifications, and problems you might encounter when using the Data Protector Oracle integration. For general Data Protector troubleshooting information, see the HP OpenView Storage Data Protector Troubleshooting Guide. Before You Begin ✓ Ensure that the latest official Data Protector patches are installed. See the online Help index: “patches” on how to verify this.
Integrating Oracle and Data Protector Troubleshooting General Troubleshooting Data Protector reports “12:8422” error when using Data Protector Oracle integration after an upgrade of Oracle 8i to Oracle 9i Problem After Oracle 8i is upgraded to Oracle 9i, the following error is returned during the configuration of Oracle instance or during the backup: *RETVAL*8422 Action Rename the Oracle 8i svrmgrl binary to something else so that Data Protector will not find it.
Integrating Oracle and Data Protector Troubleshooting Start SQL*Plus from the directory: bin/sqlplus /nolog Start SQL*Plus and type: connect ; select * from dba_tablespaces; exit If this fails, open the Oracle target database. 2. Verify that you can access the recovery catalog (if used) as follows: Export and as described on page 117.
Integrating Oracle and Data Protector Troubleshooting Start SQL*Plus from the directory: bin/sqlplus /nolog Start SQL*Plus and type: connect exit and then connect exit If this fails, see the Oracle documentation for instructions on how to create a TNS configuration file (TNSNAMES.ORA). 4.
Integrating Oracle and Data Protector Troubleshooting Start SQL*Plus and type: connect ; select * from rc_database; exit If this fails, start the configuration using Data Protector or see the Oracle documentation for details about how to register an Oracle target database in the recovery catalog database. 6. Verify backup and restore directly to disk using an RMAN channel type disk.
Integrating Oracle and Data Protector Troubleshooting release channel 'dev0'; } If this fails, see the Oracle documentation for details on how to execute a backup and restore directly to disk using RMAN. Checking Prerequisites Related to the Oracle Side of the Integration on Windows Systems For more detailed information about how to perform any of the following procedures, see the Oracle documentation. 1.
Integrating Oracle and Data Protector Troubleshooting 3. Verify that the TNS listener is correctly configured for the Oracle target database and for the recovery catalog database. This is required for properly establishing network connections: From the directory run the following command: bin\lsnrctl status If this fails, startup the TNS listener process and see the Oracle documentation for instructions on how to create a TNS configuration file (LISTENER.ORA).
Integrating Oracle and Data Protector Troubleshooting 4. Verify that the Oracle target database and the recovery catalog database are configured to allow remote connections with system privileges: Set the directory.
Integrating Oracle and Data Protector Troubleshooting 6. Verify backup and restore directly to disk using an RMAN channel type disk. If you use the recovery catalog: Set and start RMAN from the directory: Oracle 9i/10g: bin\rman target catalog cmd_file=rman_script Oracle 8i: Use rcvcat instead of catalog in the above syntax.
Integrating Oracle and Data Protector Troubleshooting Configuration Problems on UNIX Systems IMPORTANT If you have encountered any errors up to this point when performing the procedures described in the previous section, please contact Oracle support. The respective tests must be done before you even start checking the Data Protector Oracle configuration. 1.
Integrating Oracle and Data Protector Troubleshooting The output must state that the respective MML is required by the Oracle executable. The following is an extract from the command output on HP-UX: bin/oracle: shared executable shared library dynamic path search: SHLIB_PATH enabled second embedded path disabled first Not Defined shared library list: static /opt/omni/lib/libob2oracle8.sl(libob2oracle8_64bit.sl) dynamic /usr/lib/librt.2 dynamic /usr/lib/libnss_dns.1 dynamic /usr/lib/libdld.
Integrating Oracle and Data Protector Troubleshooting See the online Help index “standard backup procedure” for details about how to do a filesystem backup. 4. Verify the permissions of the current user account Your user account should enable you to perform an Oracle backup or restore with Data Protector. Use the testbar2 utility to check the permissions: /opt/omni/bin/testbar2 -perform:checkuser (HP-UX and Solaris systems) or /usr/omni/bin/testbar2 -perform:checkuser (other UNIX systems).
Integrating Oracle and Data Protector Troubleshooting 2. Verify that the Data Protector Oracle integration Media Management Library (MML) is loaded Once the setup has finished, you need to restart the Oracle services and verify that the :\<%SystemRoot%>\system32\orasbt.dll MML is loaded. Proceed as follows: a. Switch to the :\<%SystemRoot%>\system32 directory and right-click orasbt.dll. b. Select Properties and click the Version tab from the orasbt.dll Properties window.
Integrating Oracle and Data Protector Troubleshooting Figure 1-25 Checking the Inet Start-Up Parameters: 5. Examine the system errors The system errors are reported in the \log\debug.log file on the Oracle Server system. Backup Problems on UNIX Systems At this stage, you should have performed all the verification steps described in the previous sections. After this, proceed as follows: 1.
Integrating Oracle and Data Protector Troubleshooting or /usr/omni/config/cell/cell_server (other UNIX systems) file, which contains the name of the Cell Manager system.
Integrating Oracle and Data Protector Troubleshooting Export of the Recovery Catalog Database failed. Action Start SQL*Plus and grant the execute permission to the LT_EXPORT_PKG as follows (make sure that the user sys has the SYSDBA privilege granted beforehand): sqlplus 'sys/@CDB as sysdba' SQL> grant execute on sys.lt_export_pkg to public; Restart the failed backup session.
Integrating Oracle and Data Protector Troubleshooting Oracle 8i: Use rcvcat instead of catalog in the above syntax. Backup of Archive Logs on RAC Cannot be Performed Problem On RAC, the archive logs are not installed on a NFS mounted disk. Backup of archive logs cannot be performed. Action Edit the archive logs backup specification: • Add an additional allocate channel command for each node. • Add a command to connect to each instance.
Integrating Oracle and Data Protector Troubleshooting Backup Problems on Windows At this stage, you should have performed all the verification steps described in the previous sections. After this, proceed as follows: 1. Check your Oracle Server configuration To check the Oracle Server configuration, see “Checking the Configuration” on page 33. 2.
Integrating Oracle and Data Protector Troubleshooting EXP-00083: The previous problem occurred when calling SYS.LT_EXPORT_PKG.schema_info_exp . exporting statistics Export terminated successfully with warnings. [Major] From: ob2rman.pl@machine "MAKI" Time: 10/01/01 16:07:53 Export of the Recovery Catalog Database failed.
Integrating Oracle and Data Protector Troubleshooting Restore Problems At this stage, you should have performed all the verification steps described in the previous sections. After this, proceed as follows: 1.
Integrating Oracle and Data Protector Troubleshooting Other UNIX /usr/omni/bin/testbar2 -type:Oracle8 -appname: -perform:restore -object: -version: -bar: Windows \bin\testbar2 -type:Oracle8 -appname: -perform:restore -object: -version: -bar: IMPORTANT The hostname should not be specified in the object option. It is automatically provided by testbar2.
Integrating Oracle and Data Protector Troubleshooting • If you are restoring datafiles the database should be in the Mount state. Open a command window and enter the following: sqlplus/nolog SQL>connect /@ as sysdba SQL>shutdown immediate SQL>startup mount 4. Check your environment variables. The message below sometimes appears when you are restoring database items to a new host: "Binary util_orarest is missing. Cannot get information from the remote host.
Integrating Oracle and Data Protector Troubleshooting 6. Try putting the database into the Open state manually after using the Data Protector GUI to recover and restore a backup session. If you have used the Data Protector GUI to recover and restore a backup session, and you see the following error message: Oracle Error: ORA-1589: must use RESETLOGS or NORESETLOGS option for database open.
Integrating Oracle and Data Protector Troubleshooting 1. Rename the util_orarest.exe to util_orarest.exe.orig 2. Rename the util_orarest9.exe to util_orarest.exe Problem The Recovery Catalog was lost and the control file cannot be restored from Data Protector managed backup The Recovery Catalog was not used, the RMAN autobackup feature was not used (for Oracle 9i/10g), and the control file cannot be restored from Data Protector managed backup. A valid control file backup exists on tape.
Integrating Oracle and Data Protector Troubleshooting restore database; recover database; sql 'alter database open resetlogs'; release channel 'dev_0'; } At this point you must manually register any backups made after the control file backup that was restored. After that, continue with the restore procedure.
Integrating Oracle and Data Protector Troubleshooting Can’t dlopen() a library containing Thread Local Storage: /JRE/lib/PA_RISC/native_threads/libjava.sl The problem occurs when the Radius Authentication Adapter is installed. In this case, libclntsh.sl is dynamically linked with the library libjava.sl that provides thread local storage. Action Uninstall the Radius Authentication Adapter to remove libjava.sl from the list of dynamic libraries for libclntsh.sl.
Integrating Oracle and Data Protector Troubleshooting 142 Chapter 1
2 Integrating SAP R/3 and Data Protector Chapter 2 143
Integrating SAP R/3 and Data Protector In This Chapter In This Chapter This chapter explains how to configure and use the Data Protector SAP R/3 integration.
Integrating SAP R/3 and Data Protector Introduction Introduction Data Protector integrates with the SAP R/3 Database Server to offer online backup of your SAP R/3 databases. If the SAP R/3 system uses an Oracle database, then the Data Protector SAP R/3 integration can be used for backup. If any other database is used by SAP, then the corresponding Data Protector integration of that database (for example, Informix) must be used instead.
Integrating SAP R/3 and Data Protector Introduction Data Protector has an advanced media management system that allows you to keep track of all media and the status of each medium, set the protection for stored data, fully automate operations as well as organize and manage devices and media. • Scheduling Data Protector has a built-in scheduler that allows you to automate backups to run periodically. With the Data Protector scheduler, the backups you configure run unattended at the periods you specify.
Integrating SAP R/3 and Data Protector Prerequisites and Limitations Prerequisites and Limitations This section provides you with a list of prerequisites and limitations you must be aware of before using the integration. Prerequisites • The database used by SAP R/3 must be an Oracle database. If any other database is used by SAP, then the corresponding Data Protector integration of that database (for example, Informix) must be used instead.
Integrating SAP R/3 and Data Protector Prerequisites and Limitations Limitations Refer to the HP OpenView Storage Data Protector Product Announcements, Software Notes, and References for a list of general Data Protector limitations. This section describes limitations specific for this integration. • Do not use double quotes (" ") in object-specific pre-exec and post-exec commands. • Do not configure RMAN Offline SAP R/3 backups using the Internal user since the backups will not work.
Integrating SAP R/3 and Data Protector Integration Concept Integration Concept This integration links SAP R/3 backup utilities (BRTOOLS) with Data Protector. SAP R/3 backup utilities provide an interface between an SAP R/3 Database Server and media management applications, like Data Protector.
Integrating SAP R/3 and Data Protector Integration Concept • BRRESTORE This utility restores the backed up data using the BRBACKUP and BRARCHIVE utilities. These backup utilities can be started directly using Data Protector, or interactively using SAPDBA, which is an SAP R/3 administration utility. NOTE Data Protector supports all SAP R/3 backup utilities options, except for the -a and -b options. In order for Data Protector to support also the -a and -b options, set the OB2BRTNOSECU omnirc variable to 1.
Integrating SAP R/3 and Data Protector Integration Concept Figure 2-1 SAP R/3 Backup Concept Legend SM The Data Protector Session Manager, which is the Data Protector Backup Session Manager during backup or the Data Protector Restore Session Manager during restore. Database Library The interface between SAP R/3 Server processes and Data Protector.
Integrating SAP R/3 and Data Protector Integration Concept Backup Flow Using Backint The backup session undergoes the following stages if the backup is performed in backint mode. See Figure 2-2 for details. NOTE It is not possible to perform an incremental backup in backint mode.
Integrating SAP R/3 and Data Protector Integration Concept BMA Data Protector Backup Media Agent RMA Data Protector Restore Media Agent GUI/CLI Data Protector User Interface 1. The backup session can be started using the Data Protector GUI, or interactively using the SAP R/3 utilities. If the backup session is started using the Data Protector User Interface (or using the scheduler), then the Backup Session Manager (BSM) is started.
Integrating SAP R/3 and Data Protector Integration Concept 3. The backint program obtains the SAP R/3 configuration from the Cell Manager, divides the files for backup into subsets (provided that the specified concurrency is greater than 1) and starts the sapback program for each subset. Each sapback process connects to the BSM, which then starts General Media Agents on the corresponding client systems and establishes a connection between the sapback processes and General Media Agents.
Integrating SAP R/3 and Data Protector Integration Concept (SmWaitForNewClient omnirc global variable) and completes the backup session, as long as no backint is started within this time frame. Backup Flow Using Recovery Manager A backup session using RMAN mode differs from a backup session in backint mode in step 3. See Figure 2-3 on page 156 for details. BRBACKUP starts RMAN, which then connects to the Data Protector Database Library via the Oracle Server processes.
Integrating SAP R/3 and Data Protector Integration Concept Figure 2-3 SAP R/3 Architecture: RMAN Mode Legend Restore Flow Using Backint BSM Data Protector Backup Session Manager BMA Data Protector Backup General Media Agent GUI/CLI Data Protector User Interface SAP R/3 restore can be initiated using Data Protector, or interactively using the SAP R/3 utilities. However, only a standard filesystem restore is performed using Data Protector.
Integrating SAP R/3 and Data Protector Integration Concept The restore session proceeds according to the following stages if the restore is performed in backint mode. 1. Using the SAPDBA utility, the objects to be restored are selected. 2. The BRRESTORE first checks whether the required free disk space is available to allow the files to be restored. It then starts the first backint command to restore the Oracle Target Database’s data files.
Integrating SAP R/3 and Data Protector Data Protector SAP R/3 Configuration File Data Protector SAP R/3 Configuration File Data Protector stores the SAP R/3 integration parameters for every configured SAP R/3 instance in the following file on the Cell Manager: • On UNIX: /etc/opt/omni/server/integ/config/SAP/% • On Windows: \Config\Server\Integ\Config\Sap\% The parameters stored are: • Oracle home directory • encoded connection string
Integrating SAP R/3 and Data Protector Data Protector SAP R/3 Configuration File NOTE You can set up the parameters in the Environment section (sublist) of the file by referring to other environment variables in the following way: SAPDATA_HOME=${ORACLE_HOME}/data Syntax The syntax of the Data Protector SAP R/3 configuration file is as follows: ORACLE_HOME=''; ConnStr=''; BR_directory='; SAPDATA_HOME=''; Environmen
Integrating SAP R/3 and Data Protector Data Protector SAP R/3 Configuration File Example This is an example of the file: ORACLE_HOME='/app/oracle805/product'; ConnStr='EIBBKIBBEIBBFIBBGHBBOHBBQDBBOFBBCFBBPFBBCFBBIFBBGFBBDGBBB FBBCFBBDFBBCFBB'; BR_directory='/usr/sap/ABA/SYS/exe/run'; SAPDATA_HOME='/sap'; Environment={ } SAP_Parameters={ sap_weekly_offline=('-concurrency 1','-no_balance'); sap_daily_online=('-concurrency 3','-load_balance'); sap_daily_manual=('-concurrency 3','-manual_balance'); } speed={
Integrating SAP R/3 and Data Protector Data Protector SAP R/3 Configuration File Setting, Retrieving, Listing, and Deleting Data Protector SAP R/3 Configuration File Parameters Using the CLI The Data Protector SAP R/3 configuration file parameters are normally written to the Data Protector SAP R/3 configuration file after: • the configuration of the SAP R/3 instance in Data Protector is completed. • a new backup specification is created. • a backup that uses balancing by time algorithm is completed.
Integrating SAP R/3 and Data Protector Data Protector SAP R/3 Configuration File [-sub[list] ] specifies the sublist in the configuration file to which a parameter is written to or taken from. [-local ] specifies one of the following: • When it is used with the -getconf[ig] option, it specifies the filename for the output of the command to be written to. If the -local option is not specified, the output is written to the standard output.
Integrating SAP R/3 and Data Protector Data Protector SAP R/3 Configuration File Setting Parameters To set the Data Protector OB2OPTS and the Oracle NLS_LANG parameters for the SAP R/3 instance ICE, use the following commands on the Data Protector SAP R/3 client: Windows \bin\util_cmd -putopt SAP ICE OB2OPTS '-debug 1-200 INSTANCE.txt' -sublist Environment \bin\util_cmd -putopt SAP ICE NLS_LANG 'AMERICAN_AMERICA.
Integrating SAP R/3 and Data Protector Data Protector SAP R/3 Configuration File Listing Parameters To list all the Data Protector SAP R/3 configuration file parameters for the SAP R/3 instance ICE, use the following command on the Data Protector SAP R/3 client: • On Windows: \bin\util_cmd -getconf SAP ICE • On HP-UX and Solaris: /opt/omni/lbin/util_cmd -getconf SAP ICE • On other UNIX: /usr/omni/bin/util_cmd -getconf SAP ICE Deleting Parameters To remove the value of the OB2OPTS param
Integrating SAP R/3 and Data Protector Configuring the Integration Configuring the Integration Configuration Overview Configuring the Data Protector SAP R/3 integration consists of these steps: 1. If you intend to use the Oracle Recovery Manager to backup the SAP R/3 database files, install and configure the Data Protector Oracle integration. When the Data Protector Oracle integration is configured, it is recommended to run a test Data Protector Oracle backup using the Oracle Recovery Manager. 2.
Integrating SAP R/3 and Data Protector Configuring the Integration Such a user is the user ora from the group sapsys; or, you can identify such a user by running the following command on the SAP R/3 Database Server system: ps -ef|grep ora_pmon_ or ps -ef|grep ora_lgwr_ Figure 2-4 Finding the Oracle User It can be seen from the example above that the user ora has sufficient privileges within the SAP R/3 database to backup and restore the SAP R/3 database.
Integrating SAP R/3 and Data Protector Configuring the Integration Configuring an SAP R/3 Database Server Before You Begin It is recommended that you configure and run a Data Protector test filesystem backup of the SAP R/3 Database Server (a client system in the Data Protector cell). In case of problems, this type of backup is much easier to troubleshoot than the integration itself. A test filesystem backup includes installing a Disk Agent on the SAP R/3 Database Server.
Integrating SAP R/3 and Data Protector Configuring the Integration integration. However, you need to create a link to the Data Protector backint interface on all other nodes. Enter the following command on all other nodes: ln -s /opt/omni/lbin/backint \ /usr/sap//sys/exe/run In a cluster environment, the environment variable OB2BARHOSTNAME must be defined as the virtual hostname before running the configuration from the command line (on the client).
Integrating SAP R/3 and Data Protector Configuring the Integration NOTE Make sure to set any Oracle and SAP R/3 related environment variables needed for the Oracle and SAP R/3 databases to function properly (for example, the Oracle NLS_LANG environment variable) on the SAP R/3 Database Server. Refer to the Oracle and SAP R/3 documentation for more information. Data Protector Inet On Windows, set the service startup account of the Data Protector Inet service as an SAP administrator account.
Integrating SAP R/3 and Data Protector Configuring the Integration Using the CLI UNIX Systems Only On UNIX, to configure an SAP R/3 Database Server, execute the following command with root privileges on the SAP R/3 Database Server: NOTE Each instance must be configured separately. util_sap.
Integrating SAP R/3 and Data Protector Configuring the Integration Directory where SAP R/3 database files are installed. This is an optional parameter. By default, it is set to . Using the GUI To configure an instance of the SAP R/3 Database Server, perform the following steps using the Data Protector GUI: 1. In the Data Protector Manager, switch to the Backup context. 2. In the Scoping Pane, expand Backup, then expand Backup Specifications, and right-click SAP R/3. 3. Click Add Backup.
Integrating SAP R/3 and Data Protector Configuring the Integration Figure 2-5 Specifying the SAP R/3 Database Server and the Oracle SID on Windows 172 Chapter 2
Integrating SAP R/3 and Data Protector Configuring the Integration Figure 2-6 Specifying the SAP R/3 Database Server and the Oracle SID on UNIX Once you have provided the required information, click Next. If the selected system is configured for the first time, the configuration window is displayed.
Integrating SAP R/3 and Data Protector Configuring the Integration Figure 2-7 Configuring an SAP R/3 Database Server on Windows Figure 2-8 Configuring an SAP R/3 Database Server on UNIX 174 Chapter 2
Integrating SAP R/3 and Data Protector Configuring the Integration 5. Enter the following information in the Configure SAP dialog box: • The Oracle Server home directory. If not specified, this is set to the default Oracle home directory. • SAP data home directory (if not entered, this is set to ) • The connection string to the Oracle Target Database. See “Glossary” on page G-1 for more information on login connection strings. • The directory where the SAP R/3 backup utilities are stored.
Integrating SAP R/3 and Data Protector Configuring the Integration NOTE The target database must be online during the check. The configuration can also be also checked if you have already created and saved a backup specification for a particular SAP R/3 Database Server. Proceed as follows: 1. In the Data Protector Manager, switch to the Backup context. In the Scoping Pane, expand Backup, Backup Specification, then SAP R/3. 2.
Integrating SAP R/3 and Data Protector Configuring the Integration Figure 2-9 Checking the SAP R/3 Configuration You can also (re)configure an SAP R/3 Database Server by right-clicking it and selecting Configure. To check the SAP R/3 configuration, start the following command on the Checking the client: SAP R/3 Configuration util_sap.exe -CHKCONF .
Integrating SAP R/3 and Data Protector Configuring the Integration On UNIX, to get the error description, start the /opt/omni/lbin/omnigetmsg 12 (HP-UX and Solaris systems) or /usr/omni/bin/omnigetmsg 12 (other UNIX systems) command.
Integrating SAP R/3 and Data Protector Configuring an SAP R/3 Backup Configuring an SAP R/3 Backup To configure an SAP R/3 backup, perform the following steps: 1. Configure the devices you plan to use for a backup. See the online Help index keyword “configuring devices” for instructions. 2. Configure media pools and media for a backup. Refer to the online Help index keyword “creating media pools” for instructions. 3. Create a Data Protector SAP R/3 backup specification.
Integrating SAP R/3 and Data Protector Configuring an SAP R/3 Backup Creating a Data Protector SAP R/3 Backup Specification To create an SAP R/3 backup specification, proceed as follows: 1. In the HP OpenView Storage Data Protector Manager, switch to the Backup context. 2. In the Scoping Pane, expand Backup, and then Backup Specifications. Right-click SAP R/3 and then click Add Backup. The Create New Backup dialog box is displayed. 3.
Integrating SAP R/3 and Data Protector Configuring an SAP R/3 Backup Each tablespace is switched into backup mode just before the backup and is switched out from backup mode immediately after the backup. As a result, the increase in archived log files is smaller compared to the backup with the util_file device type. However, if the database consists of a large number of small files, the backup can take longer. Brbackup_RMAN_Offline Backs up the shut-down database using Oracle RMAN.
Integrating SAP R/3 and Data Protector Configuring an SAP R/3 Backup Figure 2-10 Selecting Backup Objects See “Why Archive Redo Logs?” on page 186, for an explanation of the reasons for archiving redo logs, and online Help for details on backup objects. Click Next. 7. Select the device(s) you want to use for the backup. Click Properties to set the device concurrency, media pool, and preallocation policy. For more information on these options, click Help.
Integrating SAP R/3 and Data Protector Configuring an SAP R/3 Backup Click Next. 8. Select the backup options. For information on the Backup Specification Options and Common Application Options, refer to the online Help. For information on the Application Specific Option (SAP R/3 specific backup options), see “SAP R/3 Specific Backup Options” on page 186 or online Help. NOTE The SAP R/3 backup options specified here override the current settings in the init.sap file.
Integrating SAP R/3 and Data Protector Configuring an SAP R/3 Backup Figure 2-11 SAP R/3 Backup Options Click Next. 9. Optionally, schedule the backup. For more information, refer to “Scheduling a Backup” on page 198. Click Next. 10. Save the backup specification. It is recommended that you save all SAP R/3 backup specifications in the SAP group.
Integrating SAP R/3 and Data Protector Configuring an SAP R/3 Backup Figure 2-12 Saving the Backup Specification Click OK. To start the backup, see “Backing Up an SAP R/3 Database” on page 197. 11. On UNIX, after the backup specification is saved, verify that the owner of the backup specification is the specified SAP R/3 user. See “Configuring an SAP R/3 User in Data Protector (UNIX Systems Only)” on page 165 for details about this user. 12.
Integrating SAP R/3 and Data Protector Configuring an SAP R/3 Backup NOTE The parallelism of a backup (the number of streams your SAP R/3 database is backed up with) is set automatically. If load balancing is used, the parallelism represents the sum of the device concurrencies defined in the SAP R/3 backup specification. For more information on load balancing, see the online Help index “load balancing”. The database system of an SAP R/3 system must operate in the ARCHIVELOG mode.
Integrating SAP R/3 and Data Protector Configuring an SAP R/3 Backup BRBACKUP command options. For example, type -t online, for online backup. Or, type -u for some other user than default user (usually the user system). Backup Objects When the backup specification is saved, this field lists the string passed by omnisap.exe to the BRBACKUP command. BR Archive Enter the BRARCHIVE command options. See the SAP R/3 Online Documentation for information about BRARCHIVE command options.
Integrating SAP R/3 and Data Protector Configuring an SAP R/3 Backup influences (such as mount prompts), and is therefore best for environments with large libraries of the same quality. Each subset is backed up by one Data Protector sapback program, thus allowing concurrent backup of all subsets of the same type. Data Protector automatically stores backup speed information in the speed section of the Data Protector integration configuration file on the Cell Manager.
Integrating SAP R/3 and Data Protector Configuring an SAP R/3 Backup (HP-UX and Solaris systems), or /usr/omni/bin (other UNIX systems) directory. Only the filename must be provided in the backup specification. Post-exec Specifies an object post-exec command with options that will be started on the SAP R/3 Database Server after backup. The command/script is started by Data Protector omnisap.
Integrating SAP R/3 and Data Protector Configuring an SAP R/3 Backup Objects outside database With this option, you save all non-database files of the SAP R/3 and Oracle environments. This means that the following directory trees can be saved: /sapmnt/ /usr/sap/, /usr/sap/trans/ It is recommended that you save these directories in a separate backup session.
Integrating SAP R/3 and Data Protector Configuring an SAP R/3 Backup You can perform two types of online backups as well as offline backups. • To start an offline backup, specify the -t offline and -d util_file BRBACKUP options. You can alternatively specify backup_dev_type = util_file and backup_type = offline in the SAP parameter file. • The two types of online backups differ according to the duration in which tablespaces are in backup mode.
Integrating SAP R/3 and Data Protector Configuring an SAP R/3 Backup • In a disaster situation (such as the loss of a production database and recovery catalog), the restoration and recovery of data is complicated. It may not be possible without the help of Oracle Support. If the Recovery Manager does not have administrative data stored in the recovery catalog, it cannot recover the database on the basis of the backups that have been made.
Integrating SAP R/3 and Data Protector Configuring an SAP R/3 Backup the backup specification.
Integrating SAP R/3 and Data Protector Configuring an SAP R/3 Backup \Config\server\integ\config\sap\% (Windows systems) file. See “Data Protector SAP R/3 Configuration File” on page 158. Creating an SAP /R3 Backup Specification for Manual Balancing To use manual balancing, you have to edit the SAP R/3 backup specifications.
Integrating SAP R/3 and Data Protector Configuring an SAP R/3 Backup SID> file (UNIX systems), or in the \Config\server\integ\config\sap\% file (Windows systems): manual_balance={ SAP-R3={ fileA=0; fileB=1; fileC=0;fileD=2;}} Configure your backup specification SAP-R3 to back up the files fileA, fileC and fileD on device Device_1, and fileB on device Device_2. The backup specification then looks like: BARLIST "SAP-R3" OWNER galeja.zimco.
Integrating SAP R/3 and Data Protector Configuring an SAP R/3 Backup 2. In the Scoping Pane, expand Backup, then Backup Specifications, SAP R/3, and right-click the backup specification you want to preview. 3. Click Preview Backup to open the Start Preview dialog box. Select the type of backup you want to run as well as the network load. See online Help for a description of these options.
Integrating SAP R/3 and Data Protector Backing Up an SAP R/3 Database Backing Up an SAP R/3 Database To run a backup of an SAP R/3 database, use any of the following methods: Backup Methods • Schedule a backup of an existing SAP R/3 backup specification using the Data Protector Scheduler. See “Scheduling a Backup” on page 198. • Start an interactive backup of an existing SAP R/3 backup specification using the Data Protector GUI or the Data Protector CLI. See “Running an Interactive Backup” on page 200.
Integrating SAP R/3 and Data Protector Backing Up an SAP R/3 Database To start an incremental backup, specify Incremental mode in the Data Protector GUI or incr mode in the CLI, as follows: omnib -sap_list -barmode incr NOTE It is not possible to perform an incremental backup in backint mode. Aborting a Running Session In the Actions menu, click Abort to abort a running SAP R/3 backup session, and then confirm the action.
Integrating SAP R/3 and Data Protector Backing Up an SAP R/3 Database A backup schedule can be tailored according to your business needs. If you need to keep the database online continuously, then you should back it up frequently, including backup of the archived redo logs, which is required in case you need a recovery to a particular point in time. For example, you may decide to perform daily backups and make multiple copies of the online redo logs and the Archived Redo Logs to several different locations.
Integrating SAP R/3 and Data Protector Backing Up an SAP R/3 Database Figure 2-14 Scheduling Backups Click OK and then Apply to save the changes. NOTE It is not possible to perform an incremental backup in the backint mode. Running an Interactive Backup An interactive backup can be performed any time after a backup specification has been created and saved. Starting a Backup Using the GUI To start an interactive backup of an SAP R/3 database using the Data Protector GUI, proceed as follows: 1.
Integrating SAP R/3 and Data Protector Backing Up an SAP R/3 Database In the Start Backup dialog box, select the Backup type and Network load options. For information on these options, click Help. Click OK. Figure 2-15 Starting an Interactive Backup An interactive backup can also be started from the CLI. Cluster-Aware Clients In a cluster environment, the environment variable OB2BARHOSTNAME must be defined as the virtual hostname before running a backup from the command line (on the client).
Integrating SAP R/3 and Data Protector Backing Up an SAP R/3 Database Tru64 Cluster Before starting a backup on the Tru64 Cluster, create the following links: ln –s /sapfiles/admin/dbs/initsap.dba initSAP.dba ln –s /sapfiles/admin/dbs/initsap.ora initSAP.ora ln –s /sapfiles/admin/dbs/initsap.sap init SAP.
Integrating SAP R/3 and Data Protector Backing Up an SAP R/3 Database set the service startup account of the Data Protector Inet service to be your logon user account. This does not apply if you initiate the backup or restore using the Data Protector User Interface. To configure the Data Protector Inet service startup account, perform the following steps: 1. In the Control Panel, go to Administrative Tools, Services. 2. Select the Data Protector Inet service and restart it.
Integrating SAP R/3 and Data Protector Restoring an SAP R/3 Database Restoring an SAP R/3 Database You can restore SAP R/3 databases in any of the following ways: • Use the Data Protector GUI or CLI. • Use SAP R/3 commands. Considerations You cannot perform a restore of backups created by the Oracle RMAN using the Data Protector GUI or CLI. Before you start to restore your data using the Data Protector User Interface, you need detailed information about backed up objects.
Integrating SAP R/3 and Data Protector Restoring an SAP R/3 Database filenames are displayed correctly only if the encoding is set to the encoding of the filesytem and not with the encoding of the database (ja_JP.eucJP). Limitations • You cannot restore SAP R/3 tablespaces that are located on raw partitions using the Data Protector GUI. Instead, use SAP R/3 restore tools (for example, brrestore).
Integrating SAP R/3 and Data Protector Restoring an SAP R/3 Database Figure 2-16 Restoring SAP R/3 Database Objects 3. Select the backed up SAP R/3 object you want to restore. You can also select the search interval for browsing object versions in the Data Protector database by clicking the drop-down list button of the Search Interval option. If you select Interval in the drop-down list, you can set your own search interval by specifying the From: and To: options and then clicking the Update button. 4.
Integrating SAP R/3 and Data Protector Restoring an SAP R/3 Database Restoring Using the Data Protector CLI Cluster-Aware Clients In a cluster environment, the environment variable OB2BARHOSTNAME must be defined as the virtual hostname before starting a restore procedure from the command line (on the client).
Integrating SAP R/3 and Data Protector Restoring an SAP R/3 Database UNIX: omnir -sap computer.company.com:ABA.0 -session 2006/01/23-1 -tree /app/oracle/ABA/sapdata1/btabd_1/btabd_1.dat The restore session can be monitored in the Data Protector Monitor window, where mount prompts for the required media are also displayed. Refer to the man pages for more information on the Data Protector omnir command. TIP If you have a sparse file, restore using the sparse option to perform a faster restore.
Integrating SAP R/3 and Data Protector Restoring an SAP R/3 Database See the SAP R/3 System Online Documentation for instructions on how to use the sapdba or brrestore utilities. Using Another Device Data Protector supports restore using a device other than the one that was used at backup time.
Integrating SAP R/3 and Data Protector Restoring an SAP R/3 Database Check the instructions from the database/application vendor on how to prepare for a disaster recovery. See also the HP OpenView Storage Data Protector Disaster Recovery Guide for instructions on how to approach system disaster recovery using Data Protector. This is a general procedure for recovering an application: 1. Complete the recovery of the operating system. 2.
Integrating SAP R/3 and Data Protector Restoring an SAP R/3 Database 2. Run the following script: run { allocate channnel 'dev0' type disk; replicate controlfile from ''; release channel 'dev0'; } Figure 2-17 Where is the folder to which the control file was restored.
Integrating SAP R/3 and Data Protector Monitoring an SAP R/3 Backup and Restore Monitoring an SAP R/3 Backup and Restore The Data Protector GUI enables you to monitor current or previous backup and restore sessions. NOTE Only the Data Protector users in the Admin group and those granted the Monitor user rights are given access to the Data Protector monitoring functionality. Monitoring is automatically activated when you start a restore or backup.
Integrating SAP R/3 and Data Protector Monitoring an SAP R/3 Backup and Restore 2. In the Actions menu, select Clear Sessions. Or click the Clear Sessions icon on the toolbar. To remove a particular completed or aborted session from the current sessions list, right-click the session and select Remove From List. NOTE All completed or aborted sessions are automatically removed from the Results Area of the Monitor context if you restart the Data Protector GUI.
Integrating SAP R/3 and Data Protector Troubleshooting Troubleshooting This section lists general checks and verifications plus problems you might encounter when using the Data Protector SAP R/3 integration. For general Data Protector troubleshooting information, see the HP OpenView Storage Data Protector Troubleshooting Guide. Before You Begin ✓ Ensure that the latest official Data Protector patches are installed. See the online Help index: “patches” on how to verify this.
Integrating SAP R/3 and Data Protector Troubleshooting Troubleshooting on Windows Systems Prerequisites Concerning the Oracle Side of the Integration The following steps should be performed to verify that Oracle is installed as required for the integration to work. These steps do not include verifying Data Protector components. 1. Verify that you can access the Oracle Target Database and that it is opened, as follows: Set and variables.
Integrating SAP R/3 and Data Protector Troubleshooting Figure 2-18 Checking the Status of the Oracle Listener a. The status of the respective listener service in the Services window should be Started, otherwise you must start it manually. b.
Integrating SAP R/3 and Data Protector Troubleshooting Repeat the procedure using SYSOPER instead of SYSDBA. Set the directory If you are using the recovery catalog: bin\rman target rcvcat If you are not using the recovery catalog: bin\rman target nocatalog If this fails, refer to the Oracle documentation for instructions on how to set up the password file and any relevant parameters in the init.ora file.
Integrating SAP R/3 and Data Protector Troubleshooting b. If this fails, refer to the SAP R/3 Online Help to learn how to execute backup and restore directly to disk using the SAP R/3 backup utility. Check the error message and resolve these problems before you continue. 4. Verify that the SAP R/3 backup tools correctly start backint (which is provided by Data Protector): Move the original backint and create a test script named backint.
Integrating SAP R/3 and Data Protector Troubleshooting 2. Perform a filesystem backup of the SAP R/3 Database Server: Perform a filesystem backup of the SAP R/3 Database Server system so that you can eliminate any potential communication problems between the SAP R/3 Database Server and the Data Protector Cell Manager system. Do not start troubleshooting an online database backup unless you have successfully completed a filesystem backup of the SAP R/3 Database Server system.
Integrating SAP R/3 and Data Protector Troubleshooting Figure 2-19 Checking the Inet Start-Up Parameters: 5. Examine the environment variables: If you need to export some variables before starting the Oracle Server Manager, TNS listener, or other Oracle utility, these variables must be defined in the Environment section of the Data Protector SAP R/3 configuration file on the Cell Manager. See “Data Protector SAP R/3 Configuration File” on page 158. 6.
Integrating SAP R/3 and Data Protector Troubleshooting 2. Verify Data Protector internal data transfer using the testbar2 utility. Before you run the testbar2 utility, verify that the Cell Manager name is correctly defined on the SAP R/3 Database Server. Check the \Config\client\cell_server file, which contains the name of the Cell Manager system.
Integrating SAP R/3 and Data Protector Troubleshooting Backup fails at the beginning with the message “Internal heap ERROR 17112” Problem When using SAP 4.6D kernel on HP-UX 11.11, backup fails immediately after it was started due to a BRBACKUP core dump. A line similar to the following can be found at the beginning of the message: Internal heap ERROR 17112 addr=0x800003ffff7f3660 Action 1. Login to the SAP server as the user who is owner of the backup specification. 2.
Integrating SAP R/3 and Data Protector Troubleshooting You can also do this using the SAP R/3 utilities: Use backint, so that SAPDBA will also use this command to query: \bin\backint.exe -f inquiry -u -i where the specified is queried. If this fails, check if the backup session was performed successfully and if the query was started under the appropriate user account.
Integrating SAP R/3 and Data Protector Troubleshooting -appname: -perform:restore -object: -version: -bar: You should see only NORMAL messages displayed on your screen, otherwise examine the errors reported by the testbar2 utility by clicking the Details button in the Data Protector Monitor context. 4. Verify the restore using backint Run the following command: \bin\backint.
Integrating SAP R/3 and Data Protector Troubleshooting • Do not use non-ASCII or non-Latin 1 characters for filenames. Troubleshooting on UNIX Systems Using Oracle After Removing the Data Protector Oracle Integration This section is relevant only if Oracle RMAN has been used to back up the SAP R/3 datafiles and you have uninstalled the Data Protector Oracle integration on an Oracle server.
Integrating SAP R/3 and Data Protector Troubleshooting Start the Server Manager (Oracle8/9i) or SQL Plus (Oracle9i) from the directory: bin\svrmgrl (Oracle8/8i) or bin\sqlplus (Oracle9i) At the SVRMGR (Oracle8/8i) or SQL (Oracle9i) prompt, type: connect /@ select * from dba_tablespaces; exit If it fails, open the Oracle Target Database. 2. Verify that the TNS listener is correctly configured for the Oracle Target Database.
Integrating SAP R/3 and Data Protector Troubleshooting 3.
Integrating SAP R/3 and Data Protector Troubleshooting If you do not use the Recovery Catalog: Export as described on page 225 and start Recovery Manager: bin/rman target nocatalog cmd_file=rman_script An example of the rman_script is listed below: run {allocate channel ‘dev0’ type disk; backup (tablespace format ‘/tmp/’);} After a successful backup, try to restore the backed up tablespace by running the following restore s
Integrating SAP R/3 and Data Protector Troubleshooting If this fails, check the error messages and resolve possible problems before you continue. 3. If you are running backups in RMAN mode, verify backup and restore directly to disk using Recovery Manager channel type disk as follows: a. Re-link the Oracle software with the Database Library provided by SAP R/3 (libobk.sl). b. Use the same procedure as described for linking the Data Protector Database Library.
Integrating SAP R/3 and Data Protector Troubleshooting echo "Test backint called as follows:" echo "$0 $*" echo "exiting 3 for a failure" exit 3 Then start the following commands as the SAP R/3 user; see “Configuring an SAP R/3 User in Data Protector (UNIX Systems Only)” on page 165: brbackup -t offline -d util_file -u / -c If you receive backint arguments, this means that SAP R/3 is properly configured for backup using backint; otherwise you have to reconfigure SAP R/3.
Integrating SAP R/3 and Data Protector Troubleshooting Solaris platform: /usr/bin/ldd -s /bin/oracle The output has to state that the respective Data Protector library is required by Oracle executable. The following is an extract of the command output on HP-UX: bin/oracle: shared executable shared library dynamic path search: SHLIB_PATH enabled second embedded path disabled first Not Defined shared library list: static /opt/omni/lib/libob2oracle8.sl(libob2oracle8_64bit.
Integrating SAP R/3 and Data Protector Troubleshooting 4. Examine the environment variables: If you need to export some variables before starting the Oracle Server Manager, TNS listener, or other Oracle utility, these variables must be defined in the Environment section of the Data Protector SAP R/3 configuration file on the Cell Manager. See “Data Protector SAP R/3 Configuration File” on page 158. 5.
Integrating SAP R/3 and Data Protector Troubleshooting To get the error description, start the command: /opt/omni/lbin/omnigetmsg 12 (HP-UX and Solaris systems) or /usr/omni/bin/omnigetmsg 12 (other UNIX systems) The *RETVAL*0 indicates successful configuration. 2. Verify Data Protector internal data transfer using the testbar2 utility. Before you run the testbar2 utility, verify that the Cell Manager name is correctly defined on the SAP R/3 Database Server.
Integrating SAP R/3 and Data Protector Troubleshooting If the test fails again, call support. 3. Verify the backup using backint export OB2BARLIST= export OB2APPNAME= /opt/omni/lbin/backint -f backup -t file -u -i (HP-UX and Solaris systems) /usr/omni/bin/backint -f backup -t file -u -i (other UNIX systems) where is a file with a list of full pathnames for backup.
Integrating SAP R/3 and Data Protector Troubleshooting Util_File_Online SAP backup fails with “semop() error” Problem When the util_file_online option is used with BRBACKUP (for example, if you select the Brbackup_Util_File_Online template), the tablespaces are switched into/from backup mode individually. As there can be only one process communicating with BRBACKUP, several sapback processes are using a semaphore to synchronize their interaction with BRBACKUP.
Integrating SAP R/3 and Data Protector Troubleshooting "" -media (other UNIX systems) on the SAP R/3 Database Server system. The output of the command lists detailed information about the specified backup object, session IDs of the backup sessions containing this object, and a list of the media used.
Integrating SAP R/3 and Data Protector Troubleshooting 4. Simulate a Restore Session Once you know the information about the object to be restored, you can simulate a restore using the Data Protector testbar2 utility. Before you run testbar2, verify that the Cell Manager name is correctly defined on the SAP R/3 Database Server.
Integrating SAP R/3 and Data Protector Troubleshooting • On other UNIX: /usr/omni/bin/backint -f restore -u -i where the contents of the will be restored. If this fails, check if the session was performed successfully and if the restore was started under the appropriate user account.
Integrating SAP R/3 and Data Protector Examples of SAP R/3 Database Restore Examples of SAP R/3 Database Restore This section describes some examples of how you can restore an SAP R/3 database.
Integrating SAP R/3 and Data Protector Examples of SAP R/3 Database Restore SAPSID refers to the name of the SAP R/3 system, while the DBSID refers to the name of the database instance. When a single instance is installed, SAPSID and DBSID are the same. • ORACLE_HOME: home directory of the Oracle software is by default \ (Windows systems) or /opt/oracle/ (UNIX systems).
Integrating SAP R/3 and Data Protector Examples of SAP R/3 Database Restore Syntax for SAPDATA is: n=1, ..., 99. The environment variables SAPDATA must only be defined if directories are on a location other than the default. • TWO_TASK: identification of a remote database system This environment variable must not be set.
Integrating SAP R/3 and Data Protector Examples of SAP R/3 Database Restore Figure 2-20 Starting the SAPDBA in Expert Mode 2. When the menu appears, select the Restore/Recovery option.
Integrating SAP R/3 and Data Protector Examples of SAP R/3 Database Restore 3. When the new menu appears, you can select between different types of restore. Select Full restore and recovery option. SAPDBA will check if your database is up and running. Figure 2-22 Selecting Full Restore and Recovery 4. After the SAPDBA checks the status of the database, a new window displaying the results appears.
Integrating SAP R/3 and Data Protector Examples of SAP R/3 Database Restore 6. Select the Start restore and recover option to start the restore session. Figure 2-24 Starting the Restore Session 7. Select the Return to restore procedure and continue, if you want to specify or modify the restore parameters.
Integrating SAP R/3 and Data Protector Examples of SAP R/3 Database Restore After you have opened a database with the RESETLOGS option, it is strongly recommended to perform a whole database backup immediately. If the database is opened with the RESETLOGS option, the old redo log files are overwritten. Back up the offline redo log files before you open the database.
Integrating SAP R/3 and Data Protector Examples of SAP R/3 Database Restore 2. Select the Show the list of damaged files to determine the files that need to be restored. The SAPDBA utility lists all the lost files and their backup files. Each file shown in the list contains one of the following comments: • Backup file: on Backed up by This means that the file was backed up using the specific program.
Integrating SAP R/3 and Data Protector Examples of SAP R/3 Database Restore The lost files are restored using the SAP utility BRRESTORE. 7. Select the Start restore of backup files. SAPDBA checks if the files that are to be restored are still available. If these files are still available, an error message is displayed. Confirm that SAPDBA may overwrite these files. If you do not allow SAPDBA to overwrite these files, the restore procedure is terminated at this point.
Integrating SAP R/3 and Data Protector Examples of SAP R/3 Database Restore The SAP BRRESTORE utility restores the required files. If the redo logs are still available on the disk, they do not have to be restored. 3. Select Return to continue with the recovery process.
3 Integrating SAP DB/MaxDB and Data Protector Chapter 3 249
Integrating SAP DB/MaxDB and Data Protector In This Chapter In This Chapter This chapter explains how to configure and use the HP OpenView Storage Data Protector SAP DB/MaxDB integration. It explains the concepts and methods you need to understand in order to back up and restore SAP DB/MaxDB databases using Data Protector.
Integrating SAP DB/MaxDB and Data Protector Prerequisites and Limitations Prerequisites and Limitations This section provides a list of prerequisites and limitations you must be aware of before using the integration. Prerequisites • A license is needed in order to use the Data Protector SAP DB/MaxDB integration. Refer to the HP OpenView Storage Data Protector Installation and Licensing Guide for information about licensing.
Integrating SAP DB/MaxDB and Data Protector Introduction Introduction Backup Data Protector integrates with the SAP DB/MaxDB Database Server to offer an integrated online backup of SAP DB/MaxDB instance.
Integrating SAP DB/MaxDB and Data Protector Introduction Table 3-1 on page 253 shows what is actually backed up with regards to the selected SAP DB/MaxDB backup type and Data Protector GUI object.
Integrating SAP DB/MaxDB and Data Protector Introduction The integration supports SAP DB/MaxDB migration, meaning that an SAP DB/MaxDB instance can be restored to an SAP DB/MaxDB Server or instance other than the original. In such a case, if the SAP DB/MaxDB Server has not yet been configured for the Data Protector SAP DB/MaxDB integration, it must be configured before the restore is started. If the instance does not exist, it must be configured before the restore is started.
Integrating SAP DB/MaxDB and Data Protector Introduction • Media Management Data Protector has an advanced media management system that allows you to keep track of all media and the status of each medium, set the protection for stored data, fully automate operations as well as organize and manage devices and media. • Backup Management Backed up data can be duplicated during or after the backup to increase fault tolerance of backups, to improve data security and availability, or for vaulting purposes.
Integrating SAP DB/MaxDB and Data Protector Integration Concept Integration Concept The Data Protector SAP DB/MaxDB integration links the SAP DB/MaxDB database management software with Data Protector. From the SAP DB/MaxDB point of view, Data Protector represents a media management utility. On the other hand, the SAP DB/MaxDB database management system can be seen as a data source for backup, using media controlled by Data Protector.
Integrating SAP DB/MaxDB and Data Protector Integration Concept SAP DB/MaxDB dbmcli. The sapdbbar.exe module issues dbmcli commands that configure SAP DB/MaxDB backup media (parallelism), configure sapdb_backint and then start the backup using SAP DB/MaxDB dbmcli. SAP DB/MaxDB then starts the configured sapdb_backint component. For every SAP DB/MaxDB medium (pipe) sapdb_backint starts a DMA, which transfers the data from SAP DB/MaxDB media (pipes) to Data Protector media.
Integrating SAP DB/MaxDB and Data Protector Integration Concept Figure 3-1 SAP DB/MaxDB Backup and Restore Concept 258 Chapter 3
Integrating SAP DB/MaxDB and Data Protector Data Protector SAP DB/MaxDB Configuration File Data Protector SAP DB/MaxDB Configuration File Data Protector stores the SAP DB/MaxDB integration parameters for every configured SAP DB/MaxDB instance in the following file on the Cell Manager: • /etc/opt/omni/server/integ/config/SAPDB/% (HP-UX and Solaris systems) • \Config\server\integ\config\SAPDB\% (Windows systems).
Integrating SAP DB/MaxDB and Data Protector Data Protector SAP DB/MaxDB Configuration File • when the configuration parameters are changed Configuration File Syntax The syntax of the file is as follows: IMPORTANT To avoid problems with your backups, ensure that the syntax of your configuration file matches the examples.
Integrating SAP DB/MaxDB and Data Protector Data Protector SAP DB/MaxDB Configuration File In a cluster environment, the environment variable OB2BARHOSTNAME must be defined as the virtual hostname before running the util_cmd command from the command line (on the client).
Integrating SAP DB/MaxDB and Data Protector Data Protector SAP DB/MaxDB Configuration File Return Values The util_cmd command displays a short status message after each operation (written to the standard error): • Configuration read/write operation successful. This message is displayed when all the requested operations have been completed successfully. • Configuration option/file not found.
Integrating SAP DB/MaxDB and Data Protector Configuring the Integration Configuring the Integration It is assumed that the installation of Data Protector software components on the SAP DB/MaxDB Server system was successful. Configuration Overview To run or schedule Data Protector SAP DB/MaxDB integration backups the following task must be performed: • An SAP DB/MaxDB user with certain permissions must be added to the Data Protector admin group. See “Configuring Users” on page 263.
Integrating SAP DB/MaxDB and Data Protector Configuring the Integration • InstallMgm • ParamCheckWrite 2. Add the OS user under whose account SAP DB/MaxDB is running to Data Protector admin group. Refer to online Help index: “adding users” for more information on how to do this. 3. Add the operating system root user on the SAP DB/MaxDB Server to either the Data Protector admin or operator user group. Refer to online Help, index keyword “adding users” for more information on how to do this.
Integrating SAP DB/MaxDB and Data Protector Configuring the Integration 4. Select the Blank SAPDB Backup template. With this template, no options and no scheduling is defined, everything is set to default values. Click OK. 5. In the Results Area, in the Client drop-down list, select the client on which the SAP DB/MaxDB Server is running. In a cluster environment, select the virtual hostname for the systems on which the SAP DB/MaxDB Server is running.
Integrating SAP DB/MaxDB and Data Protector Configuring the Integration Figure 3-2 Selecting an SAP DB Server and Instance on UNIX Systems 266 Chapter 3
Integrating SAP DB/MaxDB and Data Protector Configuring the Integration Figure 3-3 Selecting an SAP DB Server and Instance on Windows Systems Click Next. If the SAP DB/MaxDB instance you have selected had not yet been configured to be used with Data Protector, the configuration dialog box appears. In the Configure SAP DB dialog box, specify the SAP DB independent program path parameter.
Integrating SAP DB/MaxDB and Data Protector Configuring the Integration IMPORTANT To backup SAP DB/MaxDB archive logs, select the Data item in the Results Area. The archive log backup is then triggered by selecting the Trans backup type when scheduling the backup or running the backup interactively. See “Backing Up an SAP DB/MaxDB Database” on page 281 for more information on scheduling the backup or running the backup interactively. Figure 3-4 Selecting SAP DB Objects 7.
Integrating SAP DB/MaxDB and Data Protector Configuring the Integration You can also specify whether you want to create additional copies (mirrors) of the backup during the backup session. Specify the desired number of mirrors by clicking the Add mirror and Remove mirror buttons. Select separate devices for the backup and for each mirror. The minimum number of devices required for mirroring SAP DB/MaxDB integration objects equals the number of devices used for backup.
Integrating SAP DB/MaxDB and Data Protector Configuring the Integration You can examine the newly created and saved backup specification in the Backup context. The backup specification itself is stored in the \Config\server\barlists\sapdb\ file on Windows Cell Manager systems and in the /etc/opt/omni/server/barlists/sapdb/ file on UNIX Cell Manager systems.
Integrating SAP DB/MaxDB and Data Protector Configuring the Integration Figure 3-6 Backup Options The following are the SAP DB/MaxDB specific backup options: Change database state Selects the SAP DB/MaxDB database mode during the backup operation. The database can be either switched to the Admin or to the Online mode. If this option is not set, the database remains in the current mode.
Integrating SAP DB/MaxDB and Data Protector Configuring the Integration The value of the Parallelism option must be equal as or lower than the SAP DB/MaxDB MAXBACKUPDEVS parameter. The value of the Parallelism option must also be equal as or lower than the sum of concurrency values for all backup devices selected in the backup specification. For more information on the Data Protector Concurrency option, see online Help index: “concurrency“.
Integrating SAP DB/MaxDB and Data Protector Configuring the Integration Modifying the Configuration of an SAP DB/MaxDB Instance Using the GUI The procedure below describes the re-configuration of an SAP DB/MaxDB instance in Data Protector in an existing backup specification: 1. In the HP OpenView Storage Data Protector Manager, switch to the Backup context. 2. In the Scoping Pane, expand Backup, Backup Specifications, and then SAP DB Server. Click an existing backup specification. 3.
Integrating SAP DB/MaxDB and Data Protector Configuring the Integration Figure 3-7 SAP DB/MaxDB Configuration Click OK to confirm the configuration. Modifying the Configuration of an SAP DB/MaxDB Instance Using the CLI UNIX Login to the SAP DB/MaxDB Server as the user under whose account the SAP DB/MaxDB application is running on the SAP DB/MaxDB Server (for example, the sapdb user in the sapsys group).
Integrating SAP DB/MaxDB and Data Protector Configuring the Integration Then execute the following command: On HP-UX: /opt/omni/lbin/util_sapdb.exe \ [-homedir ] \ -config On other UNIX: /usr/omni/bin/util_sapdb.
Integrating SAP DB/MaxDB and Data Protector Configuring the Integration The password of the SAP DB/MaxDB user created or identified as described in “Configuring Users” on page 263 NOTE The username and the SAP DB/MaxDB independent program path parameter must not contain the single quote character (‘).
Integrating SAP DB/MaxDB and Data Protector Configuring the Integration Checking the Configuration of an SAP DB/MaxDB Instance Using the GUI Follow the procedure below to check the configuration of an SAP DB/MaxDB instance using the GUI: 1. In the HP OpenView Storage Data Protector Manager, switch to the Backup context. 2. In the Scoping Pane, expand Backup, Backup Specifications, and then SAP DB Server. Click an existing backup specification. 3.
Integrating SAP DB/MaxDB and Data Protector Configuring the Integration To obtain an error description, start the following command on the SAP DB/MaxDB Server system: On HP-UX: /opt/omni/lbin/omnigetmsg 12 On other UNIX: /usr/omni/bin/omnigetmsg 12 Windows In a cluster environment, the environment variable OB2BARHOSTNAME must be defined as the virtual hostname before running the util_sapdb.exe command from the command line (on the client).
Integrating SAP DB/MaxDB and Data Protector Configuring the Integration 3. Click Preview Backup to open the Start Preview dialog box. Select the type of backup you want to run as well as the network load. For a description of these options, press F1. Figure 3-8 Previewing a Backup Testing Using the Data Protector CLI To test a backup specification, run the omnib command with the -test_bar option.
Integrating SAP DB/MaxDB and Data Protector Configuring the Integration Refer to the omnib man page for more information on the omnib command. What Happens? The session messages are displayed on the screen during the command execution. The sapdbbar.exe program is started, which then starts the Data Protector testbar2 command.
Integrating SAP DB/MaxDB and Data Protector Backing Up an SAP DB/MaxDB Database Backing Up an SAP DB/MaxDB Database During the backup, the database can be in either the Admin or in the Online mode. To perform an offline backup of an SAP DB/MaxDB instance, a regular Data Protector filesystem backup should be configured. See online Help index: “standatd backup procedure“ for more information on filesystem backups.
Integrating SAP DB/MaxDB and Data Protector Backing Up an SAP DB/MaxDB Database 4. In the Schedule property page, select a date in the calendar click Add to open the Schedule Backup dialog box. 5. Specify Recurring, Time options, Recurring options, and Session options. See Figure 3-9 on page 283. IMPORTANT To backup SAP DB/MaxDB archive logs, the Data item must be selected in the Source property page of the backup specification. Additionally, the Trans backup type under Session options must be selected.
Integrating SAP DB/MaxDB and Data Protector Backing Up an SAP DB/MaxDB Database Figure 3-9 Scheduling the Backup Specification 3. Repeat steps 1 and 2 to schedule another backup. Specify options as described, except the time, which should be set to 1 PM, and the Backup type that should be set to Diff. 4. Repeat steps 1 and 2 to schedule another backup. Specify options as described, except the time, which should be set to 6 PM, and the Backup type that should be set to Diff. 5.
Integrating SAP DB/MaxDB and Data Protector Backing Up an SAP DB/MaxDB Database Running an Interactive Backup Using the Data Protector GUI An interactive backup can be run any time after the backup specification has been created and saved. Backup Procedure To start an interactive backup of an SAP DB/MaxDB backup object using the Data Protector GUI, perform the following steps: 1. In the HP OpenView Storage Data Protector Manager, switch to the Backup context. 2.
Integrating SAP DB/MaxDB and Data Protector Backing Up an SAP DB/MaxDB Database Figure 3-10 Starting an Interactive Backup Messages appear in the Results Area as the backup session proceeds. Upon successful completion of the backup session, the Session completed successfully message and backup size are displayed. Running an Interactive Backup Using the Data Protector CLI You can start an interactive backup from the Data Protector CLI.
Integrating SAP DB/MaxDB and Data Protector Backing Up an SAP DB/MaxDB Database Refer to the omnib man page for more information.
Integrating SAP DB/MaxDB and Data Protector Backing Up an SAP DB/MaxDB Database is the name of the SAP DB/MaxDB media group is the name of the SAP DB/MaxDB medium is the name of the SAP DB/MaxDB pipe is the type of the SAP DB/MaxDB medium 1. On the SAP DB/MaxDB Server create the bsi_env file in a directory of your choice.
Integrating SAP DB/MaxDB and Data Protector Backing Up an SAP DB/MaxDB Database ERROROUTPUT /var/opt/omni/tmp/.bsi_err PARAMETERFILE TIMEOUT_SUCCESS 60 TIMEOUT_FAILURE 30 2. Login to the SAP DB/MaxDB database manager as the SAP DB/MaxDB user created or identified as described in “Configuring Users” on page 263. On the SAP DB/MaxDB Server, execute the following command to login: dbmcli -d -u , 3.
Integrating SAP DB/MaxDB and Data Protector Backing Up an SAP DB/MaxDB Database UNIX medium_put BACKDP-Data[2]/1 \ /var/opt/omni/tmp/.BACKDP_Data[2].1 PIPE DATA medium_put BACKDP-Data[2]/2 \ /var/opt/omni/tmp/.BACKDP_Data[2].2 PIPE DATA 5. Start the SAP DB/MaxDB utility session by executing the following command: util_connect 6. Start the backup.
Integrating SAP DB/MaxDB and Data Protector Restoring an SAP DB/MaxDB Database Restoring an SAP DB/MaxDB Database An SAP DB/MaxDB database can be restored using the Data Protector GUI or CLI. An integrated restore is performed. An SAP DB/MaxDB database can be either restored or migrated. Both can be accomplished using any of the following methods: • The Data Protector GUI: see “Restoring Using the Data Protector GUI” on page 295.
Integrating SAP DB/MaxDB and Data Protector Restoring an SAP DB/MaxDB Database • If the Data Protector Recovery option is not selected and archive logs have not been restored (if restore from a full or diff backup session is performed), the database remains in the Admin mode after the restore. • If the Data Protector Recovery option is not selected and archive logs have been restored, the database is, if the restored archive logs allow it, switched to the Online mode.
Integrating SAP DB/MaxDB and Data Protector Restoring an SAP DB/MaxDB Database When a transactional backup session is selected for restore, or when it is a part of the needed restore chain, and the Use existing archive logs option is selected at the same time, the archive logs from Data Protector media are applied to redo logs. Thereafter, the archive logs on the SAP DB/MaxDB Server are applied to redo logs.
Integrating SAP DB/MaxDB and Data Protector Restoring an SAP DB/MaxDB Database Figure 3-12 SAP DB/MaxDB Archive Logs Restore Process—Redo Logs Details If you select a differential or a transactional backup session to be restored, you can set the integration to: • Perform a full database restore. In this case, the integration automatically determines the chain of needed full, differential or transactional backup sessions when performing the restore.
Integrating SAP DB/MaxDB and Data Protector Restoring an SAP DB/MaxDB Database NOTE During the restore or migration, the archive logs on the SAP DB/MaxDB Server are never deleted. SAP DB/MaxDB Migration Prerequisites The integration supports SAP DB/MaxDB migration, meaning that an SAP DB/MaxDB instance can be restored to some other SAP DB/MaxDB Server or instance than the original.
Integrating SAP DB/MaxDB and Data Protector Restoring an SAP DB/MaxDB Database Restoring Using the Data Protector GUI When performing an SAP DB/MaxDB migration, some additional tasks must first be done in order to prepare the SAP DB/MaxDB Server or instance. These tasks are described in “SAP DB/MaxDB Migration Prerequisites” on page 294. To restore your data, proceed as follows in the HP OpenView Storage Data Protector Manager: 1. In the Context List, select Restore.
Integrating SAP DB/MaxDB and Data Protector Restoring an SAP DB/MaxDB Database IMPORTANT To restore SAP DB/MaxDB archive logs, select the Data item in the Results Area. The archive log restore is then triggered by selecting any of the Trans backup sessions in the next step of this procedure. 3. Right-click the Data item and select Properties from the pop-up menu to open the Properties for Data dialog box.
Integrating SAP DB/MaxDB and Data Protector Restoring an SAP DB/MaxDB Database If you select a Trans or a Diff backup session, you are given a possibility to: • Perform a full restore of the database (the Full restore of database option). In this case, the integration automatically determines the chain of needed full, differential or transactional backup sessions when performing a restore. After the restore has finished, the database is, if the Recovery option is selected, switched to the Online mode.
Integrating SAP DB/MaxDB and Data Protector Restoring an SAP DB/MaxDB Database to get a list of SAP DB/MaxDB objects. • omnidb -sapdb to get details on a specific object, including the SessionID.
Integrating SAP DB/MaxDB and Data Protector Restoring an SAP DB/MaxDB Database Example To restore an instance named “inst1” (together with configuration), backed up on an SAP DB/MaxDB Server named “srv1.company.com” from the last backup session and then perform a recovery until the end of logs, enter the following command: UNIX On HP-UX: /opt/omni/bin/omnir -sapdb -barhost srv1.company.com -instance inst1 -recover -endlogs On other UNIX: /usr/omni/bin/omnir -sapdb -barhost srv1.company.
Integrating SAP DB/MaxDB and Data Protector Restoring an SAP DB/MaxDB Database SAP DB/MaxDB Restore and Recovery Follow the procedure on the next few pages to restore and recover a database using SAP DB/MaxDB utilities from existing Data Protector SAP DB/MaxDB backup session(s).
Integrating SAP DB/MaxDB and Data Protector Restoring an SAP DB/MaxDB Database OUTPUT /var/opt/omni/tmp/.bsi_out ERROROUTPUT /var/opt/omni/tmp/.bsi_err TIMEOUT_SUCCESS 60 TIMEOUT_FAILURE 30 On other UNIX: BACKINT /usr/omni/bin/sapdb_backint INPUT /var/opt/omni/tmp/.bsi_in OUTPUT /var/opt/omni/tmp/.bsi_out ERROROUTPUT /var/opt/omni/tmp/.bsi_err TIMEOUT_SUCCESS 60 TIMEOUT_FAILURE 30 2.
Integrating SAP DB/MaxDB and Data Protector Restoring an SAP DB/MaxDB Database Create SAP DB/MaxDB media in an SAP DB/MaxDB media group.
Integrating SAP DB/MaxDB and Data Protector Restoring an SAP DB/MaxDB Database Windows recover_start BACKDP-Data[2] DATA EBID " :1 \\.\Pipe\.BACKDP-Data[2].1,TEST :2 \\.\Pipe\.BACKDP-Data[2].2" UNIX recover_start BACKDP-Data[2] DATA EBID " :1 /var/opt/omni/tmp/.BACKDP-Data[2].1, :2 /var/opt/omni/tmp/.BACKDP-Data[2].
Integrating SAP DB/MaxDB and Data Protector Restoring an SAP DB/MaxDB Database SAP DB/MaxDB Restore and Recovery Options SAP DB/MaxDB restore and recovery options can be accessed in the Data Protector GUI by clicking the Options tab in the Restore context after an SAP DB/MaxDB object has been selected.
Integrating SAP DB/MaxDB and Data Protector Restoring an SAP DB/MaxDB Database Restore to client / -destination When using the GUI, in the drop-down list, select an SAP DB/MaxDB Server to which you want to restore the database. When using the CLI, specify the -destination option and the name of the SAP DB/MaxDB Server as the argument.
Integrating SAP DB/MaxDB and Data Protector Restoring an SAP DB/MaxDB Database When using the CLI, it is not possible to change the user name and the group name. The same user as used during the backup session is used. Settings / N/A Click this button if the instance you are restoring to is not yet configured for use with this integration. See step 4. on page 273 for information on parameters that must be entered. When using the CLI, this option is not available.
Integrating SAP DB/MaxDB and Data Protector Restoring an SAP DB/MaxDB Database IMPORTANT When using this option, make sure that the backup session selected in the Properties for Data dialog box (when using GUI) or by the -session option (when using CLI) will restore enough data for the integration to apply the redo logs until the latest version or until the specified date and time. For information on how to access the Properties for Data dialog box, refer to step 3 on page 296.
Integrating SAP DB/MaxDB and Data Protector Restoring an SAP DB/MaxDB Database NOTE The selected time is the system time on the system running the Data Protector GUI or CLI. If the system to be recovered is not in the same time zone as the system running the Data Protector GUI or CLI, the point of recovery is adjusted to the local time setting on the system to be restored.
Integrating SAP DB/MaxDB and Data Protector Restoring an SAP DB/MaxDB Database Disaster Recovery Disaster recovery is a very complex process that involves products from several vendors. As such, successful disaster recovery depends on all the vendors involved. The information provided here is intended to be used as a guideline. Check the instructions from the database/application vendor on how to prepare for a disaster recovery.
Integrating SAP DB/MaxDB and Data Protector Monitoring an SAP DB/MaxDB Backup and Restore Monitoring an SAP DB/MaxDB Backup and Restore The Data Protector GUI enables you to monitor current or view previous backup and restore sessions. Monitoring is automatically activated when you start a restore or backup interactively. Monitoring Current Sessions To monitor a currently running session using the Data Protector GUI, proceed as follows: 1. In the Context List, click Monitor.
Integrating SAP DB/MaxDB and Data Protector Monitoring an SAP DB/MaxDB Backup and Restore NOTE All completed or aborted sessions are automatically removed from the Results Area of the Monitor context if you restart the Data Protector GUI. For detailed information on a completed or aborted session, see “Viewing Previous Sessions”. Viewing Previous Sessions To view a previous session using the Data Protector GUI, proceed as follows: 1. In the Context List, click Internal Database. 2.
Integrating SAP DB/MaxDB and Data Protector Monitoring an SAP DB/MaxDB Backup and Restore Figure 3-17 Viewing a Previous Session 312 Chapter 3
Integrating SAP DB/MaxDB and Data Protector Troubleshooting Troubleshooting This section lists problems you might encounter when using the Data Protector SAP DB/MaxDB integration. For general Data Protector troubleshooting information, see the HP OpenView Storage Data Protector Troubleshooting Guide. Before You Begin ✓ Ensure that the latest official Data Protector patches are installed. See online Help index: “patches” on how to verify this.
Integrating SAP DB/MaxDB and Data Protector Troubleshooting Problem An SAP DB/MaxDB instance cannot be started after restore. Action Using the SAP DB/MaxDB db_restartinfo command, check if the instance can be restarted. • If the instance cannot be restarted, most probably the existing log volumes do not contain enough data to restart the instance from data volumes. The required differential or transactional backups might not have been restored.
Integrating SAP DB/MaxDB and Data Protector Troubleshooting Action Start the SAP DB/MaxDB x_server. Refer to the SAP DB/MaxDB documentation for information on how to do that. Problem Data Protector reports the following error: Error: SAPDB responded with: -24988,ERR_SQL: sql error 1,database not running Action Start the SAP DB/MaxDB instance. Refer to the SAP DB/MaxDB documentation for information on how to do that.
Integrating SAP DB/MaxDB and Data Protector Troubleshooting Action Set the TimeoutSuccess environment variable on the Cell Manager by running the following command: util_cmd -putopt SAPDB TimeoutSuccess 1000 -sublist Environment For more information on the util_cmd command, refer to “Data Protector SAP DB/MaxDB Configuration File” on page 259. You can also set the TimeoutSuccess environment variable using the Data Protector GUI.
Glossary access rights See user rights. ACSLS (StorageTek specific term) The Automated Cartridge System Library Server (ACSLS) software that manages the Automated Cartridge System (ACS). Active Directory (Windows specific term) The directory service in a Windows network. It contains information about resources on the network and makes them accessible to users and applications.
Glossary (disk partitioning and logical volume configuration) and automatic recovery of the original system configuration and user data that was backed up during the full client backup. These files are stored as an ASR archive file on the Cell Manager (in \Config\Serve r\dr\asr on a Windows Cell Manager or in /etc/opt/omni/server/dr/asr/ on a UNIX Cell Manager) as well as on the backup medium.
Glossary backup object A backup unit that contains all items backed up from one disk volume (logical disk or mount point). The backed up items can be any number of files, directories, or the entire disk or mount point. Additionally, a backup object can be a database entity or a disk image (rawdisk). A backup object is defined by: specified in a backup specification or an interactive session.
Glossary Registry for example. File selection lists such as include-lists and exclude-lists can be specified. instant copies of EMC Symmetrix standard devices. See also BCV. backup system (ZDB specific term) A system connected to target volumes of one or multiple application systems. The backup system is typically connected to a ZDB disk arraybackup device to perform the backup of the data in a replica. See also application system, target volume, and replica.
Glossary BC Process (EMC Symmetrix specific term) A protected storage environment solution that has defined specially configured EMC Symmetrix devices as mirrors or Business Continuance Volumes to protect data on EMC Symmetrix standard devices. See also BCV. BC VA (HP StorageWorks Virtual Array specific term) Business Copy VA allows you to maintain internal copies of HP StorageWorks Virtual Array LUNs for data backup or data duplication within the same virtual array.
Glossary BRBACKUP (SAP R/3 specific term) An SAP R/3 backup tool that allows an online or offline backup of the control file, of individual data files, or of all tablespaces and, if necessary, of the online redo log files. See also SAPDBA, BRARCHIVE and BRRESTORE.
Glossary catalog protection Defines how long information about backed up data (such as file names and file versions) is kept in the IDB. See also data protection. CDB The Catalog Database is a part of the IDB that contains information about backups, object copies, restores, media management sessions, and backed up data. Depending on the selected logging level, it also contains file names and file versions. This part of the database is always local to the cell. See also MMDB.
Glossary If the specified channel is of type ‘sbt_tape’ and Oracle is integrated with Data Protector, the server process will attempt to read backups from or write data files to Data Protector. circular logging (Microsoft Exchange Server and Lotus Domino Server specific term) Circular logging is a Microsoft Exchange Server database and Lotus Domino Server database mode, in which the transaction log file contents are periodically overwritten after the corresponding data is committed to the database.
Glossary Data Protector cells is highly recommended See also MoM. COM+ Registration Database (Windows specific term) The COM+ Registration Database and the Windows Registry store COM+ application attributes, class attributes, and computer-level attributes. This guarantees consistency among these attributes and provides common operation on top of these attributes.
Glossary controls the object copy and object consolidation sessions and runs on the Cell Manager system. data file (Oracle and SAP R/3 specific term) A physical file created by Oracle that contains data structures such as tables and indexes. A data file can only belong to one Oracle database. data protection Defines how long the backed up data on media remains protected, that is, Data Protector will not overwrite it.
Glossary database server A computer with a large database stored on it, such as the SAP R/3 or Microsoft SQL database. A server has a database that can be accessed by clients. delta backup A delta backup is a backup containing all the changes made to the database from the last backup of any type. See also backup types Dbobject (Informix Server specific term) An Informix Server physical database object. It can be a blobspace, dbspace, or logical log file.
Glossary the tape, and so on. In other words, if the data rate written to the tape is less or equal the data rate which can be delivered to the device by the computer system, then the device is streaming. Streaming significantly improves the performance of the device and use of space. DHCP server A system running the Dynamic Host Configuration Protocol (DHCP) providing dynamic IP address assignment and network configuration for DHCP clients.
Glossary it to the Media Agent, which then moves it to the device. During a restore session the Disk Agent receives data from the Media Agent and writes it to the disk. Disk Agent concurrency The number of Disk Agents that are allowed to send data to one Media Agent concurrently. disk discovery The detection of disks during client backup with disk discovery.
Glossary Distributed File System (DFS) A service that connects file shares into a single namespace. The file shares can reside on the same or on different computers. DFS provides client access to the resources in a location-transparent manner. DMZ The Demilitarized Zone (DMZ) is a network inserted as a "neutral zone" between a company's private network (intranet) and the outside public network (Internet). It prevents outside users from getting direct access to company servers in the intranet.
Glossary emergency boot file (Informix Server specific term) The Informix Server configuration file ixbar. that resides in the directory /etc (on Windows) or \etc (on UNIX). is the Informix Server home directory and is the value of the SERVERNUM configuration parameter. Each line of the emergency boot file corresponds to one backup object.
Glossary failover (HP StorageWorks EVA specific term) An operation that reverses the roles of source and destination in CA+BC EVA configurations. See also CA+BC EVA. FC bridge See Fibre Channel bridge Fibre Channel An ANSI standard for high-speed computer interconnection. Using either optical or copper cables, it allows the high speed bidirectional transmission of large data files and can be deployed between sites kilometers apart.
Glossary filesystem The organization of files on a hard disk. A filesystem is backed up so that the file attributes and the file contents are stored on the backup media. first level mirror (HP StorageWorks Disk Array XP specific term) HP StorageWorks Disk Array XP allows up to three mirror copies of a Primary Volume and each of these copies can have additional two copies. The three mirror copies are called first level mirrors. See also Primary Volume, and MU numbers.
Glossary are no changes from the previous backup. See also incremental ZDB. global options file A file that allows you to customize Data Protector. It explains the global options, which cover various aspects of Data Protector, typically time-outs and limits, and affect the entire Data Protector cell. The file is located in the /etc/opt/omni/ server/options directory on HP-UX and Solaris systems and in the \Config\Serve r\Options directory on Windows systems.
Glossary HP ITO See OVO. HP OpC See OVO. HP OpenView SMART Plug-In (SPI) A fully integrated, out-of-the-box solution which "plugs into" HP OpenView Operations, extending the managed domain. Through the Data Protector integration, which is implemented as an HP OpenView SMART Plug-In, a user can have an arbitrary number of Data Protector Cell Managers monitored as an extension to HP OpenView Operations (OVO). HP OVO See OVO.
Glossary HP StorageWorks Virtual Array LUN A logical partition of a physical disk within an HP StorageWorks Virtual Array. LUNs are entities that can be replicated in the HP StorageWorks Business Copy VA configuration, or can be used as standalone entities. See also BC VA and replica. HP VPO See OVO.
Glossary incremental1 mailbox backup An incremental1 mailbox backup backs up all the changes made to the mailbox after the last full backup. incremental (re)-establish (EMC Symmetrix specific term) A BCV or SRDF control operation. In BCV control operations, an incremental establish causes the BCV device to be synchronized incrementally and to function as an EMC Symmetrix mirrored medium. The EMC Symmetrix devices must have been previously paired.
Glossary two kinds of stores: mailbox stores and public folder stores. A mailbox store consists of mailboxes that belong to individual users. A public folder store contains public folders and messages that are shared among several users. See also Key Management Service and Site Replication Service. Informix Server (Informix Server specific term) Refers to Informix Dynamic Server. initializing See formatting.
Glossary Markup Language (HTML) pages by using the Hypertext Transport Protocol (HTTP). IP address Internet Protocol address is a numeric address of a system used to uniquely identify the system on the network. The IP address consists of four groups of numbers separated by periods (full stops). ISQL (Sybase specific term) A Sybase utility used to perform system administration tasks on Sybase SQL Server. ITO See OVO. jukebox See library.
Glossary LISTENER.ORA (Oracle specific term) An Oracle configuration file that describes one or more Transparent Network Substrate (TNS) listeners on a server. load balancing By default, Data Protector automatically balances the usage of devices selected for backup, so that they are used evenly. Load balancing optimizes the device usage by balancing the number of objects written to each device.
Glossary of the logging level used during backup. Data Protector provides four logging levels: Log All, Log Directories, Log Files, and No Log. The different logging level settings influence the IDB growth, backup speed, and the convenience of browsing data for restore. logical-log files This applies to online database backup. Logical-log files are files in which modified data is first stored before being flushed to disk.
Glossary and recovery information between Lotus Domino Server and a backup solution, like Data Protector. LVM A Logical Volume Manager is a subsystem for structuring and mapping physical disk space to logical volumes on UNIX systems. An LVM system consists of several volume groups, where each volume group has several volumes. Magic Packet See Wake ONLAN. mailbox (Microsoft Exchange Server specific term) The location to which e-mail is delivered, which is set up by the administrator for each user.
Glossary media allocation policy Determines in which sequence media are used for backup. The Strict allocation policy directs Data Protector to prompt for a specific medium. The Loose policy directs Data Protector to prompt for any suitable medium. The Formatted First policy directs Data Protector to give preference to unknown media, even if unprotected media are available in the library.
Glossary modification date is kept. Files not present on the disk are always restored. See also overwrite. Microsoft Exchange Server A “client-server” messaging and a workgroup system that offers a transparent connection to many different communication systems. It provides users with an electronic mail system, individual and group scheduling, online forms, and workflow automation tools. It provides a developer with a platform on which to build custom informationsharing and messaging-service applications.
Glossary environment, this part of the database can be common to all cells. See also CMMDB, CDB. number (0, 1 or 2), used to indicate a first level mirror. See also first level mirror. MoM Several cells can be grouped together and managed from a central cell. The management system of the central cell is the Manager-of-Managers (MoM). The cells are called MoM clients. The MoM enables you to configure and manage multiple cells from a central point.
Glossary backup and at least one incremental backup, into a new, consolidated version of this object. object copy A copy of a specific object version that is created during an object copy session or a backup session with object mirroring. object copy session A process that creates an additional copy of the backed up data on a different media set. During an object copy session, the selected backed up objects are copied from the source to the target media.
Glossary standalone and SCSI library devices can be used for offline recovery. Recovery of the Cell Manager is always offline. directory \etc (on Windows) or /etc/ (on UNIX). offline redo log See archived redo log online backup A backup performed while a database application remains available for use. The database is placed into a special backup mode of operation for the time period that the backup application requires access to the original data objects.
Glossary online redo log (Oracle specific term) Redo logs that have not been archived, but are either available to the instance for recording database activity or are filled and waiting to be archived or reused. See also archived redo log. OpC See OVO. OpenSSH A set of network connectivity tools used to access remote machines securely, by using a variety of authentication and encryption methods.
Glossary number of systems and applications on in a network. Data Protector provides an integration into this management product. This integration is implemented as a SMART Plug-In for OVO management servers on HP-UX and Solaris. Earlier versions of OVO were called IT/Operation, Operations Center and Vantage Point Operations. See also merging. the system during Enhanced Automated Disaster Recovery (EADR).
Glossary • SUSPENDED - The link between the mirrored disks is suspended. That means that both disks are accessed and updated independently. However, the mirror relationship is still maintained and the pair can be resynchronized without transferring the complete disk. parallel restore Restoring backed up data to multiple disks at the same time (that is, in parallel) by running multiple Disk Agents, that receive data from one Media Agent.
Glossary Standard HP StorageWorks Disk Array XP LDEVs that act as a primary volume for the CA and BC configurations. The P-VOL is located in the MCU. See also Secondary Volume (S-VOL). protection See data protection and also catalog protection. public folder store (Microsoft Exchange Server specific term) The part of the Information Store that maintains information in public folders. A public folder store consists of a binary rich-text .edb file and a streaming native internet content .stm file.
Glossary RDF1/RDF2 (EMC Symmetrix specific term) A type of SRDF device group. Only RDF devices can be assigned to an RDF group. An RDF1 group type contains source (R1) devices and an RDF2 group type contains target (R2) devices. RDS The Raima Database Server process (service) runs on the Data Protector Cell Manager and manages the IDB. The process is started when Data Protector is installed on the Cell Manager.
Glossary recycle A process that removes the data protection from all backed up data on a medium, allowing Data Protector to overwrite it during one of the next backups. Data that belongs to the same session(s) but resides on other media is also unprotected. Recycling does not actually alter the data on the medium. redo log (Oracle specific term) Every Oracle database has a set of two or more redo log files. The set of redo log files for the database is known as the database's redo log.
Glossary replica set (ZDB specific term) A group of replicas, all created using the same backup specification. See also replica and replica set rotation. replica set rotation (ZDB specific term) The use of a replica set for regular backup production: Each time the same backup specification requiring the use of a replica set is run, a new replica is created and added to the set, until the maximum number for the set is reached.
Glossary Scheduler A function that controls when and how often automatic backups occur. By setting up a schedule, you automate the start of backups. Secondary Volume (S-VOL) (HP StorageWorks Disk Array XP specific term) Secondary Volumes, or S-VOLs, are XP LDEVs that act as a secondary CA or BC mirror of another LDEV (a P-VOL). In the case of CA, S-VOLs can be used as failover devices in a MetroCluster configuration.
Glossary on the network. Systems with shared disks can be backed up without a Data Protector Disk Agent installed. SIBF The Serverless Integrations Binary Files (SIBF) is a part of the IDB that stores raw NDMP meta data. This data is necessary to perform restore of NDMP objects. Site Replication Service (Microsoft Exchange Server specific term) The Microsoft Exchange Server 2000/ 2003 service that permits compatibility with Microsoft Exchange Server 5.5 by emulating the Exchange Server 5.
Glossary copying processes normally continue after creation. See also snapshot. split mirror backup (EMC Symmetrix specific term) See ZDB to tape. source (R1) device (EMC Symmetrix specific term) An EMC Symmetrix device that participates in SRDF operations with a target (R2) device. All writes to this device are mirrored to a target (R2) device in a remote EMC Symmetrix unit. An R1 device must be assigned to an RDF1 group type. See also target (R2) device.
Glossary sqlhosts file (Informix Server specific term) An Informix Server connectivity information file (on UNIX) or registry (on Windows) that contains the names of each of the database servers and any aliases to which the clients on a host computer can connect. SRD file The Data Protector System Recovery Data (SRD) file contains system information required for installing and configuring the operating system in case of a disaster.
Glossary standard security (MS SQL specific term) Standard security uses the login validation process of the Microsoft SQL Server for all connections. Standard security is useful in network environments with a variety of clients, some of which may not support trusted connections. It also provides backward compatibility for older versions of the Microsoft SQL Server. See also integrated security.
Glossary conventional full backup in terms of data, without putting stress on the production servers or the network. A synthetic full backup is created from a previous full backup and any number of incremental backups. system disk A system disk is a disk containing operating system files. Microsoft terminology defines the system disk as a disk containing the files required for initial step of boot process.
Glossary disk/partition as the volume/disk/ partition containing files required for the initial step of the boot process. operations. An R2 device must be assigned to an RDF2 group type. See also source (R1) device SysVol (Windows specific term) A shared directory that stores the server copy of the domain’s public files, which are replicated among all domain controllers in the domain. target system (Disaster Recovery specific term) A system after a computer disaster has occurred.
Glossary TimeFinder (EMC Symmetrix specific term) A business continuation process that creates an instant copy of single or multiple Symmetrix Logical Devices (SLDs). The instant copy is created on specially preconfigured SLDs called BCVs and is accessible via a separate device address to the system(s). TLU Tape Library Unit. TNSNAMES.ORA (Oracle and SAP R/ 3 specific term) A network configuration file that contains connect descriptors mapped to service names.
Glossary application system and can be presented to the backup system which performs the backup. See also Microsoft Volume Shadow Copy service (VSS). TSANDS.CFG file (Novell NetWare specific term) A file that allows you to specify the names of containers where you want backups to begin. It is text file located in the SYS:SYSTEM\TSA directory on the server where TSANDS.NLM is loaded. unattended operation See lights-out operation.
Glossary for reuse in subsequent backups. The vaulting procedure depends on your company's backup strategy and policies for data protection/reliability. verify A function that lets you check whether the Data Protector data on a specified medium is readable. Additionally, consistency within each block can be checked if the backup was performed with the cyclic redundancy check (CRC) option ON.
Glossary one or more physical volumes. There can be more than one volume group on the system. volume mountpoint (Windows specific term) An empty directory on a volume that can be used to mount another volume. The volume mount point acts as a gateway to the target volume. Provided that the volume is mounted, users and applications can refer to the data on the mounted volume by the full (merged) filesystem path as if both volumes are one integral part.
Glossary WINS server A system running Windows Internet Name Service software that resolves Windows networking computer names to IP addresses. Data Protector can back up WINS server data as part of the Windows configuration. writer (MS VSS specific term) A process that initiates change of data on the original volume. Writers are typically applications or system services that write persistent information on a volume.
Glossary array as a backup of the source volumes at a specific point in time, in the same way as with ZDB to disk. However, data in the replica is also streamed to a backup medium, as with ZDB to tape. If this backup method is used, data backed up in the same session can be restored using the instant recovery process, the standard Data Protector restore from tape, or on split mirror arrays, split mirror restore.
Glossary G-52
Index Index A aborting backup sessions SAP R/3 integration, 198 advantages SAP DB integration, 254 SAP R/3 integration, 145 architecture SAP DB integration, 258 SAP R/3 integration, 151, 152 B backing up Oracle, 55–69 backup options, 44 backup specifications, creating, 37 backup templates, 36 backup types, 3 examples, using RMAN, 66 offline, 55 online, 56 recovery catalog, 58 scheduling backups, 58 starting backups, 60–69 starting backups, using CLI, 61 starting backups, using GUI, 60 starting backups, us
Index BRARCHIVE, 149, 187 BRBACKUP, 149, 186, 202 BRRESTORE, 150, 157, 208 C checking configuration Oracle integration, 33 SAP DB integration, 276 SAP R/3 integration, 175 concepts Oracle integration, 5 SAP DB integration, 256–258 SAP R/3 integration, 149–157 configuration files SAP DB integration, 259–262 SAP R/3 integration, 158–164 configuration files, modifying SAP DB integration, 260 SAP R/3 integration, 161 configuring Oracle, 11–35 checking configuration, 33 example, CLI , 32 prerequisites, 13 config
Index SAP DB integration, 251 SAP R/3 integration, 148 M manual balancing SAP R/3 integration, 193 manual balancing, creating backup specifications SAP R/3 integration, 194 MC/ServiceGuard clusters, configuration, 22 linking Oracle with the MML, 14 Media Management Library See MML migration SAP DB restore, 254, 294 MML (Data Protector Media Management Library) linking with Oracle, OpenVMS, 16 linking with Oracle, UNIX, 14 modifying configuration files SAP DB integration, 260 SAP R/3 integration, 161 modifyi
Index R RAC, configuring Oracle Servers on HP-UX, 14 on other UNIX systems, 14 recovery Oracle integration, options, 88 recovery catalog, Oracle integration backup, 58 restore, 74 Recovery Manager See RMAN removing the Oracle integration, 112 from HP-UX , 112 from Solaris and other UNIX systems, 113 restore flow SAP DB integration, 257 SAP R/3 integration, backint mode, 157 SAP R/3 integration, RMAN mode, 157 restore options SAP DB integration, 304 restore types Oracle integration, 4 restoring Oracle, 70–10
Index instance objects, 252 introduction, 252 limitations, 251 monitoring sessions, 310 parallelism, 271 prerequisites, 251 restore, 290–309 restore flow, 257 restore, migration, 254, 294 restore, overview, 290 testing, 278 troubleshooting, 313–316 util_cmd, 260 viewing sessions, 311 SAP DB restore, 290–309 disaster recovery, 309 migration, 254, 294 overview, 290 restore flow, 257 restore options, 304 using another device, 308 using CLI, 297 using GUI, 295 using SAP DB utilities, 299 SAP DB troubleshooting,
Index SAP R/3 integration, 202 standby databases, Oracle integration restore, 84 starting backups, Oracle integration, 60–69 using CLI, 61 using GUI, 60 using RMAN, 62 starting backups, SAP DB integration, 281–289 using CLI, 285 using GUI, 284 using SAP DB utilities, 286 starting backups, SAP R/3 integration, 197–203 using BRBACKUP, 202 using CLI, 202 using GUI, 200 using sapdba, 202 T testing the integration SAP DB integration, 278 SAP R/3 integration, 195 transactional backups SAP DB integration, 252 tr
