Page 1 HP Data Protector A.06.1 1 Zero downtime backup integration guide for Oracle, SAP R/3, Microsoft SQL Server, Microsoft Exchange Server, and Microsoft Volume Shadow Copy Service B6960-90163 Part number: B6960-90163 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
Integrations ..................25 Document conventions and symbols ..............27 Data Protector graphical user interface ..............28 General information ..................29 HP technical support ..................29 Subscription service ................... 30 HP websites ...................... 30 Documentation feedback ..................30 1 Data Protector Oracle ZDB integration ....... 31 Introduction ......................
Page 4 Cluster-aware clients ..................56 Linking Oracle Server with the Data Protector MML ......... 56 Configuring Oracle user accounts ..............57 Configuring Oracle operating system user accounts ........57 Configuring Oracle database users accounts ........... 59 Configuring Oracle databases ..............60 Using the Data Protector GUI ..............
Page 5 SBT_LIBRARY parameter ..............125 Example of full database restore and recovery ........126 Example of point-in-time restore ............127 Example of tablespace restore and recovery .......... 129 Example of datafile restore and recovery ..........131 Example of archive log restore ............. 135 Example of database restore using a different device (with the automatic device selection functionality disabled) ..........
Page 6 Using the Data Protector CLI ..............186 Checking the configuration ................ 188 Using the Data Protector GUI ............... 188 Using the Data Protector CLI ..............189 Configuring the SAP R/3 parameter file ............190 Backup ......................191 Considerations ..................192 Creating backup specifications ..............
Page 7 Verifying the backup configuration .............. 233 Verifying restore ..................235 Configuration and backup problems ............238 Restore problems ..................240 3 Data Protector Microsoft SQL Server ZDB integration ..243 Introduction ....................243 Integration concepts ..................244 Configuring the integration ................245 Prerequisites .....................
Page 8 Configuring the integration ................287 Prerequisites ..................... 287 Before you begin ..................288 Backup ......................289 Configuring Exchange Server ZDB .............. 290 Creating ZDB specifications ..............290 Examples of using omnicreatedl ............300 Modifying ZDB specifications ............... 303 Checking Exchange files for consistency ..........304 Scheduling backups ..................
Page 9 Configuring the integration ................347 Configuring the application system for instant recovery-enabled backup sessions ....................347 Configuring HP StorageWorks Enterprise Virtual Array ........349 Prerequisites ..................351 Configuring the Integration ..............350 Configuring HP StorageWorks Disk Array XP ..........351 Prerequisites ..................
Page 10 Instant recovery using Microsoft Virtual Disk Service ........ 393 Instant recovery using HP StorageWorks EVA SMIS-S Agent ..... 394 Instant recovery using HP StorageWorks Disk Array XP Agent ....396 Microsoft Exchange Server writer instant recovery specifics ...... 397 Instant recovery procedure ..............400 Troubleshooting ....................
Page 11 Figures Data Protector graphical user interface ..........29 Data Protector Oracle integration concept ........... 38 Oracle backup set ZDB concept ............40 Oracle backup set ZDB flow ............. 42 Oracle proxy-copy ZDB concept ............46 Oracle proxy-copy ZDB flow ............. 47 Finding the Oracle user ..............
Page 12 Backup offline option ..............89 Saving the backup specification ............90 Selecting ZDB to disk or ZDB to disk+tape session using the Data Protector scheduler ..................99 Selecting ZDB to disk or ZDB to disk+tape session when starting an interactive backup ................. 101 Taking the Oracle resource group offline ..........
Page 13 VA backup options ................ 198 EVA backup options ............... 199 Selecting backup objects ..............201 Application specific options ............203 Scheduling backups ............... 207 Setting environmental variables ............213 Selecting objects for restore ............217 Selecting the target client ..............218 Selecting the XP restore ..............
Page 14 Restore options ................270 Point-in-Time restore ................ 275 Restoring database with a new name ..........276 Path system variable ............... 289 omniex2000SM.bat file ..............300 Exchange ZDB specification ............304 Example script for MS Exchange Server 2000 ........306 Starting interactive backups ............308 Restoring Exchange database ............
Page 15 Additional options for Microsoft Exchange Server 2007 in a CCR environment .................. 369 Selecting Microsoft Exchange Server 2003 storage groups ....372 Selecting a replicated Microsoft Exchange Server 2007 storage group ..................373 1 10 Scheduling a backup ..............378 1 1 1 Restore objects ................
Page 16 Tables Edition history ................. 17 Document conventions ..............27 Oracle recovery methods ..............34 Oracle database user accounts ............59 Environmental variables ..............72 Oracle backup options ..............91 Required database states ..............105 Backup and restore sessions ............164 Supported disk arrays and array configurations .........
Page 17: 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 18 Publication history...
Page 19: About This Guide
Conceptual information can be found in the HP Data Protector concepts guide, which is recommended to fully understand the fundamentals and the model of Data Protector. It is also recommended to read the HP Data Protector zero downtime backup concepts guide for fundamentals of Data Protector integrations with disk arrays.
Page 20 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 21 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 22: 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 23: 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 24: 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 25: 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 Zero downtime backup integration guide...
Page 26 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 27: Document Conventions And Symbols
Document conventions and symbols Table 2 Document conventions Convention Element Blue text: Table 2 on page 27 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 28: 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 29: 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 30: 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 31: Data Protector Oracle Zdb Integration
Supported disk arrays The following disk arrays can be used for ZDB of Oracle: • EMC Symmetrix (EMC) • HP StorageWorks Disk Array XP (XP) • HP StorageWorks Virtual Array (VA) • HP StorageWorks Enterprise Virtual Array (EVA) NOTE: With the Data Protector EMC integration, only ZDB to tape is supported.
Page 32: Backup And Restore Types
• The tablespaces are in backup mode (online backup) or the database is shut down (offline backup) only during the short period required to create a replica (split the mirror disks or create snapshots). • The load to the application system is significantly reduced. Following the replica creation, tape backup can be started on the copied data, at leisure, using a separate backup system.
Page 33 Backup of archive logs has to be done following the standard Data Protector Oracle integration backup procedure. For more information on Oracle archive log backup with Data Protector see the HP Data Protector integration guide . NOTE: On EMC, decision support, application testing, and similar tasks are possible only if the Oracle binaries are installed on the backup system as well.
Page 34: Oracle Recovery Methods
Table 3 on page 34 provides an overview of recovery methods, depending on the type of backup that was performed and type of recovery required. Table 3 Oracle recovery methods Disk array Backup Recover the whole database until Recover a part of type database until A point in time,...
Page 35: Integration Concepts
RMAN scripts to recover the database. Instant recovery Perform instant recovery without database recovery. See the HP Data Protector zero downtime backup concepts guide for an overview of ZDB concepts and terminology. Integration concepts The Data Protector Oracle integration links the Oracle database management software with Data Protector.
Page 36 • Recovery (restore, recovery, and duplication) 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.
Page 37 The Data Protector backup specification allows you to configure a backup and then use the same specification several times. Furthermore, scheduled backups can only be performed using a backup specification. Backup and restore of an Oracle target database can be performed using the Data Protector User Interface or the RMAN utility.
Page 38: Data Protector Oracle Integration Concept
prepares the environment to start the restore, and issues the RMAN restore command. RMAN checks the recovery catalog (if one is used) or the control file to gather the information about the Oracle backup objects. It also contacts the Oracle Server processes, which initialize the restore through MML.
Page 39: Oracle Backup Set Zdb Concepts
The Data Protector General Media Agent, which reads and writes data from and to media devices. Oracle backup set ZDB concepts See the HP Data Protector zero downtime backup concepts guide for a general description of ZDB-to-disk, ZDB-to-tape, and ZDB-to-disk+tape and instant recovery concepts.
Page 40: Oracle Backup Set Zdb Concept
By default, instant recovery for such a configuration is not enabled. You can enable instant recovery by setting the ZDB_ORA_INCLUDE_CF_OLF, ZDB_ORA_INCLUDE_SPF, and ZDB_ORA_NO_CHECKCONF_IR omnirc variables to 1. See “ZDB integrations omnirc variables” on page 425. IMPORTANT: If you enable instant recovery by setting the above mentioned variables, note that the control file, SPFILE, and online redo logs are overwritten during instant recovery.
Page 41 For more information on an alternative Oracle backup and restore concept, see “ZDB integrations omnirc variables” on page 425. Legend The General Media Agent writes data from a replica to backup media. The General Media Agent typically resides on the backup system. The session manager controls backup and restore sessions and writes session information to the IDB.
Page 42: Backup Process
Backup process Figure 4 Oracle backup set ZDB flow NOTE: ZDB Agents are SYMA on EMC, SSEA on XP, SNAPA on VA, and SMISA on EVA. Data Protector Oracle ZDB integration...
Page 43 This section provides only the information relevant to the Data Protector Oracle ZDB integration. Operations on a replica (mounting, activating volume/disk groups,...) described below are dependent on or triggered by ZDB options. See the HP Data Protector zero downtime backup administrator's guide for more information on these options. •...
Page 44: Oracle Proxy-Copy Zdb Concepts
Data Protector Oracle archive logs backup procedure. Oracle proxy-copy ZDB concepts See the HP Data Protector zero downtime backup concepts guide for a general description of ZDB-to-disk, ZDB-to-tape, ZDB-to-disk+tape, and instant recovery concepts.
Page 45 • Oracle control file, online redo log files, and SPFILE reside on a different volume group (if LVM is used) or source volume than Oracle datafiles. By default, instant recovery is enabled if this option is selected in the GUI. •...
Page 46: Oracle Proxy-Copy Zdb Concept
Figure 5 Oracle proxy-copy ZDB concept The General Media Agent writes data from a replica to backup media. The General Media Agent typically resides on the backup system. The session manager controls backup and restore sessions and writes the session information to the IDB.
Page 47: Backup Process
Backup process Figure 6 Oracle proxy-copy ZDB flow See the HP Data Protector zero downtime backup administrator's guide for a general description of the ZDB-to-disk, ZDB-to-tape, and ZDB-to-disk+tape sessions flows and for an explanation of actions triggered by ZDB options.
Page 48 This section provides only the information relevant to the Data Protector Oracle ZDB integration. Operations on a replica (mounting, activating volume/disk groups...) described below are dependent on or triggered by ZDB options. See the HP Data Protector zero downtime backup administrator's guide for more information on these options. •...
Page 49: Configuring The Integration
• HP Data Protector installation and licensing guide for instructions on how to install Data Protector on various architectures and how to install a Data Protector disk array integration (EMC, XP, VA, or EVA) with Oracle.
Page 50 A Data Protector disk array integration (EMC, XP, VA, or EVA) must be correctly installed and configured. For installation, see the HP Data Protector installation and licensing guide. For configuration, see the HP Data Protector zero downtime backup administrator's guide.
Page 51: Limitations
Limitations • The MAXPIECESIZE RMAN parameter option is not supported because the restore of multiple backup pieces created during a backup is not possible using the Data Protector Oracle integration. • The Oracle recovery catalog database must be used as RMAN repository for backup and restore operations.
Page 52 • Identify the Oracle database user that will be used by Data Protector for backup. This user must have the SYSDBA privilege granted. For example, it could be the Oracle user sys, which is created during database creation. See the Oracle documentation for more information on user privileges in Oracle. •...
Page 53: Backup Set Method
Select the location for archive logs: • If SPFILE is used: Run: alter system set log_archive_dest=path_to_archive_logs SCOPE=SPFILE; • If the init.ora file is used: Run: log_archive_start=true log_archive_dest=path_to_archive_logs The default path of the file is: Windows: ORACLE_HOME\database\initDB_NAME.ora UNIX: ORACLE_HOME/dbs/initDB_NAME.ora where DB_NAME is the name of the Oracle database instance. Mount the target database and to enable the archive log mode, start SQL*Plus and type: startup mount...
Page 54: System
• Ensure that the Oracle software on the backup system and application system have the same directory structure. That means that ORACLE_HOME for both Oracle installations has to be identical. • Ensure that the following files are the same on the application system and the backup system.
Page 55 Connect to the Oracle target database locally using the Oracle Net software as the Oracle database administrator with the SYSDBA role. Example If the DB_NAME of the target database is PROD, the DB_NAME of the Oracle recovery catalog database is RMANCAT, and ORACLE_HOME is /oracle/PROD, then the commands will look like: su - ora uid=101(ora) gid=101(dba)
Page 56: Enabling Instant Recovery In An Asm Configuration For The Xp Array
Oracle Server system as follows: Windows: set OB2BARHOSTNAME=virtual_server_name UNIX: export OB2BARHOSTNAME=virtual_server_name HP-UX with RAC: To enable instant recovery, create an MC/ServiceGuard package containing only the virtual IP and the virtual hostname parameters and distribute it among the RAC nodes.
Page 57: Configuring Oracle User Accounts
by setting the Data Protector SBT_LIBRARY parameter. On how to set the parameter, see the util_cmd man page. The parameter is saved in the Data Protector Oracle instance configuration file. MML is invoked by the Oracle server when it needs to write to or read from devices using Data Protector.
Page 58 Clients Description Add the OSDBA user account and root user account from both the application system and backup system to the Data Protector admin or operator user group. The OSDBA user on the backup system must have the same numerical user ID and group ID as the OSDBA user on the application system (for example, uid=101(ora) gid=101(dba)).
Page 59: Configuring Oracle Database Users Accounts
Figure 8 Example user configuration in a cluster environment Configuring Oracle database users accounts Identify or create the following Oracle database user accounts. You need to provide these user accounts when you configure the Oracle database as described in “Configuring Oracle databases”...
Page 60: Configuring Oracle Databases
User Description The owner of the recovery catalog (for example, rman). Required Recovery catalog to log in to the catalog database. Needed if you use the recovery user catalog. Required to log in to the standby database. Applicable only in Standby database Oracle Data Guard environments.
Page 61: Configuring Oracle - General (Windows)
In the Configure Oracle dialog box and in the General page, specify the pathname of the Oracle Server home directory. Figure 9 Configuring Oracle - General (Windows) Figure 10 Configuring Oracle - General (UNIX) Zero downtime backup integration guide...
Page 62: 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 63: Configuring Oracle - Catalog
In the Catalog page, select Use target database control file instead of recovery catalog to use the primary database control file. To use the recovery database catalog as an RMAN repository for backup history, select Use recovery catalog and specify the login information to the recovery catalog.
Page 64: Configuring Oracle - Standby
If you have Oracle Data Guard configuration for non-ZDB sessions and 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 65: Using The Data Protector Cli
In the ZDB page, select Backup method and then select PROXY or BACKUP SET in the drop-down list. In Backup control file copy location, you can specify the location on the source volumes where a backup copy of the current control file will be made during ZDB to disk.
Page 66 On the Oracle Server system, from the directory: Windows: Data_Protector_home\bin HP-UX, Solaris: /opt/omni/lbin run: Windows: perl -I..\lib\perl util_oracle8.pl -config -dbname DB_NAME -orahome ORACLE_HOME PRIMARY_DB_LOGIN CATALOG_DB_LOGINZDB_OPTIONS [STANDBY_DB_LOGIN] [-client CLIENT_NAME] UNIX: util_oracle8.pl -config -dbname DB_NAME -orahome ORACLE_HOME PRIMARY_DB_LOGINCATALOG_DB_LOGIN ZDB_OPTIONS[STANDBY_DB_LOGIN] [-client CLIENT_NAME] where:...
Page 67 [-ctlcp_location BACKUP_CONTROL_FILE_COPY_LOCATION] [-pfile PARAMETER_FILE] [-bkphost BACKUP_SYSTEM] If you have Oracle Data Guard configuration for non-ZDB sessions and if you intend to back up a standby database, you must provide the STANDBY_DB_LOGIN information. If your ZDB method is backup set, you must provide the BACKUP_SYSTEM information. Parameter description CLIENT_NAME Name of the Oracle Server system with the database to be configured.
Page 68 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 with the backup set method used and the parameter file location specified.
Page 69: Checking The Configuration
-pfile /app10g/oracle10g/product/10.1.0/dbs/pfile.ora -bkphost bcksys 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. 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 70: Checking Configuration For Instant Recovery
*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: /opt/omni/lbin/omnigetmsg 12 error_number IMPORTANT: On UNIX, it is possible that although you receive *RETVAL*0, backup still fails because Data Protector does not check if the specified user has appropriate Oracle backup permissions.
Page 71: Setting Environmental Variables
UNIX: util_oracle8.pl -CHKCONF_IR -dbname DB_NAME If the control files, SPFILE, and redo logs are on the same volume group (if LVM is used) or source volume as datafiles, a warning is displayed stating that instant recovery is not possible. You can either: •...
Page 72: Using The Data Protector Gui
NOTE: Environmental variables are not supported on HP OpenVMS systems. Table 5 Environmental variables Environmental variable Default Description value This variable is applicable when Data Protector tries to connect to a target or catalog database. It specifies how long (in...
Page 73: Using The Data Protector Cli
In the Advanced dialog box, specify the variable name, its value, and click Add. Figure Figure 15 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/ Other UNIX : /usr/omni/bin/ Zero downtime backup integration guide...
Page 74: Switching Between Oracle Backup Methods
–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 75: Backup
Configure a non-ZDB backup specification and run the backup of Oracle data on the application system to verify that you have properly configured the Oracle environment. See the HP Data Protector integration guide for Oracle and SAP on how to create a non-ZDB backup specification.
Page 76: Creating Backup Specifications
Creating backup specifications Online ZDB To perform an online ZDB of an Oracle database, the database has to run in the ARCHIVELOG mode. Offline ZDB To perform an offline ZDB, create only a ZDB backup specification. Cluster-aware clients Before you perform an offline ZDB in a cluster environment, take the Oracle Database resource offline and bring it back online after the replica is created.
Page 77: Selecting An Oracle Zdb Template And Split Mirror Backup
In the Backup type drop-down list, select the Split mirror backup option and in the Sub type drop-down list, select the split-mirror agent that is installed on the application and the backup systems (EMC Symmetrix or HP StorageWorks XP). Figure 16 on page 77.
Page 78: Selecting An Oracle Zdb Template And Snapshot Backup
In the Backup type drop-down list, select the Snapshot backup option and in the Sub type drop-down list, select the snapshot agent you have installed on the application and the backup system (HP StorageWorks VA or HP StorageWorks EVA SMI-S). See Figure 17 on page 78.
Page 79 In Application system, select the Data Protector Oracle integration client. In a non-RAC cluster environment, select the virtual server. RAC: Select the virtual server of the Oracle resource group. In Backup system, select the backup system. Select other disk array specific backup options (see Figure 18 on page 79 for EMC,...
Page 80: Emc Backup Options
Figure 18 EMC backup options On XP To enable instant recovery, leave the Track the replica for instant recovery option selected. Note that restore using Data Protector will not be possible if this option is cleared. Data Protector Oracle ZDB integration...
Page 81: Xp Backup Options
Figure 19 XP backup options On VA To enable instant recovery, leave the Track the replica for instant recovery option selected. Zero downtime backup integration guide...
Page 82: Va Backup Options
Figure 20 VA backup options On EVA To enable instant recovery, select the Track the replica for instant recovery option. Data Protector Oracle ZDB integration...
Page 83: Eva Backup Options
Figure 21 EVA backup options Click Next. Zero downtime backup integration guide...
Page 84 In Application database, type the name of the database to be backed up. The database name can be obtained using SQL*Plus: SQL>select name from v$database; NOTE: In a single-instance configuration, the database name is usually the same as its instance name. In this case, the instance name can be also used. The instance name can be obtained as follows: SQL>select instance_name from v$instance;...
Page 85: Specifying An Oracle Server System (Windows)
Figure 22 Specifying an Oracle Server system (Windows) Zero downtime backup integration guide...
Page 86: Specifying An Oracle Server System (Unix)
Figure 23 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 87: Selecting Backup Objects
Select the Oracle database objects to be backed up. NOTE: Since temporary tablespaces do not contain permanent database objects, RMAN and Data Protector do not back them up. For more information, see Oracle documentation. Figure 24 Selecting backup objects Click Next. If the backup method configured for this instance does not correspond to the method in the backup specification, Data Protector will display a warning and abort the configuration.
Page 88 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 89: Backup Offline Option
Set the backup options. For information on other the Backup Specification Options and Common Application Options, press F1. Offline ZDB To perform an offline ZDB, select the Backup offline option in the Application Specific Options dialog box. This option stops the database before creating a replica, and restarts it after the replica is created.
Page 90: Saving The Backup Specification
For information on other Application Specific Options, see Table 6 on page 91 or press F1. Click Next. Optionally, schedule the backup. For more details, see “Scheduling backup specifications” on page 98. Note that only the Full backup type is supported. Click Next.
Page 91: Oracle Backup Options
For online backup, create also a standard Data Protector Oracle integration backup specification for backing up the application system archived log files. See the HP Data Protector integration guide. TIP: The backup specification for the backup of archived log files can be either...
Page 92: Examples Of Pre-Exec And Post-Exec Scripts On Unix
Pre-exec, Post-exec Specify a command or RMAN script that will be started by ob2rman.pl on the Oracle Server system before the backup (pre-exec) or after it (post-exec). RMAN scripts must have the .rman extension. Do not use double quotes. For example, you can provide scripts to shut down and start an Oracle instance.
Page 93: Editing The Oracle Rman Script
$ORACLE_HOME/bin/sqlplus << EOF connect sys/manager@$ORACLE_SQLNET_NAME as sysdba startup 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.
Page 94 To edit an Oracle RMAN script, click Edit in the Application Specific Options window (see Figure 31 on page 107), 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 95 To change OB2DMAP, you have to manually edit the RMAN script. On HP StorageWorks XP, for an Oracle direct backup, add OB2DMP=1. • Depending on the backup objects selection, an RMAN backup statement for the backup of the whole database instance, and/or for any combination of RMAN commands to back up tablespaces and datafile.
Page 96 • If the Archived Redo Logs were selected for a backup, an RMAN backup statement for the backup of Oracle archive logs. The backup statement consists of the Oracle format of the backup file: format 'Backup_Specification_Name<DB_NAME_%s:%t:%p>.dbf' 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 obligatory %s:%t:%p substitution variables and DB_NAME.
Page 97: Starting Backup Sessions
backup incremental level <incr_level> format 'New1<DIPSI_%s:%t:%p>.dbf' proxy only database backup format 'New1<DIPSI_%s:%t:%p>.dbf' controlfile; Starting backup sessions To run a ZDB-to-disk, ZDB-to-tape, or ZDB-to-disk+tape backup session of an Oracle database, use any of the following methods: Backup methods • Schedule a backup of an existing Oracle ZDB backup specification using the Data Protector Scheduler.
Page 98: Scheduling Backup Specifications
• With the Oracle backup set ZDB method, you must manually re-synchronize the recovery catalog database with the current control file after you modified the physical schema of a database (for example, if you add or drop a tablespace, add a new datafile, or add or drop a rollback segment) and before you start the next backup.
Page 99: Selecting Zdb To Disk Or Zdb To Disk+Tape Session Using The Data Protector
Specify Recurring, Time options, Recurring options, and Session options.. Note that only the Full backup type is supported. In the case of a ZDB-to-disk or a ZDB-to-disk+tape session, specify the Split mirror/snapshot backup option. See Figure 27 on page 99. NOTE: You can run a ZDB-to-disk or a ZDB-to-disk+tape session only if the Track the replica for instant recovery option is selected in the backup...
Page 100: Running An Interactive Backup
Running an interactive backup An interactive backup can be performed any time after a backup specification has been created and saved. You can use the Data Protector GUI or CLI. Starting a backup using the GUI To start an interactive ZDB session of an Oracle database using the Data Protector GUI, proceed as follows: In the Context List, click Backup context.
Page 101: Selecting Zdb To Disk Or Zdb To Disk+Tape Session When Starting An
To start an Oracle ZDB-to-disk session using the Data Protector CLI, run: omnib -oracle8_list Name -disk_only where Name is the name of the backup specification. For more information on the omnib command, see its man page or the HP Data Protector command line interface reference. Zero downtime backup integration guide...
Page 102: Restore
NOTE: It is not possible to run a ZDB-to-disk or a ZDB-to-disk+tape session if the Track the replica for instant recovery backup option is not selected in the backup specification. Restore You can restore the following database objects using both the Data Protector GUI or RMAN: •...
Page 103: Taking The Oracle Resource Group Offline
Figure 29 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 30 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 104: 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 105: 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 7 Required database states Item to restore Database state Control file, duplicating a database NoMount (started) Mount All other items...
Page 106 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. Data Protector Oracle ZDB integration...
Page 107: 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 31 Recovery catalog settings dialog Zero downtime backup integration guide...
Page 108: 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: /var/opt/omni/tmp After the restore, run the following script: run { allocate channel 'dev0' type disk;...
Page 109: Restoring Oracle Database Objects
To restore the control file: Open the sqlplus window and put the database in the nomount state. See “Changing the database state” on page 105. In the Data Protector GUI, switch to the Restore context. Under Restore Objects, expand Oracle Server, expand the client on which the database, for which you want to restore the control file, resides, and then click the database.
Page 110: 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 119. 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 111 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 112: Options Page
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. Set the other restore options.
Page 113: 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 114: 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 115: Duplicating An Oracle Database
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 116 LOG_FILE_NAME_CONVERT initialization parameters appropriately. Thus, the target database files will not be overwritten by the duplicate database files. 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 117 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 118: Oracle Duplicate Options
Figure 35 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 119: 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 120: 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 121: Restore And Recovery Options
Select this option to create a standby database. Default: selected. DORECOVER Available if For Standby was selected. 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.
Page 122 Recover until The options in this drop-down list allow you to specify to which point in time you would like the recovery to be performed. • Now Data Protector starts RMAN to recover the database to the most recent time possible by applying all archived redo logs.
Page 123: 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 124 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' Data Protector Oracle ZDB integration...
Page 125: Connection Strings Used In The Examples
Data Protector MML. The parameter must be specified for each RMAN channel separately. For details on the Data Protector MML location, see the HP Data Protector integration guide for Oracle and SAP. 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...
Page 126: Example Of Full Database Restore And Recovery
Example of full database restore and recovery To perform a full database restore and recovery, you also need to restore and apply all the archive logs. To perform a full database restore and recovery: Log in to the Oracle RMAN: •...
Page 127: Example Of Point-In-Time Restore
Start the full database restore: • On Windows: ORACLE_HOME\bin\rman target sys/manager@PROD catalog rman/rman@CATAL cmdfile=Data_Protector_home\tmp\restore_datafile • On UNIX: ORACLE_HOME/bin/rman target sys/manager@PROD catalog rman/rman@CATAL cmdfile=/var/opt/omni/tmp/restore_datafile Example of point-in-time restore To perform a point-in-time restore, you also need to restore and apply the archive logs to the specified point in time.
Page 128 Start the point-in-time restore: For a non-ZDB or ZDB backup set session: run{ allocate channel 'dev1' type 'sbt_tape' parms 'SBT_LIBRARY=/opt/omni/lib/libob2oracle8.so, ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=DB_NAME)'; set until time 'Mar 14 2004 11:40:00'; restore database; recover database; sql 'alter database open'; release channel 'dev1'; For a ZDB proxy-copy session, allocate one channel for restoring proxy-copy sessions and one channel for database recovery.
Page 129: Example Of Tablespace Restore And Recovery
Start the point-in-time restore: • 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 Example of tablespace restore and recovery If a table is missing or corrupted, you need to perform a restore and recovery of the entire tablespace.
Page 130 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: For a non-ZDB or ZDB backup set session: run{ allocate channel dev1 type 'sbt_tape' parms 'SBT_LIBRARY=/opt/omni/lib/libob2oracle8.so, ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=DB_NAME)';...
Page 131: Example Of Datafile Restore And Recovery
For a ZDB proxy-copy session, allocate one channel for restoring proxy-copy sessions and one channel for database recovery. Release the proxy-copy channel before the recovery: run{ allocate channel 'dev1' type 'sbt_tape' parms 'SBT_LIBRARY=/opt/omni/lib/libob2oracle8.so, ENV=(OB2BARTYPE=Oracle8,OB2PROXYCOPY=1, OB2APPNAME=DB_NAME)'; allocate channel 'dev2' type 'sbt_tape' parms 'SBT_LIBRARY=/opt/omni/lib/libob2oracle8.so, ENV=(OB2BARTYPE=Oracle8, OB2APPNAME=DB_NAME)';...
Page 132 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 For a non-ZDB or ZDB backup set session: run{ allocate channel dev1 type 'sbt_tape' parms 'SBT_LIBRARY=/opt/omni/lib/libob2oracle8.so, ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=DB_NAME)';...
Page 133 For a non-ZDB or ZDB backup set session: run{ allocate channel dev1 type 'sbt_tape' parms 'SBT_LIBRARY=Data_Protector_home\bin\orasbt.dll, ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=DB_NAME)'; sql "alter database datafile ''C:\oracle\data\oradata\DATA\temp01.dbf'' offline"; restore datafile 'C:\oracle\data\oradata\DATA\temp01.dbf'; recover datafile 'C:\oracle\data\oradata\DATA\temp01.dbf'; sql "alter database datafile ''C:\oracle\data\oradata\DATA\temp01.dbf'' online"; release channel dev1; For a ZDB proxy-copy session, allocate one channel for restoring proxy-copy sessions and one channel for the recovery process.
Page 134 • If the database is in a mount state, the script to restore and recover the datafile should have the following format: UNIX For a non-ZDB or ZDB backup set session: run{ allocate channel dev1 type 'sbt_tape' parms 'SBT_LIBRARY=/opt/omni/lib/libob2oracle8.so, ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=DB_NAME)'; restore datafile '/opt/oracle/data/oradata/DATA/temp01.dbf';...
Page 135: Example Of Archive Log Restore
'Oracle_home\data\oradata\DATA\temp01.dbf'; release channel dev1; For a ZDB proxy-copy session, allocate one channel for restoring proxy-copy sessions and one channel for the recovery process. Release the proxy-copy channel before the recovery: run{ allocate channel dev1 type 'sbt_tape' parms 'SBT_LIBRARY=Data_Protector_home\bin\orasbt.dll, ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=DB_NAME)'; allocate channel dev2 type 'sbt_tape' parms 'SBT_LIBRARY=Data_Protector_home\bin\orasbt.dll, ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=DB_NAME, OB2PROXYCOPY=1)';...
Page 136: Example Of Database Restore Using A Different Device (With The Automatic Device Selection Functionality Disabled)
Log in to the Oracle RMAN: • 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 Start the archive log restore: run{ allocate channel dev1 type 'sbt_tape' parms 'SBT_LIBRARY=/opt/omni/lib/libob2oracle8.so, ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=DB_NAME)'; restore archivelog all; release channel dev1;} You can also save the script into a file and perform an archive log restore using the saved files: Create a file restore_arch in the /var/opt/omni/tmp (UNIX systems) or...
Page 137: 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 138: Instant Recovery And Database Recovery
"DAT1" "DAT2" Instant recovery and database recovery For general information on instant recovery, see the HP Data Protector zero downtime backup concepts guide and the HP Data Protector zero downtime backup administrator's guide. For information on instant recovery in cluster environment (Cluster File System (CFS), MC/ServiceGuard, and Microsoft Cluster Server), see HP Data Protector zero downtime backup administrator's guide.
Page 139: Instant Recovery Using The Data Protector Gui
The instant recovery procedure is the same as without RAC. However, if instant recovery is to be performed to some other node than the one that was backed up, the following procedure must be performed before the standard instant recovery procedure: Make sure that the MC/SG virtual package is running on the target node.
Page 140: Selecting Backup Sessions (Xp Example)
Keep the replica after the restore option set to enable a restart of an instant recovery session. For HP StorageWorks Enterprise Virtual Array, replica is kept on the array only if the Copy replica data to the source location is selected.
Page 141: Oracle Recovery Options
At this point, you can decide whether to perform a database recovery immediately after an instant recovery or not: • To perform only an instant recovery, click Restore. NOTE: You can perform a database recovery at a later time either from the Data Protector Manager Restore Context or manually using the RMAN CLI.
Page 142: Oracle Database Recovery After The Instant Recovery
Click Restore or Preview. Note that preview only checks if the replica can be restored. It does not check if the database recovery will be successful. Data Protector recovers the database after performing instant recovery by switching the database to a mount state, restoring the necessary incremental backups and archived redo logs from tape, and applying the redo logs.
Page 143: Selecting The Database For Recovery
To recover the database, the following two options are available: • Perform a recovery from the Data Protector Manager Restore Context: Expand Oracle Server and select the database to recover. In the Source tab, under Restore action, select Perform recovery only. Figure 38 Selecting the database for recovery In the Options tab, select the recovery options.
Page 144: Oracle In Veritas Cluster Instant Recovery
release channel dev1; For additional examples on how to recover the database after an instant recovery, see “Restoring Oracle using RMAN” on page 123. Oracle in Veritas Cluster instant recovery If Oracle on the application system runs in a Veritas Cluster, the following two Veritas Cluster resources must be disabled before instant recovery is performed, and enabled after instant recovery has finished to prevent the failover of the Oracle Veritas Cluster Service Group:...
Page 145: Aborting Sessions
On the application system, enter the following commands to enable the two Veritas Cluster resources: a. hares -modify mountpoint_resource_name Enabled 1 where mountpoint_resource_name is the name of the Veritas Cluster mountpoint resource for the Oracle database files. hares -modify application_resource_name Enabled 1 where application_resource_name is the name of the Veritas Cluster application resource for the Oracle application.
Page 146: Before You Begin
“Problems” on page 154 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. For general ZDB, restore, and instant recovery troubleshooting information, see the troubleshooting sections in the HP Data Protector zero downtime backup administrator's guide.
Page 147 Start SQL*Plus from the bin directory in the ORACLE_HOME directory: sqlplus /nolog Start SQL*Plus and type: connect user_name/password@service as sysdba; select * from dba_tablespaces; exit If this fails, open the Oracle target database. • On the application system, verify that you can access the recovery catalog (if used) and that it is opened as follows: Export or set the ORACLE_HOME and DB_NAME variables as described in Step 1...
Page 148: Checking The Status Of The Oracle Listener
Start the listener from the bin directory in the ORACLE_HOME directory: lsnrctl status service If this fails, startup the listener process and see the Oracle documentation for instructions on how to create a configuration file (LISTENER.ORA). On Windows, the listener process can be started in the Control Panel >...
Page 149 • From the application system, verify that the target database and recovery catalog database are configured to allow remote connections with the system privileges and to allow backup: • If you use the recovery catalog database: Export or set the ORACLE_HOME and DB_NAME variables as described in Step on page 146.
Page 150 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 Data Protector Oracle ZDB integration...
Page 151 • Examine the system errors reported in the following file on the application system (Oracle proxy-copy ZDB method) or backup system (Oracle backup set ZDB method): HP-UX , Solaris: /var/opt/omni/log/debug.log Windows: Data_Protector_home\log\debug.log Additionally, if your backup or restore failed: •...
Page 152 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 153 and a list of the media used. For detailed syntax of the omnidb command, see its man page. • Ensure that the database is in the correct state. If you are trying to restore a database item using the Data Protector GUI and the GUI hangs try one of the following: •...
Page 154: Problems
Problems Problem SQL*Plus is unable to connect to destination Action Check if the Oracle listener process is up and running. Check if there are any environment variables you need to enter (for example, TNS_ADMIN). Enter these variables in the Data Protector Oracle configuration files on the Cell Manager. See the util_cmd man page for information.
Page 155 SmWaitForFirstClient=minutes • If you performed a clean installation: SmWaitForFirstBackupClient=minutes See the HP Data Protector troubleshooting guide for more information on the global options file. Problem Backup Set ZDB fails after changing the physical schema of the Database Backup fails after you have modified the physical schema of a database, for example, if you added or dropped a tablespace, added a new datafile, or added or dropped a rollback segment.
Page 156: Restore After A Switch Between Zdb Methods Fails
list backup; to display a list of the objects in the recovery catalog. Check the list of Proxy Copy sessions, listed at the end. To synchronize the recovery catalog and the IDB, run the RMAN command: resync catalog; After the synchronization is performed, restore should be possible. Problem Restore after a switch between ZDB methods fails If you perform a restore to a specified time (T_RESTORE) that lies in the time interval...
Page 157 ENV(OB2BARTYPE=Oracle8,OB2APPNAME=DB_NAME, OB2PROXYCOPY=1)'; RESTORE DATAFILE list_of_backup_set_backups UNTIL T_RESTORE CHANNEL 'dev_0'; RESTORE DATAFILE list_of_proxy-copy_backups UNTIL T_RESTORE CHANNEL 'dev_1'; RELEASE 'dev_0'; RECOVER DATABASE UNTIL T_RECOVER ... RELEASE 'dev_1'; Where: T_RESTORE specifies the time to which to restore and T_RECOVER the time to which to apply the transactions.
Page 158 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 159 RMAN-06004: ORACLE error from recovery catalog database: RMAN-20003: target database incarnation not found in recovery catalog Action Connect to the target and recovery catalog database using RMAN and reset the database to register the new incarnation of database in the recovery catalog: rman target Target_Database_Login catalog Recovery_Catalog_Login RMAN>...
Page 160 • 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. For example, if you are using two nodes, the backup specification might look as follows: run { allocate channel 'dev_0' type 'sbt_tape' parms...
Page 161 At this point you must manually register any backups made after the control file backup that was restored. After that, continue with the restore procedure. For the backup piece handle search the Data Protector internal database and session outputs of previous backup sessions. Problem Binary util_orarest is missing The message below sometimes appears when you are restoring database items to...
Page 162 is skipped. Then you can edit the script and run it manually afterwards. On how to set the omnirc variable, see the online Help index: “omnirc options”. To start a restore using Data Protector again, clear the OB2RMANSAVE variable by deleting its content or commenting or removing the whole variable.
Page 163: Data Protector Sap R/3 Zdb Integration
2 Data Protector SAP R/3 ZDB integration Introduction This chapter explains how to configure and use the Data Protector SAP R/3 ZDB integration (SAP R/3 ZDB 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 164: Integration Concepts
For general Data Protector procedures and options, see the online Help. For details on ZDB terminology, ZDB types, advantages of offline and online backups, and instant recovery concepts, see the HP Data Protector zero downtime backup concepts guide. Integration concepts...
Page 165: Zdb Flow
“ZDB integrations omnirc variables” on page 425. ZDB flow For details on how ZDB options affect the ZDB flow, including mounting, activating volume/disk groups and so on, see the HP Data Protector zero downtime backup administrator's guide. Zero downtime backup integration guide...
Page 166: Sap R/3 Zdb Session Flow
Figure 42 SAP R/3 ZDB session flow (BRBACKUP started on the application system) The SAP R/3 backup specification is read and the Data Protector omnisap.exe program is started on the application system. Omnisap.exe starts BRBACKUP, which switches the database to the backup mode (online backup) or shuts down the database (offline backup), and starts the split command on the application system, with the list of files to be included in the replica creation.
Page 167: Data Protector Sap R/3 Configuration File
The Data Protector ob2smbsplit command resolves the backup configuration, creates a replica, and preparing the replica for backup. The mountpoints for the backed up object are created on the backup system. The backup volume/disk groups are activated and the filesystems are mounted on the backup system.
Page 168 • character set (ORA_NLS_CHARACTERSET) • speed parameters (time needed for a specific file to back up - in seconds) • manual balancing parameters The configuration parameters are written to the Data Protector SAP R/3 configuration file: • during configuration of the integration •...
Page 169 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” on page 182. Example This is an example of the file: ORACLE_HOME='/app/oracle805/product';...
Page 170: Setting, Retrieving, Listing, And Deleting Data Protector Sap R/3 Configuration File 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) or /opt/omni/lbin (HP-UX, Solaris systems) directory. Cluster-aware clients...
Page 171 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. [-local filename] specifies one of the following: •...
Page 172 • On Windows: Data_Protector_home\bin\util_cmd -getopt SAP ICE OB2OPTS -sublist Environment • On HP-UX, Solaris: /opt/omni/lbin/util_cmd -getopt SAP ICE OB2OPTS \ -sublist Environment Listing parameters To list all the Data Protector SAP R/3 configuration file parameters for the Oracle instance ICE, use the following command on the Data Protector SAP R/3 client: •...
Page 173: Configuring The Integration
Data Protector SAP R/3 client: • On Windows: Data_Protector_home\bin\util_cmd -putopt SAP ICE OB2PTS "" -sublist Environment • On HP-UX, Solaris: /opt/omni/lbin/util_cmd -putopt SAP ICE OB2OPTS "" -sublist Environment Configuring the integration To configure the integration: Configure the required user accounts. See “Configuring user...
Page 174: Before You Begin
Ensure that you have correctly installed Data Protector. • For information on how to install the Data Protector disk array integration (EMC, XP, VA, or EVA) with SAP R/3 in various architectures, see the HP Data Protector installation and licensing guide.
Page 175: Cluster-Aware Clients
Cluster-aware clients • Configure SAP R/3 databases only on one cluster node, since the configuration files reside on the Cell Manager. UNIX: During the configuration, Data Protector creates a link to the Data Protector backint and splitint programs on the currently active node. On all the other nodes, do it manually.
Page 176 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 177: Configuring Sql*Net V2 Or Net8 Tns Listener
Example Oracle instance: PRO Application system: alpha.hp.com listener.ora LISTENER = (DESCRIPTION_LIST = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP) (HOST = alpha.hp.com) (PORT = 1522) SID_LIST_LISTENER = (SID_LIST = (SID_DESC = (GLOBAL_DBNAME = PRO) (SID_NAME = PRO) (ORACLE_HOME = /app/oracle815/product) PRO = tnsnames.ora...
Page 178: Checking The Connection
Start the SQL*Net V2 or Net8 TNS listener by running the following on the Oracle Server system: UNIX: ORACLE_HOME/bin/lsnrctl start Windows: ORACLE_HOME\bin\lsnrctl start Checking the connection To check the connection to the Oracle instance from the application system: Log in to the application system as the Oracle OS user. Export/set the ORACLE_HOME and ORACLE_SID variables.
Page 179: Enabling Archived Logging
For instructions on how to set up the password file, see the Oracle documentation. Enabling archived logging When you set the database to the archived logging mode, you protect the unsaved online redo logs from being overwritten. Online backup of data files is useless without the related redo logs because you cannot recover the database to a consistent state.
Page 180: Sharing Directories On The Application System
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 181: Unix Application System
/oracle/SID/sapbackup and the backup system is backup.company.com. To share the sapbackup directory: HP-UX: In the file /etc/exports on the application system, add the line: /oracle/SID/sapbackup -root=backup.company.com Solaris: In the file /etc/dfs/dfstab on the application system, add the line: share -F nfs -o root=backup.company.com...
Page 182: Choosing Authentication Mode
the name my_SAPinstance. Then, the SAPDATA_HOME Windows registry key on the backup system must have the value \\mycomputer.company.com\my_SAPinstance. If the sapbackup and sapreorg directories do not reside together, share each directory separately and also create a separate Windows registry key on the backup system (SAPBACKUP, SAPREORG).
Page 183: Before You Begin
• Optionally, if you choose database authentication mode, Oracle database user account. The user account is used by BRBACKUP and BRARCHIVE during backup. • Directory in which the SAP backup utilities are stored Data Protector then creates the configuration file for the SAP R/3 database on the Cell Manager and verifies the connection to the database.
Page 184: 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 185 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 186: Using The Data Protector Cli
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 systems: /opt/omni/lbin Run: util_sap.exe -CONFIG ORACLE_SID ORACLE_HOME targetdb_connection_string SAPTOOLS_DIR...
Page 187 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: Run: /opt/omni/lbin/omnigetmsg 12 error_number Zero downtime backup integration guide...
Page 188: Checking The Configuration
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 You can check the configuration of an SAP R/3 database after you have created at...
Page 189: Using The Data Protector Cli
Figure 46 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: /opt/omni/lbin run: util_sap.exe -CHKCONF ORACLE_SID where ORACLE_SID is the name of the Oracle instance.
Page 190: Configuring The Sap R/3 Parameter File
HP-UX, Solaris: /opt/omni/lbin run: util_sap.exe -CHKCONF_IR ORACLE_SID [-verbose] The -verbose option creates a file with a list of control files and redo log files that are on the same source volumes as the database files. If this list in not empty, a warning is displayed, stating that instant recovery is impossible.
Page 191: What I Backed Up
Backup The integration provides online and offline database backups of the following types: • ZDB to disk • ZDB to tape • ZDB to disk+tape To configure a backup, create a ZDB backup specification. Archived logs can only be backed up in a ZDB to disk+tape, ZDB to tape, or non-ZDB (standard backup) session.
Page 192: Considerations
ZDB to disk only: Archived logs cannot be backed up. To back up archived logs, create a non-ZDB (standard) SAP R/3 backup specification. For information, see the HP Data Protector integration guide for Oracle and SAP. • Configurable backup modes are supported only through using the templates.
Page 193: Creating Backup Specifications
• By default, Data Protector supports all BRTOOL options except -a and -b. To enable support for -a and -b, set the OB2BRTNOSECU omnirc variable to 1. On how to set the omnirc variable, see the online Help index: “omnirc options”. Creating backup specifications Create a backup specification using the Data Protector Manager.
Page 194: Selecting A Template
In the Create New Backup dialog box, select a template (Figure 47 on page 194) and click OK. Figure 47 Selecting a template Table 12 Backup templates Blank SAP Backup No predefined options. Brbackup_SMB_Offline Used for an offline ZDB (split mirror or snapshot backup).
Page 195 offline for a shorter period of time than if SMB_offline was used, but splitint must be supported by BRTOOLS. Brbackup_SPLITINT_Online Used for an online ZDB (split mirror or snapshot backup) using splitint. The database is active during the creation of a replica. The database is in the backup mode for a shorter period of time than if SMB_online was used, but splitint must be supported by BRTOOLS.
Page 196: Emc Backup Options
In Application system, select the SAP R/3 client to be backed up. In cluster environments, select the virtual server. In Backup system, select the backup system. Specify other disk array specific backup options (see Figure 48 on page 196 for EMC, Figure 49 on page 197 for XP,...
Page 197: Xp Backup Options
Figure 49 XP backup options Zero downtime backup integration guide...
Page 198: Va Backup Options
Figure 50 VA backup options Data Protector SAP R/3 ZDB integration...
Page 199: Eva Backup Options
Figure 51 EVA backup options Click Next. Zero downtime backup integration guide...
Page 200 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: • UNIX: In Username, type the Oracle OS user described in “Configuring user accounts”...
Page 201: Selecting Backup Objects
Select SAP R/3 objects to be backed up. You can select individual tablespaces, data files, or archived logs. NOTE: If you plan to do instant recovery, select the whole DATABASE item. Figure 52 Selecting backup objects Click Next. Zero downtime backup integration guide...
Page 202 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. NOTE: Parallelism (the number of streams your SAP R/3 database is backed up with) is set automatically.
Page 203: Application Specific Options
Set backup options. For information on the application specific options, see Table 13 on page 204. Figure 53 Application specific options Click Next. Optionally, schedule the backup. See “Scheduling backup specifications” on page 206. Click Next. 1 1. Save the backup specification, specifying a name and a backup specification group.
Page 204: Sap R/3 Backup Options
TIP: Preview your backup specification before using it for real. See “Previewing backup sessions” on page 207. Table 13 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 205 SAP R/3 system before the backup (pre-exec) or after it (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: /opt/omni/bin Backup mode Not applicable for ZDB. Use default RMAN Not applicable for ZDB.
Page 206: Modifying Backup Specifications
NOTE: The total number of sapback processes started in one session using Data Protector is limited to 256. Modifying backup specifications To modify your backup specification, click its name in the Scoping Pane of the Backup context, then click the appropriate tab, and apply the changes. Scheduling backup specifications You can run unattended backups at specific times or periodically.
Page 207: Previewing Backup Sessions
Figure 54 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 208: Using The Data Protector Cli
Using the Data Protector CLI From the directory: Windows: Data_Protector_home\bin HP-UX, Solaris: /opt/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: •...
Page 209: Using The Data Protector Cli
-sap_list backup_specification_name ZDB to disk: omnib -sap_list backup_specification_name -disk_only For details, see the omnib man page or the HP Data Protector command line interface reference. Using the SAP BRTOOLS Log in to the SAP R/3 backup system or SAP R/3 application system as the Oracle OS user.
Page 210 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 211: Configuring Sap Compliant Zdb Sessions
If you do not supply the path, the system searches for the parameter file in the directory: UNIX: ORACLE_HOME/dbs Windows: SAPDATA_HOME\database Run the BRBACKUP command. The command syntax depends on whether you are logged in to the application system or backup system: Application system: brbackup -t {online_split | offline_split | online_mirror | offline_mirror} [–q split] -d util_file -m all -c -u...
Page 212 Proceed to the Source page of the backup specification. NOTE: In environments in which the control file and datafiles reside on the same source disk, Data Protector does not let you proceed to the Source page if the Track the replica for instant recovery option is selected. Specifically, the Data Protector instant recovery check fails.
Page 213: Using The Data Protector Cli
Figure 55 Setting environmental variables 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: util_cmd –putopt SAP instance_name OB2_MIRROR_COMP 1 –sublist Environment Zero downtime backup integration guide...
Page 214: Manual Balancing
Manual balancing Manual balancing means that you manually group files into subsets, which are then backed up in parallel. To group files into subsets, add the manual_balance section to the Data Protector SAP R/3 configuration file as described in the following example. Example Suppose that we have a backup specification named SAP-R3 with the following files to be backed up: fileA, fileB, fileC, fileD .
Page 215: Sap Recovery Methods
the database within the same session. However, you can only restore (and recover) the whole database. To restore only a part of the database or the archived logs, use the standard restore method. Table 14 on page 215 shows which restore methods are available, depending on the backup session you restore from.
Page 216: Considerations
Instant recovery + You can do an instant recovery. You can include database recovery database recovery in the instant recovery session or do it afterwards, using the SAP BRTOOLS. Not available. Considerations • SAP R/3 tablespaces located on raw partitions cannot be restored using the Data Protector GUI.
Page 217: 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 218: Selecting The Target Client
In the Destination tab, select the client to restore to (Target client). By default, this is the application system. See Figure 57 on page 218. For details on options, press F1. Figure 57 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 219: Selecting The Xp Restore
EMC and XP: This step is relevant only if you have both the EMC Symmetrix Agent and HP StorageWorks XP Agent components installed on the application system. EMC: Select EMC Symmetrix restore. XP: Select StorageWorks XP restore. See Figure 58 on page 219.
Page 220: Emc - Selecting Restore To The Application System Directly
1 1. EMC and XP: In the EMC Symmetrix mode or Mirror mode drop-down list, select Disabled. This sets the restore from backup media to the application system directly. See Figure 59 on page 220. Figure 59 EMC - Selecting restore to the application system directly Figure 60 XP - Selecting restore to the application system directly Click Finish to start the restore.
Page 221: Instant Recovery
The message Session completed successfully is displayed at the end of a successful session. Instant recovery For general information on instant recovery, see HP Data Protector zero downtime backup concepts guide and HP Data Protector zero downtime backup administrator's guide. For information on instant recovery in cluster environment (Cluster File System (CFS), MC/ServiceGuard, and Microsoft Cluster Server), see HP Data Protector zero downtime backup administrator's guide.
Page 222: Sap R/3 Source Options
In the Source tab, select the objects to recover. Only whole databases can be selected. For HP StorageWorks Disk Array XP, it is recommended to leave the Keep the replica after the restore option selected to enable a restart of an instant recovery session.
Page 223 At this point, you can decide whether to perform a database recovery immediately after an instant recovery or not: • To perform only an instant recovery, click Restore. • To automatically perform a database recovery after an instant recovery, select the recovery options. For details refer to “Database recovery options”...
Page 224 lower or equal number than the specified log sequence or thread number are applied. Selected SCN number: Only archive logs until the specified SCN number are applied. Open database after recovery Opens the database after the recovery was performed. Reset logs Resets the archive logs after the database is opened.
Page 225: Instant Recovery Using The Data Protector Cli
Figure 62 SAP R/3 recovery options Instant recovery using the Data Protector CLI From the directory: Windows : Data_Protector_home\bin HP-UX : /opt/omni/bin/ run: omnir -sap –host ClientName -session SessionID {DISK_ARRAY_XP_OPTIONS | ENTERPRISE_VIRTUAL_ARRAY_OPTIONS} [-appname DB_Name Zero downtime backup integration guide...
Page 226: Instant Recovery From Replicas Containing The Control File
[-preview] The order of options is important. On Windows clients, the user name and group name options are not required. For a detailed description of the options, see the HP Data Protector command line interface reference. Instant recovery from replicas containing the control file During an instant recovery from a replica that contains the control file, the current control file and, possibly, online redo logs get overwritten.
Page 227: Restoring Using Another Device
Restore missing archived redo logs required for database recovery. Example: # sqlplus user/password@net_service_name SQL> select SEQUENCE#, NAME from V$ARCHIVED_LOG where (NEXT_TIME>to_date('2007/10/03') and (FIRST_CHANGE#<='until_SCN'); # brrestore -a log_no,... -d util_file -c force -u user/password Recover the target database. Example: # rman target user/password@net_service_name RMAN>...
Page 228: Localized Sap R/3 Objects
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. Data Protector SAP R/3 ZDB integration...
Page 229: Before You Begin
For general ZDB, restore, and instant recovery related troubleshooting, see the troubleshooting sections in the HP Data Protector zero downtime backup administrator's guide. See also the troubleshooting section in the SAP R/3 chapter of the HP Data Protector integration guide. Before you begin •...
Page 230: Verifying The Prerequisites (Oracle Side)
The database reported error while performing requested operation. Action Review user group membership for the user account which is used in Oracle database access authentication. For details, see “Configuring user accounts” on page 175. Verifying the prerequisites (Oracle side) Perform the following verification steps, in numerical order, to verify that Oracle is installed properly: On the application system, verify that the target database is online, as follows: UNIX :...
Page 231: Verifying The Prerequisites (Sap Side)
In order to establish the TNS network connection, verify that Net8 software is configured correctly for the target database, as follows: • On the application system, perform the following: UNIX : $ORACLE_HOME/bin/lsnrctl status service Windows : %ORACLE_HOME%\bin\lsnrctl status service If it fails, either start the TNS listener process or refer to the Oracle documentation on how to create the TNS configuration file (LISTENER.ORA).
Page 232: Verifying The Configuration
On the application system, verify a restore from the disk, as follows: brrestore -d disk -u user/password If it fails, refer to the SAP Online help for instructions on how to execute a restore to disk using the SAP restore utility. On the application system, verify that SAP is configured properly, as follows: Move the original backint.
Page 233: Verifying The Backup Configuration
See the online Help index “standard backup procedure” for details about how to do a filesystem backup. If it fails, refer to the HP Data Protector troubleshooting guide for help with troubleshooting a filesystem backup. Verify the environment variable on the application system:...
Page 234 To get the error description, on the Cell Manager, run: Windows: : Data_Protector_home\bin\omnigetmsg 12 error_number which is located on the Cell Manager. HP-UX, Solaris: /opt/omni/lbin/omnigetmsg 12 error_number Verify the SAP user. Check that the respective user group has the See Private Objects user right selected.
Page 235: Verifying Restore
On the application system, verify the backup using backint: Execute the following command to ensure that communication within Data Protector is established and that a backup of files can be performed: • Create a non-ZDB backup specification on the backup system. •...
Page 236 Verify that files are backed up and in the Data Protector database: • Using the omnidb command; See the appropriate man page on using the omnidb command. • Using backint; SAP tools also use this command to make a query. /opt/omni/lbin/backint –f inquiry –u ORACLE_SID -i input_file where input_file is what will be queried.
Page 237 Verify the restore using testbar2: Execute the following to ensure that restore is possible: /opt/omni/bin/testbar2 –type:SAP –appname:ORACLE_SID –perform:restore –file:file_name -bar barlist_name -object objectName If it fails, proceed as follows: • Check the backup session - was it successful? • Check that the files are in the Data Protector database. •...
Page 238: Configuration And Backup Problems
Configuration and backup problems The following list gives a description of problems and actions to be taken to resolve them: • The Server Manager is unable to connect to the destination Check whether the Oracle TNS listener process is up and running. Check whether there are any environment variables required for a successful remote connection to the target database;...
Page 239 On UNIX systems, check the output of the following command on the application system: /opt/omni/lbin/util_sap.exe -CHKCONF ORACLE_SID In case of an error, the error number is displayed in the form: *RETVAL*Error_number To get the error description, start the following command on the application system: /opt/omni/lbin/omnigetmsg 12 Error_number On Windows systems, perform the following procedure using the Data Protector...
Page 240: Restore Problems
BR0301E SQL error -1033 at location BrDbConnect-2 ORA-01033: ORACLE initialization or shutdown in progress BR0310E Connect to database instance HOOHOO failed Before you start a backup, ensure that the database instance is the open or shutdown mode. Problem Configuration fails due to a script failure During configuration of an SAP R/3 database, Data Protector reports the following error: Integration cannot be configured.
Page 241 • Do not use non-ASCII or non-Latin 1 characters for filenames. Problem Restore of SAP R/3 tablespaces located on raw partitions fails When restoring SAP tablespaces that are located on raw partitions using the Data Protector GUI, the restore fails with a message similar to the following: [Major] From: VRDA@joca.company.com "SAP"...
Page 242 Data Protector SAP R/3 ZDB integration...
Page 243: Data Protector Microsoft Sql Server Zdb Integration
The following disk arrays and array configurations are supported: Supported array Supported configurations EMC Symmetrix (EMC) Dual host TimeFinder HP StorageWorks Disk Array XP (XP) BC, CA, combined BC+CA HP StorageWorks Enterprise Virtual Array (EVA) BC, combined CA+BC HP StorageWorks Virtual Array (VA)
Page 244: Integration Concepts
Instant recovery ZDB to disk+tape Standard restore, instant recovery For a description of ZDB and instant recovery concepts, see the HP Data Protector zero downtime backup concepts guide. Integration concepts Data Protector integrates with SQL Server through the Data Protector sql_bar.exe executable, installed on SQL Server.
Page 245: Configuring The Integration
Figure 63 Backup and restore concepts Configuring the integration Prerequisites • You need a license to use the SQL Server ZDB integration. See the HP Data Protector installation and licensing guide for information. • Ensure that you correctly installed and configured SQL Server.
Page 246: Before You Begin
Data Protector filesystem ZDB and restore. See the online Help for instructions. Data Protector SQL Server configuration file Data Protector stores integration parameters for every configured SQL Server on the Cell Manager in: HP-UX, Solaris: /etc/opt/omni/server/integ/config/MSSQL/client_name%instance_name Windows: Data_Protector_home\Config\Server\Integ\Config\MSSQL\client_name%instance_name Data Protector Microsoft SQL Server ZDB integration...
Page 247: Configuring Users
Configuration parameters are the username and password of the SQL Server user, who must have permissions to run backups and restores within SQL Server (assuming the standard security is used). They are written to the Data Protector SQL Server configuration file during configuration of the integration. The content of the configuration file is: Login='user';...
Page 248: Configuring Sql Server Instances
Configuring SQL Server instances An SQL Server instance is configured during the creation of the first backup specification. The configuration consists of setting the user account that Data Protector should use to connect to the SQL Server instance. The specified login information is saved to the Data Protector SQL Server instance configuration file on the Cell Manager.
Page 249: Using The Data Protector Gui
Using the Data Protector GUI In the Context List, click Backup. In the Scoping Pane, expand Backup Specifications, right-click MS SQL Server, and click Add Backup. In the Create New Backup dialog box, select the Blank Microsoft SQL Server Backup template and specify backup type. For details, see Step 3 on page 255.
Page 250: Configuring Sql Server
In the Configure MS SQL Server dialog box, specify the user account that Data Protector should use to connect to the SQL Server instance. • SQL Server authentication: SQL Server user account. Specify a username and password. • Windows authentication: Windows domain user account (preferred option). Specify a username, password, and the domain.
Page 251: Using The Data Protector Cli
NOTE: It is recommended that the SQL Server system administrator configures the integration. For details about security, see the SQL Server documentation. Click OK to confirm the configuration. The SQL Server instance is configured. Exit the GUI or proceed with creating the backup specification at Step 7 on page 261.
Page 252: Changing And Checking Configuration
Changing and checking configuration You can check and change configuration using 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 MS SQL Server. Click a backup specification for which you want to change the configuration.
Page 253: Using The Data Protector Cli
Right-click SQL Server and select Check Configuration. See Figure 66 on page 253. Figure 66 Checking configuration Using the Data Protector CLI To change the configuration, run the command for configuring SQL Server instances again, entering different data. To check configuration, run: sql_bar chkconf [-instance:instance_name] If the optional parameter -instance:instance_name is not specified, the default instance is checked.
Page 254: Backup
If -instance:instance_name is not specified, Data Protector returns configuration for the default instance. Backup To run ZDB of an existing SQL Server ZDB specification: • Schedule a backup using the Data Protector Scheduler. • Start an interactive backup using the Data Protector GUI or CLI. Prerequisites •...
Page 255: Selecting A Split Mirror Backup
Backup template. XP, EMC: In the Backup type drop-down list, select Split mirror backup. In the Sub type drop-down list, select either EMC Symmetrix or HP StorageWorks XP. See Figure on page 255. Figure 67 Selecting a split mirror backup VA, EVA: In the Backup type drop-down list, select Snapshot backup.
Page 256: Selecting A Snapshot Backup
Figure 68 Selecting a snapshot backup Click OK. Data Protector Microsoft SQL Server ZDB integration...
Page 257: Emc Backup Options
Under Client systems, select the SQL Server system. In cluster environments, select the virtual server of the SQL Server resource group. In the Backup system drop-down list, select the backup system. Select other disk array specific backup options (see Figure 70 on page 258 for EMC, Figure 71...
Page 258: Xp Backup Options
Figure 70 XP backup options To enable instant recovery, leave Track the replica for instant recovery selected. Data Protector Microsoft SQL Server ZDB integration...
Page 259: Va Backup Options
Figure 71 VA backup options EVA: To enable instant recovery, select Track the replica for instant recovery. Zero downtime backup integration guide...
Page 260: Eva Backup Options
Figure 72 EVA backup options Click Next. In Application database, specify the name of the SQL Server instance. Windows Server 2008 only: If you intend to use the Integrated authentication option, specify the User and group/domain options. For information on the options, press F1.
Page 261: Selecting User Databases
If the client is not configured, the Configure MS SQL Server dialog box appears. Configure it as described in “Configuring SQL Server instances” on page 248. Select the databases to be backed up. IMPORTANT: To enable instant recovery, create different backup specifications for user and system databases.
Page 262 Select the devices. Click Properties to set the media pool and preallocation policy. The device concurrency is set to 1 and cannot be changed. For more information on options, press F1. To create additional backup copies (mirrors), specify the desired number by clicking Add mirror/Remove mirror.
Page 263: Sql Server Specific Backup Options
Figure 74 Saving a backup specification SQL Server Specific Backup Options SQL Server specific backup options are specified by clicking the Advanced tab in the Application Specific Options group box. Zero downtime backup integration guide...
Page 264: Sql Server Backup Options
Figure 75 Application specific options Table 16 SQL Server backup options Concurrent streams Sets the number of concurrent streams used to back up SQL Server databases from the replica to tape. Applicable for ZDB–to–tape and ZDB–to–disk+tape sessions. Fast direct mode Ignored for ZDB sessions.
Page 265: Scheduling Backups
NOTE: Do not use double quotes (" ") in object-specific pre-exec and post-exec commands. Scheduling backups You can run unattended ZDB at specific times or periodically. For details on scheduling, see the online Help index: “scheduled backups”. NOTE: You cannot run ZDB to disk or ZDB to disk+tape if Track the replica for instant recovery is not selected in the backup specification.
Page 266: Using The Data Protector Gui
Using the Data Protector GUI In the Context List, click Backup. In the Scoping Pane, expand Backup Specifications, and then MS SQL Server. Right-click the backup specification you want to start and select Start Backup. Select Network load. For information on network load, click Help. Click OK. For ZDB sessions, the backup type is set to Full.
Page 267: Before You Begin
restore scenario, and instant recovery. For more information, see the following sections. Before you begin • Before starting restore, verify that the database is not being in use. Standard restore NOTE: There is no need to create an empty database before restore, because the database and its files are generated automatically by SQL Server.
Page 268: Restore Objects
Select the SQL Server objects that you want to restore. See Figure 77 on page 268. Figure 77 Restore objects To select backup object specific options, right-click the object and select Properties. Data Protector Microsoft SQL Server ZDB integration...
Page 269: Selecting Object Specific Options
Figure 78 Selecting object specific options You can select the version (backup date) from which you want to restore and choose SQL Server specific restore options. Note that some options are not available for restore of data files. See “Restore options”...
Page 270: Restore Options
If you want to restore your data to another client or instance, specify new locations for the databases in the Options property page. See “Restore options” on page 271. NOTE: When you click Options, the cell is browsed for running SQL Server instances that can become target instances for restore.
Page 271: Restore Options
In the Devices page, select devices to use for the restore. The Automatic device selection option is selected by default, but it is recommended to select the Original device selection option. IMPORTANT: If you decide to select the Automatic device selection option, ensure that the number of available devices is equal to or greater than the number of devices that were used for backup.
Page 272 Option Description Stop at This option is only available for database objects. Specifies the exact time when the rollforward of transactions will be stopped. Therefore, to enable database recovery to a particular point in time, backup you restore from must be a transaction log backup.
Page 273: Restoring To Another Sql Serverinstance Or/And Another Sql Server
Option Description Restore database This option is only available for database objects. with a new name Restores the database under a different name. Specify the database logical filename and the destination filename (suboptions of Restore files to new locations). Restore files to new Restores files to a new location.
Page 274: Instant Recovery
Start restore. See “Restore” on page 266. Instant recovery See the HP Data Protector zero downtime backup concepts guide and HP Data Protector zero downtime backup administrator's guide for general information on instant recovery. Prerequisites • If you restore user databases, put the databases offline: Start SQL Server Enterprise Manager.
Page 275: Point-In-Time Restore
To recover user databases to a specific point in time: a. In the Source property page, under Restore Objects, right-click a database and click Properties. b. In the Backup version drop-down list, select the required replica. The latest version is selected by default. Select Point in time restore.
Page 276: Monitoring Sessions
Figure 81 Restoring database with a new name Click Restore MS SQL Server. If you restore system databases, SQL Server displays errors because its services are offline. Therefore, when restore completes, start SQL Server manually using SQL Server Enterprise Manager. Monitoring sessions You can monitor currently running or view previous sessions in the Data Protector GUI.
Page 277: Troubleshooting
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. For general ZDB, restore, and instant recovery related troubleshooting, see the HP Data Protector zero downtime backup administrator's guide. Before you begin •...
Page 278: Problems
Additionally, if your backup failed: • Verify the configuration file to check if the Cell Manager is correctly set on SQL Server. • If you do not see the SQL Server instance as the application database when creating a backup specification, enter the instance name yourself. When “not-named instance”...
Page 279 • SQL Server VDI.LOG file contains an entry similar to: 2000/03/15 13:19:31 pid(2112) Error at BuildSecurityAttributes: SetSecurityDescriptorDacl Status Code: 1338, x53A Explanation: The security descriptor structure is invalid. SQL Server service and Data Protector Inet are running under different accounts. The integration cannot access SQL Server due to security problems. Action Restart the Data Protector Inet service under the same account as the SQL Server service is running.
Page 280 Action Recover the database to the latest point in time using SQL Query Analyzer: RESTORE DATABASE database_name WITH RECOVERY After the recovery, additional transaction logs cannot be applied. Problem Database restore fails with “Error has occurred while executing SQL statement” If the database to be restored is still running, an error similar to the following may be reported: [Warning] From: OB2BAR@taz "(DEFAULT)"...
Page 281 Problem Instant recovery of SQL Server databases fails Action Restart SQL Server instance services after instant recovery completes. If restarting services does not automatically start the recovery of all system databases, start the SQL Server instance in a single-user mode and manually start the recovery of the master database.
Page 282 Problem Database is left in unrecovered state after restore completed successfully If you set the time for Stop at beyond the end of the RESTORE LOG operation, the database remains in the unrecovered state as if the RESTORE LOG operation was run with Leave the database non-operational.
Page 283 Action To solve the problem: In the HP Data Protector Manager, switch to the Restore context. In the Scoping Pane, expand Restore Objects and then MS SQL Server. Select name of the Microsoft SQL Server for which you want to perform restore.
Page 284 In the Version and Options property pages, specify the appropriate options. For details, see “ Standard restore” on page 267. 1 1. Click OK to close the Properties window. In the Options, Devices, and Media property pages, specify the appropriate options.
Page 285: Data Protector Microsoft Exchange Server Zdb Integration
HP StorageWorks Virtual Array (VA) All ZDB types (ZDB to tape, ZDB to disk, and ZDB to disk+tape) are supported by this integration. For ZDB types description, see the HP Data Protector zero downtime backup concepts guide and the online Help.
Page 286: Integration Concepts
Standard restore (database) + standard restore (transaction logs) For a description of ZDB and instant recovery concepts, see the HP Data Protector zero downtime backup concepts guide. Integration concepts The Exchange ZDB integration backs up Microsoft Information Store (MIS), Key Management Service (KMS), and Site Replication Service (SRS), which are replicated within a disk array.
Page 287: Configuring The Integration
ZDB and restore processes. Configuring the integration Prerequisites • You need a license to use the Exchange Server ZDB integration. See the HP Data Protector installation and licensing guide for information. • Ensure that you correctly installed and configured Exchange Server.
Page 288: Before You Begin
Before you begin • Configure devices and media for use with Data Protector. See the online Help index: “configuring devices” and “creating media pools” for instructions. For ZDB to disk, configure a backup device (for example, a standalone file device), as you will have to select it when configuring a backup specification.
Page 289: Backup
Figure 82 Path system variable • In cluster environments, prior to configuring a ZDB specification, create a new physical resource (LUN for VA, virtual disk for EVA, and LDEV for XP) for the cluster and move the Exchange Server database and transaction log files to it. For information on moving the Exchange Server database and transaction log files, see the following documents available at http://support.microsoft.com: •...
Page 290: Configuring Exchange Server Zdb
• Schedule a backup using the Data Protector Scheduler. • Start an interactive backup using the Data Protector GUI or CLI. Limitations • Backup preview is not supported. Considerations • You can perform transaction logs backups only if circular logging is disabled for the involved Exchange Server.
Page 291 The omnicreatedl command creates a ZDB specification with included Stop/quiesce the application and Restart the application scripts (omniEx2000.exe) for mounting/dismounting backed up databases and checking their consistency. Additionally, omnicreatedl creates a transaction logs backup specification for each storage group specified in a ZDB specification (circular logging disabled). See Figure 98.
Page 292: General Options
IMPORTANT: If parameters contain spaces, use double quotes when specifying them in the omnicreatedl command. For example, -storage_group "First Storage Group". Table 18 General options Parameter Description Instructs omnicreatedl to create a ZDB specification and -ex2000 transaction logs backup specification for all specified storage groups (circular logging disabled).
Page 293 0 to 2 separated by a comma, for example: 2,0,1 A sequence does not set the order in which the replicas are used. The algorithm of using replicas is described in the HP Data Protector zero downtime backup concepts guide. A range must be specified in ascending order.
Page 294: Va Options
Parameter Description This parameter is optional. -instant_restore Select to perform ZDB to disk or ZDB to disk+tape and leave the replica on a disk array for instant recovery. If this option is not set, you cannot perform instant recovery from the replica created or reused in this session.
Page 295 Parameter Description This parameter is optional. -instant_recovery Select to perform a ZDB to disk or ZDB to disk+tape and leave the replica on a disk array for instant recovery. Also, specify -snapshots number.The options -use_existing_snapshotand -leave_versionare automatically selected. If this option is not set, you cannot perform instant recovery from the replica created or reused in this session.
Page 296: Eva Options
Parameter Description Specify this option to apply LUN security to child LUNs (target -lun_security volumes or snapshots) created by the integration. If Secure Manager is activated, specify this option and configure passwords correctly; otherwise, the backup fails. Table 21 EVA options Parameter Description Instructs omnicreatedl to create a snapshot ZDB specification.
Page 297 Parameter Description Specifies a snapshot policy depending on the type of already -snapshot_policy existing snapshots for the same source volume. {strict | loose} When -strict is selected, Data Protector attempts to create snapshots as specified by -snapshot_type. If the source volumes used in the session have existing snapshots of a different type, the selected type is not created (the session is aborted).
Page 298: Exchange Server Options
Parameter Description Available if combined configuration is selected. -ca_failover_option {follow_replica_direction Specify to control the replication direction after a failover. Select follow_replica_direction to follow the replication m a i n t a i n _ r e p l i c a _ l o c a t i o n } direction and create replicas on the array remote to current source.
Page 299 TIP: To create an Exchange ZDB specification and a transaction logs backup specification, you can also use the omniex2000SM.bat file, located in the Data_Protector_home\bin directory on the application system. The script provides templates and examples of omnicreatedl usage. You can modify omniex2000SM.bat using any text editor.
Page 300: Examples Of Using Omnicreatedl
Figure 83 omniex2000SM.bat file Examples of using omnicreatedl Example 1 - XP: Data Protector Microsoft Exchange Server ZDB integration...
Page 301 To create a ZDB specification BS1, using device dev1, for all storage groups running on Exchange Server on the application system computer_app.company.com and backup system computer_bck.company.com using the BC configuration, run: omnicreatedl -ex2000 -datalist BS1 -device dev1 -all_storage_groups -split_mirror -sse -local computer_app.company.com computer_bck.company.com Example 2 - XP: To create a ZDB specification BS2, using device dev1, for two storage groups (First...
Page 302 To create a ZDB-to-disk+tape or ZDB-to-disk specification Exchange_example to back up Site Replication Service to the backup device dev1, using the replica set with 5 replicas, run: omnicreatedl -ex2000 -datalist Exchange_example -device dev1 -snapshot -va computer1.company.com computer2.company.com -instant_recovery -snapshots 5 -annotation SRS The omnicreatedl creates a transaction logs backup specification file SRS (LOGS) computer1.company.com for Site Replication Service log files backup (circular logging disabled).
Page 303: Modifying Zdb Specifications
omnicreatedl -ex2000 -datalist Exchange_example -device dev1 -snapshot -smis computer1.company.com computer2.company.com -instant_recovery -snapshots 3 -wait_clonecopy 50 -annotation The omnicreatedl creates a transaction logs backup specification file SRS (LOGS) computer1.company.com for Site Replication Service log files backup (circular logging disabled). When omnib or Data Protector GUI is used to start backup, select ZDB to disk+tape.
Page 304: Checking Exchange Files For Consistency
In the Scoping Pane, expand Backup Specifications, then Filesystem, and click a ZDB specification. See Figure Figure 84 Exchange ZDB specification Modify backup devices, set ZDB options, schedule, and start backup. For a particular database, back up .edb and .stm files. To create additional backup copies (mirrors), specify the desired number by clicking Add mirror/Remove mirror under the Destination tag.
Page 305 How To: Use the Eseutil Utility to Detect File Header Damage in Exchange 2003 (825088) available at http://support.microsoft.com. IMPORTANT: Page level integrity check is not supported on EVA. Proceed as follows: Copy the utility to the backup system. The esefile resides on the Exchange 2000 Installation CD at: CD:\ENGLISH\EXCH2000\ENT\SUPPORT\UTILS\I386\ESEFILE The eseutil resides in Exchange_Server_home\bin once the Exchange Server 2003 is installed.
Page 306: Example Script For Ms Exchange Server 2000
Figure 85 Example script for MS Exchange Server 2000 See the HP Data Protector zero downtime backup administrator's guide for information on the mountpoint creation. The commands in the script ensure that *.edb database files specified in the backup specification are checked for consistency.
Page 307: Scheduling Backups
Scheduling backups You can run unattended ZDB at specific times or periodically. For details on scheduling, see the online Help index: “scheduled backups”. NOTE: You cannot run ZDB to disk or ZDB to disk+tape if -instant_restore (XP) or -instant_recovery (VA, EVA) is not selected in the backup specification. Scheduling example To schedule a database ZDB 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...
Page 308: Using The Data Protector Gui
NOTE: You cannot run ZDB to disk or ZDB to disk+tape if -instant_restore (XP) or -instant_recovery (VA, EVA) is not selected in the backup specification. Using the Data Protector GUI In the Context List, click Backup. In the Scoping Pane, expand Backup Specifications and then Filesystem. Right-click the backup specification you want to start and select Start Backup.
Page 309: Restore
where Name is the backup specification name. For more information on omnib, see its man page. Restore Data Protector offers restore from backup media to the application system on LAN (standard restore), where you can select among various restore options depending on your restore scenario, and instant recovery.
Page 310: Point-In-Time Recovery
TIP: You can improve data transfer rate by configuring a backup device on the application system. See the online Help index: “configuring, backup devices” for details. You can also perform a restore using another device. See the online Help index “select, devices for restore”.
Page 311: Restoring Exchange Database
In the Scoping Pane, expand Restore Objects, Filesystem, and then select the client (backup system). Mark the drive letter on which the database resides. Figure 87 Restoring Exchange database Exchange database consists of two files: name.edb and name.stm. For a particular database, select both files.
Page 312: Selecting The Application System
Under the Destination tab, select the application system as the Target client. Figure 88 Selecting the application system Set restore options. For information, see the online Help index: “restore, options“. In the Devices page, select devices to use for the restore. Note that you can use a different device for restore than the one used for backup.
Page 313: Selecting Xp Restore
XP, EMC: Select StorageWorks XP restore. Click Next. Figure 89 Selecting XP restore Zero downtime backup integration guide...
Page 314: Rollforward Recovery
In the Start Restore Session dialog box, select Disabled in the Mirror mode drop-down list. This sets a direct restore from the backup media to the application system on LAN. Figure 90 XP Restore option Click Finish to start restore. Rollforward recovery IMPORTANT: The procedure described below gives instructions on how to copy .edb, .stm, and...
Page 315 In the Context List, select Restore. Zero downtime backup integration guide...
Page 316: Restoring Exchange Database
Proceed as follows: • To restore the database, expand Restore Objects, Filesystem, and the name of the backed up server. Then select the [Exchange 2000] object as shown Figure • To restore transaction logs, expand Restore Objects, Filesystem, and the name of the backed up server.
Page 317: Restoring Log Files
Figure 92 Restoring log files Make the following selections in the Results Area: • To restore the Exchange database, select .edb and .stm files. For a particular database, select both files. You can restore a storage group by selecting the storage group folder when the entire storage group was backed up and all databases reside in the same directory.
Page 318: Selecting The Application System
Select the application system as the Target client under the Destination tab. Figure 93 Selecting the application system Set restore options. For information, see the online Help index: “restore, options“. Click Restore. The Start Restore Session dialog box is displayed. Specify Report level and Network load.
Page 319: Selecting Xp Restore
XP, EMC: Select StorageWorks XP restore. Click Next. Figure 94 Selecting XP restore Zero downtime backup integration guide...
Page 320: Instant Recovery
Figure 95 XP Restore option Click Finish to start restore. Instant recovery See the HP Data Protector zero downtime backup concepts guide and HP Data Protector zero downtime backup administrator's guide for general information on instant recovery. You can recover Exchange databases using: •...
Page 321: Point-In-Time Recovery
For detailed procedure on how to recover the Exchange Server, see Offline Backup and Restoration Procedures for Exchange (296788) at http://support.microsoft.com. When following the Microsoft procedure, see the HP Data Protector zero downtime backup administrator's guide for information on copying backed up .edb and .stm files to the appropriate database using instant recovery.
Page 322: Selecting Xp Restore
XP, EMC: Select StorageWorks XP restore. Click Next. Figure 96 Selecting XP restore Data Protector Microsoft Exchange Server ZDB integration...
Page 323: Troubleshooting
For general Data Protector troubleshooting information, see the HP Data Protector troubleshooting guide. For general ZDB, restore, and instant recovery related troubleshooting, see the HP Data Protector zero downtime backup administrator's guide. Zero downtime backup integration guide...
Page 324: Before You Begin
Ensure that the latest official Data Protector patches are installed. See the online Help index: “patches” on how to verify this. • See the HP Data Protector product announcements, software notes, and references for general Data Protector limitations, as well as recognized issues and workarounds.
Page 325: Problems
See the HP Data Protector troubleshooting guide for instructions on troubleshooting devices. • Try to restart the Microsoft Exchange Server and start the backup again. • Check that the Exchange_home\bin directory is added to the Windows Path environment variable. For details, see “Configuring the...
Page 326: Disabling Circular Logging
Figure 98 Disabling circular logging Problem Omnicreatedl cannot create a backup specification and the session is aborted The following error is reported: [ERROR] Could not obtain any data for backup from host app_sys. Make sure the Exchange server is running and Data Protector Exchange Integration installed.
Page 327 • Check that Exchange_home\bin is listed in the Path system variable. For instructions, see Creating ZDB specifications. Problem Error starting service If the KMS service password is not kept on disk, the following error is reported: [Major] From: OB2BAR_main@machine.com "" Time: 10/20/2003 5:17:24 PMError starting service.
Page 328 Data Protector Microsoft Exchange Server ZDB integration...
Page 329: Integrating The Data Protector Zdb Integrations And Microsoft Volume Shadow Copy Service
5 Integrating the Data Protector ZDB integrations and Microsoft Volume Shadow Copy Service Introduction A traditional backup process is based on the direct communication between the backup application and the application whose data is backed up. This backup method requires from the backup application an individual interface for each application it backs up.
Page 330 Data Protector supports the integration with VSS. The Data Protector Volume Shadow Copy integration provides a unified communication interface that can coordinate backup and restore of an application regardless of their specific features. With this approach, a backup application does not need to handle each application to be backed up specifically.
Page 331: Actors Of The Traditional Backup Model
Figure 99 Actors of the traditional backup model Figure 100 Actors of the Data Protector VSS integration backup model Without using the Volume Shadow Copy Service, Data Protector has to communicate with each application to be backed up individually. The Data Protector VSS integration introduces a unified backup and restore interface and provides the coordination among the participants of the backup and restore process.
Page 332: Vss Backup Types
VSS backup types The following backup types are available with the Data Protector VSS integration: • Local backup The volume shadow copies are presented to the same application system from which they were created. The shadow copies are backed up to tape or to disk from the application system.
Page 333: Backup
Refer to the HP Data Protector zero downtime backup concepts guide for a general description of ZDB (split mirror or snapshot backup) and instant recovery concepts. For a complete list of supported VSS writers and provider, see the latest support matrices at http://www.hp.com/support/manuals.
Page 334 When you select writers and components you want to back up and start a VSS integration backup, Data Protector communicates with the Volume Shadow Copy Service (backup coordinator) to notify that the backup is about to start. The coordinator identifies all writers that support the VSS feature and passes the list of available writers and their characteristics (Writer Metadata Document) back to Data Protector.
Page 335 Depending on the backup options selected in the backup specification, the ZDB type selected in the backup specification or at the start of the backup, and the backup type (local or transportable), the following scenarios, which are not mutually exclusive, are possible. The replica can be: •...
Page 336: Data Consistency
Figure 101 Local VSS backup Figure 102 Transportable VSS backup Data consistency The filesystem backup does not guarantee application data consistency, only filesystem consistency. Application data consistency can be achieved only by using supported application writers, such as Microsoft Exchange Server writer. Integrating the Data Protector ZDB integrations and Microsoft Volume Shadow Copy Service...
Page 337: Backup With The Enterprise Virtual Array Vss And Vds Hardware Provider
Backup with the Enterprise Virtual Array VSS and VDS hardware provider There are three replica types available when backing up using the Enterprise Virtual Array (EVA) hardware provider: • Standard snapshot • Vsnap • Snapclone However, in the Data Protector GUI, you can select only between standard snapshot (Snapshot (Differential)) and snapclone (Mirror/Clone (Plex)).
Page 338: Standard Restore From Tape
For detailed information on the VSS integration instant recovery concepts, see the “Instant recovery” on page 391. For detailed information on the general instant recovery concepts, see the HP Data Protector zero downtime backup concepts guide and HP Data Protector zero downtime backup administrator's guide.
Page 339: Restoring Files
Data Protector first restores the metadata, which was collected during the backup. Then it examines the metadata to identify the backup components and determine the restore method. It also checks if restore to specific volumes is possible. Data Protector connects to the coordinator (VSS service) to notify that the restore is about to start, which in turn communicates with the writer.
Page 340: Querying The Vssdb
VSSDB. You can query and manage the items of the VSSDB using the omnidbvss command. For information on the command syntax, description, and examples, see the HP Data Protector command line interface reference. The following tasks can be performed using the omnidbvss command: •...
Page 341: Deleting Backup Sessions
Deleting backup sessions Using the omnidbvss command, you can delete: • A specific instant recovery-enabled backup session (a replica version), identified by the session ID, from the non-persistent part of the VSSDB and disk array, or only from the VSSDB. •...
Page 342: Microsoft Exchange Server 2007 Writer Concepts
session continues with creating a new replica and leaving the old one on the array. Note that in this case, if there is no space on the disk array for creating a new replica, the backup session also fails. If you set the OB2VSS_IGNORE_BACKUP_DISK_CHANGES omnirc variable to 1, the backup session continues by removing the old replica and creating a new one in its place.
Page 343: Restore
Restore With Microsoft Exchange Server 2007 writer, you can restore your data not only to the original location (from which the backup was performed) but also to a different location. You can restore: • A whole storage group • A single store In both cases the respective LCR or CCR copies can also be restored.
Page 344: Prerequisites And Limitations
Shadow Copy Service integration. Additional limitations and recommendations that are not directly connected to the integration (such as operating system and GUI limitations) and disk array limitations are listed in the HP Data Protector product announcements, software notes, and references.
Page 345: Limitations
Limitations For a list of general Data Protector limitations, see the HP Data Protector product announcements, software notes, and references. • Maximum 512 shadow copies per volume are allowed. The number of shadow copies per volume is limited by system resources.
Page 346: Disk Array Xp Hardware Provider Limitations
specify too many objects in a backup specification, since they might reside on too many source volumes. For example, a Microsoft Exchange Server storage group should typically not reside on more than four source volumes, and only one storage group should be selected for backup if the storage group occupies four source volumes.
Page 347: Configuring The Integration
Not all VSS writers supported by Data Protector can be used with the instant recovery functionality. For a list of the VSS writers that support the instant recovery functionality, see the latest support matrices at http://www.hp.com/support/ manuals. Configuring the integration...
Page 348 resolve operation, Data Protector contacts VDS to get information about the storage IDs of the source volumes presented on the application system. The information about the storageIDs is required during instant recovery, in case such information cannot be gathered at restore time. If resolving is not performed before a backup session, one of the following happens: •...
Page 349: Configuring Hp Storageworks Enterprise Virtual Array
• HP Operations Manager (HP StorageWorks SMI-S EVA provider part). • HP StorageWorks Business Copy (BC) EVA microcode and license. • If the alternate paths solution is used, install HP MPIO DSM for EVA. • An EVA license for, at least, basic and snapshot operation.
Page 350: Configuring The Integration
To set, delete, list, or check the login information, use the omnidbsmis —ompasswd CLI command. For command syntax and examples, see the HP Data Protector command line interface reference. The information you provide is kept in the ZDB database for EVA integration (SMISDB).
Page 351: Prerequisites
Install Data Protector components and licenses: • An instant recovery license. • The HP StorageWorks XP Agent. If this agent is not installed, it is not possible to restore data from the disk array XP. For installation and licensing information, see the HP Data Protector installation and licensing guide.
Page 352: Vss And Vds Provider Configuration For Zdb And Instant Recovery
For details on how to configure the provider, see the hardware provider documentation. Configuring the VSS hardware provider for Enterprise Virtual Arrray Open the HP StorageWorks VSS Configuration Utility for EVA and follow the steps below: Ensure that the correct management appliance IP address is specified.
Page 353: Configuring The Vss Hardware Provider For Disk Array Xp
Configuring the VSS hardware provider for Disk Array XP Before running ZDB sessions, open the HP StorageWorks XP VSS Hardware Provider Configuration Utility and choose the configuration mode for your backups: VSS Compliant Mode or Resync Mode.
Page 354: Microsoft Exchange Server Writer Specific Configuration
• Non-strict If any folder on the volume does not belong to the component, the ZDB to disk or instant recovery fails. • Disabled A check detects whether there is more than one component on the volume and whether there is any other data besides the component’s data on the volume, but the session will not fail.
Page 355: Microsoft Exchange Server 2007 Configuration In Ccr Environments
mount the database after restore of an LCR copy to the location where original database resides. Microsoft Exchange Server 2007 configuration in CCR environments In CCR environments where a production database resides on a different EVA disk array from the database copy, and the backup system and the application system are not the same physical system, ensure that: •...
Page 356: Writer Description
VSS writers either come with the Windows operating system or with applications. For a complete list of supported VSS writers and providers, see the latest support matrices at http://www.hp.com/support/manuals. The Data Protector Microsoft VSS integration does not provide any restore method for writers requesting a custom restore.
Page 357 Writer name Description Restore method DHCP Jet Writer This is a system writer, used to back up and Files are restored after restore DHCP Service database. DHCP Service a reboot. provides dynamic IP address assignment and network configuration for Dynamic Host Configuration Protocol (DHCP) clients.
Page 358 Writer name Description Restore method Microsoft This is a writer used to back up and restore Standard VSS restore Exchange Server Microsoft Exchange Server. Microsoft Exchange and instant recovery. Writer Server is a mail and groupware server. Microsoft Virtual This is a writer used to back up and restore Standard VSS restore Server 2005 Microsoft Virtual Server 2005.
Page 359 Writer name Description Restore method Registry Writer This VSS writer using a custom API, is used to Custom restore method back up and restore Windows Registry. Windows Registry is a database repository of information containing the Windows system configuration. Remote Storage This is a system writer used to back up and Files are restored after Writer...
Page 360: Backing Up Writers Data
Split mirror replica This type of replica is produced using mirroring technology, provided by HP StorageWorks Disk Array XP. Mirroring technology allows a duplicate (a mirror) of the filesystem or application data to be created during normal application use. When...
Page 361: Hp Storageworks Eva Specifics
Snapshot replica This type of replica is produced using snapshot technology, provided by HP StorageWorks Enterprise Virtual Array. With a snapshot replica, no synchronization is required before creating the fixed point-in-time copies, because a snapshot is a logical copy of pointers to the data rather than the data itself.
Page 362: Hp Storageworks Disk Array Xp Specifics
370. To create a new backup specification for the VSS integration, proceed as follows: In the HP Data Protector Manager, switch to the Backup context. In the Scoping Pane, expand Backup Specifications. Integrating the Data Protector ZDB integrations and Microsoft Volume Shadow Copy Service...
Page 363 Right-click MS Volume Shadow Copy Writers and click Add Backup. Zero downtime backup integration guide...
Page 364: Selecting Vss Transportable Backup
In the Create New Backup dialog box, select the backup type. You can choose between the following types: • Local or network backup This type is used for single host VSS backup. To perform a backup for instant recovery purposes, you need a hardware provider. Otherwise, no hardware provider is required for this type of backup.
Page 365 Specify the following options: • The name of the application system. When backing up cluster-aware writers (such as SQL Server via the MSDE Writer, or Exchange Server in the LCR or CCR environment), specify the virtual server name given in the particular writer resource group as the application system.
Page 366: Vss Transportable Backup Options
For descriptions of these options, press F1. Click Next. Figure 104 VSS transportable backup options In this page, the selection of your VSS client is displayed. On Windows Server 2008, you can specify the User and group/domain options. For information on these options, press F1. Click Next.
Page 367 Select the backup objects you want to back up. Make sure that in case of instant-recovery enabled sessions, you select all objects (for example all storage groups, all virtual machines ...) residing on a specific source volume that will be backed up. only a whole source volume to be backed up, regardless of the number of virtual machines residing on the volume.
Page 368: Selecting Microsoft Exchange Server 2007 Ccr Copy Backup
Figure 105 Selecting Microsoft Exchange Server 2007 CCR copy backup objects Figure 106 Selecting Microsoft Hyper–V VSS writer backup objects If a writer requires all of its components to be backed up, lower-level items are automatically selected. If you select such a writer for backup, all its components will be backed up.
Page 369: Additional Options For Microsoft Exchange Server 2007 In A Ccr Environment
Microsoft Exchange Server 2007 Writer in a CCR environment: Optionally, to specify clustering options, right-click Microsoft Exchange Writer and click Additional options. Figure 107 Additional options for Microsoft Exchange Server 2007 in a CCR environment For backup to tape, select the devices you want to use for the backup to tape. Click Properties to set the device concurrency, media pool, and preallocation policy.
Page 370: Vss Specific Backup Options
Following the wizard, select the backup options and schedule your backup. TIP: If you are not sure about selecting the backup options, keep the default values. For details about the options common to all Data Protector backup specifications, see the online Help. Once you have defined all backup options and the schedule, you need to name and save the newly-created backup specification.
Page 371 Recommendations • With the HP StorageWorks EVA provider, an Exchange storage group should not reside on more than four source volumes. However, the recommended configuration is that transaction logs reside on one source volume and the stores on another source volume.
Page 372: Selecting Microsoft Exchange Server 2003 Storage Groups
the restore of last full backup will roll forward the store to the latest state (recorded in the logs). Consistency check A backup of the Microsoft Exchange Server database is considered as successful only if the consistency check of the replicated datafiles succeeds. The consistency check is enabled by default.
Page 373: Selecting A Replicated Microsoft Exchange Server 2007 Storage Group
storage groups are backed up in the same way as original (production) storage groups. You can select any combination of storage groups for backup. However, you cannot select original and replicated storage group in the same backup specification. See Figure 109.
Page 374 • Before using XP VSS hardware provider in the resync mode, consider all applicable limitations of this mode. The limitations are listed in “HP StorageWorks Disk Array XP specifics” on page 362 and “Limitations” on page 398. Due to these limitations, it is recommended to rather use XP provider in VSS compliant mode, or EVA VSS provider, or VSS software provider.
Page 375: Microsoft Hyper-V Vss Writer Backup Specifics
Microsoft Hyper-V VSS writer backup specifics With the Hyper-V VSS writer, it is possible to back up: • The Hyper-V configuration • Virtual machines The following two types of backups are supported by the Data Protector VSS integration: • Online backup Online backup of Hyper-V writer data is possible using a software provider or hardware provider.
Page 376: Scheduling The Backup
• The guest operating system must have the Hyper-V VSS integration services installed and should not use dynamics disks. • The snapshot file (avhd file) needs to be configured on the same volume as the virtual disk file (vhd file). •...
Page 377 To schedule a Microsoft Volume Shadow Copy Writers backup specification, perform the following steps in the Data Protector GUI: In the HP Data Protector Manager, switch to the Backup context. In the Scoping Pane, expand Backup, then Backup Specifications. Click MS Volume Shadow Copy Writers.
Page 378: Running An Interactive Backup
Specify Recurring, Time options, Recurring options, and Session options. Note that the backup type for ZDB sessions that are to be used for instant recovery is set to Full. In the case of a ZDB-to-disk or a ZDB-to-disk+tape session, specify the Split mirror/snapshot backup option.
Page 379: Restoring Writers Data
In the HP Data Protector Manager, switch to the Backup context. In the Scoping Pane, expand Backup; then expand the Backup Specifications and the MS Volume Shadow Copy Writers items. Right-click the backup specification you want to run, and then select Start Backup from the pop-up menu.
Page 380: Restore Procedure
384. To restore Microsoft VSS objects using the Data Protector GUI, proceed as follows: In the HP Data Protector, switch to the Restore context. Expand Restore Objects, expand MS Volume Shadow Copy Writers, expand the client from which you want to restore the data, and then click MS Volume Shadow Copy Writers.
Page 381: Restore Objects
In the Results Area, select the writers or writers’ components (for component restore) or files or a group of files (for file restore mode). Figure 1 1 1 Restore objects You can select the top-level item (full writer restore) or only specific components. If you select a full writer restore, but some components of this writer were not backed up in the same session, the unavailable components are shaded and you cannot select them.
Page 382 a. Right-click a storage group, a store, or logs and click Restore as. b. In the MS Exchange additional options dialog box, select the target location for the components you want to restore: target server, target storage group, and target stores. The following options are available: •...
Page 383: 12 Restore To Different Location Options (Exchange Server 2007 Writer)
Figure 1 12 Restore to different location options (Exchange Server 2007 Writer) In the Options property page, select the MS Volume Shadow Copy specific restore options. Refer to “Restore options” on page 384. In the Devices and Media property pages, the devices and media for restore are automatically selected.
Page 384: Restore Options
Restore options The following restore options are specific to the Data Protector MS Volume Shadow Copy integration. NOTE: Do not use these options for Microsoft Exchange Server 2007 writer since there are other Exchange Server 2007 specific options provided for restore to another location. Restore to another client By default, the components or files are restored to the client from which the application data was backed up.
Page 385: 13 Msde Writer
Figure 1 13 MSDE writer When you expand the MSDE Writer item in the Results Area, all Microsoft SQL Server instances are displayed. Each instance contains all databases it includes. System databases (master, model, msdb and pub) are always listed there. IMPORTANT: If system databases are restored, the whole internal database structure will be changed.
Page 386: Microsoft Exchange Server Writer Restore Specifics
Microsoft Exchange Server writer restore specifics Microsoft Exchange Server Writer is used to restore Microsoft Exchange Server database files. When restoring from a Microsoft Exchange backup, the following two scenarios are possible: • One or more databases are corrupted, but the log files are not damaged. In this case the database is restored and transaction logs are applied.
Page 387: Point-In-Time Restore After Loss Of A Log File
In the Data Protector GUI, switch to the Restore context. Expand Restore Objects and MS Volume Shadow Copy Writers and select the client from which you want to restore the data. In the Results Area, expand Microsoft Exchange Writer and select the stores you want to recover.
Page 388: Microsoft Exchange Server 2007 Writer Restore Specifics
Switch to the Restore context. Expand Restore Objects and Microsoft Volume Shadow Copy Writers and select the client from which you want to restore the data. In the Results Area, expand Microsoft Exchange Writer and select the whole storage group. Do not select individual stores. Figure 1 15 Selecting Microsoft Exchange Server 2003 stores for point-in-time restore Proceed as with general VSS writer restore.
Page 389 The following restore scenarios are supported: • Restore of a storage group or individual stores to the original location. • Restore of LCR and CCR copies (storage groups or individual stores) to the location where the original database resides. • Restore of a storage group or individual stores and LCR and CCR copies (storage groups or individual stores) to a different location: •...
Page 390 You can restore different storage groups to original and different location in the same restore session if the target restore client system is the same for all storage groups involved. During restore to original location, all stores in the storage group are dismounted, even if only one store from the storage group will be restored.
Page 391: Microsoft Hyper-V Vss Writer Restore Specifics
380. Re-create the virtual machine cluster group using Failover Cluster Management. Instant recovery For general information and concepts on instant recovery, see the HP Data Protector zero downtime backup concepts guide and HP Data Protector zero downtime backup administrator's guide.
Page 392: Overview
Instant recovery restores data directly from a replica to source volumes. All data in the replica is restored (regardless of selections during backup). For instant recovery concepts, see the HP Data Protector zero downtime backup concepts guide. Instant recovery can be performed: •...
Page 393: Limitations
Alternately, you can use the omnidbvss command to list sessions. For information about omnidbvss, see the HP Data Protector command line interface reference. • Concurrent instant recovery sessions utilizing the same backup system or the same application system are not supported.
Page 394: Instant Recovery Using Hp Storageworks Eva Smis-S Agent
• By selecting the Restore using Microsoft Virtual Disk Service option, you can restore your data without using HP StorageWorks EVA SMIS-S Agent or HP StorageWorks XP Agent. Disadvantages • It is not possible to perform another instant recovery using the same replica.
Page 395 Retain source for forensics option in the Data Protector GUI. HP StorageWorks EVA considerations • If you restore using HP StorageWorks EVA, before instant recovery, it is recommended to check if the SMI-S CIMOMs were configured properly in the Data Protector cell by running the omnidbsmis -ompasswd -check [HostName] command.
Page 396: Instant Recovery Using Hp Storageworks Disk Array Xp Agent
Instant recovery using HP StorageWorks Disk Array XP Agent This type of instant recovery can be performed if backup was performed with the XP VSS hardware provider in the resync mode.
Page 397: Microsoft Exchange Server Writer Instant Recovery Specifics
• If you perform a backup in one mode and then the same backup in the other mode, restore of the backup performed in the VSS compliant mode (the "switch of disks" restore) will fail because the relationship between the S-VOL and its P-VOL will be detected from the other backup performed in the resync mode.
Page 398 or to a different location. For details, see “Microsoft Exchange Server 2007 writer restore specifics” on page 388. Note that restore to the original location will fail if not all objects residing on the target volume are selected for restore. Fore example, if you have four stores and transaction logs on the target volume, and you select only one store for restore, restore session will fail.
Page 399 supported. In this case, perform manual failover of Exchange Server before the restore. • Restore to a different location can be only performed using Microsoft Virtual Disk Service. Therefore, with XP VSS hardware provider, restore to a different location is possible only after the backup session was run in the VSS compliant mode.
Page 400: Instant Recovery Procedure
Instant recovery procedure Prerequisites • For Microsoft Exchange Server 2003, manually dismount the databases to be recovered. Procedure In the HP Data Protector Manager, switch to the Instant Recovery context. Integrating the Data Protector ZDB integrations and Microsoft Volume Shadow Copy Service...
Page 401: 16 Selecting Writers Components For Instant Recovery
In the Scoping Pane, expand MS Volume Shadow Copy Writers under Restore Objects, expand the backup specification from which you want to restore, and click the backup session from which you want to restore. Figure 1 16 Selecting writers components for instant recovery Zero downtime backup integration guide...
Page 402 In the Source property page, specify writers and/or components for recovery. Select the configuration check mode. For more information, see “Configuration check” on page 353. To perform additional steps after the instant recovery before recovering the database, select the No recovery option. Data Protector will not perform a database recovery and you can finish the recovery steps (such as applying transaction logs) later on manually.
Page 403 RSG when data is restored. Select the target server first and then from the Original drop-down list, select the stores to be restored. • Restore to a non-Exchange location and create RSG Select this option to restore your data to a non-Exchange location. After restore, Data Protector will create a Recovery Storage Group called DP RSG on the target server.
Page 404: 17 Restore To Different Location Options (Exchange Server 2007 Writer)
Figure 1 17 Restore to different location options (Exchange Server 2007 Writer) Integrating the Data Protector ZDB integrations and Microsoft Volume Shadow Copy Service...
Page 405 For both instant recovery types, to retain the source volume, select Retain source for forensics. When Restore using HP StorageWorks EVA is selected, aditional options are available. In case of Microsoft Exchange Server 2007 writer restore to a different location, these options are not available.
Page 406: 18 Selecting Instant Recovery Options (Eva Integration)
Figure 1 18 Selecting instant recovery options (EVA integration) Integrating the Data Protector ZDB integrations and Microsoft Volume Shadow Copy Service...
Page 407: 19 Selecting Instant Recovery Options (Xp Integration)
Figure 1 19 Selecting instant recovery options (XP integration) Click Restore. If you restored Microsoft Exchange Server data, manually re-mount the database stores. In case of restore to Recovery Storage Group, re-mount the database stores in this RSG. If you restored an LCR or CCR copy to the original database, perform additional steps: •...
Page 408: Troubleshooting
To perform an instant recovery in the cluster environment, use the above instant recovery procedure. Use virtual hostnames. For details on performing an instant recovery in cluster configurations, see the HP Data Protector zero downtime backup administrator's guide. Additional steps after restore of a Microsoft Exchange Server CCR database copy to the original...
Page 409: Before You Begin
Ensure that the latest official Data Protector patches are installed. See the online Help index: “patches” on how to verify this. • See the HP Data Protector product announcements, software notes, and references for general Data Protector limitations, as well as recognized issues and workarounds.
Page 410: Backup Problems
Actions Stop the Virtual Disk Service (VDS): • Check that Virtual Disk Service is started, stop it using the command net stop vds or via the Control Panel. • If the above step does not help, stop the Virtual Disk Service by terminating the process vds.exe using the Task Manager.
Page 411 Action Restart the Information Store. For more information, see the web page http://support.microsoft.com/kb/945424/ en-us. Problem Microsoft Exchange Server 2003 aborts the backup if the shadow copy creation takes over 20 seconds If an Exchange Server 2003 Writer is being backed up, the session can fail with VSSBAR reporting: Snapshot could not be created.
Page 412 The same applies to a Microsoft SQL Server database. Problem No HP StorageWorks SMI-S EVA provider login entries are configured within SMISDB Action Add the login information for HP StorageWorks SMI-S EVA provider by running:...
Page 413: Error Reported By Registry
Figure 120 Error reported by registry it means that the Windows registry is out of space. If there are too many entries in the Windows system registry, the registry runs out of space and consequently backup fails. Although Data Protector does not write anything to registry directly, the registry contains entries about all volumes and disks ever presented on the system recorded by the volume storage driver.
Page 414 Run the following command, where SessionID is the session whose target volume(s) could not be removed: omnidbvss -remove session SessionID -reference Upon successful removal, the command should display the confirmation message Removing references of session SessionID from VSSDB. Problem Backup of a Microsoft Exchange Server 2007 CCR database copy fails During a backup session of a database copy in a Microsoft Exchange Server CCR environment, Data Protector reports a major error notifying that the backup session has failed.
Page 415: Restore Problems
In the Data Protector GUI, while creating a backup specification, the Microsoft Exchange Writer(Exchange Replication Service) object is not displayed on the pane for selection of backup objects. This problem may occur in LCR environments, due to a Microsoft Exchange Server 2007 issue with incorrect display of database copy states in Exchange Management Console.
Page 416 Problem After restore, the system restart error is displayed In some cases, if the HBAs are changed on the application system, the software driver from previous HBAs can cause this error after restore. Action Remove older drivers of uninstalled HBAs from the application system. Problem After an SQLServer writer instant recovery is restarted, the database cannot be brought online...
Page 417: User Scenario For Microsoft Exchange Server 2003 Backup And Restore
Example - VSS transportable backup This example describes a backup scenario for Microsoft Exchange Server 2003 using VSS transportable backup together with HP StorageWorks EVA. The data is to be backed up on tape once a day for the storage group containing critical mailboxes and every second day for all other storage groups.
Page 418: Microsoft Exchange Server 2003 Storage Groups
Figure 121 Microsoft Exchange Server 2003 storage groups For the first storage group (Lists_Group), create the following backup specification: Select VSS transportable backup as the backup type. Select the application and backup system and specify Snapshot (Differential) as the replica type. Expand the Microsoft Exchange Server 2003 writer and select the first storage group (Lists_Group) for backup.
Page 419: Example Restore Scenario For Microsoft Exchange Server 2003
Using the Data Protector scheduler you need to schedule the backup specification to start a VSS transportable backup everyday. In the Recurring box, select Daily, set Recurring options to 1 day and set the backup protection to 4 days. Example restore scenario for Microsoft Exchange Server 2003 In this example the Microsoft Exchange Server 2003 is configured as in “Example - VSS transportable...
Page 420 Example 2. Example - restoring a complete storage group after loss of transaction logs In this example, the first store (Staff_Store) and transaction logs in the first storage group (Lists_Group) are damaged but the second store (Mailbox_Group) is intact. Since the transaction logs are damaged, a point-in-time restore of the whole storage group will be performed.
Page 421: A Appendix
A Appendix In this appendix This appendix gives information on the following topics: • “Reconfiguring an Oracle instance for instant recovery” on page 421 • “ZDB integrations omnirc variables” on page 425 Reconfiguring an Oracle instance for instant recovery If the control files or redo logs are located on the same volume group (if LVM is used) or source volume as the database files, the control files and online redo logs are overwritten during instant recovery.
Page 422 Move the log files to a different location using operating system tools. Start the database in mount mode: $ sqlplus SQL> connect user/password@service as sysdba; SQL> startup mount; Register the new locations for each moved file: SQL> alter database rename file 'OldPathName' to 'NewPathName';...
Page 423: Examples For Moving The Control Files And Redo Logs To Different Locations
Examples for moving the control files and redo logs to different locations Example - Moving Online Redo Logs In the following example for Oracle9i on HP-UX, the data files are on the same source volume as the control files and redo logs, which is /opt/oracle/product/9.2.0.
Page 424 Shut down the database: SQL> connect user/password@service as sysdba; SQL> shutdown SQL> exit Move the log files to a different location. $ mv /opt/oracle/product/9.2.0/oradata/redo* /oracle/logs Start the database in mount mode: $ sqlplus SQL> connect user/ password@service as sysdba; SQL> startup mount; Rename the new locations for each moved file: alter database rename file '/opt/oracle/product/9.2.0/oradata/redo01.log' to...
Page 425: Zdb Integrations Omnirc Variables
Data Protector ZDB integrations customizing. See the online Help index: “omnirc options” for information on how to use the omnirc file. For information on Data Protector ZDB agents omnirc file variables, see the HP Data Protector zero downtime backup administrator's guide.
Page 426 NOTE: This variable is not supported on EMC. The default value is 0. Possible values are 0 and 1. If an offline backup is performed using the Data Protector SAP R/3 integration, the variable is ignored and the integration behaves as if the variable was set to 1. Instant Recovery The instant recovery process depends on whether the control file and redo logs reside on the same disk array source volume as datafiles or not:...
Page 427 Prerequisites The prerequisites for this variable to be set to 1 are: • Data Protector Oracle Server integration: Oracle datafiles, Oracle control file, and Oracle online redo logs must be installed on a disk array. • Data Protector SAP R/3 integration: Oracle datafiles and Oracle control file must be installed on a disk array.
Page 428: Oracle Proxy-Copy Zdb And Restore Concepts When The Zdb_Ora_Include_Cf_Olf Variable Is Set To 1
Figure 122 Oracle proxy-copy ZDB and restore concepts when the ZDB_ORA_INCLUDE_CF_OLF variable is set to 1 Appendix...
Page 429: Oracle Backup Set Zdb And Restore Concept When The
Figure 123 Oracle backup set ZDB and restore concept when the ZDB_ORA_INCLUDE_CF_OLF variable is set to 1 Zero downtime backup integration guide...
Page 430: Sap R/3 Backup And Restore Concept When The
Figure 124 SAP R/3 backup and restore concept when the ZDB_ORA_INCLUDE_CF_OLF variable is set to 1 with online backup, or in case of offline backup ZDB_ORA_INCLUDE_SPF: Data Protector Oracle Server integration related variable. The default value is 0. Possible values are 0 and 1. The variable is ignored and the integration behaves as if the variable was set to 1 if offline backup is performed using the Data Protector SAP R/3 integration.
Page 431 ZDB_ORA_NO_CHECKCONF_IR: Data Protector Oracle Server integration related variable. The default value is 0. Possible values are 0 and 1. By default, the Oracle configuration is checked whether or not the control file, SPFILE, and online redo logs are on different volume groups than datafiles. To check the configuration, the CLI binary omniresolve is used internally.
Page 432 Appendix...
Page 433: 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 434 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 435 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 436 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 437 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 438 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 439 (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 440 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 441 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 442 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 443 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 444 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 445 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 446 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 447 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 448 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 449 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 450 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 451 (HP StorageWorks Disk Array XP specific term) HP StorageWorks Disk Array XP allows up to three mirror copies of a primary Zero downtime backup integration guide...
Page 452 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 453 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 454 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 455 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 456 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 457 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 458 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 459 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 460 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 461 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 462 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 463 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 464 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 465 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 466 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 467 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 468 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 469 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 470 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 471 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 472 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 473 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 474 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 475 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 476 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 477 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. Zero downtime backup integration guide...
Page 478 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 479 (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 480 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 481 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 482 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 483 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 484 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 485 (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 486 (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 487 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 488 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 489 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 490 Glossary...
Page 491: Index
Index backing up Oracle, 97 - 102 backup options, 91 advantages backup types, 32 Oracle integration, 31 backup set ZDB concepts, 39 - 44 integration, 333 backup set ZDB session flow, 42 - 44 architecture backup specifications, creating, 76 integration, 331, 336 proxy-copy ZDB concepts, 44 - 49 audience, 19...
Page 492 backing up VSS, 360 - 379 backup specifications, scheduling architecture, 331, 336 MS SQL Server integration, 265 backup flow, 333 backup templates backup specifications, creating, 362 SAP R/3 integration, 194 backup types, 332 backup types, 332 example, MS Exchange Server Oracle integration, 32 2003, 417...
Page 493 configuring database recovery checking, 353 Oracle integration, after instant Microsoft Exchange Server writer, recovery, 138 database recovery integration, 347 Oracle integration, options, 119 configuring MS SQL Server SAP R/3 integration, 221 checking configuration, 252 database recovery options configuring Disk Array XP with VSS, 351 SAP R/3 integration, 223...
Page 494 interactive backups Oracle integration, 100 help integration, 378 obtaining, 29 introduction MS Exchange Server integration, 285 technical support, 29 MS SQL Server integration, 243 Oracle integration, 31 SAP R/3 integration, 163 integration, 329 Informix backup backup specifications, creating, 193 instant recovery, 332 considerations, 395 limitations...
Page 495 MS Exchange Server backup offline backup, Hyper-V writer , 375 backup options, 292 omnirc variables, 425 - 431 MS Exchange Server configuration, 287 online backup, Hyper-V writer , 375 - 289 Oracle backup MS Exchange Server integration backup types, 32 concepts, 286 proxy-copy ZDB session flow, 47 -...
Page 496 227 preparing for instant recovery, 138 restoring SAP R/3 RAC, configuring Oracle Servers instant recovery, 221 HP-UX, 56 restoring VSS on other UNIX systems, 56 using GUI, 380 reconfiguring an Oracle instance for restoring MS Exchange Server...
Page 497 restoring Informix restore options, 273 SAP R/3 backup restoring MS Exchange Server backup templates, 194 instant recovery, 320 - 323 backup types, 191 point in time recovery, 309, 310 manual balancing, 214 roll forward recovery, 309, 314 SAP compliant ZDB, 211 restoring MS SQL Server scheduling backups, 206...
Page 498 191 - 209 - 214 100 - 102 configuration, 167 - 191 storage groups, 372 restore, 214 - 225 Subscriber's Choice, HP, 30 troubleshooting, 228 - 241 concepts, 164 - 167 SAP R/3 restore, 214 - 225 technical support database...
Page 499 338 flow, 333 using GUI, 380 VSS integration backup, 360 - 379 restore, 379 - 408 websites VSS restore HP Subscriber's Choice for Business, restore options, 384 troubleshooting, 408 - 417 , 30 backup, 360 - 379 product manuals, 19...
Page 500 writers specifics, VSS integration, 355 - Microsoft Exchange Server, 386 Microsoft Exchange Server 2007, Microsoft Hyper-V writer, 375, 391 MSDE, 384 XP agent instant recovery considerations, 397 ZDB session flow Oracle integration, proxy-copy, 47 - 49 ZDB flow SAP R/3 integration, 165 ZDB session flow Oracle integration, backup...

HP Data Protector A.06.11 Integration Manual

Publication History

About this Guide

Data Protector Oracle ZDB Integration

Data Protector SAP R/3 ZDB Integration

Data Protector Microsoft SQL Server ZDB Integration

Data Protector Microsoft Exchange Server ZDB Integration

Quick Links

Troubleshooting

Related Manuals for HP Data Protector A.06.11

Summary of Contents for HP Data Protector A.06.11