Page 1 HP Data Protector A.06.1 1 Integration guide for Oracle and SAP B6960-90158 Part number: B6960-90158 First edition: September 2009...
Page 2 Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services.
Page 3: Table Of Contents
Linking on HP OpenVMS systems ............36 Configuring Oracle user accounts ..............37 Configuring Oracle operating system user accounts ........37 Configuring Oracle database users accounts ........... 39 Configuring user accounts on HP OpenVMS ..........39 Integration guide for Oracle and SAP...
Page 4 Configuring Oracle databases ..............41 Using the Data Protector GUI ..............42 Using the Data Protector CLI ..............45 Checking the configuration ................53 Using the Data Protector GUI ..............53 Using the Data Protector CLI ..............53 Setting environmental variables ..............55 Using the Data Protector GUI ..............
Page 5 Connection strings used in the examples ..........120 SBT_LIBRARY parameter ..............121 Example of full database restore and recovery ........121 Example of point-in-time restore ............122 Example of tablespace restore and recovery .......... 124 Example of datafile restore and recovery ..........126 Example of archive log restore .............
Page 6 Choosing authentication mode ..............173 Configuring SAP R/3 databases ..............173 Before you begin ................174 Using the Data Protector GUI ............... 174 Using the Data Protector CLI ..............177 Checking the configuration ................ 179 Using the Data Protector GUI ............... 179 Using the Data Protector CLI ..............
Page 7 Prerequisites on the SAP side of the integration ........208 Configuration problems ............... 209 Backup problems ................212 Restore problems ................214 Troubleshooting on UNIX systems ..............217 Prerequisites concerning the Oracle side of the integration ....... 217 Prerequisites on the SAP side of the integration ........221 Configuration problems ...............
Page 8 Using the Data Protector CLI ..............250 Using SAP DB/MaxDB utilities ............. 251 Restore ......................255 Restore and recovery overview ..............255 Before you begin ..................259 Restoring using the Data Protector GUI ............259 Restoring using the Data Protector CLI ............262 Restoring using SAP DB/MaxDB utilities ............
Page 9 Figures Data Protector graphical user interface ..........25 Data Protector Oracle integration concept ........... 32 Finding the Oracle user ..............37 Configuring Oracle - General (Windows) ........... 42 Configuring Oracle - General (UNIX) ..........42 Configuring Oracle - Primary ............43 Configuring Oracle - Catalog ............
Page 10 Devices page ................107 Oracle duplicate options ..............113 Resuming a session ................ 137 Checking the status of the Oracle listener ......... 141 SAP R/3 architecture ..............155 SAP R/3 architecture: backint mode ..........156 SAP R/3 architecture: RMAN mode ..........158 Specifying an SAP R/3 system and Oracle instance ......
Page 11 Properties for data ................. 261 SAP DB/MaxDB restore and recovery options ........270 Integration guide for Oracle and SAP...
Page 12 Tables Edition history ................. 13 Document conventions ..............23 Oracle database user accounts ............39 Oracle database configuration parameters ......... 48 Environmental variables ..............55 Oracle backup options ..............68 MML filenames on different platforms ..........88 Required database states ..............97 Backup types ................
Page 13: Publication History
Guide 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...
Page 14 Publication history...
Page 15: About This Guide
Documentation & Help component on Windows or the OB2-DOCS component on UNIX. Once installed, the guides reside in the Data_Protector_home\docs directory on Windows and in the /opt/omni/doc/C directory on UNIX. You can find these documents from the Manuals page of the HP Business Support Center website: http://www.hp.com/support/manuals In the Storage section, click Storage Software and then select your product.
Page 16 This guide describes the integrations of Data Protector with Oracle, SAP R/3, and SAP DB/MaxDB. • HP Data Protector integration guide for IBM applications: Informix, DB2, and Lotus Notes/Domino This guide describes the integrations of Data Protector with the following IBM applications: Informix Server, IBM DB2, and Lotus Notes/Domino Server.
Page 17 HP Data Protector integration guide for HP Reporter This manual describes how to install, configure, and use the integration of Data Protector with HP Reporter. It is intended for backup administrators. It discusses how to use the application for Data Protector service management.
Page 18: Online Help
• HP Data Protector product announcements, software notes, and references This guide gives a description of new features of HP Data Protector A.06.1 1. It also provides information on installation requirements, required patches, and limitations, as well as known issues and workarounds.
Page 19: Documentation Map
Documentation map Abbreviations Abbreviations in the documentation map that follows are explained below. The guide titles are all preceded by the words “HP Data Protector”. Abbreviation Guide Command line interface reference Concepts Concepts guide Disaster recovery guide Getting started guide...
Page 20: Map
Abbreviation Guide Install Installation and licensing guide MO GS Media Operations getting started guide MO RN Media Operations product announcements, software notes, and references MO UG Media Operations user guide MPE/iX MPE/iX system user guide Product announcements, software notes, and references Trouble Troubleshooting guide ZDB Admin...
Page 21: Integrations
Integrations Look in these guides for details of the following integrations: Integration Guide HP Operations Manager for UNIX/for Windows IG-OMU, IG-OMW HP Performance Manager IG-PM/PA HP Performance Agent IG-PM/PA Integration guide for Oracle and SAP...
Page 22 Integration Guide HP Reporter IG-R HP Service Information Portal IG-SIP 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...
Page 23: Document Conventions And Symbols
Document conventions and symbols Table 2 Document conventions Convention Element Blue text: Table 2 on page 23 Cross-reference links and e-mail addresses Blue, underlined text: http://www.hp.com Website addresses Italic text Text emphasis • File and directory names • System output Monospace text •...
Page 24: Data Protector Graphical User Interface
NOTE: Provides additional information. TIP: Provides helpful hints and shortcuts. Data Protector graphical user interface Data Protector provides a cross-platform (Windows and UNIX) graphical user interface. You can use the original Data Protector GUI (Windows only) or the Data Protector Java GUI. For information about the Data Protector graphical user interface, see the online Help.
Page 25: General Information
General information General information about Data Protector can be found at http://www.hp.com/go/ dataprotector. HP technical support For worldwide technical support information, see the HP support website: http://www.hp.com/support Before contacting HP, collect the following information: • Product model names and numbers •...
Page 26: Subscription Service
Subscription service HP recommends that you register your product at the Subscriber's Choice for Business website: http://www.hp.com/go/e-updates After registering, you will receive e-mail notification of product enhancements, new driver versions, firmware updates, and other product resources. HP websites For additional information, see the following HP websites: •...
Page 27: Integrating Oracle And Data Protector
1 Integrating Oracle and Data Protector Introduction Data Protector offers offline as well as online backup of the Oracle Server instances. To enable database recovery from an online backup, the respective Oracle Server instance must operate in the ARCHIVELOG mode. The online backup concept is widely accepted.
Page 28: Integration Concepts
Flashback logs, the current control file, and online redo logs are not backed up. • In Oracle Data Guard environment, backup of standby database. Restore types Using the Data Protector Oracle integration, you can restore the following: • The whole database or parts of it •...
Page 29 How does the integration work? Ob2rman.pl executes RMAN, which directs the Oracle server processes on the target database to perform backup, restore and recovery. RMAN maintains the required information about the target databases in the recovery catalog, the Oracle central repository of information, and in the control file of a particular target database. The main information which ob2rman.pl provides to RMAN is: •...
Page 30 regardless of the backup type (full or incremental), is selected and controlled by Oracle. Oracle incremental backups can be differential or cumulative. By default, Data Protector performs Oracle differential incremental backups. By changing the default RMAN script created by Data Protector, you can specify also a cumulative backup. For information on differential and cumulative Oracle backups, see the Oracle Recovery Manager User’s Guide.
Page 31 specified in the backup specification. Further on, ob2rman.pl prepares the environment to start the backup, and issues the RMAN backup command. RMAN instructs the Oracle Server processes to perform the specified command. The Oracle Server processes initialize the backup through MML, which establishes a connection to the Data Protector Backup Session Manager.
Page 32: Data Protector Oracle Integration Concept
The concept of Oracle integration, data and the control flow are shown in Figure on page 32, and the related terms are explained in the following table. Figure 2 Data Protector Oracle integration concept Oracle 10g/1 1g database files can also be part of ASM configuration. They can reside in the flash recovery area.
Page 33: Configuring The Integration
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 Data Protector installation and licensing guide for information about licensing. •...
Page 34: Limitations
Pre-exec or Post-exec option when creating a backup specification. • On an HP OpenVMS client running the Oracle integration, you can only configure a Data Protector admin user with the username <Any> and the group name <Any>. This limitation is due to the lack of the user group name concept on OpenVMS.
Page 35: Before You Begin
RAC: Configure an Oracle database on every node from where you want to run backups and restores. HP-UX with RAC: If you want to use virtual hostname, create an MC/ServiceGuard package containing only the virtual IP and the virtual hostname parameters and distribute it among the RAC nodes.
Page 36: Linking Oracle Server With The Data Protector Mml
Data Protector. Linking on HP OpenVMS systems On Oracle Server systems running on HP OpenVMS, link the MML SYS$SHARE:LIBOBK2SHR64.EXE with the Oracle Server: Make sure Oracle RMAN is set up and you are able to access it. This can be achieved by performing a test backup using the following RMAN script: allocate channel d1 type disk;...
Page 37: Configuring Oracle User Accounts
You are now ready to use the MML with RMAN to perform backups. For information on how to use RMAN, see the Oracle documentation. After relinking To test the MML (SBT) interface, configure Oracle using the GUI (see “Configuring Oracle databases”...
Page 38 Data Protector admin or operator user group. Configure a Data Protector admin user with the username <Any> HP OpenVMS clients and the group name <Any>. For information on adding users to Data Protector user groups, see the online Help index: “adding users”.
Page 39: Configuring Oracle Database Users Accounts
Oracle Data Guard environments. Needed to back up the standby user database. Configuring user accounts on HP OpenVMS To configure an Oracle user on HP OpenVMS, proceed as follows: Modify the location of ORAUSER.COM and ORATAB files as instructed in OMNI$ROOT:[LOG]LOGIN.COM based on the Oracle version used. For example: •...
Page 40 Uncomment the following lines in OMNI$ROOT:[LOG]LOGIN.COM: $@OMNI$ROOT:[BIN]OMNI$CLI_SETUP.COM $@OMNI$ROOT:[BIN.PERLl]PERL_SETUP.COM $DEFINE /NOLOG /PROCESS PERL_ENV_TABLES "LNM$PROCESS", "LNM$JOB", "LNM$SERVER", "LNM$GROUP", "LNM$SYSTEM" Oracle 10g R2 Uncomment the following line: $@OMNI$ROOT:[BIN]OMNI$ORA_OCI_SETUP.COM Oracle 9i If you run the Media Agent and Data Protector Oracle integration agents on the same OpenVMS system, modify the group ID of the omniadmin user as DBA using the MCR AUTHORIZE utility: a.
Page 41: Configuring Oracle Databases
TIP: To determine the status of processes (OMNI$I*) and subprocesses (OMNI$ADMIN_*) on your OpenVMS system, use the following command procedure: $@OMNI$ROOT:[BIN}OMNI$DIAGNOSE.COM This command procedure displays the active parent processes, the session of job name, and the logfile name. Configuring Oracle databases Configuration of an Oracle database consists of providing Data Protector with the following data: •...
Page 42: Using The Data Protector Gui
Using the Data Protector GUI Configure an Oracle database when you create the first backup specification for the database. Start with the procedure described in “Creating backup specifications” on page 58 and at Step 5 on page 62 proceed as follows: In the Configure Oracle dialog box and in the General page, specify the pathname of the Oracle Server home directory.
Page 43: Configuring Oracle - Primary
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. RAC: List all net services names for the primary database separated by a comma.
Page 44: Configuring Oracle - Catalog
Figure 7 Configuring Oracle - Catalog 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.
Page 45: Using The Data Protector Cli
Using the Data Protector CLI NOTE: On HP OpenVMS, to invoke the Data Protector CLI, run: $@OMNI$ROOT:[BIN]OMNI$CLI_SETUP.COM UNIX only: Log in to the Oracle Server system with an OSDBA user account. On the Oracle Server system, from the directory: Windows: Data_Protector_home\bin...
Page 46 CATALOG_DB_LOGIN is: -rcuser CATALOG_USERNAME -rcpasswd CATALOG_PASSWORD -rcservice catalog_net_service_name STANDBY_DB_LOGIN is: -stbuser STANDBY_USERNAME -stbpasswd STANDBY_PASSWORD -stbservice standby_net_service_name_1[,standby_net_service_name_2, ...] Oracle Data Guard: If you intend to back up a standby database, you must provide the STANDBY_DB_LOGIN information. For standby database backup, a recovery catalog must be used.
Page 47 The message *RETVAL*0 indicates successful configuration, even if followed by additional messages. Example The following example represents configuration on HP-UX or Solaris of an Oracle database and its recovery catalog in Oracle Data Guard environment. The following names are used in the example: •...
Page 48: Oracle Database Configuration Parameters
If you need to export some variables before starting SQL*Plus, listener, or RMAN, these variables must be defined in the Environment section of the Data Protector Oracle global configuration file or using the Data Protector GUI. Configuring multiple Oracle databases simultaneously In large environments with multiple Oracle databases, it can be time-consuming to configure each database separately, especially if the configuration parameters need to be updated frequently.
Page 49 Parameter Description OSUSER An operating system user account (user name and group or domain) under which you want the configuration and (UNIX and Windows Server browsing of Oracle databases to start. This user will be 2008 clients only) automatically added to the Data Protector admin user group for the client specified in Client.
Page 50: Keeping Parameters In An Xls File
• CSV (comma separated values file) When creating the file, consider the following: • In the first line, list parameters that you want to specify. In subsequent lines, list parameter values for Oracle databases that you want to configure. • Parameter names in the first line are not case-sensitive.
Page 51: Encoding A Password
• Encode the passwords before you save them in your XLS or CSV file, using the Data Protector util_cmd command. For example, to encode the password BlueMoon, run: util_cmd –encode BlueMoon Figure 1 1 Encoding a password Once you receive the encoded password, copy it to your file. Figure 9 shows an example of a file in which all the passwords are encoded.
Page 52 [-encode] [-chkconf] [-force] {-passwordfile FileName|Param=Value [Param=Value...]} For the options description, see the omniintconfig.pl man page or the HP Data Protector command line interface reference. Examples Suppose you are logged in to the Windows client on which you have created the file C:\My_documents\Oracle_instances.xls. To configure the Oracle databases IN1 and IN2 using the information from the file, run: perl.exe omniintconfig.pl -passwordfile...
Page 53: Checking The Configuration
The -force option instructs Data Protector to continue configuring Oracle databases if the configuration check for an Oracle database fails. Suppose you are logged in to a UNIX client. To check the configuration of the Oracle database IN2, run: omniintconfig.pl -chkconf CellManager=galaxy Client=star Instance=IN2 Checking the configuration You can check the configuration of an Oracle database after you have created at least one backup specification for the database.
Page 54 If an error occurs, the error number is displayed in the form *RETVAL*error_number. To get the error description, on the Cell Manager, run: Windows: Data_Protector_home\bin\omnigetmsg 12 error_number HP-UX, Solaris, and Linux: /opt/omni/lbin/omnigetmsg 12 error_number Other UNIX systems: /usr/omni/bin/omnigetmsg 12 error_number HP OpenVMS: Set up the Data Protector CLI environment by running: $@OMNI$ROOT:[BIN]OMNI$CLI_SETUP.COM...
Page 55: Setting Environmental Variables
Oracle databases. Once specified, they are saved to related Data Protector Oracle database configuration files. For details on how environmental variables affect your environment, see Table NOTE: Environmental variables are not supported on HP OpenVMS systems. Table 5 Environmental variables Environmental variable Default Description...
Page 56: Using The Data Protector Cli
In the Advanced dialog box, specify the variable name, its value, and click Add. Figure Figure 12 Setting environmental variables Click OK. Using the Data Protector CLI From the directory: Windows: Data_Protector_home\bin HP-UX, Solaris, and Linux: /opt/omni/lbin/ Integrating Oracle and Data Protector...
Page 57: Backup
Other UNIX : /usr/omni/bin/ run: util_cmd –putopt Oracle8 DatabaseName Variable Value –sublist Environment For details, see the util_cmd man page or the HP Data Protector command line interface reference. Example To set the environmental variable OB2_RMAN_COMMAND_TIMEOUT to 100 seconds for the Oracle database INST2, run: util_cmd –putopt Oracle8 INST2 OB2_RMAN_COMMAND_TIMEOUT 100...
Page 58: Creating Backup Specifications
This allows you to apply all the options to a backup specification with a few mouse clicks, rather than having to specify all the options over and over again. This task is optional, as you can use one of the default templates as well. If you prefer using predefined templates, see “Creating backup specifications”...
Page 59 In the Create New Backup dialog box, double-click Blank Oracle Backup to create a backup specification without predefined options, or use one of the pre-defined templates given below Archive Backs up the Archived Redo Logs. Archive_Delete Backs up the Archived Redo Logs, then deletes them after the backup.
Page 60 Click OK. Integrating Oracle and Data Protector...
Page 61 In the Client, select the Data Protector Oracle integration client. In a cluster environment, select the virtual server. RAC: Select the virtual server of the Oracle resource group. Oracle Data Guard: Select either a primary system or secondary (standby) system. In Application database, type the name of the database to be backed up.
Page 62: Specifying An Oracle Server System (Unix)
Figure 13 Specifying an Oracle Server system (UNIX) Click Next. NOTE: When you click Next, Data Protector performs a configuration check. UNIX clients only: The check is started under the specified OSDBA user account. If it completes successfully, the OSDBA user and group are also saved in both the Oracle database specific configuration file and Oracle client global configuration file, overriding previous values if they exist.
Page 63 Select the Oracle database objects to be backed up. For example, a single tablespace can be separately selected for backup, but for a complete online backup of the database, the ARCHIVELOGS must also be selected. Oracle 10g/1 1g: The archived logs can reside in the flash recovery area. In this case, if you select the FLASH RECOVERY AREA to be backed up, you do not need to select also ARCHIVELOGS.
Page 64: Selecting Backup Objects
Figure 14 Selecting backup objects Click Next. 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. You can also specify whether you want to create additional copies (mirrors) of the backup during the backup session.
Page 65 Set the backup options. For information on other the Backup Specification Options and Common Application Options, press F1. 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 15 on page 66),...
Page 66: Oracle Specific Options
Figure 15 Oracle specific options Click Next. Optionally, schedule the backup. For more details, see “Scheduling backup specifications” on page 81. Click Next. Integrating Oracle and Data Protector...
Page 67: Saving The Backup Specification
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. Therefore, do not use a punctuation in the names of backup specifications, since the Oracle channel format is created from the backup specification name.
Page 68: Oracle Backup Options
It is recommended to test the backup specification. See “Testing the integration” on page 74 for details. Table 6 Oracle backup options Disable recovery catalog By default, Data Protector backs up the recovery catalog in auto backup every backup session. Select this option to disable backup of the recovery catalog.
Page 69: Examples Of Pre-Exec And Post-Exec Scripts On Unix
“Examples of pre-exec and post-exec scripts on UNIX” on page 69. Provide the pathname of the command or RMAN script. HP OpenVMS : Provide the pathname of the command (OMNI$ROOT:[BIN]). Examples of pre-exec and post-exec scripts on UNIX Pre-exec example...
Page 70: Editing The Oracle Rman Script
echo "Oracle database \"$DB_NAME\" started." exit 0 else echo "Cannot find Oracle SQLPLUS ($ORACLE_HOME/bin/sqlplus)." exit 1 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.
Page 71 To edit an Oracle RMAN script, click Edit in the Application Specific Options window (see Figure 22 on page 99), edit the script, and then click Save to save the changes to the script. See the Oracle Recovery Manager User’s Guide and References for more information on Oracle RMAN commands.
Page 72 NOTE: When an Oracle format of the backup file is manually defined or changed by editing the RMAN script, any user-defined combination of the Oracle substitution variables can be added to the %s:%t:%p substitution variables and DB_NAME, which are obligatory. •...
Page 73: Creating Copies Of Backed Up Objects
NOTE: When an Oracle format of the backup file is manually defined or changed by editing the RMAN script, any user-defined combination of the Oracle substitution variables can be added to the %s:%t:%p substitution variables and DB_NAME, which are obligatory. •...
Page 74: Testing The Integration
Add the following command to the RMAN script before any allocate channel command: set duplex=<on | 2 | ... > IMPORTANT: If more than one allocated channel is used, it may happen that some original and copied objects are backed up to the same medium. To prevent this, you should use only one allocated channel when backing up using the duplex mode.
Page 75: Testing Using The Data Protector Gui
The procedure consists of checking both the Oracle and the Data Protector parts of the integration to ensure that communication between Oracle and Data Protector is established, that the data transfer works properly, and that the transactions are recorded either in the recovery catalog (if used) or in the control file. Details of the test backup, such as media protection, backup user and backup status are registered in the Data Protector database and in the Oracle control files.
Page 76: Testing Using The Cli
On OpenVMS, to invoke the Data Protector CLI, execute: $@OMNI$ROOT:[BIN]OMNI$CLI_SETUP.COM Run the omnib command with the -test_bar option as follows: • On Windows: Data_Protector_home\bin\omnib -oracle8_list backup_specification_name -test_bar • On HP-UX, Solaris, and Linux: /opt/omni/bin/omnib -oracle8_list \ backup_specification_name -test_bar Integrating Oracle and Data Protector...
Page 77: Starting Backup Sessions
• On other UNIX systems: /usr/omni/bin/omnib -oracle8_list \ backup_specification_name -test_bar • On OpenVMS: $omnib -oracle8_l qist backup_specification_name -test_bar The ob2rman.pl command is started, which then starts the BACKUP VALIDATE DATABASE RMAN command. Starting backup sessions There are two strategies for backing up a database. These are an offline or consistent database backup, and an online or inconsistent database backup.
Page 78 Shut down the database cleanly. A clean shutdown means that the database is not shut down using the ABORT option. Mount the database if you are backing it up using RMAN. Back up all datafiles, control files and, optionally, parameter files. Restart the database in the normal online mode.
Page 79 If the Oracle target database is not operating in the ARCHIVELOG mode, proceed as follows: If SPFILE is used: Shut down the database. Mount the database. Start SQL*Plus and type: alter database archivelog; alter database open; alter system archive log start SCOPE=SPFILE; If PFILE is used: Shut down the database.
Page 80 Backup methods • Schedule a backup of an existing Oracle backup specification using the Data Protector Scheduler. See “Scheduling backup specifications” on page 81. • Start an interactive backup of an existing Oracle backup specification using the Data Protector GUI or the Data Protector CLI. See “Running an interactive backup”...
Page 81: Scheduling Backup Specifications
Scheduling backup specifications For more information on scheduling, see the online Help index: “scheduled backups”. A backup schedule can be tailored according to your business needs. If you have to keep the database online continuously, then you should back it up frequently, including the backup of the Archived Redo Logs, which is required in case you need database recovery to a particular point in time.
Page 82: Running An Interactive Backup
Specify Recurring, Time options, Recurring options, and Session options.. Note that the backup type can be full or incremental, with the incremental level as high as Incr 4. See Figure 18 on page 82. See the RMAN documentation for details on incremental backup levels. Figure 18 Scheduling backups Click OK and then Apply to save the changes.
Page 83 In the Scoping Pane, expand Backup Specifications and then Oracle Server. Right-click the backup specification you want to start and click Start Backup. Integration guide for Oracle and SAP...
Page 84: Starting An Interactive Backup
Figure 19 Starting an interactive backup Starting a backup using the CLI On an Oracle Server, switch to the directory: Windows: Data_Protector_home\bin HP-UX, Solaris, and Linux: /opt/omni/bin Other UNIX: /usr/omni/bin HP OpenVMS: To set up the CLI, run: $@OMNI$ROOT:[BIN]OMNI$CLI_SETUP.COM Integrating Oracle and Data Protector...
Page 85: Starting Oracle Backup Using Rman
Run: omnib -oracle8_list backup_specification_name [-barmode Oracle8Mode][list_options] 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.
Page 86 If you use the recovery catalog, run: • On Windows: ORACLE_HOME\bin\rman target Target_Database_Login catalog Recovery_Catalog_Login • On UNIX: ORACLE_HOME/bin/rman target Target_Database_Login catalog Recovery_Catalog_Login • On HP OpenVMS: Run ORAUSER.COM using $@OMNI$ROOT:[LOG]LOGIN.COM. Execute $rman target target_connect_string catalog catalog_connect_string. Target database login...
Page 87 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'; 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.
Page 88: Mml Filenames On Different Platforms
On Windows and UNIX clients, set the SBT_LIBRARY parameter to point to the correct platform–specific Data Protector MML. The location and the filename of the Data Protector MML depend on the platform: HP-UX, Solaris, and Linux: /opt/omni/lib Other UNIX systems: /usr/omni/lib Windows: Data_Protector_home\bin...
Page 89 Recovery_Catalog_Login • On UNIX: bin/rman target Target_Database_Login catalog Recovery_Catalog_Login • On HP OpenVMS: Run ORAUSER.COM using $@OMNI$ROOT:[LOG]LOGIN.COM. Execute $rman target target_connect_string catalog catalog_connect_string. Examples of the RMAN scripts Some examples of RMAN scripts that must be executed from the RMAN> prompt are...
Page 90 NOTE: In the following examples, the SBT_LIBRARY parameter is set to /opt/omni/lib/libob2oracle8.so, which is the correct path for 32–bit Solaris clients. 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...
Page 91 Backing up all archived logs and tablespaces If you want to back up the Archived Redo Logs and the tablespace SYSTEM and RONA of the previous database using three parallel channels and a backup specification named ora1, the RMAN script should look like this: run { allocate channel 'dev_0' type 'sbt_tape' parms 'SBT_LIBRARY=/opt/omni/lib/libob2oracle8.so,...
Page 92 Backing up the flash recovery area If you want to back up the Oracle 10g/1 1g Flash Recovery Area using three parallel channels and a backup specification named ora1, the RMAN script should look like this: run { allocate channel 'dev_0' type 'sbt_tape' parms 'SBT_LIBRARY=/opt/omni/lib/libob2oracle8.so, ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=ORACL,OB2BARLIST=ora1)';...
Page 93 If a backup specification named ora1 backs up the database and allows for up to 10 corrupted blocks per datafile /oracle/data1.dbs (UNIX systems) or C:\oracle\data1.dbs (Windows systems), then the appropriate RMAN script would be: On UNIX run { set maxcorrupt for datafile '/oracle/data1.dbs' to 10;...
Page 94: Restore
Restore You can restore the database objects using: • Data Protector GUI. See “Restoring Oracle using the Data Protector GUI” on page 96. • RMAN. See “Restoring Oracle using RMAN” on page 118. Restorable items You can restore the following database objects using both the Data Protector GUI or RMAN: •...
Page 95: Taking The Oracle Resource Group Offline
Figure 20 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 DB_NAME.world resource, which is an Oracle Database resource. Figure 21 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.
Page 96: Prerequisites
run { allocate channel dev1 type 'sbt_tape' parms 'SBT_LIBRARY=Path_to_Data_Protector_MML, 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. • The database must be in the Mount state if the whole database is being restored, or in the NoMount state if the control file is being restored or a database duplication is performed.
Page 97: Changing The Database State
Changing the database state Before you restore any database item or you perform a duplication of a database, ensure that the database is in the correct state: Table 8 Required database states Item to restore Database state Control file, duplicating a database NoMount (started) Mount All other items...
Page 98 Under Restore Objects, expand Oracle Server, expand the client on which the database, for which you want to restore the recovery catalog, resides, and then click the database. Integrating Oracle and Data Protector...
Page 99: Recovery Catalog Settings Dialog
In the Restore action drop-down list, select Perform RMAN Repository Restore. In the Results Area, select RECOVERY CATALOG. If you want to change the recovery catalog login information, right-click RECOVERY CATALOG and click Properties. In Recovery Catalog Settings, specify the login information for recovery catalog. Figure 22 Recovery catalog settings dialog Integration guide for Oracle and SAP...
Page 100: Restoring The Control File
The recovery catalog is not required for this restore option. The control files (ctrlDB_NAME.dbf) are restored to: Windows: Data_Protector_home\tmp HP-UX, Solaris, and Linux: /var/opt/omni/tmp Other UNIX: /usr/opt/omni/tmp HP OpenVMS: OMNI$ROOT:[TMP] After the restore, run the following script: run { allocate channel 'dev0' type disk;...
Page 101 The control file was automatically backed up by RMAN and the recovery catalog is not available. 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.
Page 102: Restoring Oracle Database Objects
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. If you do not have up-to-date versions of these files, restore them as described in “Restoring the recovery catalog database”...
Page 103: Source Page
In the Restore action drop-down list, select the type of restore you wish to perform. For information on the options, see “Restore, recovery, and duplicate options” on page 114. IMPORTANT: If you do not select Perform Restore and Recovery or Perform Recovery Only, you will have to recover the database objects manually using RMAN.
Page 104 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. NOTE: When restoring to a new location, current datafiles will be switched to the restored datafile copies only if you have selected...
Page 105 In the Options page, from the Client drop-down list, select the client on which the Data Protector Oracle integration agent will be started. To restore the database objects to a different database than it is selected, click Settings and specify the login information for the target database. Oracle Data Guard: If you restore the primary database, specify the login information for the primary database.
Page 106: Options Page
Figure 24 Options page Integrating Oracle and Data Protector...
Page 107: Devices Page
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.
Page 108: Restoring Tablespaces And Datafiles
If you performed an Oracle database restore and recovery until point in time, and the session has finished successfully, reset the database to register the new incarnation of database in the recovery catalog. Connect to the target and recovery catalog database using RMAN and reset the database: rman target Target_Database_Login catalog Recovery_Catalog_Login...
Page 109: Restoring And Recovering An Oracle Database In Oracle Data Guard Environment
When the restore has been completed put the datafiles and tablespaces back online with the following procedures: Open a command line window and enter the following commands: sqlplus /nolog SQL>connect user/password@service as sysdba If you are restoring a datafile enter: SQL>alter database datafile 'datafile_name' online;...
Page 110: Duplicating An Oracle Database
If the archived redo logs required for recovery are accessible on disk, restore only damaged datafiles and restart redo apply process. If you have lost the entire standby database, it is better to perform duplication of the database (unless only a few damaged datafiles or tablespaces need to be restored). Perform duplication of the database also when: •...
Page 111 Limitations • Database duplication is not supported using proxy copy backups of the primary database. • If you perform duplication of a database (not for standby) on the same system on which the target or production database resides, note that you cannot use the same database name for the target and duplicate databases when the duplicate database resides in the same Oracle home directory as the target database.
Page 112 In the Options page, from the Client drop-down list, select the client on which the Data Protector Oracle integration agent (ob2rman.pl) will be started. Click Settings to specify the login information (a user name, password, and net services name) for the auxiliary database. If you do not provide the login information, the duplication session will fail.
Page 113: Oracle Duplicate Options
Figure 26 Oracle duplicate options 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.
Page 114: Restore, Recovery, And Duplicate Options
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. You can select which database, tablespace, or datafiles they would like to restore and up to which point in time they would like them to be restored.
Page 115: Duplicate Options
If this is not specified in the case of restore or recovery, the login information of the selected database that resides on the selected client will be used. If this is not specified in the case of duplication, the duplication session will fail. User name, User group (UNIX systems only) Specify the operating system user account under which you want the restore to start.
Page 116: Restore And Recovery Options
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.
Page 117 Data Protector starts RMAN to recover the database to the most recent time possible by applying all archived redo logs. By default, this option is selected. • Selected time Use this option to specify an exact time to which the archive logs are applied. •...
Page 118: Restoring Oracle Using Rman
NOTE: Oracle recommends that you perform a complete backup immediately after a database was opened with the Reset Logs option. Restoring Oracle using RMAN Data Protector acts as a media management software for the Oracle system, therefore RMAN can be used for a restore. This section only describes examples of how you can perform a restore.
Page 119 Make sure that the following environment variables are set: • ORACLE_BASE • ORACLE_HOME • ORACLE_TERM • DB NAME • PATH • NLS_LANG • NLS_DATE_FORMAT Windows example ORACLE_BASE=Oracle_home ORACLE_HOME=Oracle_home\product\10.1.0 ORACLE_TERM=HP DB_NAME=PROD PATH=$PATH:Oracle_home\product\10.1.0\bin NLS_LANG=american NLS_DATE_FORMAT='Mon DD YYYY HH24:MI:SS' UNIX example ORACLE_BASE=/opt/oracle Integration guide for Oracle and SAP 1 19...
Page 120: Connection Strings Used In The Examples
ORACLE_HOME=/opt/oracle/product/10.1.0 ORACLE_TERM=HP DB_NAME=PROD PATH=$PATH:/opt/oracle/product/10.1.0/bin NLS_LANG=american NLS_DATE_FORMAT='Mon DD YYYY HH24:MI:SS' HP OpenVMS example ORACLE_HOME=DKA400:[ORACLE9I] ORACLE_TERM=HP DB_NAME=PROD • Check that the /etc/oratab file has the following line: Windows: PROD:Oracle_home\product\10.1.0:N UNIX: PROD:/opt/oracle/product/10.1.0:N HP OpenVMS: • Oracle 9i: Oracle_home/oratab TEST:/DKA400/ORACLE9I:N CAT:/DKA400/ORACLE9I:N The last letter determines whether the database will automatically start upon bootup (Y) or not (N).
Page 121: Sbt_Library Parameter
SBT_LIBRARY parameter On Windows and UNIX clients, set the SBT_LIBRARY RMAN script parameter to point to the correct platform-specific Data Protector MML. The parameter must be specified for each RMAN channel separately. For details on the Data Protector MML location, see Step 3 on page 88.
Page 122: Example Of Point-In-Time Restore
Start the full database restore and recovery: run{ allocate channel 'dev1' type 'sbt_tape' parms 'SBT_LIBRARY=/opt/omni/lib/libob2oracle8.so, ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=DB_NAME)'; restore database; recover database; sql 'alter database open'; release channel 'dev1'; You can also save the script into a file and perform a full database restore using the saved files.
Page 123 Log in to the Oracle RMAN: If you use the recovery catalog database, run: • On Windows: ORACLE_HOME\bin\rman target sys/manager@PROD catalog rman/rman@CATAL • On UNIX: ORACLE_HOME/bin/rman target sys/manager@PROD catalog rman/rman@CATAL • On OpenVMS: rman target sys/manager@PROD sys/manager@PROD catalog rman/rman@CAT If you do not use the recovery catalog, run: •...
Page 124: Example Of Tablespace Restore And Recovery
Start the point-in-time restore: If you use the recovery catalog database, run: • On Windows: ORACLE_HOME\bin\rman target sys/manager@PROD catalog rman/rman@CATAL cmdfile=Data_Protector_home\tmp\restore_PIT • On UNIX: ORACLE_HOME/bin/rman target sys/manager@PROD catalog rman/rman@CATAL cmdfile=/var/opt/omni/tmp/restore_PIT If you do not use the recovery catalog, run: • On Windows: ORACLE_HOME\bin\rman target sys/manager@PROD nocatalog cmdfile=Data_Protector_home\tmp\restore_PIT •...
Page 125 Start the tablespace restore and recovery. • If the database is in the open state, the script to restore and recover the tablespace should have the following format: run{ allocate channel dev1 type 'sbt_tape' parms 'SBT_LIBRARY=/opt/omni/lib/libob2oracle8.so, ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=DB_NAME)'; sql 'alter tablespace TEMP offline immediate'; restore tablespace TEMP;...
Page 126: Example Of Datafile Restore And Recovery
Start the tablespace restore. If you use the recovery catalog database, run: • On Windows: ORACLE_HOME\bin\rman target sys/manager@PROD catalog rman/rman@CATAL cmdfile=Data_Protector_home\tmp\restore_TAB • On UNIX: ORACLE_HOME/bin/rman target sys/manager@PROD catalog rman/rman@CATAL cmdfile=/var/opt/omni/tmp/restore_TAB If you do not use the recovery catalog, run: • On Windows: ORACLE_HOME\bin\rman target sys/manager@PROD nocatalog cmdfile=Data_Protector_home\tmp\restore_TAB •...
Page 127 Start the datafile restore and recovery: • If the database is in an open state, the script to restore the datafile should have the following format: UNIX run{ allocate channel dev1 type 'sbt_tape' parms 'SBT_LIBRARY=/opt/omni/lib/libob2oracle8.so, ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=DB_NAME)'; sql "alter database datafile ''/opt/oracle/data/oradata/DATA/temp01.dbf'' offline";...
Page 128 ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=DB_NAME)'; restore datafile '/opt/oracle/data/oradata/DATA/temp01.dbf'; recover datafile '/opt/oracle/data/oradata/DATA/temp01.dbf'; release channel dev1; Windows run{ allocate channel dev1 type 'sbt_tape' parms 'SBT_LIBRARY=Data_Protector_home\bin\orasbt.dll, ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=DB_NAME)'; restore datafile 'Oracle_home\data\oradata\DATA\temp01.dbf'; recover datafile 'Oracle_home\data\oradata\DATA\temp01.dbf'; release channel dev1; You can also save the script into a file and perform a datafile restore using the saved files: Create a file restore_dbf the /var/opt/omni/tmp or Data_Protector_home\tmp (Windows systems) directory.
Page 129: Example Of Archive Log Restore
Example of archive log restore To restore an archive log: Log in to the Oracle RMAN: If you use the recovery catalog database, run: • On Windows: ORACLE_HOME\bin\rman target sys/manager@PROD catalog rman/rman@CATAL • On UNIX: ORACLE_HOME/bin/rman target sys/manager@PROD catalog rman/rman@CATAL •...
Page 130: Example Of Database Restore Using A Different Device (With The Automatic Device Selection Functionality Disabled)
Start the archive log restore: If you use the recovery catalog database, run: • On Windows: ORACLE_HOME\bin\rman target sys/manager@PROD catalog rman/rman@CATAL cmdfile=Data_Protector_home\tmp\restore_arch • On UNIX: ORACLE_HOME/bin/rman target sys/manager@PROD catalog rman/rman@CATAL cmdfile=/var/opt/omni/tmp/restore_arch If you do not use the recovery catalog database, run: •...
Page 131: Restoring Using Another Device
Run: run { allocate channel 'dev_0' type 'sbt_tape' parms 'SBT_LIBRARY=C:/PROGRA~1/OmniBack/bin/orasbt.dll, ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=CAN,OB2BARLIST=test)'; allocate channel 'dev_1' type 'sbt_tape' parms 'SBT_LIBRARY=C:/PROGRA~1/OmniBack/bin/orasbt.dll, ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=CAN,OB2BARLIST=test)'; allocate channel 'dev_2' type 'sbt_tape' parms 'SBT_LIBRARY=C:/PROGRA~1/OmniBack/bin/orasbt.dll, ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=CAN,OB2BARLIST=test)'; send device type 'sbt_tape' 'NO_AUTO_DEVICE_SELECTION=1'; send device type 'sbt_tape' 'CHDEV=dev1>dev2'; restore database; NOTE: The line device type 'sbt_tape' 'NO_AUTO_DEVICE_SELECTION=1';...
Page 132: Disaster Recovery
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. Also see the HP Data Protector disaster recovery guide for instructions on how to approach system disaster recovery using Data Protector.
Page 133: Viewing Previous Sessions
Double-click the session you want to monitor. Clearing sessions To remove all completed or aborted sessions from the Results Area of the Monitor context: In the Scoping Pane, click Current Sessions. In the Actions menu, select Clear Sessions. Or click the Clear Sessions icon on the toolbar.
Page 134: Resuming Sessions
Details about Oracle backup and restore sessions are also written in the following logs on the Oracle Server system: • Data Protector writes the logs in: Windows: Data_Protector_home\log\oracle8.log HP-UX, Solaris, and Linux: /var/opt/omni/log/oracle8.log Other UNIX: usr/omni/log/oracle8.log HP OpenVMS: OMNI$ROOT:[LOG]ORACLE8.LOG • Oracle writes the logs in the Oracle_user_dump_directory\sbtio.log file.
Page 135 run{ allocate channel 'dev_0' type 'sbt_tape' parms 'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=ORCL,OB2BARLIST=New1)'; allocate channel 'dev_1' type 'sbt_tape' parms 'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=ORCL,OB2BARLIST=New1)'; allocate channel 'dev_1' type 'sbt_tape' parms 'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=ORCL,OB2BARLIST=New1)'; backup incremental level <incr_level> format 'New1<ORCL_%s:%t:%p>.dbf' NOT BACKED UP SINCE TIME "TO_DATE('5/15/2009 15:30:00', 'MM/DD/YY HH24:MI:SS')" database; sql 'alter system archive log current'; backup format 'New1<ORCL_%s:%t:%p>.dbf' NOT BACKED UP SINCE TIME "TO_DATE('5/15/2009 15:30:00',...
Page 136: Using The Data Protector Gui
NOTE: Ensure that the Cell Manager and your Oracle Server client are synchronized. Otherwise, if Time is not correct, the resume session functionality does not work properly. NOTE: The smallest backup unit is a backup set. Therefore, consider the following for the RMAN option FILESPERSET: •...
Page 137: Using The Data Protector Cli
Log in to the Cell Manager or to any client with the User Interface component installed. Go to the following directory: Windows: Data_Protector_home\bin HP-UX, Solaris, and Linux: /opt/omni/bin/ Other UNIX : /usr/omni/bin/ To resume a backup session, run: omnib –resume SessionID To resume a restore session, run: omnir –resume SessionID...
Page 138: Aborting Sessions
For details, see the omnib and omnir man pages or the HP Data Protector command line interface reference. Example To resume the backup session 2009/05/13–1, run: omnib –resume 2009/05/13–1 Aborting sessions You can abort currently running sessions by clicking the abort button.
Page 139: Troubleshooting
Data Protector Oracle integration. You can start at “Problems” on page 147 and if you cannot find a solution there, perform general checks and verifications. For general Data Protector troubleshooting information, see the HP Data Protector troubleshooting guide. Before you begin •...
Page 140: Checks And Verifications
• See the HP Data Protector product announcements, software notes, and references for general Data Protector limitations, as well as recognized issues and workarounds. • http://www.hp.com/support/manuals for an up-to-date list of supported versions, platforms, and other information. Checks and verifications For more detailed information about how to perform any of the following procedures, see the Oracle documentation.
Page 141: Checking The Status Of The Oracle Listener
Export or set the ORACLE_HOME and DB_NAME variables as described in Step 1 on page 140. Start SQL*Plus from the bin directory in the ORACLE_HOME directory: sqlplus /nolog Start SQL*Plus and type: connect Recovery_Catalog_Login select * from rcver; exit If this fails, open the recovery catalog. •...
Page 142 Start SQL*Plus from the bin directory in the ORACLE_HOME directory: sqlplus /nolog Start SQL*Plus and type: connect Target_Database_Login exit and then connect Recovery_Catalog_Login exit If this fails, see the Oracle documentation for instructions on how to create a configuration file (NAMES.ORA). •...
Page 143 Start SQL*Plus and type: connect Recovery_Catalog_Login; select * from rc_database; exit If this fails, start the configuration using Data Protector, or see the Oracle documentation for information on how to register an Oracle target database in the recovery catalog database. •...
Page 144 If you have special Oracle environment settings, ensure that they are entered in the Data Protector Oracle configuration files on the Cell Manager. See the util_cmd man page or the HP Data Protector command line interface reference for information on setting the variables in the Data Protector Oracle configuration files.
Page 145 Create an Oracle backup specification to back up to a null device or file. If the backup succeeds, the problem may be related to the backup devices. See the HP Data Protector troubleshooting guide for instructions on troubleshooting devices. • If restore failed: Run the omnidb command to see objects in the database.
Page 146 The output of the command lists detailed information about the specified Oracle object, as well as the session IDs of the backup sessions containing this object and a list of the media used. For detailed syntax of the omnidb command, see its man page.
Page 147: Problems
SQL>alter database open resetlogs; Problems Problem Data Protector reports “12:8422” error when using Data Protector Oracle integration after an upgrade of Oracle 8i to Oracle 9i 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...
Page 148 Action Set the OB2SHMEM_IPCGLOBAL omnirc variable in the /opt/omni/.omnirc file to 1 to use the memory windowing properly, and restart the failed backup session. See the HP Data Protector troubleshooting guide for details on using the omnirc file. Problem Backup fails after a point in time restore and recovery...
Page 149 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. The connection parameters should be given as username/passwd@INSTANCE.
Page 150 • Replace the util_orarest.exe utility with the new util_orarest9.exe (both located in the /usr/omni/bin directory on Linux): Rename the util_orarest.exe to util_orarest.exe.orig 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, and the control file cannot be restored from Data Protector managed backup.
Page 151 Action To resolve the problem: Close Data Protector. Set the environment variable on the system where the Cell Manager resides: OB2_ORARESTHOSTNAME = target_Oracle_host Restart Data Protector and try to restore the database items again. When the restore is complete, close Data Protector and re-set the following environment variable: OB2_ORARESTHOSTNAME = empty Restart Data Protector.
Page 152 Integrating Oracle and Data Protector...
Page 153: Integrating Sap R/3 And Data Protector
2 Integrating SAP R/3 and Data Protector Introduction This chapter explains how to configure and use the Data Protector SAP R/3 integration (SAP R/3 integration). It describes concepts and methods you need to understand to back up and restore the following files of the SAP R/3 database environment (SAP R/3 objects): •...
Page 154: Integration Concepts
• To the original location • To another client • To another directory You can restore Data Protector backups using: • The Data Protector user interface • The SAP BRTOOLS user interface When the restore completes, you can recover the database to a specific point in time using the SAP BRTOOLS interface.
Page 155: Sap R/3 Architecture
Figure 29 SAP R/3 architecture Legend Data Protector Session Manager: Backup Session Manager during backup and Restore Session Manager during restore. Database Library A set of Data Protector executables that enable data transfer between Oracle Server and Data Protector. Required only if Oracle data files are backed up in the RMAN mode.
Page 156: Sap R/3 Architecture: Backint Mode
Legend sapback/saprest Program that performs the actual backup/restore of files. omnisap.exe Data Protector program that starts the SAP backup tools. Figure 30 SAP R/3 architecture: backint mode Legend BSM/RSM Data Protector Backup/Restore Session Manager BMA/RMA Data Protector Backup/Restore Media Agent Integrating SAP R/3 and Data Protector...
Page 157 Legend GUI/CLI Data Protector graphical/command-line user interface Integration guide for Oracle and SAP...
Page 158: Backup Flow
Figure 31 SAP R/3 architecture: RMAN mode Backup flow If the backup session is started: • Using the Data Protector interface (or the scheduler): BSM is started, which reads the appropriate Data Protector backup specification, checks if the devices are available, and starts omnisap.exe on the SAP R/3 client. The omnisap.exe agent exports the appropriate environment variables and starts BRBACKUP or BRARCHIVE.
Page 159 BRBACKUP does the following: • Changes the state of the Oracle Target Database (opened or closed), according to the backup type (online or offline). • Switches the Oracle Target Database to the ARCHIVELOG mode. The archived redo log files are written to the archiving directory by Oracle and are backed up later using BRARCHIVE.
Page 160: Restore Flow
Restore flow You can start a restore using the Data Protector user interface or SAP BRTOOLS user interface. However, only a standard filesystem restore can be performed using Data Protector. When you select objects to be restored and start a restore using SAP BRTOOLS, the following happens (depending on which mode you use): •...
Page 161 • user name and user group • temporary directory used for the copy of the control file or redo logs • list of control files and redo logs that will be copied to a safe location • character set (ORA_NLS_CHARACTERSET) •...
Page 162 [ENV_var2='value2'; ...] SAP_Parameters={backup_spec_name=('-concurrency #_of_concurrency ' | '-time_balance' | '-load_balance' | '-manual_balance' | '-channels #_of_RMAN_channels'); speed={ AVERAGE=1; 'filename'=#_of_seconds_needed_to_back_up_this_file; compression={'filename'=size_of_the_file_in_bytes_after_the _compression; manual_balance={backup_specification_name={ 'filename'=device_number; The ORA_NLS_CHARACTERSET parameter is set automatically by Data Protector during SAP R/3 database configuration. For details on how to configure SAP R/3 database for use with Data Protector, see “Configuring SAP R/3 databases”...
Page 163: Parameters Using The Cli
-putopt (setting a parameter), util_cmd -getopt (retrieving a parameter), or util_cmd -getconf (listing all parameters) command on the Data Protector SAP R/3 client. The command resides in the Data_Protector_home\bin (Windows systems), /opt/omni/lbin (HP-UX, Solaris, and Linux systems), or/usr/omni/bin (other UNIX systems) directory. Cluster-aware clients...
Page 164 The util_cmd synopsis The syntax of the util_cmd command is as follows: util_cmd -getconf[ig] SAP oracle_instance [-local filename] util_cmd -getopt[ion] [SAP oracle_instance] option_name [-sub[list] sublist_name] [-local filename] util_cmd -putopt[ion] [SAP oracle_instance] option_name [option_value] [-sub[list] sublist_name] [-local filename] where: option_name is the name of the parameter option_value is the value for the parameter [-sub[list] sublist_name] specifies the sublist in the configuration file to which a parameter is written to or taken from.
Page 165 Data_Protector_home\bin\util_cmd -putopt SAP ICE OB2OPTS '-debug 1-200 debug.txt' -sublist Environment Data_Protector_home\bin\util_cmd -putopt SAP ICE BR_TRACE "'10'" -sublist Environment HP-UX, Solaris, and Linux /opt/omni/lbin/util_cmd -putopt SAP ICE OB2OPTS '-debug \ 1-200 debug.txt' -sublist Environment /opt/omni/lbin/util_cmd -putopt SAP ICE BR_TRACE "'10'" -sublist Environment...
Page 166: Configuring The Integration
Data Protector SAP R/3 client: • On Windows: Data_Protector_home\bin\util_cmd -getopt SAP ICE OB2OPTS -sublist Environment • On HP-UX, Solaris, and Linux: /opt/omni/lbin/util_cmd -getopt SAP ICE OB2OPTS \ -sublist Environment • On other UNIX: /usr/omni/bin/util_cmd -getopt SAP ICE OB2OPTS -sublist \ Environment...
Page 167: Prerequisites
BRARCHIVE), see the SAP R/3 application documentation. • Ensure that you have a license to use the Data Protector SAP R/3 integration. For information, see the HP Data Protector installation and licensing guide. • Ensure that you have correctly installed Data Protector.
Page 168: Cluster-Aware Clients
user accounts” on page 168. For information on changing the Data Protector Inet account, see the online Help index: “changing Data Protector Inet account”. If there are several SAP R/3 instances running on the same system with different SAP administrator accounts configured for each instance, create an additional, common SAP administrator account.
Page 169: Checking The Connection
Oracle operating Operating system user account that is added to the following user system user account groups: UNIX systems: dba and sapsys • • Windows systems: ORA_DBA and ORA_SID_DBA local groups For example, user oraSID. UNIX systems only: Ensure that this user is the owner of the filesystem or of the raw logical volume on which the database is mounted.
Page 170: Authentication Password File
Example For the following configuration: Oracle instance: PRO ORACLE_HOME: /app/oracle816/product run: uid=102(oraprod) gid=101(dba) export ORACLE_SID=PRO export ORACLE_HOME=/app/oracle816/product export SHLIB_PATH=/app/oracle816/product/lib:/opt/omni/lbin sqlplus /nolog SQLPLUS> connect system/manager@PRO as sysdba; Connected. SQLPLUS> connect system/manager@PRO as sysoper; Connected. Authentication password file Enable the use of the authentication password file for the database administrator: Shut down the Oracle target database.
Page 171 In the initORACLE_SID.ora file, set log_archive_start = true and specify the log_archive_dest option. Example This is an example of the initORACLE_SID.ora file for the Oracle instance PRO: # @(#)initSID.ora 20.4.6.1 98/03/30 ##################################################### (c)Copyright SAP AG, Walldorf ##################################################### ..
Page 172: Linking Oracle Server With The Data Protector Mml
Mount the Oracle database and start the archived logging mode using the Oracle Server Manager. Run: startup mount alter database archivelog; archive log start; alter database open; Example For the Oracle instance PRO, run: UNIX: export ORACLE_SID=PRO Windows: set ORACLE_SID=PRO sqlplus /nolog SQLPLUS>...
Page 173: Choosing Authentication Mode
NOTE: For testing purposes, you can override this automatic selection. You can manually specify which Data Protector MML should be used by setting the Data Protector SBT_LIBRARY parameter. The parameter is saved in the Data Protector SAP R/3 instance configuration file. On how to set the parameter, see the util_cmd man page.
Page 174: Before You Begin
SAP backup utilities to: HP-UX, Solaris, and Linux: /opt/omni/lbin Other UNIX: /usr/omni/bin On Windows, Data Protector copies the backint program from Data_Protector_home\bin to the directory that stores the SAP backup tools.
Page 175: Specifying An Sap R/3 System And Oracle Instance
In Application database, type the Oracle instance name (ORACLE_SID). Specify the User and group/domain options, which are available on UNIX and Windws Server 2008 clients, as follows: • UNIX: In Username, type the Oracle OS user described in “Configuring user accounts”...
Page 176 In the Configure SAP dialog box, specify the pathname of the Oracle Server home directory and SAP R/3 data home directory. If you leave the fields empty, the default ORACLE_HOME directory is used. Under Oracle login information to target database, specify the following: •...
Page 177: Using The Data Protector Cli
Log in to the SAP R/3 system using the Oracle operating system user account. At the command prompt, change current directory to the following directory: Windows systems: Data_Protector_home\bin HP-UX, Solaris, and Linux systems: /opt/omni/lbin Other UNIX systems: /usr/omni/bin/ Run: Integration guide for Oracle and SAP...
Page 178 If you receive the message *RETVAL*error_number where error_number is different than zero, an error occurred. To get the error description: Windows: Data_Protector_home\bin\omnigetmsg 12 error_number which is located on the Cell Manager. HP-UX, Solaris, and Linux: Run: Integrating SAP R/3 and Data Protector...
Page 179: Checking The Configuration
/opt/omni/lbin/omnigetmsg 12 error_number Other UNIX: Run: /usr/omni/bin/omnigetmsg 12 error_number TIP: To get a list of Oracle instances that are used by the SAP R/3 application, run: util_sap.exe -APP To get a list of tablespaces of an Oracle instance, run: util_sap.exe -OBJS0 ORACLE_SID To get a list of database files of a tablespace, run: util_sap.exe -OBJS1 ORACLE_SID TABLESPACE Checking the configuration...
Page 180: Using The Data Protector Cli
Figure 35 Checking the SAP R/3 configuration Using the Data Protector CLI Log in to the SAP R/3 system as the Oracle OS user. From the directory: Windows: Data_Protector_home\bin HP-UX, Solaris, and Linux: /opt/omni/lbin Other UNIX : /usr/omni/bin/ run: util_sap.exe -CHKCONF ORACLE_SID where ORACLE_SID is the name of the Oracle instance.
Page 181: Backup
Backup The integration provides online and offline database backups of the following types: Table 1 1 Backup types Full Backs up all the selected SAP R/3 objects. Incr Oracle RMAN backup incremental level 1 (available only if you are using Oracle RMAN). Backs up changes made to the selected SAP R/3 data files since the last Full backup.
Page 182: Backup Types
You can specify BRBACKUP options when you create a backup specification. If no options are specified, the SAP R/3 application refers to the current settings in the SAP parameter file. In such a case, before running a backup, ensure that the SAP parameter file is correctly configured.
Page 183: Considerations
TIP: When you create a backup specification, select a backup template that already contains the desired BRBACKUP options. Considerations • Before you start a backup, ensure that the SAP R/3 database is in the open or shutdown mode. • Backup sessions that back up the same Oracle instance cannot run simultaneously. •...
Page 184: Backup Templates
In the Create New Backup dialog box, select a template and click OK. Table 14 Backup templates Blank SAP Backup No predefined options. Brarchive_CopyDeleteSave Creates a second copy of offline redo logs, saves them, deletes them after the backup, and archives the newly-created redo logs.
Page 185 In Client, select the SAP R/3 system on which the backup should be started. In cluster environments , select the virtual server. In Application database, select the Oracle instance (ORACLE_SID) to be backed Specify the User and group/domain options, which are available on UNIX and Windws Server 2008 clients, as follows: •...
Page 186: Selecting Backup Objects
Select SAP R/3 objects to be backed up. You can select individual tablespaces, data files, or archived logs. Figure 36 Selecting backup objects Click Next. Select devices to use for the backup. To specify device options, right-click the device and click Properties. Specify the number of parallel backup streams in the Concurrency tab and the media pool.
Page 187: Application Specific Options
Set backup options. For information on the application specific options, see Table 15 on page 188. Figure 37 Application specific options Click Next. Optionally, schedule the backup. See “Scheduling backup specifications” on page 190. Click Next. Save the backup specification, specifying a name and a backup specification group.
Page 188: Sap R/3 Backup Options
TIP: Preview your backup specification before using it for real. See “Previewing backup sessions” on page 191. Table 15 SAP R/3 backup options Option Description Log file If you want to create a backint log file during backup, specify a pathname for the file.
Page 189 (post-exec). Do not use double quotes. Provide only the name. The command must reside in the directory: Windows: Data_Protector_home\bin HP-UX, Solaris, and Linux: /opt/omni/bin Other UNIX: /usr/omni/bin Backup mode Specifies the RMAN backup type to be used. Available only if the whole database is selected for backup.
Page 190: Modifying Backup Specifications
Option Description Objects outside Specifies non-database files of the Oracle SAP R/3 environment database to be saved. Save these files in a separate backup session. NOTE: The total number of sapback processes started in one session using Data Protector is limited to 256.
Page 191: Previewing Backup Sessions
Figure 38 Scheduling backups Previewing backup sessions Preview the backup session to test it. You can use the Data Protector GUI or CLI. Using the Data Protector GUI In the Context List, click Backup. In the Scoping Pane, expand Backup Specifications and then SAP R/3. Right-click the backup specification you want to preview and click Preview Backup.
Page 192: What Happens During The Preview
Windows: Data_Protector_home\bin HP-UX, Solaris, and Linux: /opt/omni/bin/ Other UNIX: /usr/omni/bin/ run: omnib -sap_list backup_specification_name -test_bar What happens during the preview? The omnisap.exe command is started, which starts the Data Protector testbar command to test the following: • Communication between the Oracle instance and Data Protector (only if RMAN is used) •...
Page 193: Using The Data Protector Cli
-sap_list backup_specification_name [-barmode SAP_mode][List_options] where SAP_mode is one of the following: full|incr For details, see the omnib man page or the HP Data Protector command line interface reference. Example To start a full backup using the SAP R/3 backup specification RONA, run:...
Page 194: Backing Up Using Oracle Recovery Manager
Export/set the following environmental variables: ORACLE_SID=SAP_instance_name ORACLE_HOME=Oracle_software_home_directory [SAPBACKUP_TYPE=OFFLINE] Default is ONLINE. SAPDATA_HOME=database_files_directory SAPBACKUP=BRTOOLS_logs_and_control_file_copy_directory SAPREORG=BRSPACE_logs_directory OB2BARLIST=backup_specification_name The backup specification is needed only to specify which Data Protector devices should be used for backup. Other information from the backup specification, like SAP R/3 objects to be backed up or the BRBACKUP options, is ignored and has to be specified manually at run time.
Page 195: Manual Balancing
• RMAN stores information about backups in the recovery catalog. For security reasons, keep the catalog in a separate database. This requires more administrative work. • In a disaster situation (such as the loss of a production database and recovery catalog), the restore and recovery of data is complicated.
Page 196: Restore
fileA=0; fileB=1; fileC=0;fileD=2;}} When you group files into subsets, consider the following: • Use only one file from the same hard disk at a time. • The number of files in a subset must be equal to or smaller than the sum of the concurrencies of all devices specified for backup.
Page 197: Restoring Using The Data Protector Gui
• Restore preview is not supported. Restoring using the Data Protector GUI In the Context List, click Restore. In the Scoping Pane, expand SAP R/3, expand the client from which the data was backed up, and then click the Oracle instance you want to restore. Integration guide for Oracle and SAP...
Page 198: Selecting Objects For Restore
In the Source page, select SAP R/3 files to be restored. To restore a file under a different name or to a different directory, right-click the file and click Restore As/Into. To restore a file from a specific backup session, right-click the file and click Restore Version.
Page 199: Selecting The Target Client
In the Destination tab, select the client to restore to (Target client). See Figure on page 199. For details on options, press F1. Figure 40 Selecting the target client In the Options page, set the restore options. For information, press F1. In the Devices page, select devices to use for the restore.
Page 200: Restoring Using The Data Protector Cli
Restoring using the Data Protector CLI From the directory: Windows: Data_Protector_home\bin HP-UX, Solaris, and Linux: /opt/omni/bin/ Other UNIX : /usr/omni/bin/ run: omnir -sap Client:Set -session SessionID -tree FileName where FileName is the pathname of the SAP R/3 file to be restored.
Page 201: Restoring Using The Sap Commands
Restoring using the SAP commands You can start a restore of the SAP R/3 database using the SAP BRRESTORE command. The command uses the Data Protector backint interface to restore files backed up with Data Protector. Log in to the SAP R/3 client as the Oracle OS user. Ensure that you have enough disk space.
Page 202: Using The Data Protector Cli Or Sap Commands
Using the Data Protector CLI or SAP commands If you are restoring using the Data Protector CLI or SAP R/3 commands, specify the new device in the file: Windows: Data_Protector_home\Config\Server\cell\restoredev UNIX: /etc/opt/omni/server/cell/restoredev Use the format: "DEV 1" "DEV 2" where DEV 1 is the original device and DEV 2 the new device. IMPORTANT: Delete this file after use.
Page 203: Sparse Files
Windows: set OB2SPARSE=sparse UNIX: export OB2SPARSE=sparse Disaster recovery For general information, see the HP Data Protector disaster recovery guide. Restoring the control file The control file contains all the information about the database structure. If the control file is lost, restore the control file before you restore any other part of the database: Restore the control file using the standard Data Protector restore procedure.
Page 204: Monitoring Sessions
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 Data Protector troubleshooting guide. Before you begin • Ensure that the latest official Data Protector patches are installed. See the online Help index: “patches”...
Page 205: General Troubleshooting
General troubleshooting Problem Data Protector reports “12:8422” error when using Data Protector Oracle integration after an upgrade of Oracle8i to Oracle9i After Oracle8i is upgraded to Oracle9i, the following error is returned during the configuration of Oracle instance or during the backup: *RETVAL*8422 Action Rename the Oracle8i svrmgrl binary to something else so that Data Protector will...
Page 206 Verify that you can access the Oracle Target Database and that it is opened, as follows: Set ORACLE_HOME and ORACLE_SID variables. Start the SQL Plus from the ORACLE_HOME directory: bin\sqlplus At theSQL prompt, type: connect user/passwd@service select * from dba_tablespaces; exit If this fails, open the Oracle Target Database.
Page 207: Checking The Status Of The Oracle Listener
Verify that the TNS listener is correctly configured for the Oracle Target Database. This is required for properly establishing network connections: Start the listener from the ORACLE_HOME directory: bin\lsnrctl status service quit If it fails, start up the TNS listener process and refer to the Oracle documentation for instructions on how to create a TNS configuration file (LISTENER.ORA).
Page 208: Prerequisites On The Sap Side Of The Integration
If you are running backups in RMAN mode, verify that the Oracle Target Database is configured to allow remote connections with system privileges: Set ORACLE_HOME as described in Step 1 on page 218 and start the Server Manager from the ORACLE_HOME directory: bin\svrmgrl At the wSVRMGR prompt, type connect Target_Database_Login as SYSDBA;...
Page 209: Configuration Problems
The procedure described in the previous sections must be performed before you start checking the Data Protector configuration. Verify that the Data Protector software has been installed properly. Refer to the HP Data Protector installation and licensing guide for details. Integration guide for Oracle and SAP...
Page 210 Perform a filesystem backup of the SAP Database Server. Perform a filesystem backup of the SAP Database Server system so that you can eliminate any potential communication problems between the SAP 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 Database Server system.
Page 211: Checking The Inet Start-Up Parameters
If you use the command line to start the Data Protector commands, verify the inet startup parameters. Check the Data Protector Inet service startup parameters on the SAP Database Server system. Proceed as follows: a. In the Control Panel, go to Administrative Tools, Services. b.
Page 212: Backup Problems
SAP backup specification to back up to a nul or file device. If the backup succeeds, the problem may be related to the backup devices.Refer to the HP Data Protector troubleshooting guide for instructions on troubleshooting devices.If the test fails again, call support.
Page 213 Backup fails at the beginning with the message “Internal heap ERROR 171 12” When using SAP 4.6D kernel on HP-UX 1 1.1 1, backup fails immediately after it was started due to a BRBACKUP core dump. A line similar to the following can be found...
Page 214: Restore Problems
ORA-01033: ORACLE initialization or shutdown in progress BR0310E Connect to database instance HOOHOO failed Action Before you start a backup, ensure that the database instance is in the open or shutdown mode. Restore problems At this stage, you should have performed all the verification steps described in the previous sections.
Page 215 Verify that a backup object exists on the backup media and in the IDB: This can be done by executing the command Data_Protector_home\bin\omnidb -SAP "object_name" -session "Session_ID" -media on the SAP 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.
Page 216 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 Database Server. Check the Data_Protector_home\Config\client\cell_server, which contains the name of the Cell Manager system.
Page 217: Troubleshooting On Unix Systems
Problem Restore sessions fail due to invalid characters in filenames On Windows systems, where the Oracle Database Character Set (DBCS) is not set to the same value as the default Windows character set for non-Unicode programs, and where SAP tools are used to create Oracle datafiles, restore fails if the datafiles contain non-ASCII or non-Latin 1 characters.
Page 218 Verify that you can access the Oracle Target Database and that it is opened, as follows: Export ORACLE_HOME and ORACLE_SID as follows: • if you are using an SH - like shell enter the following commands: ORACLE_HOME="ORACLE_HOME" export ORACLE_HOME ORACLE_SID ="ORACLE_SID" export ORACLE_SID •...
Page 219 Verify that the TNS listener is correctly configured for the Oracle Target Database. This is required for properly establishing network connections: Export ORACLE_HOME as described in Step 1 on page 218 and start the listener from the ORACLE_HOME directory: bin/lsnrctl start service exit If it fails, startup the TNS listener process and refer to the Oracle documentation for instructions on how to create TNS configuration file (LISTENER.ORA).
Page 220 If you run backups in RMAN mode, verify that the Oracle Target Database is configured to allow remote connections with system privileges: Export ORACLE_HOME as described in Step 1 on page 218 and start the SQL Plus from the ORACLE_HOME directory: bin/svrmgrl At the SQL prompt, type: connect Target_Database_Login as SYSDBA;...
Page 221: Prerequisites On The Sap Side Of The Integration
If you run backups in the RMAN mode, verify backup and restore directly to disk using the Recovery Manager channel type disk. If you use the Recovery Catalog: Export ORACLE_HOME as described in Step 1 on page 218 and start Recovery Manager: bin/rman target Target_Database_Login rcvcat Recovery_Catalog_Login cmd_file=rman_script...
Page 222 Verify backup directly to disk as follows: brbackup -d disk -u user/password If this fails, check the error messages and resolve possible problems before you continue. Verify restore directly to disk as follows: brrestore -d disk -u user/password If this fails, check the error messages and resolve possible problems before you continue.
Page 223: Configuration Problems
Data Protector configuration. Verify that the Data Protector software has been installed properly. Refer to the HP Data Protector installation and licensing guide for details. Perform a filesystem backup of the SAP R/3 Database Server: Perform a filesystem backup of the SAP Database Server system so that you can eliminate any potential communication problems between the SAP Database Server and the Data Protector Cell Manager system.
Page 224: Backup Problems
See also “Configuring user accounts” on page 168. Examine system errors: System errors are reported in the/var/opt/omni/log/debug.log (HP-UX, Solaris, and Linux systems) or /usr/omni/log/debug.log (other UNIX systems) file on the SAP Server. Problem Configuration fails due to a script failure...
Page 225 In case of an error, the error number is displayed in the form *RETVAL*Error_number. To get the error description, start the command: /opt/omni/lbin/omnigetmsg 12 Error_number (HP-UX, Solaris, and Linux systems) or /usr/omni/bin/omnigetmsg 12 Error_number (other UNIX systems) The message *RETVAL*0 indicates successful configuration.
Page 226 Create an SAP backup specification to back up to a null or file device. If the backup succeeds, the problem may be related to the backup devices. Refer to the HP Data Protector troubleshooting guide for instructions on troubleshooting devices.
Page 227 Backup fails at the beginning with the message “Internal heap ERROR 171 12” When using SAP 4.6D kernel on HP-UX 1 1.1 1, backup fails immediately after it was started due to a BRBACKUP core dump. A line similar to the following can be found...
Page 228: Restore Problems
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.
Page 229 Verify a user for the restore: Verify that user specified for the restore session is the user of backup session and that he/she belongs to the Data Protector operator or admin group. “Configuring user accounts” on page 168. Integration guide for Oracle and SAP...
Page 230 Verify that a backup object exists on the backup media and in the IDB: This can be done by executing the command /opt/omni/bin/omnidb -SAP "object_name" -session "Session_ID" -media (HP-UX, Solaris, and Linux systems) or /usr/omni/bin/omnidb -SAP "object_name" -session "Session_ID" -media (other UNIX systems) on the SAP Database Server system.
Page 231 Before you run testbar2, verify that the Cell Manager name is correctly defined on the SAP Database Server. Check the /etc/opt/omni/client/cell_server (HP-UX, Solaris, and Linux systems) or /usr/omni/config/cell/cell_server (other UNIX systems) file, which contains the name of the Cell Manager system.
Page 232 Verify the restore using backint Run the following command: • On HP-UX, Solaris, and Linux: /opt/omni/lbin/backint -f restore -u ORACLE_SID -i input_file • On other UNIX: /usr/omni/bin/backint -f restore -u ORACLE_SID -i input_file where the contents of the input_file will be restored.
Page 233: Integrating Sap Db/Maxdb And Data Protector
3 Integrating SAP DB/MaxDB and Data Protector Introduction This chapter explains how to configure and use the Data Protector SAP DB integration (SAP DB integration). It describes the concepts and methods you need to understand to back up and restore SAP DB/MaxDB database objects (SAP DB/MaxDB objects). Data Protector integrates with SAP DB/MaxDB Server to offer online backup of an SAP DB/MaxDB Server instance (SAP DB/MaxDB instance).
Page 234: Integration Concepts
• To another SAP DB/MaxDB client • To another SAP DB/MaxDB instance As part of the restore session, you can also recover the database to a specific point in time or to the last archive log. You can also back up and restore SAP DB/MaxDB objects using SAP DB/MaxDB utilities.
Page 235: Sap Db Integration Architecture
Figure 43 SAP DB integration architecture The Data Protector integration software consists of the following components: • The sapdbbar module, installed on the SAP DB/MaxDB Server system, which controls activities between the SAP DB/MaxDB Server and Data Protector backup and restore processes. •...
Page 236: Backup Flow
the backup has finished, the archive logs can either be deleted or kept on the SAP DB/MaxDB Server, depending on the selected options. The integration also takes advantage of the concept of SAP DB/MaxDB media and media groups, thus providing parallel backup and restore of SAP DB/MaxDB objects. Several SAP DB/MaxDB media are grouped in an SAP DB/MaxDB media group, which is then backed up or restored in streams.
Page 237: Configuring The Integration
To enable transactional backups (log backups), you need to activate the SAP DB/MaxDB Automatic Log Backup. • Ensure that you have correctly installed Data Protector. See the HP Data Protector installation and licensing guide on how to install Data Protector in various architectures.
Page 238: Cluster-Aware Clients
• To test whether the SAP DB/MaxDB system and the Cell Manager communicate properly, configure and run a Data Protector filesystem backup and restore on the SAP DB/MaxDB system. Cluster-aware clients Configure SAP DB/MaxDB instances only on one cluster node, since the configuration files reside on the Cell Manager.
Page 239: Before You Begin
Data Protector then creates the SAP DB/MaxDB instance configuration file on the Cell Manager and verifies the connection to the instance. TIP: Once the configuration file is created, you can set, retrieve, and list the configuration file parameters using the Data Protector util_cmd command. For details, see the util_cmd man page.
Page 240: Specifying An Sap Db/Maxdb Instance
In Client, select the SAP DB/MaxDB Server system. In a cluster environment, select the virtual server. In Application database, type the SAP DB/MaxDB instance name. For information on the User and group/domain options, press F1. Figure 44 Specifying an SAP DB/MaxDB instance Click Next.
Page 241: Using The Data Protector Cli
In the Configure SAP DB dialog box, specify the SAP DB independent program path parameter. This parameter is the independent program path directory specified during the installation of the SAP DB/MaxDB application. To automatically detect the directory, leave the Auto-detect option selected. Under Connection, type the username and password of the SAP DB/MaxDB database user as described in Configuring SAP DB/MaxDB...
Page 242 UNIX: /opt/omni/lbin run: util_sapdb \[-homedir SAPDBMaxDB_independent_program_directory] \-config Instance Name username password Parameter description SAPDBMaxDB_independent_program_directory The SAP DB/MaxDB independent program path parameter. This parameter is the independent program path directory specified during the installation of the SAP DB/MaxDB application on the SAP DB/MaxDB Server. This parameter is optional.
Page 243: Handling Errors
UNIX: util_sapdb -homedir SAPDB_independent_program_directory/indep_prog -config sapdb_inst sapdb_user sapdb_pass TIP: To change the configuration parameters, run the same command using new values. Handling errors If an error occurs, the error number is displayed in the form *RETVAL*error_number. UNIX only: To obtain an error description, from the directory: /opt/omni/lbin run: omnigetmsg 12 Error_number...
Page 244: Backup
From the directory: Windows: Data_Protector_home\bin UNIX: /opt/omni/lbin run: util_sapdb -chkconf Instance_Name where Instance_Name is the name if the SAP DB/MaxDB instance. A successful configuration check displays the message *RETVAL*0. Backup The integration provides online database backups of different types. What is backed up depends on which objects and backup type you select.
Page 245: Selecting Sap Db/Maxdb Objects
In Client, select the SAP DB/MaxDB Server system. In a cluster environment, select the virtual server. In Application database, type the SAP DB/MaxDB instance name. For information on the User and group/domain options, press F1. Click Next. If the SAP DB/MaxDB instance is not configured yet for use with Data Protector, the Configure SAP DB dialog box is displayed.
Page 246: Application Specific Options
Select devices to use for the backup. To specify device options, right-click the device and click Properties. Specify the device Concurrency, media pool, and preallocation policy. Click Next. Set backup options. For information on application specific options (Figure 47), Table Click Next.
Page 247: Modifying Backup Specifications
TIP: Preview your backup specification before using it for real. See Previewing backup sessions. Table 18 SAP DB/MaxDB backup options Option Description Change database state Specifies the SAP DB/MaxDB database mode during backup (Admin or Online). If this option is OFF, the database remains in the current mode.
Page 248: Scheduling Example
Scheduling example To back up SAP DB/MaxDB objects at 8:00, 13:00, and 18:00 during week days: In the Schedule property page, select the starting date in the calendar and click Add to open the Schedule Backup dialog box. Under Recurring, select Weekly. Under Time options, select 8:00. Under Recurring Options, select Mon, Tue, Wed, Thu, and Fri.
Page 249: Using The Data Protector Gui
The message Session completed successfully is displayed at the end of a successful preview. Using the Data Protector CLI From the directory: Windows: Data_Protector_home\bin HP-UX, Solaris, and Linux: /opt/omni/bin/ Other UNIX systems: /usr/omni/bin/ run: omnib -sapdb_list backup_specification_name -test_bar What happens during the preview? The sapdbbar program is started, which then starts the Data Protector testbar2 command.
Page 250: Starting Backup Sessions
The message Session completed successfully is displayed at the end of a successful backup session. Using the Data Protector CLI From the directory: Windows: Data_Protector_home\bin HP-UX , Solaris, and Linux: /opt/omni/bin/ Other UNIX systems: /usr/omni/bin/ run: Integrating SAP DB/MaxDB and Data Protector...
Page 251: Using Sap Db/Maxdb Utilities
omnib -sapdb_list ListName [-barmode sapdbmode] [list_options] [-preview] ListName is the name of the backup specification. sapdbmode specifies the backup type. You can select full, diff, or trans. For List_options, see the omnib man page. Example To start a full backup using an existing SAP DB/MaxDB backup specification called TEST, and to set data protection to 10 weeks, run: omnib -sapdb_list TEST -barmode full -protect weeks 10 Using SAP DB/MaxDB utilities...
Page 252 In the SAP DB/MaxDB database manager, register the location of the bsi_env file created in Step 1 of this procedure by running: Windows: dbm_configset -raw BSI_ENV location\inst_name.bsi_env UNIX: dbm_configset -raw BSI_ENV location/inst_name.bsi_env Integrating SAP DB/MaxDB and Data Protector...
Page 253 Create SAP DB/MaxDB media, grouping them under the same name (media_group_name). The number of created media should equal the parallelism you plan to use for backup. To create a medium medium_name, run the following command, depending on the SAP DB/MaxDB version: •...
Page 254 UNIX, MaxDB version 7.6: medium_put BACKDP-Data[2]/1 \ /var/opt/omni/tmp/inst_name.BACKDP_Data[2].1 PIPE \ DATA 0 8 NO NO \" \" "BACK" medium_put BACKDP-Data[2]/2 \ /var/opt/omni/tmp/inst_name.BACKDP_Data[2].2 PIPE \ DATA 0 8 NO NO \" \" "BACK" Windows, other SAP DB/MaxDB versions: medium_put BACKDP-Data[2]/1 \ \\.\Pipe\inst_name.BACKDP_Data[2].1 PIPE DATA medium_put BACKDP-Data[2]/2 \ \\.\Pipe\inst_name.BACKDP_Data[2].2 PIPE DATA...
Page 255: Restore
Name of the SAP DB/MaxDB media media_group_name group. Name of the SAP DB/MaxDB medium. medium_name Name of the SAP DB/MaxDB pipe. pipe_name Type of the SAP DB/MaxDB medium. medium_type Restore Restore SAP DB/MaxDB objects in any of the following ways: •...
Page 256 IMPORTANT: There are several scenarios, depending on the backup option Keep archive logs and the recovery option Use existing archive logs, in which a gap of transactions between the sequence of redo logs on the SAP DB/MaxDB Server and the restored volumes can occur.
Page 257 NOTE: The Use existing archive logs option is disabled in case of SAP DB/MaxDB migration, thus allowing only for the restore of redo logs from the backed up archive logs on backup media (if trans backup session is restored). Integration guide for Oracle and SAP...
Page 258: Sap Db/Maxdb Restore Process
Figure 49 SAP DB/MaxDB restore process Figure 50 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.
Page 259: Before You Begin
selected, it is switched to the Online mode. Otherwise, the database is left in the Admin mode. Restoring only the selected trans or diff backup session is useful if the database remains offline or in the Admin mode after a restore from full backup session, which is then followed by a restore from diff or trans backup session.
Page 260: Selecting Objects For Restore
In the Source page, select objects for restore. Figure 51 Selecting objects for restore To restore SAP DB/MaxDB objects from a specific backup session, right-click the Data item, click Properties, and specify Backup version in the Properties for Data dialog box. Selecting a Trans or Diff backup session enables you to: •...
Page 261 Figure 52 Properties for data IMPORTANT: The Configuration item is restored from the same backup session as selected for the Data item, regardless of what you select for the Configuration item. In the Options page, set the restore and recovery options. For information, see SAP DB/MaxDB restore options.
Page 262: Restoring Using The Data Protector Cli
The message Session completed successfully is displayed at the end of a successful session. Restoring using the Data Protector CLI From the directory: Windows: Data_Protector_home\bin HP-UX, Solaris, and Linux: /opt/omni/bin/ Other UNIX systems: /usr/omni/bin/ run: omnir -sapdb -barhost ClientName -instance InstanceName [-destination ClientName]...
Page 263: Restoring Using Sap Db/Maxdb Utilities
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: On HP-UX, Solaris, and Linux: /opt/omni/bin/omnir -sapdb -barhost srv1.company.com -instance inst1 -recover -endlogs On other UNIX systems: /usr/omni/bin/omnir -sapdb -barhost srv1.company.com -instance...
Page 264: Sap Db/Maxdb Restore And Recovery
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). In the procedure, the following conventions are used: inst_name is the name of the instance to be restored username,password is the connection string for the SAP DB/MaxDB database user created or identified as described in Configuring SAP DB/MaxDB...
Page 265 Login to the SAP DB/MaxDB database manager as the SAP DB/MaxDB database user created or identified as described in Configuring SAP DB/MaxDB users. On the SAP DB/MaxDB Server, execute the following command to login: dbmcli -d inst_name -u username,password In the SAP DB/MaxDB database manager, switch the database to the Admin mode by executing the following command: db_admin Skip this step if the location of the bsi_env file is already registered on the...
Page 266 Skip this step if the SAP DB/MaxDB media and pipes to be used with Data Protector are already existing on the SAP DB/MaxDB Server. Note that to restore a Data Protector SAP DB/MaxDB backup session, the number of SAP DB/MaxDB media and pipes required equals the parallelism value used during the backup session.
Page 267 medium_put BACKDP-Data[2]/2 \ \\.\Pipe\inst_name.BACKDP_Data[2].2 PIPE DATA 0 8 \ NO NO \"\" "BACK" UNIX, MaxDB version 7.6: medium_put BACKDP-Data[2]/1 \ /var/opt/omni/tmp/inst_name.BACKDP_Data[2].1 PIPE \ DATA 0 8 NO NO \"\" "BACK" medium_put BACKDP-Data[2]/2 \ /var/opt/omni/tmp/inst_name.BACKDP_Data[2].2 PIPE \ DATA 0 8 NO NO \"\" "BACK" Windows, other SAP DB/MaxDB versions: medium_put BACKDP-Data[2]/1 \ \\.\Pipe\inst_name.BACKDP_Data[2].1 PIPE DATA...
Page 268 Start the restore from a Data Protector backup session by executing the following command: recover_start media_group_name backup_type EBID "inst_name SessionID:1 pipe_name1,inst_name SessionID:2 pipe_name2[, ...]" Windows: recover_start BACKDP-Data[2] DATA EBID "inst_name SessionID:1 \\.\Pipe\inst_name.BACKDP-Data[2].1,TEST SessionID:2 \\.\Pipe\inst_name.BACKDP-Data[2].2" UNIX: recover_start BACKDP-Data[2] DATA EBID "inst_name SessionID:1 /var/opt/omni/tmp/inst_name.BACKDP-Data[2].1,inst_name SessionID:2 /var/opt/omni/tmp/inst_name.BACKDP-Data[2].2"...
Page 269: Sap Db/Maxdb Migration
SAP DB/MaxDB migration 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 Before you begin. Follow the procedure in the section SAP DB/MaxDB restore and recovery to migrate the SAP DB/MaxDB database using SAP DB/MaxDB utilities from existing Data...
Page 270 Figure 53 SAP DB/MaxDB restore and recovery options The following are SAP DB/MaxDB specific backup options: Migration Options To restore selected SAP DB/MaxDB object to the same SAP DB/MaxDB Server and instance, leave the migration options as they are. Use the migration options only in case of SAP DB/MaxDB migration (when restoring to some other SAP DB/MaxDB Server or to some other instance than those that were backed up).
Page 271 The selected SAP DB/MaxDB Server must be a part of the Data Protector cell and must have the Data Protector SAP DB Integration software component installed. Restore to instance / -newinstance DestinationInstanceName When using the GUI, you can either: • Select an instance in the Restore to instance drop-down list. The drop-down list shows only the instances that are already configured for use with this integration.
Page 272 IMPORTANT: There are several scenarios, depending on the backup option Keep archive logs and the recovery option Use existing archive logs, in which a gap of transactions between the sequence of redo logs on the SAP DB/MaxDB Server and the restored volumes can occur.
Page 273 Latest version / -endlogs Select this option to recover the database until the last log. When using the CLI, this is the default option. Until date / -time: YYYY-MM-DD.hh.mm.ss When using the GUI, select this option to recover the database until the point you select in the Until date drop-down menu.
Page 274: Restoring Using Another Device
Troubleshooting This section lists problems you might encounter when using the Data Protector SAP DB integration. For general Data Protector troubleshooting information, see the HP Data Protector troubleshooting guide. Before you begin • Ensure that the latest official Data Protector patches are installed. See online Help index: “patches”...
Page 275: Problems
Problems Problem Data Protector reports the following error during backup or restore: [Critical] From: OB2BAR_SAPDBBAR@machine.company.com "INSTANCE" Time: 02/06/04 18:17:18 Error: SAPDB responded with: -24920,ERR_BACKUPOP: backup operation was unsuccessful The database was unable to fulfill a request (-2025, Invalid number of backup devices). Action Increase the value of the SAP DB/MaxDB MAXBACKUPDEVS parameter to a value that is greater than or equal to the value of the Data Protector Parallelism option,...
Page 276 • Increase the number of Disk Agent buffers for the device used for the restore. • If all objects of the backup are recorded in the IDB, perform the following steps: In the Internal Database context of the Data Protector GUI, search for all objects belonging to the same backup.
Page 277 Action Some other user is connected to the SAP DB/MaxDB instance and is performing administrative tasks (utility session). Such SAP DB/MaxDB tasks are of the "Utility" type and can be displayed using the dbmcli show task command. Finish these tasks. Problem Data Protector reports the following error: Error: SAPDB responded with:...
Page 278: Sap Db/Maxdb Cluster-Related Troubleshooting
SAP DB/MaxDB cluster-related troubleshooting In a cluster environment, the environment variable OB2BARHOSTNAME must be defined as the virtual hostname before performing some procedures run from the command line (on the client). The OB2BARHOSTNAME variable is set as follows: UNIX export OB2BARHOSTNAME=virtual_hostname Windows set OB2BARHOSTNAME=virtual_hostname Integrating SAP DB/MaxDB and Data Protector...
Page 279: Glossary
Glossary access rights 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.
Page 280 an archived redo log is determined by the mode the database is using: • ARCHIVELOG - The filled online redo log files are archived before they are reused. The database can be recovered if an instance or a disk fails. A “hot” backup can be performed only when the database is running in this mode.
Page 281 associated with managing data and disk and provides striping and mirroring capabilities to optimize performance. automigration (VLS specific term) The functionality that allows data backups to be first made to the VLS' virtual tapes and then migrated to physical tapes (one virtual tape emulating one physical tape) without using an intermediate backup application.
Page 282 located (drive on Windows and mount point on UNIX). For integration objects — backup stream identification, indicating the backed up database/application items. • Description: For filesystem objects — uniquely defines objects with identical client name and mount point. For integration objects —...
Page 283 See also BCV. (HP StorageWorks Disk Array XP specific term) The Business Copy XP allows to maintain internal copies of HP StorageWorks Disk Array XP LDEVs for purposes such as data backup or data duplication. The copies (secondary volumes or S-VOLs) can be...
Page 284 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. The copies (child or Business Copy LUNs) can be used for various purposes, such as backup, data analysis or development.
Page 285 (HP StorageWorks Disk Array XP specific term) Continuous Access XP allows you to create and maintain remote copies of HP StorageWorks Disk Array XP LDEVs for purposes such as data duplication, backup, and disaster recovery. CA operations involve the main (primary) disk arrays and the remote (secondary) disk arrays.
Page 286 The Catalog Database is a part of the IDB that contains information about backup, restore, object copy, object consolidation, object verification, and media management sessions. 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.
Page 287 Change Log (Windows specific term) A module that can be queried to Provider determine which objects on a filesystem have been created, modified, or deleted. channel (Oracle specific term) An Oracle Recovery Manager resource allocation. Every allocated channel starts a new Oracle process, which performs backup, restore, and recovery actions.
Page 288 cluster-aware It is an application that supports the cluster Application application Programming Interface. Each cluster-aware application declares its own critical resources (disk volumes (on Microsoft Cluster Server), volume groups (on MC/ServiceGuard), application services, IP names and addresses, and so on). cluster continuous (Microsoft Exchange Server specific term) Cluster continuous replication...
Page 289 It provides database consistency information used for recovery. copy set (HP StorageWorks EVA specific term) A pair that consists of the source volumes on a local EVA and their replica on a remote EVA.
Page 290 Data Replication (HP StorageWorks EVA specific term) A logical grouping of (DR) group EVA virtual disks. It can contain up to eight copy sets provided they have common characteristics and share a common CA EVA log.
Page 291 Dbobject (Informix Server specific term) An Informix Server physical database object. It can be a blobspace, dbspace, or logical log file. DC directory The Detail Catalog (DC) directory contains DC binary files, which store information about file versions. It represents the DCBF part of the IDB, which occupies approximately 80% of the IDB.
Page 292 tape a little and resumes to write to 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.
Page 293 Disk Agent A component needed on a client to back it up and restore it. The Disk Agent controls reading from and writing to a disk. During a backup session, the Disk Agent reads data from a disk and sends it to the Media Agent, which then moves it to the device.
Page 294 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. DNS server In the DNS client-server model, this is the server containing information about a portion of the DNS database that makes computer names available to client resolvers querying for name...
Page 295 dynamic client client backup with disk discovery. EMC Symmetrix Symmetrix Agent (SYMA). Agent (SYMA) (EMC Symmetrix specific term) emergency boot (Informix Server specific term) The Informix Server configuration file file ixbar.server_id that resides in the directory INFORMIXDIR/etc (on Windows) or INFORMIXDIR\etc (on UNIX).
Page 296 A failover can occur mostly because of software or hardware failures or maintenance on the primary node. 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.
Page 297 (HP StorageWorks Disk Array XP specific term) HP StorageWorks Disk Array XP allows up to three mirror copies of a primary Integration guide for Oracle and SAP...
Page 298 volume and each of these copies can have additional two copies. The three mirror copies are called first-level mirrors. See also primary volume number. flash recovery (Oracle specific term) Flash recovery area is an Oracle 10g/1 1g area managed directory, filesystem, or Automatic Storage Management disk group that serves as a centralized storage area for files related to backup and recovery (recovery files).
Page 299 Data_Protector_program_data\Config\Server\Options (Windows Server 2008), Data_Protector_home\Config\Server\Options (other Windows systems), or /etc/opt/omni/server/options (HP-UX or Solaris systems). group (Microsoft Cluster Server specific term) A collection of resources (for example disk volumes, application services, IP names, and addresses) that are needed to run a specific cluster-aware applications.
Page 300 HP Operations Manager, extending the managed domain. Plug-In (SPI) Through the Data Protector integration, which is implemented as an HP Operations Manager SMART Plug-In, a user can have an arbitrary number of Data Protector Cell Managers monitored as an extension to HP Operations Manager.
Page 301 HP StorageWorks A logical partition of a physical disk within an HP StorageWorks Virtual Array LUN Virtual Array. LUNs are entities that can be replicated in the HP StorageWorks Business Copy VA configuration, or can be used as standalone entities.
Page 302 See also backup types. incremental An incremental mailbox backup backs up all the changes made mailbox backup to the mailbox after the last backup of any type. incremental1 An incremental1 mailbox backup backs up all the changes made mailbox backup to the mailbox after the last full backup.
Page 303 Information Store (Microsoft Exchange Server specific term) The Microsoft Exchange Server service that is responsible for storage management. Information Store in Microsoft Exchange Server manages two kinds of stores: mailbox stores and public folder stores. A mailbox store consists of mailboxes that belong to individual users.
Page 304 ISQL (Sybase specific term) A Sybase utility used to perform system administration tasks on Sybase SQL Server. Java GUI Client The Java GUI Client is a component of the Java GUI that contains only user interface related functionalities and requires connection to the Java GUI Server to function.
Page 305 library Also called autochanger, jukebox, autoloader, or exchanger. A library contains media in repository slots. Each slot holds one medium (for example, DDS/DAT). Media are moved between slots and drives by a robotic mechanism, allowing random access to media. The library can contain multiple drives. lights-out A backup or restore operation that takes place outside of normal operation or...
Page 306 An LCR copy is used for disaster recovery because you can switch to the LCR copy in a few seconds. If an LCR copy is used for backup and if it is located on a different disk than the original data, then the I/O load on a production database is minimal.
Page 307 login ID (Microsoft SQL Server specific term) The name a user uses to log on to Microsoft SQL Server. A login ID is valid if Microsoft SQL Server has an entry for that user in the system table syslogin. login information (Oracle and SAP R/3 specific term) The format of the login to the Oracle information is user_name/password@service, where:...
Page 308 A mailbox store consists of a binary rich-text .edb file and a streaming native internet content .stm file. Main Control Unit (HP StorageWorks Disk Array XP specific term) An HP (MCU) StorageWorks XP disk array that contains the primary volumes for the CA and BC configurations and acts as a master device.
Page 309 During a restore or object verification session, a Media Agent locates data on the backup medium and sends it to the Disk Agent for processing. For a restore sssion, the Disk Agent then writes the data to the disk. A Media Agent also manages the robotics control of a library.
Page 310 See also shadow copy, shadow copy provider, replica, and writer. mirror (EMC target volume. Symmetrix and HP StorageWorks Disk Array XP specific term) mirror rotation (HP replica set rotation. StorageWorks Disk Array XP specific term)
Page 311 The Data Protector Media Session Manager, which runs on the Cell Manager and controls media sessions, such as copying media. MU number (HP StorageWorks Disk Array XP specific term) Mirror Unit number. An integer number (0, 1 or 2), used to indicate a first-level mirror. See also first-level mirror.
Page 312 OBDR capable A device that can emulate a CD-ROM drive loaded with a device bootable disk and can thus be used as a backup or boot device for disaster recovery purposes. object backup object. object The process of merging a restore chain of a backup object, consolidation consisting of a full backup and at least one incremental backup, into a new, consolidated version of this object.
Page 313 object verification A process that verifies the data integrity of specified backup session objects or object versions and the ability of selected Data Protector network components to deliver them to a specified host. Object verification sessions can be run interactively, or as specified in automated post-backup, or scheduled specifications.
Page 314 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. During this period, the database is fully operational, but there may be a small performance impact and log files may grow very quickly.
Page 315 Oracle instance (Oracle specific term) Each installation of an Oracle database on one or more systems. One computer system can have several instances of a database running. ORACLE_SID (Oracle specific term) A unique name for an Oracle Server instance. To switch among Oracle Servers, specify the desired ORACLE_SID.
Page 316 IP names and addresses) that are needed to run a specific cluster-aware application. pair status (HP StorageWorks Disk Array XP specific term) A mirrored pair of disks can have various status values depending on the action performed on it. The three most important status values are: •...
Page 317 Windows and as shell scripts on UNIX. See also post-exec. primary volume (HP StorageWorks Disk Array XP specific term) Standard HP (P-VOL) 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.
Page 318 CA and BC applications. The commands communicate through a RAID Manager instance with the HP StorageWorks Disk Array XP Disk Control Unit. This instance translates the commands into a sequence of low level SCSI commands.
Page 319 Recovery Catalog (Oracle specific term) A set of Oracle tables and views that are used by Recovery Manager to store information about Oracle databases. This information is used by Recovery Manager to manage the backup, restore, and recovery of Oracle databases. The recovery catalog contains information about: •...
Page 320 Remote Control (HP StorageWorks Disk Array XP specific term) The Remote Unit (RCU) Control Unit (RCU) acts as a slave of an MCU in a CA configuration. In bidirectional configurations, the RCU can act as an MCU. Removable (Windows specific term) A Windows service used for managing...
Page 321 A process that copies data from backup media to a client. resync mode (HP StorageWorks Disk Array XP VSS provider specific term) One of two XP VSS hardware provider operation modes. When the XP provider is in the resync mode, the source volume (P-VOL) and its replica (S-VOL) are in the suspended mirror relationship after a backup.
Page 322 By setting up a schedule, you automate the start of backups. secondary volume (HP StorageWorks Disk Array XP specific term) secondary (S-VOL) 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.
Page 323 One binary file is created per session. The files are grouped by year and month. snapshot (HP StorageWorks VA and HP StorageWorks EVA specific term) A form of replica produced using snapshot creation techniques. Integration guide for Oracle and SAP...
Page 324 StorageWorks EVA specific term) snapshot creation (HP StorageWorks VA and HP StorageWorks EVA specific term) A replica creation technique, in which copies of source volumes are created using storage virtualization techniques. The replicas are considered to be created at one particular point in time, without pre-configuration, and are immediately available for use.
Page 325 (HP StorageWorks Disk Array XP specific term) split mirror (EMC Symmetrix and HP StorageWorks Disk Array XP specific creation term) A replica creation technique, in which a pre-configured set of target volumes (a mirror) is kept synchronized with a set of source volumes until the time at which a replica of the contents of the source volumes is required.
Page 326 SSE Agent (HP StorageWorks Disk Array XP specific term) A Data Protector software module that executes all tasks required for a split mirror backup integration. It communicates with the HP StorageWorks...
Page 327 management systems, file systems, or other objects may exist. The volume management systems, file systems are built on this storage. Typically, these can be created or exist within a storage system such as a disk array. switchover See failover. Sybase Backup (Sybase specific term) An industry-standard interface developed Server API for the exchange of backup and recovery information between...
Page 328 System Recovery file. Data file System State (Windows specific term) The System State data comprises the Registry, COM+ Class Registration database, system startup files, and the Certificate Services database (if the server is a certificate server). If the server is a domain controller, Active Directory services and the SYSVOL directory are also contained in the System State data.
Page 329 this system to the original system configuration. The difference between a faulty system and a target system is that a target system has all faulty hardware replaced. target volume (ZDB specific term) A storage volume to which data is replicated. Terminal Services (Windows specific term) Windows Terminal Services provide a multi-session environment that allows clients to access a virtual...
Page 330 database backups. By applying transaction log backups, you can recover the database to a specific point in time. transaction log Files that record transactions of the database modifications, and files provide fault tolerance in case of a database disaster. transaction logs (Data Protector specific term) Keep track of IDB changes.
Page 331 (CRC) option ON. Virtual Controller (HP StorageWorks EVA specific term) The firmware that manages Software (VCS) all aspects of storage system operation, including communication with Command View EVA through the HSV controllers.
Page 332 (HP StorageWorks EVA specific term) A unit of storage allocated from an HP StorageWorks Enterprise Virtual Array storage pool. Virtual disks are the entities that are replicated using the HP StorageWorks Enterprise Virtual Array snapshot functionality. See also...
Page 333 Copy Service Microsoft Volume Shadow Copy Service. VSS compliant (HP StorageWorks Disk Array XP VSS provider specific term) mode One of two XP VSS hardware provider operation modes. When the XP provider is in the VSS compliant mode, the source volume (P-VOL) and its replica (S-VOL) are in simplex, unpaired state after a backup.
Page 334 one or more characters, and the question mark (?) typically represents a single character. Wildcard characters are often used in operating systems as a means of specifying more than one file by name. Windows Data Protector allows you to back up Windows CONFIGURATION CONFIGURATION, including Windows Registry, user profiles, backup...
Page 335 information. The ZDB database is used for ZDB, instant recovery, and split mirror restore. See also zero downtime backup (ZDB). ZDB to disk (ZDB specific term) A form of zero downtime backup where the replica produced is kept on the disk array as a backup of the source volumes at a specific point in time.
Page 336 Glossary...
Page 337: Index
Index backing up Oracle, 77 - 85 - 93 backup options, 68 architecture backup specifications, creating, 58 SAP DB integration, 235 backup types, 27 SAP R/3 integration, 155 examples, using RMAN, 89 audience, 15 recovery catalog, 80 scheduling backups, 81 starting backups, 82 - 85 - 93 starting backups, using...
Page 338 backing up SAP R/3, 181 - 196 backup specifications, modifying backup flow, 158 SAP DB integration, 247 backup specifications, creating, 183 SAP R/3 integration, 190 backup templates, 184 backup specifications, scheduling backup types, 181 SAP DB integration, 247 backup modes, 154 backup templates backup specification, modifying, 190...
Page 339 control files, Oracle integration examples, scheduling backups restore, 100 SAP R/3 integration, 190 conventions document, 23 creating backup specifications full backups Oracle integration, 58 SAP DB integration, 233 SAP DB integration, 244 SAP R/3 integration, 153, 181 SAP R/3 integration, 183 help Data Guard, Oracle integration obtaining, 25...
Page 340 CLI, 84 MML (Data Protector Media starting backups, using GUI, 82 Management Library) starting backups, using RMAN, 85 linking with Oracle, HP OpenVMS, starting backups, 82 - 85 - 93 Oracle configuration modifying backup specifications checking configuration, 53...
Page 341 136 standby databases, Data Guard, 109 using another device, 131 RAC, configuring Oracle Servers using GUI, 96 HP-UX, 35 restoring SAP R/3 on other UNIX systems, 35 using GUI, 197 recovery restoring SAP DB/MaxDB Oracle integration, options, 114...
Page 342 SAP DB/MaxDB backup concepts, scheme, 235 SAP DB integration backup modes, 244 introduction, 233 backup specification, modifying, 247 limitations, 237 backup specifications, creating, 244 monitoring sessions, 274 backup options, 247 SAP DB/MaxDB backup backup types, 233 architecture, 235 differential backups, 233 SAP DB/MaxDB configuration, 237 - 244 full...
Page 343 133 SBT_LIBRARY, Oracle integration, 36, 88, 121 scheduling backups Oracle integration, 81 websites SAP R/3 integration, 190 HP Subscriber's Choice for Business, SAP DB integration, 247 standby databases, Oracle integration , 26 restore, 109 product manuals, 15 starting backups...

HP Data Protector A.06.11 Integration Manual

Publication History

About this Guide

Integrating Oracle and Data Protector

Integrating SAP R/3 and Data Protector

Integrating SAP Db/Maxdb and Data Protector

Glossary

Index

Quick Links

Troubleshooting

Related Manuals for HP Data Protector A.06.11

Summary of Contents for HP Data Protector A.06.11