HP Application Recovery Manager software Integration guide Part number: N/A First edition: March 2008
Legal and notice information © Copyright 2008 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and 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.
Contents Publication history .............................................................. 13 About this guide ................................................................. 15 Intended audience ............................................................................................. 15 Documentation set ............................................................................................. 15 Guides ..............................................................................................
Prerequisites and limitations ................................................................................ Prerequisites ............................................................................................... Limitations .................................................................................................. Configuring the integration ................................................................................. Configuring HP StorageWorks Enterprise Virtual Array .................
Before you begin ........................................................................................ Checks and verifications .............................................................................. Common problems ...................................................................................... Backup problems ........................................................................................ Restore problems .............................................................................
Database recovery scenarios ............................................................... 129 Example of an RMAN recovery script .................................................... 131 Monitoring sessions ......................................................................................... 132 Monitoring current sessions ........................................................................ 133 Viewing previous sessions ..........................................................................
Modifying backup specifications ................................................................. Scheduling backup specifications ................................................................ Scheduling example ........................................................................... Starting backup sessions ............................................................................ Backup methods .................................................................................
Figures 1 Application Recovery Manager graphical user interface ....................... 20 2 Actors of the traditional backup model ............................................... 25 3 Actors of the Application Recovery Manager VSS integration backup model ............................................................................................ 26 4 Local VSS backup ............................................................................ 30 5 Transportable VSS backup .................................
21 Finding the Oracle user .................................................................... 96 22 Configuring Oracle - General (Windows) ........................................... 99 23 Configuring Oracle - General (UNIX) ................................................. 99 24 Configuring Oracle - Primary .......................................................... 100 25 Configuring Oracle - Options .......................................................... 101 26 XP backup options .....................
49 Scheduling backups ....................................................................... 173 50 SAP R/3 source options — EVA ...................................................... 178 51 SAP R/3 source options — XP ......................................................... 179 52 SAP R/3 recovery options .............................................................. 183 53 Oracle backup and restore concepts when the ZDB_ORA_INCLUDE_CF_OLF variable is set to 1 ..............................
Tables 1 Edition history ................................................................................. 13 2 Documentation map ......................................................................... 17 3 Document conventions ...................................................................... 18 4 VSS specific backup options .............................................................. 54 5 Oracle backup options ...................................................................
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 Part number Guide edition Product N/A March 2008 Application Recovery Manager Release A.06.
Publication history
About this guide This guide provides information about: • Integrating Oracle and Application Recovery Manager • Integrating SAP R/3 and Application Recovery Manager • Integrating application and Application Recovery Manager through the VSS interface Conceptual information can be found in the online Help. Intended audience This guide is intended for backup administrators who want to: • configure • back up • and restore database applications using Application Recovery Manager.
http://www.hp.com/support/manuals In the Storage section, click Storage Software and then select your product. • HP Application Recovery Manager software installation and licensing guide This guide describes how to install the Application Recovery Manager software, taking into account the operating system and architecture of your environment. This guide also gives details on how to upgrade Application Recovery Manager, as well as how to obtain the proper licenses for your environment.
Online help Application Recovery Manager provides context-sensitive (F1) Help and Help Topics for Windows and UNIX platforms. You can access the online help from the top-level directory on the installation CD without installing Application Recovery Manager: • Windows: Unzip AppRM_help.zip and open AppRM_help.chm. • UNIX: Unpack the zipped tar file AppRM_help.tar.gz, and access the online help system through AppRM_help.htm.
X Recommendations X Requirements X X X X X Support matrices X X X X X X X X X Supported configurations Troubleshooting X CLI reference Concepts guide X Integration guide Procedures/Tasks X Administrator's guide X Product announcements Planning strategy Installation guide X Getting started Online Help Limitations X X X X X Document conventions and symbols Table 3 Document conventions Convention Element Blue text: Table 3 on page 18 Cross-reference links and e-mail add
Convention Element text Emphasized monospace text CAUTION: Indicates that failure to follow directions could result in damage to equipment or data. IMPORTANT: Provides clarifying information or specific instructions. NOTE: Provides additional information. TIP: Provides helpful hints and shortcuts. Application Recovery Manager graphical user interface Application Recovery Manager provides a cross-platform (Windows and UNIX) graphical user interface.
Figure 1 Application Recovery Manager graphical user interface General Information General information about Application Recovery Manager can be found at http:// www.hp.com/go/apprm. HP technical support For worldwide technical support information, see the HP support website: http://www.hp.
• Detailed questions 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: • • • • • http://www.hp.com http://www.hp.com/go/software http://www.hp.com/service_locator http://www.hp.
About this guide
1 Integrating the Application Recovery Manager ZDB integrations and Microsoft Volume Shadow Copy Service Overview 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. The number of applications on the market is constantly increasing.
However, the production application as well as the backup application must conform to the VSS specification. Figure 2 on page 25 and Figure 3 on page 26 show the differences between the traditional backup model and the model with the Application Recovery Manager Microsoft Volume Shadow Copy integration.
Figure 2 Actors of the traditional backup model Integration guide 25
Figure 3 Actors of the Application Recovery Manager VSS integration backup model Without using the Volume Shadow Copy Service, Application Recovery Manager has to communicate with each application to be backed up individually. The Application Recovery Manager VSS integration introduces a unified backup and restore interface and provides the coordination among the participants of the backup and restore process.
makes ZDB and IR capabilities suitable for high-availability systems and mission-critical applications. Application Recovery Manager ZDB and IR techniques utilize snapshot technologies of disk-based arrays. The following are the basic principles behind ZDB and IR: • Create, at high speed, a copy of the data to be backed up and then perform backup operations on the copy, rather than on the original data.
Instant recovery considerations • The instant recovery functionality restores data from a replica on the backup system to the source volumes on the application system. Therefore, using instant recovery, it is only possible to selectively restore separate writer’s components if they reside on separate source volumes.
• coordinating restore session start • requesting the instant recovery Backup During the Application Recovery Manager VSS integration backup, Application Recovery Manager does not interact directly with each writer, but through the VSS interface. It uses the VSSBAR agent to coordinate the backup process. The consistency of data is a responsibility of the VSS writer and not dependent on Application Recovery Manager functionality. The backup process of the VSS writers consists of the following phases: 1.
Figure 4 Local VSS backup Figure 5 Transportable VSS backup 30 Integrating the Application Recovery Manager ZDB integrations and Microsoft Volume Shadow Copy Service
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 2003 writer. Backup with the EVA hardware provider There are three replica types available when backing up using the EVA hardware provider: • Standard snapshot • Vsnap • Snapclone However, in the GUI, you can select only between snapshot and snapclone.
Restore Restore from ZDB-to-disk sessions is performed using instant recovery. ZDB-to-disk session information is saved in the IDB, and the related array-specific information required for instant recovery is saved in the VSS database (VSSDB). IMPORTANT: During instant recovery, the whole replica is restored. This means not only are the originally selected backup objects restored, but the complete content of all the volume groups that contained them.
Restore With Microsoft Exchange Server 2007 writer you can restore your data not only to the original location (from where the backup was performed) but also to a different location. You can restore: • A whole storage group (including LCR or CCR copies) • A single store (including LCR or CCR copies) You can restore them to: • Original storage group • Different storage group • Non-Exchange location. After restore is completed, Recovery Storage Group (RSG) can be created automatically.
• HP Application Recovery Manager software installation and licensing guide on how to install Application Recovery Manager on various architectures and how to install the Application Recovery Manager Microsoft Volume Shadow Copy Service integration and ZDB agents. • Writers and shadow copy providers documentation for instructions on how to install and configure writers and providers on your system.
• When Enterprise Virtual Array (EVA) VSS hardware provider is used, and the disks array of the application system and the disk array of the backup system are not controlled by the same Command View. • When the Disk Array XP VSS hardware provider is used in the resync mode, no matter if one or two disk arrays are used. In the above situations, there is only one instant recovery scenario that is supported. For a successful instant recovery, follow the steps: 1.
completed when the waiting period expires, Application Recovery Manager aborts the backup session. You can increase the waiting period duration by setting the OB2VSS_WAIT_TIMEOUT omnirc variable. The variable value determines the period (in seconds) for which Application Recovery Manager agent waits for mirrors, which are created in one session, to become fully synchronized.
or RAID Manager XP for this purpose. Do not delete references from the ZDB database before you make sure that all LUNs that had been created in that backup session have been deleted from the array. • If the Disk Array XP VSS hardware provider is in the resync mode, and the backup system is configured as the virtual server in a quorum cluster, you must create a host group on the disk array that contains host bus adapter (HBA) World Wide Names (WWNs) from all physical systems in your cluster.
• Do not manually mount target volumes that have been created by Application Recovery Manager. Configuring HP StorageWorks Enterprise Virtual Array This section describes how to configure the Application Recovery Manager HP StorageWorks Enterprise Virtual Array (EVA) integration for use with the VSS integration. Prerequisites • Install HP storage components and licenses: • HP StorageWorks Virtual Controller Software (VCS or XCS) and Command View (CV) EVA.
Configuring the Integration Before you start configuration, make sure you met the prerequisites described in “Prerequisites” on page 40. Then set the login information for SMIS-S EVA provider running on a management system. To set, delete, list, or check the login information, use the omnidbsmis —ompasswd CLI command. For command syntax and examples, see the HP Application Recovery Manager software command line interface reference.
Configuring HP StorageWorks Disk Array XP This section describes how to configure the Application Recovery Manager HP StorageWorks Disk Array XP integration for use with the VSS integration. Prerequisites • Install Disk Array XP components and licenses: • RAID Manager library on the application and backup systems. See the RAID Manager library documentation for installation instructions. RAID Manager Library is firmware-dependant.
• Maximum three replicas (S-VOLs) can be created for a source volume (P-VOL) if the XP provider is in the resync mode. For supported backup and connectivity topologies, see HP Application Recovery Manager software administrator's guide. For general Application Recovery Manager and integration-specific limitations, see HP Application Recovery Manager software product announcements, software notes, and references.
Configuring the VSS Hardware Provider for Disk Array XP Before you run backups, open the HP StorageWorks XP VSS Hardware Provider Configuration Utility and choose the configuration mode for your backups: VSS Compliant Mode or Resync Mode. NOTE: Changing the modes between backup sessions can impact the restore. For details, see “HP StorageWorks Disk Array XP considerations” on page 63.
• The VSS/VDS hardware provider is configured for the same Command View on both EVAs due to the hardware provider limitation, which can detect only one EVA disk array. Otherwise, the presentation of replicas to the backup system fails and consequently the backup session fails. Also in case where the application and backup systems are the same, ensure that the VSS/VDS hardware provider is configured for the same Command View on both EVAs.
Configuration check modes You can select between three configuration check modes: • Strict If any file or folder on the volume does not belong to the component, the backup or instant recovery fails. • Non-strict If any folder on the volume does not belong to the component, the backup 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.
Configuration steps 1. Configure disk arrays needed for the backup. 2. Create an Application Recovery Manager VSS backup specification specifying the VSS components to back up, as well as the Application Recovery Manager backup options that define the behavior of your backup or restore session. The Microsoft SQL Server or Microsoft Exchange Server has to be running on the application system for a backup to start.
A range of snapshot techniques is available, each with its own particular merits from the storage and data processing points of view. Application Recovery Manager supports the following snapshot replica types using the EVA hardware provider: • Snapshot with pre-allocation of disk space (standard snapshot). • Snapshot without pre-allocation of disk space (vsnap or Virtually Capacity-Free Snapshot).
backup specification, note that the Number of replicas rotated should not be more than three in all backup specifications together. • You can change the XP hardware provider mode between different backup sessions using the same backup specification, but this is not recommended when you use replica rotation, because restore of such a backup can fail. For details, see “HP StorageWorks Disk Array XP considerations” on page 63.
4. In the Create New Backup dialog box, select the backup type. You can choose between the following types: • Local backup This type is used for single host VSS backup. • VSS transportable backup Use this option to create a shadow copy or replica on the application system and present it to the backup system.
5. 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 SqlServerWriter, or Exchange Server in the CCR environment), specify the virtual server name given in the particular writer resource group as the application system. • For transportable backup, the name of the backup system. • To enable restore using Application Recovery Manager, leave Track the replica for instant recovery selected.
created: by default, standard snapshot (disk space is pre-allocated). This replica type is not supported by XP provider. A provider may support one or both types. If you select an unsupported replica type, the backup will fail. For more information on EVA provider replica types, see “Snapshot replica” on page 45. Optionally, specify the configuration, mount, and replica management options: • Select Keep the replica after the backup to keep the replica on a disk array after backup.
Figure 7 VSS transportable backup options Integration guide 51
6. Select the backup objects you want to back up. Figure 8 Selecting backup objects (Exchange Server 2007 LCR copy and SQL writer) NOTE: Do not select too many objects because they might reside on more than four source volumes. If the objects reside on more than four source volumes, create several backup specifications where objects do not reside on more than four source volumes. If a writer requires all of its components to be backed up, lower-level items are automatically selected.
c:\mnt\1). To select a mounted disk, select the mountpoint. A hardware provider is required for this backup object. Microsoft Exchange Writer: Optionally, to specify options for the consistency check of Microsoft Exchange Server Writer, right-click Microsoft Exchange Writer and click Additional options. Microsoft Exchange Server 2007 Writer in a CCR environment: Optionally, to specify cluster options, right-click Microsoft Exchange Writer and click Additional options.
10. You can run backup using one of the following methods: • Schedule the backup of an existing Microsoft Volume Shadow Copy Writers backup specification using the Application Recovery Manager Scheduler. • Start an interactive backup of an existing Microsoft Volume Shadow Copy Writers backup specification. VSS specific backup options Table 4 VSS specific backup options Option Description Pre-exec Specify a command that will be started by vssbar.exe on the application system before the backup.
backup session backing up a specific storage group can be running on the same application system at once. Consequently, if you start a backup while another one is in progress, the latter waits until the first one finishes. Recommendations • With EVA provider, an Exchange storage group should not reside on more than four source volumes. • Configuration with transaction logs residing on different source volume than stores enables you to perform a rollforward recovery when only the stores are lost.
Figure 10 Selecting Microsoft Exchange Server 2003 storage groups Microsoft Exchange Server 2007 writer backup specifics In an LCR or CCR environment, the replicated storage groups are represented as a new instance of Exchange writer, Exchange Replication Service. The replicated storage groups are backed up in the same way as original production storage groups. You can select any of these storage groups (original or replicated) for a backup. However, you cannot select both in the same backup specification.
Figure 11 Selecting a replicated Microsoft Exchange Server 2007 storage group In a CCR environment, you can select a cluster node from where you want your backup to be performed, regardless of which instance (Information Store or Replication Service) resides on this node.
• Vssbar.exe could not be started on the selected node. To avoid the session failure, you can select the option Revert to active node on failure in the same dialog box. The backup will be restarted on the original server (active cluster node) and the original storage group will be backed up. If Information Store instance is backed up, this option is ignored.
5. Specify Recurring, Time options, Recurring options, and Session options. Figure 12 Scheduling a backup 6. Click OK to return to the Schedule property page. 7. Click Apply to save the changes. Running an interactive backup An interactive backup can be started using the Application Recovery Manager GUI by following these steps: 1. In the HP Application Recovery Manager software GUI, switch to the Backup context. 2.
Restore You can restore the Application Recovery Manager Microsoft Volume Shadow Copy Service integration backup objects using the Application Recovery Manager GUI. 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 Application Recovery Manager software concepts guide.
• If you select the Restore using Microsoft Virtual Disk Service option, you can restore your data without using HP StorageWorks EVA SMI-S Agent. Disadvantages • It is not possible to perform another restore from the same backup. • With the EVA intergration, this method of instant recovery changes the physical location of the application production data. After instant recovery, a replica becomes the source volume, therefore, the physical location of the original storage changes.
Copy of replica data with the source volume not retained With this method, the source volume is directly overwritten by the replica. The old source volume is not retained and if the restore session fails, the original application data residing on the source volumes is lost. You can select to retain the replica and thus enable to perform another restore from this backup. Advantages • Disk group of the source volume is not changed after instant recovery.
IMPORTANT: After instant recovery, restored filesystems are mounted to the same mount points or drive letters as they were at the backup time. If these mount points or drive letters have other filesystems mounted, these filesystems are automatically dismounted before instant recovery, and the restored filesystems are mounted afterwards. Restore Using HP StorageWorks Disk Array XP This type of restore can be performed if a backup was created with the XP provider in the resync mode.
P-VOL will be detected from the other backup performed in the resync mode. This pair relationship should not be removed during restore and thus a switch of the source volume with the replica cannot be performed. To restore such a backup, perform one of the following prior to restore: • Manually remove the S-VOLs that were created during backups made in resync mode using the omnidbvss command.
Microsoft Exchange Server writer recovery specifics This section provides specific information on the instant recovery point-in-time, and rollforward restore of the Microsoft Exchange Server Writer. With Microsoft Exchange Server 2003, you can restore a whole storage group or individual stores only to the original location. With Microsoft Exchange Server 2007 Writer, you can restore a whole storage group or individual stores to the original and to a different location.
Microsoft Exchange Server 2007 recovery specifics Exchange Server 2007 offers additional restore option: • Restore to a different location than the location from where the backup was made (original location). The following restore scenarios are supported: • Restore of a whole storage group or individual stores to the original location. • Restore of LCR and CCR copies (their storage groups or individual stores) to the original database.
You can restore two storage groups to both original and a different location in the same restore session if the target restore client system is the same. During restore to original location, all stores in the storage group to be restored are dismounted even if only one store from the storage group will be restored. Stores are left dismounted after the restore.
• All stores in a RSG must originate from the same storage group due to the Microsoft Exchange Server limitations. • If you have a CCR environment where the original database resides on a different EVA disk array than the database copy and you perform backup of the database copy, note that the restore of this copy to original database will fail, because restore to a different disk array is not supported. In this case, perform manual failover of the databases before the restore.
For Exchange Server 2007 writer specifics (prerequisites and limitations), see “Microsoft Exchange Server 2007 recovery specifics” on page 66. Limitations • The number of replicas available for instant recovery is limited by Number of replicas rotated, which sets the size of the replica set. You can view these replicas in the Instant Recovery GUI context by expanding Restore Sessions. Replicas are identified by the backup specification name and the session ID.
2. In the Scoping Pane, expand MS Volume Shadow Copy Writers under Restore Objects, expand the writer you want to restore and click the backup session from which you want to perform the restore.
Figure 14 Selecting Exchange Server 2007 writers components for instant recovery to a different location Integration guide 71
3. 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 43. To perform additional steps after the instant recovery before recovering the database, such as restoring logs backed up using third–party backup software, select the No recovery option.
Select this option to restore your data to a non-Exchange location. This means that the restored data will not be managed by Exchange Server and Recovery Storage Group (RSG) will not be created. You can create 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.
Figure 15 Restore to different location options (Exchange Server 2007 Writer) 74 Integrating the Application Recovery Manager ZDB integrations and Microsoft Volume Shadow Copy Service
4. Optionally, select the VDS or disk array options under the Options tab. For both types of restore, to retain the source volume, select Retain source for forensics. For a Restore using HP StorageWorks EVA, additional options are available: • The restore method: Copy replica data to the source volume or Switch the replica. If you select Copy replica data to the source volume, a full copy of the replica is created in the source storage (the copy is then switched with the source volume).
Figure 16 Selecting instant recovery options (EVA integration) 76 Integrating the Application Recovery Manager ZDB integrations and Microsoft Volume Shadow Copy Service
Figure 17 Selecting instant recovery options (XP integration) 5. Click Restore. 6. If you restored Microsoft Exchange Server writers data, manually re-mount the database stores. If you restored the data to AppRM RSG, manually re-mount the stores in the RSG. 7. If you restored an LCR or CCR copy to the original database, perform additional steps: • In case of an LCR restore, it is recommended to seed the restored database to synchronize the restored original database with its copy.
recovery in cluster configurations, see the HP Application Recovery Manager software administrator's guide. Additional steps after restore of a CCR copy to the original database In a CCR environment, after an instant recovery of a CCR copy to the original database residing on the application system, perform the following steps to enable normal operation of the original and copy databases: CAUTION: Do not move the clustered mailbox server without first performing the following steps.
• See the HP Application Recovery Manager software product announcements, software notes, and references for general Application Recovery Manager limitations, as well as recognized issues and workarounds. • See http://www.hp.com/support/manuals for an up-to-date list of supported versions, platforms, and other information. Checks and verifications • On the application and backup systems, examine system errors reported in: HP-UX: /var/opt/omni/log/debug.log Windows: AppRM_home\log\debug.
Actions 1. 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. VDS will be started automatically as needed. • Alternatively, you could also log in to the system again and check if the system requests your confirmation to stop a crashed VDS.
The reason may be the failure of the previous backup and, due to a Microsoft Exchange Server 2003 issue, the Exchange Server Writer could not perform a proper cleanup. 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 there are too many source volumes selected for backup (more than four) it may happen that the creation of snapshots takes too long and VSS fails the snapshots creation process. Action Do not select too many objects in a backup specification because they might reside on more than four source volumes. This means that for example a Microsoft Exchange Server storage group should not reside on more than four source volumes and only one storage group should be specified for backup in this case.
• By Windows operating system: Figure 18 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 Application Recovery Manager 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. Action The registry should be cleaned up.
as the backup system) is a virtual server. In this case, after a failover, replicas on the other (failed-over) system cannot be properly removed from the database. Action To remove the false entry from the VSSDB: 1. In the error messages, find the ID of the session which could not remove the target volume. 2. Run: omnidbvss -remove session SessionID -reference where SessionID is the session whose target volume(s) could not be removed. 3.
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.
Integrating the Application Recovery Manager ZDB integrations and Microsoft Volume Shadow Copy Service
2 Application Recovery Manager Oracle integration Introduction You can employ a variety of backup strategies to best meet your system priorities. If database availability is the highest priority, for instance, your backup strategy should include online backups that are performed frequently to minimize recovery time. This strategy limits downtime, but uses system resources more intensively.
The online backup concept is widely used since it enables high application availability. Offline backup requires shutting down the database while creating a replica, and therefore does not offer high availability. Backup and restore types Backup Using Application Recovery Manager, you can perform the following types of backup: • Online ZDB During the creation of a replica, the database on the application system is in hot backup mode.
Depending on the location of the Oracle control file, online redo log files, and SPFILE, the following two options are possible: • 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. • Oracle control file, online redo log files, and SPFILE reside on the same volume group (if LVM is used) or source volume as Oracle datafiles.
Figure 19 Oracle integration concept 90 SM The session manager controls backup and restore sessions and writes the session information to the IDB. Disk Array Agent The disk array Agents (ZDB Agents) are SSEA (on XP), and SMISA (on EVA).
Backup process Figure 20 Oracle integration backup flow See the HP Application Recovery Manager software administrator's guide for a general description of the ZDB session flow and for an explanation of actions triggered by ZDB options. This section provides only the information relevant to the Application Recovery Manager Oracle integration.
Operations on a replica (mounting, activating volume/disk groups...) described below are dependent on or triggered by ZDB options. See the HP Application Recovery Manager software administrator's guide for more information on these options. • Backup Session Manager reads an Oracle backup specification and the backup is started on the application system. • In the case of online backup, the database is switched to the backup mode. In the case of an offline backup session, the database is shut down.
NOTE: A replica of the archive logs is not created; therefore, the archive logs should be backed up from the application system, using third–party backup software. The backup is not performed using RMAN and is not registered within Oracle. Configuring the integration Prerequisites • It is assumed that you are familiar with the Oracle database administration and the basic Application Recovery Manager functionality. • You need a license to use the Application Recovery Manager Oracle integration.
• The Oracle Server software must be installed on the application system and the Oracle target database must be open or mounted there. • Oracle net services must be properly configured and running (on the application system) for the Oracle target database. The net services are needed for the Application Recovery Manager Oracle agent to be connected to the Oracle database on the application system through Oracle.
SQL> connect system/manager@PROD as sysdba; Connected. • For online backup only, enable the Oracle automatic log archiving: 1. Shut down the Oracle target database instance on the application system. 2. Back up the entire database using a filesystem backup. 3. 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.
5. Back up the entire database. Cluster-aware clients In cluster environment, if you intend to use the Application Recovery Manager CLI, set the Application Recovery Manager environment variable OB2BARHOSTNAME to the virtual server name.
to the corresponding Application Recovery Manager user group (admin or operator) and must also become the owner of the backup specification to be able to back up the Oracle database using Application Recovery Manager. IMPORTANT: Additionally, the user root on the Oracle Server has to be added to the Application Recovery Manager admin or operator user group for both, the application and backup system.
Using the Application Recovery Manager GUI Configure an Oracle database when you create first backup specification for the database.
1. In the Configure Oracle dialog box and in the General page, specify the pathname of the Oracle Server home directory.
2. In the Primary page, specify the login information to the primary database. Note that the user must have the SYSDBA privilege granted. In Services, type the net service name for the primary database instance. The backup will be performed on the system where this database instance resides. RAC: List all net services names for the primary database separated by a comma.
3. In the Options page, you can specify a location for a copy of your current control file. If you want that the current control file is backed up, specify a location on a source volume. The copy to that location will be made before a backup and the source volume on which the copy will exist will be added to the list of the source volumes to be replicated during the backup. Figure 25 Configuring Oracle - Options Click OK. The Oracle database is configured.
2. On the Oracle Server system, from the directory: Windows: AppRM_home\bin UNIX: /opt/omni/lbin run: Windows: perl -I..\lib\perl util_oracle8.pl -config -dbname DB_NAME -orahome ORACLE_HOME PRIMARY_DB_LOGIN [-ctlcp_location BACKUP_CONTROL_FILE_COPY_LOCATION] [-client CLIENT_NAME] UNIX: util_oracle8.
RAC: Each net service name must resolve into a specific database instance. BACKUP_CONTROL_FILE_COPY_LOCATION A location on a source volume where a copy of the current control file is made before a backup. The source volume on which the copy will exist will be added to the list of the source volumes to be replicated during the backup. This is optional. Example The following example represents configuration on UNIX of an Oracle database with the control file copy location specified.
Checking the configuration You can check the configuration of an Oracle database after you have created at least one backup specification for the database. If you use the Application Recovery Manager CLI, a backup specification is not needed. Using the Application Recovery Manager GUI 1. In the Context List, select Backup. 2. In the Scoping Pane, expand Backup Specifications and then Oracle Server. Click the backup specification to display the server with the database to be checked. 3.
Handling errors If an error occurs, the error number is displayed in the form *RETVAL*error_number. To get the error description: Windows: On the Cell Manager:AppRM_home\bin\omnigetmsg 12 error_number UNIX: Run: /opt/omni/lbin/omnigetmsg 12 error_number IMPORTANT: On UNIX, it is possible that although you receive a *RETVAL*0, the backup still fails.
Or: • Set the ZDB_ORA_INCLUDE_CF_OLF, ZDB_ORA_INCLUDE_SPF, and ZDB_ORA_NO_CHECKCONF_IR omnirc variables and ignore the warning. However, note that the control file, SPFILE, and online redo logs are overwritten during instant recovery. See “ZDB integrations omnirc variables” on page 197 on how to set the omnirc variables. Backup Creating backup templates You can create backup templates to apply the same scheduling options to a number of backup specifications.
You cannot perform a backup of the archived redo log files. For that, use third–party backup software. Procedure To create an Oracle backup specification: 1. In the Context List, click Backup. 2. In the Scoping Pane, expand Backup Specifications, right-click Oracle Server, and click Add Backup. 3. In the Create New Backup dialog box, select Blank Backup or some other template which you might created. In Backup type, select: XP: Split mirror backup EVA: Snapshot backup Click OK.
4. In the Application system drop-down list, select the Application Recovery Manager Oracle integration client. In a non-RAC cluster environment, select the virtual server. RAC: Select either the node or the virtual server of the Oracle resource group. In the Backup system drop-down list, select the backup system. Select other disk array specific backup options (see Figure 26 on page 108 for XP or Figure 27 on page 109 for EVA backup options). For detailed information on the options, press F1.
Figure 27 EVA backup options Click Next.
5. Specify the application that you want to back up. 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; RAC: Note that the database name is the same for all instances.
Figure 29 Specifying an Oracle Server system (UNIX) Click Next. 6. If the Oracle database is not configured yet for use with Application Recovery Manager, the Configure Oracle dialog box is displayed. Configure the Oracle database for use with Application Recovery Manager as described in “Configuring Oracle databases” on page 97.
7. In this page, the backup objects are selected. Note that only the whole database can be backed up. Figure 30 Selecting backup objects Click Next.
8. Set the backup options. Offline backup: To perform an offline backup, in the Application Specific Options dialog box, select the Backup offline option. This option stops the database before creating a replica, and restarts it after the replica is created. Figure 31 Backup offline option TIP: In the Post-exec option, you can specify the script that can be run after the backup session on the application system.
Click Next. 9. Optionally, schedule the backup. For more details, see “Scheduling backup specifications” on page 117. Click Next. 10. Save the backup specification. It is recommended that you save all Oracle backup specifications in the Oracle group. IMPORTANT: The word DEFAULT is a reserved word and therefore must not be used for backup specification names or labels of any kind.
For example, you can provide scripts to shut down and start an Oracle instance or you can provide a post-exec script that will back up the archive logs and control file to tape using an RMAN backup script or third–party backup software. For examples of shut-downing and starting an Oracle instance on UNIX, see “Examples of pre-exec and post-exec scripts on UNIX” on page 115. Provide the pathname of the command or RMAN script. Backup offline Select this option to perform an offline backup session.
startup EOF echo "Oracle database \"$DB_NAME\" started." exit 0 else echo "Cannot find Oracle SQLPLUS ($ORACLE_HOME/bin/sqlplus)." exit 1 fi Backing up with third–party backup software The Application Recovery Manager Oracle backup can be integrated with third–party backup software to move the Oracle replicated datafiles from EVA or XP disk array to tape. The copying of replica is performed on the backup system, so there is no load on the application system during backup to tape.
same source volume on the application system has finished the backup or instant recovery; otherwise, the session will fail. • On XP, if the LVM mirroring configuration is used, Application Recovery Manager displays a warning during a backup because the volume group source volumes on the application system do not have their BC pairs assigned. This message should be ignored.
5. Specify Recurring, Time options, and Recurring options. For details press F1. Figure 33 Scheduling backups Click OK and then Apply to save the changes. Running an interactive backup An interactive backup can be performed any time after a backup specification has been created and saved. You can use the Application Recovery Manager GUI or CLI. Starting a backup using the GUI To start an interactive of an Oracle database using the Application Recovery Manager GUI, proceed as follows: 1.
where Name is the name of the backup specification. For more information on the omnib command, see its man page or the HP Application Recovery Manager software command line interface reference. Restore Using Application Recovery Manager GUI or CLI, you can restore whole database and select to recover the database to a certain point in time. You can select to recover the database using existing archive logs, which must be provided, or you can provide your own script for database recovery.
recent one from a backup performed by third–party backup software, or recreate it. • The archive logs to the selected point in time must be available for the database recovery. Limitations • The restore of control file and archive logs is not supported by Application Recovery Manager. • The recovery process will fail if the log entry with the specified logseq number or SCN number was created before the target volume.
Figure 34 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.
ZDB_IR_VGCHANGE=vgchange -a s 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: 1. Make sure that the MC/SG virtual package is running on the target node. 2.
5. 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 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. Set other HP StorageWorks Enterprise Virtual Array or HP StorageWorks Disk Array XP options. For details, press F1.
Figure 37 Selecting a backup session for restore and selecting Disk Array XP options 124 Application Recovery Manager Oracle integration
6. To perform not only instant recovery, but also recovery of a database, click the Options tab, select Recovery, and then the database recovery options. For a recovery until a selected time, logseq/thread number, or SCN number, it is recommended to reset the log files. You can reset the logs if you select Open database after recovery. See “Recovery options” on page 127 or press F1 for details on available options. Figure 38 Oracle recovery options 7. Click Restore or Preview.
Windows: AppRM_home\bin run: omnir -oracle –host ClientName -session SessionID {DISK_ARRAY_XP_OPTIONS | ENTERPRISE_VIRTUAL_ARRAY_OPTIONS} [–recover {disk | prog program_name} {now | time MM/DD/YY hh:mm:ss | logseq LogSeqNum thread ThreadNumber | SCN Number} -appname DB_name —parallelism Number [-open [-resetlogs]] [–user UserName -group GroupName]] [-preview] [GENERAL_OPTIONS] where: DISK_ARRAY_XP_OPTIONS are: [-keep_version] [—check_config] ENTERPRISE_VIRTUAL_ARRAY_OPTIONS are: {—copyback [wait_clonecopy m
Recovery options Recovery Use this option to perform recovery of the database after restore. During recovery, the archived logs are applied. Note that the logs must be available to the database to be recovered. You can select which logs to apply according to a SCN number, logseq, or you can apply all available logs. You can also specify a desired time and Oracle will apply the appropriate logs.
When you select the Use script/program option, the other recovery options selected in the GUI are written to the file recoverDB_NAME in the AppRM_home temporary directory. The file has the following format: parallelism = number until = now|specified_until open = 0|1 resetlogs = 0|1 In this way, you can parse the options selected in the GUI with your script or program. Parallelism Select this option to specify the number of concurrent data streams that are used during database recovery.
• After a complete database recovery (Recover until now) when the current control file was used in database recovery. If you reset the logs when the Recover until option is set to Now, a warning is displayed, stating that you should reset the logs only if you use an older control file for restore. NOTE: Oracle recommends that you perform a complete backup immediately after a database was opened with the Reset Logs option.
Scenario 1 Datafiles need to be restored. An instant recovery session for the datafiles is available. The control file and archive logs do not need to be restored. Perform: 1. Select the session to be restored in the Instant Recovery context of the Application Recovery Manager GUI. 2. In the Options page, select the options Use existing archive logs and Recover until Now. 3. Start Restore. Scenario 2 Datafiles need to be restored. A third-party backup of the datafiles is available.
Scenario 4 Datafiles and old archive logs need to be restored. An instant recovery session for the datafiles is available, as well as a third-party RMAN backup of the archive logs. The control file does not need to be restored. Perform: 1. Create the RMAN recovery script for the restore of the backed up archive logs. 2. Select the session to be restored in the Instant Recovery context of the Application Recovery Manager GUI. 3. Start Restore without specifying any recovery option. 4.
If the archive logs were backed up as files, the files can be restored before the Application Recovery Manager restore with recovery is run. You can then select recovery with the Use existing archive logs option in the GUI. You can restore all archive log files, or you can check which logs are required to recover to a certain point in time.
Monitoring current sessions To monitor a currently running session using the Application Recovery Manager GUI: 1. In the Context List, click Monitor. In the Results Area, all currently running sessions are listed. 2. Double-click the session you want to monitor. Clearing sessions To remove all completed or aborted sessions from the Results Area of the Monitor context: 1. In the Scoping Pane, click Current Sessions. 2. In the Actions menu, select Clear Sessions.
Troubleshooting This section contains a list of general checks and verifications and a list of problems you might encounter when using the Application Recovery Manager Oracle integration. You can start at “Problems” on page 136 and if you cannot find a solution there, perform general checks and verifications. For general Application Recovery Manager troubleshooting information, see the online Help index: “troubleshooting” and HP Application Recovery Manager software administrator's guide.
1. UNIX: Export the ORACLE_HOME and DB_NAME variables as follows: • if you are using an sh - like shell, enter the following commands: ORACLE_HOME="ORACLE_HOME" export ORACLE_HOME DB_NAME="DB_NAME" export DB_NAME • if you are using a csh - like shell, enter the following commands: setenv ORACLE_HOME "ORACLE_HOME" setenv DB_NAME "DB_NAME" Windows: Set the ORACLE_HOME and DB_NAME variables. 2. Start SQL*Plus from the bin directory in the ORACLE_HOME directory: sqlplus /nolog 3.
• Verify that the Application Recovery Manager software has been installed properly. See the HP Application Recovery Manager software installation and licensing guide for details. • Check if the SYSDBA privilege is granted to the Oracle administrator. • If you have special Oracle environment settings, ensure that they are entered in the Application Recovery Manager Oracle configuration files on the Cell Manager.
Action Try to configure the application system in such a way that it consumes as little resources as possible. This error can be reproduced without using Application Recovery Manager by starting SQL*Plus on the application system, and connecting to the target database on the application system.
Application Recovery Manager Oracle integration
3 Application Recovery Manager SAP R/3 integration Introduction This chapter explains how to configure and use the Application Recovery Manager SAP R/3 integration (SAP R/3 integration).
Supported array Supported configurations HP StorageWorks Enterprise Virtual Array (EVA) BC This chapter provides information specific to the Application Recovery Manager SAP R/3 integration. For general Application Recovery Manager 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 Application Recovery Manager software concepts guide.
Figure 39 SAP R/3 integration architecture The SAP BRBACKUP utility can be shared on the application system and only started from the backup system (recommended configuration by SAP) or directly installed on the backup system. ZDB flow For details on how ZDB options affect the ZDB flow, including mounting, activating volume/disk groups and so on, see the HP Application Recovery Manager software administrator's guide.
Figure 40 SAP R/3 ZDB session flow 1. The SAP R/3 backup specification is read and the Application Recovery Manager omnisap.exe program is started on the backup system. 2. 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 (splitint) on the backup system, with the list of files to be included in the replica creation.
4. The remaining ZDB options are processed and the details on the session are written to the ZDB database. The session then finishes. 5. The backup system is disabled (filesystems are unmounted on all platforms and volume/disk groups deactivated on UNIX). 6. XP only: Links are re-established, depending on how ZDB options are specified.
IMPORTANT: To avoid problems with your backups, take extra care to ensure the syntax and punctuation of your configuration file match the examples.
OSGROUP='dba'; TMP_DIR='/var/opt/omni/tmp'; CF_OLF='/sap/admin/dbfs/control01.dbf;/sap/admin/dbfs/control02.
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: • When it is used with the -getconf[ig] option, it specifies the filename for the output of the command to be written to.
This message is displayed when either an option with the specified name does not exist in the configuration, or the file specified as the -local parameter does not exist. • Configuration read/write operation failed. This message is displayed if any fatal errors occurred, for example: the Cell Manager is unavailable, the Application Recovery Manager SAP R/3 configuration file is missing on the Cell Manager, etc.
• On HP-UX: /opt/omni/lbin/util_cmd -getopt SAP ICE OB2OPTS \ -sublist Environment Listing parameters To list all the Application Recovery Manager SAP R/3 configuration file parameters for the Oracle instance ICE, use the following command on the Application Recovery Manager SAP R/3 client: • On Windows: AppRM_home\bin\util_cmd -getconf SAP ICE • On HP-UX: /opt/omni/lbin/util_cmd -getconf SAP ICE Deleting parameters To remove the value of the OB2OPTS parameter for the Oracle instance ICE, use the following
8. Configure the SAP R/3 parameter file. See “Configuring the SAP R/3 parameter file” on page 165. Prerequisites • Ensure that you have correctly installed and configured the SAP R/3 application. The database used by the SAP R/3 application must be an Oracle database. • For supported versions, platforms, and other information, see the HP Application Recovery Manager software product announcements, software notes, and references or http://www.hp.com/support/manuals.
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, Application Recovery Manager creates a link to the Application Recovery Manager splitint program on the currently active node. On all the other nodes, do it manually.
User root (UNIX only) Default OS user account added to the dba user group. Oracle database user Database user account granted at least the following Oracle roles: • sysdba • sysoper For example, user system.
Configuring SQL*Net V2 or Net8 TNS listener 1. Ensure that the listener.ora and tnsnames.ora files on the application system are configured as shown in the following example. The files are located in: UNIX: ORACLE_HOME/network/admin Windows: ORACLE_HOME\network\admin Example Oracle instance: PRO Application system: alpha.hp.com listener.ora LISTENER = (DESCRIPTION_LIST = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP) (HOST = alpha.hp.
2. 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: 1. Log in to the application system as the Oracle OS user. 2. Export/set the ORACLE_HOME and ORACLE_SID variables. 3. Start sqlplus. 4.
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. TIP: Archive the redo log files generated during the online backup immediately after BRBACKUP completes.
2. 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=PROWindows: set ORACLE_SID=PRO sqlplus /nolog SQLPLUS> connect user/passwd@PRO; Connected. SQLPLUS> startup mount ORACLE instance started.
NOTE: The sapreorg, and BR*Tools home directory must be accessible only if you want to run SAP compliant ZDB sessions (BRBACKUP started on the backup system and not on the application system). saparch must be accessible if you want to back up archive logs using a post-exec command. HP-UX application system 1. Share the directories on the application system through NFS with root permissions.
Configuring SAP R/3 databases You need to provide Application Recovery Manager with the following configuration parameters: • • • • • Oracle Server home directory SAP R/3 data home directory Oracle database user account (it is used by BRBACKUP during backup) Directory in which the SAP backup utilities are stored If Oracle 10g Instant Client is installed on the backup system, the directory in which the SQL tools are installed.
4. 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 46 for XP or Figure 45). For details on the options, press F1. NOTE: Select Track the replica for instant recovery.
5. In Client, select the SAP R/3 application system. In cluster environments, select the virtual server. In Application database, type the Oracle instance name (ORACLE_SID). UNIX only: In Username, type the Oracle OS user described in “Configuring users” on page 150. In Group name, type dba. Figure 41 Specifying an SAP R/3 system and Oracle instance Click Next.
6. In the Configure SAP dialog box, specify the pathname of the Oracle Server home directory and SAP R/3 data home directory. Under Oracle login information to target database, type the Oracle database user account described in “Configuring users” on page 150. In Service, type the Oracle service name. In Backup and restore executables directory, specify the pathname of the directory in which the SAP backup utilities reside.
7. To configure the backup system, repeat Step 5 and Step 6, specifying the backup system as the Client. If you installed Oracle 10g Instant Client software on the backup system, specify the SQL path (the path to the sqlplus binary) as well. Note that if the application system is not properly configured, Application Recovery Manager tries to reconfigure it using the backup system parameters by default. If the application system is properly configured, the configuration remains as it is.
Parameter description ORACLE_SID Oracle instance name. ORACLE_HOME Pathname of the Oracle Server home directory. targetdb_connection_string Oracle database user account in the format user_name/password@Oracle_service. SAPTOOLS_DIR Pathname of the directory that stores the SAP backup utilities. SAPDATA_HOME Pathname of the directory where the SAP R/3 data files are installed. By default, this parameter is set to ORACLE_HOME. SQL_PATH Pathname of the directory where the SQLPlus tools are installed.
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 least one backup specification for this database. Use the Application Recovery Manager GUI or CLI.
Figure 44 Checking the SAP R/3 configuration Using the Application Recovery Manager CLI Log in to the SAP R/3 system as the Oracle OS user. From the directory: Windows: AppRM_home\bin HP-UX: /opt/omni/lbin run: util_sap.exe -CHKCONF ORACLE_SID where ORACLE_SID is the name of the Oracle instance. A successful configuration check displays the message *RETVAL*0. If you receive the message *RETVAL*error_number where error_number is different than zero, an error occurred.
Configuring the SAP R/3 parameter file To configure the integration, you need to set some parameters in the SAP parameter file on the application system. The file template is located in: UNIX: ORACLE_HOME/dbs/initORACLE_SID.sap Windows: ORACLE_HOME\database\initORACLE_SID.sap Table 7 SAP parameter file settings Parameter Value/Description primary_db This parameter defines the service name of the Oracle database to link the backup system to the application system.
Considerations • Before you start a backup, ensure that the SAP R/3 database is in the open or shutdown mode. • ZDB and instant recovery sessions that use the same source volume on the application system cannot run simultaneously. • XP only: If the LVM Mirroring configuration is used, Application Recovery Manager displays a warning during a backup because the volume group source volumes on the application system do not have their BC pairs assigned. The message should be ignored.
4. 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 46 for XP or Figure 45 for EVA). For details on the options, press F1. NOTE: To enable instant recovery, leave Track the replica for instant recovery selected. In this case, you must back up the whole database.
Figure 45 EVA backup options 168 Application Recovery Manager SAP R/3 integration
Figure 46 XP backup options Click Next. 5. In Client, select the SAP R/3 system on which the backup should be started. In cluster environments , select the virtual server. In Application database, select the Oracle instance (ORACLE_SID) to be backed up. UNIX only: In Username, type the Oracle OS user name described in “Configuring users” on page 150. In Group name, type dba. Click Next. 6.
7. Select SAP R/3 objects to be backed up. If Track the replica for instant recovery is not selected and you use a third–party backint, you can select individual tablespaces, data files, or archived logs. Figure 47 Selecting backup objects Click Next.
8. Set backup options. For information on the application specific options, see Table 9 on page 171. Figure 48 Application specific options Click Next. 9. Optionally, schedule the backup. See “Scheduling backup specifications” on page 172. Click Next. 10. Save the backup specification, specifying a name and a backup specification group. Table 9 SAP R/3 backup options Option Description Backup Type Select an online or offline backup. During an online backup, the database is open.
Option Start third party backint Description Starts a third–party backint on the backup system, which then backs up the replica to tape. You need to properly configure the third–party software before you use this option. See Backing up with third–party backup software for the prerequisites. If the Application Recovery Manager backup is started on the backup system, this option is selected by default. If started on the application system, the option is disabled.
1. In the Schedule property page, select the starting date in the calendar and click Add to open the Schedule Backup dialog box. 2. Under Recurring, select Weekly. Under Time options, select 8:00. Under Recurring Options, select Mon, Tue, Wed, Thu, and Fri. Click OK. 3. Repeat Step 1 on page 173 and Step 2 on page 173 to schedule backups at 13:00 and 18:00. 4. Click Apply to save the changes. Figure 49 Scheduling backups Starting backup sessions Interactive backups are run on demand.
Using the Application Recovery Manager GUI 1. In the Context List, click Backup. 2. In the Scoping Pane, expand Backup Specifications, and then SAP R/3. Right-click the backup specification you want to start and click Start Backup. 3. Click OK. The message Session completed successfully is displayed at the end of a successful backup session.
3. Create the splitint options file: Windows: AppRM_home\tmp\splitintORACLE_SID.opt HP-UX: /var/opt/omni/tmp/splitintORACLE_SID.
4. Run the SAP brbackup command. For example, to back up data files, control files, and redo logs, run: brbackup -m all -t online_mirror -q split -c force To back up just the data files, run: brbackup —m 1–n —t online_mirror -q split c —force where n is the SAP number of the data file. NOTE: The –q option is required unless you use a third–party backint for backing up to tapes. Restore After the restore, you can recover the database to a specific point in time using the SAPDBA utility.
• If the control file and online redo logs are on the same source volumes as datafiles, the control file is overwritten during the instant recovery. As a consequence, you must restore the overwritten files from a separate backup before you can perform database recovery beyond the replica creation time. To avoid this issue, select the option to keep the current control files when starting a restore. Instant recovery using the Application Recovery Manager GUI To perform an instant recovery: 1.
4. 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. The option is selected by default, except for an offline backup where the database was in NOARCHIVELOG mode during the backup.
Figure 51 SAP R/3 source options — XP Integration guide 179
5. In the Options tab, set the general and database recovery options: To ensure that the current control files and online redo logs are preserved, select Keep current control files and redo logs. If set, the current control files and online redo logs are copied to a temporary location (default AppRM_home\tmp on Windows or /var/opt/omni/tmp on UNIX) before instant recovery starts. When the instant recovery completes, the files are copied back to their original location.
NOTE: The copies of log and control files in the temporary directory, created in different instant recovery sessions, are preserved. Each copy has got a time stamp. Let us assume that an instant recovery session fails in such a way that the copy of the current control files is not returned to the original location if the restore session is not successful. It means that the current control files have been replaced with the control files from the replica.
Selected logseq/ thread number: Specifies an incomplete recovery. Only archive logs with a 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. 182 Open database after recovery Opens the database after the recovery was performed. Reset logs Resets the archive logs after the database is opened. This option is by default not selected if the Recover until option is set to Now.
Figure 52 SAP R/3 recovery options Instant recovery using the Application Recovery Manager CLI From the directory: Windows: AppRM_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 Integration guide 183
[-user UserName -group GroupName] [–keep_files] [-recover {now | time MM/DD/YY hh:mm:ss | logseq LogSeqNumber thread ThreadNumber | SCN Number} [-open [-resetlogs]]] ] [-preview] On UNIX clients, the user name and group name options are required. For a detailed description of the options, see the HP Application Recovery Manager software command line interface reference. Localized SAP R/3 objects Oracle Server uses its own encoding, which may differ from the encoding used by the filesystem.
System messages generated during backups are sent to both the SAP R/3 and the Application Recovery Manager monitor. Troubleshooting This section lists general checks and verifications plus problems you might encounter when using the Application Recovery Manager SAP R/3 integration. For general Application Recovery Manager troubleshooting information, see the online Help.
1. On the SAP R/3 system on which you plan to start the backup, verify that the target database is online, as follows: UNIX: export ORACLE_SID=Oracle_SID export ORACLE_HOME=Oracle_home_path $ORACLE_HOME/bin/sqlplus Windows: set ORACLE_SID=Oracle_SID set ORACLE_HOME=Oracle_home_path %ORACLE_HOME%\bin\sqlplus At the SQLPlus prompt, type: connect user/passwd@service select * from dba_tablespaces exit; Try starting the target database.
2. In order to establish the TNS network connection, verify that Net8 software is configured correctly for the target database, as follows: • On the SAP R/3 system on which you plan to start the backup, 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).
1. On the SAP R/3 system on which you plan to start the backup, verify a backup directly to disk, as follows: brbackup -d disk -u user/password If it fails, refer to the SAP Online help for instructions on how to execute a backup to disk using the SAP backup utility. 2.
3. Verify the permissions of the SAP user on application system: SAP user permissions must be set to enable you to perform an SAP backup or restore with Application Recovery Manager. See “Configuring users” on page 150. 4. Examine the system errors: System errors are reported in the following file on the Oracle Server: /var/opt/omni/log/debug.
• 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; for example, TNS_ADMIN and SHLIB_PATH. Set these environment variables using the Application Recovery Manager GUI. Refer to Application Recovery Manager SAP R/3 configuration file for more information on the Application Recovery Manager SAP configuration file.
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 Application Recovery Manager GUI: 1. In the Context List, select Backup. 2. In the Scoping Pane, expand Backup, Backup Specifications, and then SAP R/3. A list of SAP backup specifications is displayed. 3.
Actions Use any of the following solutions: • For new Oracle installations, set the DBCS to UTF-8. • If you do not use other non-Unicode programs, set the language for non-Unicode programs to the same value as DBCS. • Do not use non-ASCII or non-Latin 1 characters for filenames.
A Appendix In this appendix This appendix gives information on the following topics: • “Reconfiguring an Oracle instance for instant recovery” on page 193 • “ZDB integrations omnirc variables” on page 197 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.
4. Start the database in mount mode: $ sqlplus SQL> connect user/password@service as sysdba; SQL> startup mount; 5. Register the new locations for each moved file: SQL> alter database rename file 'OldPathName' to 'NewPathName'; where OldPathName and NewPathName are full paths to the log file. 6. Open the database in normal mode: SQL> alter database open; Moving Control Files To move the control files from the source volumes to be replicated, to other locations: 1.
c. Move the control files to a different location. d. Restart the database: SQL> startup Examples for moving the control files and redo logs to different locations Example - Moving Online Redo Logs In the following example for 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. To move the online redo log files from /opt/oracle/product/9.2.0 to /oracle/logs (which is not replicated): 1.
2. Shut down the database: SQL> connect user/password@service as sysdba; SQL> shutdown SQL> exit 3. Move the log files to a different location. $ mv /opt/oracle/product/9.2.0/oradata/redo* /oracle/logs 4. Start the database in mount mode: $ sqlplus SQL> connect user/ password@service as sysdba; SQL> startup mount; 5. Rename the new locations for each moved file: alter database rename file '/opt/oracle/product/9.2.0/oradata/redo01.log' to '/oracle/logs/redo01.log'; Database altered.
1. Determine if the database uses the SPFILE parameter: SQL> show parameter spfile; NAME TYPE VALUE ------------------------- ----------- ------------------spfile string ?/dbs/spfile@.ora 2. Specify the new location for the control files by running the following command: SQL> alter system setcontrol_files='/oracle/logs/RCVCAT/control01.ctl','/oracle/logs/RCVCAT/control02','/oracle/logs/RCVCAT/control03.ctl' scope=spfile; 3. Shut down the database: SQL> shutdown 4.
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: • If this variable is set to 0 (default), during a backup session, Application Recovery Manager creates target volumes only for the source volumes containing Oracle datafiles. Target volumes for source volumes containing Oracle control file and Oracle online redo logs are not created.
Figure 53 Oracle backup and restore concepts when the ZDB_ORA_INCLUDE_CF_OLF variable is set to 1 ZDB_ORA_INCLUDE_SPF: The default value is 0. Possible values are 0 and 1. By default (if this variable is set to 0), during a backup session, Application Recovery Manager checks if Oracle datafiles and the SPFILE are on the same source volumes. If the SPFILE and datafiles are on the same volumes and instant recovery is enabled, the backup session is aborted.
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. This binary needs to have the setuid bit set on UNIX. Setting this variable to 1, the check will be skipped, and the omniresolve binary will not be used to check the Oracle configuration.
Glossary access rights See user rights. 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. The directory services provide a consistent way to name, describe, locate, access and manage resources regardless of the physical system they reside on. application agent A component needed on a client to back up or restore online database integrations.
Application Recovery Manager software. For backup and restore, SAP R/3 programs issue orders for the Application Recovery Manager backint interface. 202 backup object A backup unit that contains all items backed up from one disk volume (logical disk or mount point). The backed up items can be the entire disk or mount point. Additionally, a backup object can be a database/application entity or a disk image (rawdisk).
By Type - according to the type of data available for backups/templates. Default view. By Group - according to the group to which backup specifications/templates belong. By Name - according to the name of backup specifications/templates. BC (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.
BRRESTORE (SAP R/3 specific term) An SAP R/3 tool that can be used to restore files of the following type: • Database data files, control files, and online redo log files saved with BRBACKUP • Redo log files archived with BRARCHIVE • Non-database files saved with BRBACKUP You can specify files, tablespaces, complete backups, log sequence numbers of redo log files, or the session ID of the backup. See also SAPDBA, BRBACKUP, and BRARCHIVE.
client or client system Any system configured with any Application Recovery Manager functionality and configured in a cell. cluster-aware application It is an application that supports the cluster 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).
See also HP StorageWorks EVA SMI-S Agent and HP StorageWorks SMI-S EVA provider. 206 container (HP StorageWorks EVA specific term) Space on a disk array, which is pre-allocated for later use as a snapclone. control file (Oracle and SAP R/3 specific term) An Oracle data file that contains entries specifying the physical structure of the database. It provides database consistency information used for recovery.
DMZ The Demilitarized Zone (DMZ) is a network inserted as a "neutral zone" between a company's private network (intranet) and the outside public network (Internet). It prevents outside users from getting direct access to company servers in the intranet. 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 resolution across the Internet.
nodes using three physical topologies: point-to-point, loop, and switched. 208 filesystem The organization of files on a hard disk. first-level mirror (HP StorageWorks Disk Array XP specific term) HP StorageWorks Disk Array XP allows up to three mirror copies of a primary volume and each of these copies can have additional two copies. The three mirror copies are called first-level mirrors. See also primary volume and MU number.
storage. This balances the need for fast retrieval from hard disk with the lower cost of optical platters. Holidays file A file that contains information about holidays. You can set different holidays by editing the Holidays file: /etc/opt/omni/server/Holidays on the UNIX Cell Manager and AppRM_home\Config\Server\holidays on the Windows Cell Manager. HP StorageWorks Disk Array XP LDEV A logical partition of a physical disk within an HP StorageWorks Disk Array XP.
restore. The Inet service is started as soon as Application Recovery Manager is installed on a system. The Inet process is started by the inetd daemon. 210 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.
operator. This implies that no operator personnel is present to work with the backup application. Local Continuous Replication (Microsoft Exchange Server specific term) Local continuous replication (LCR) is a single-server solution that creates and maintains an exact copy (LCR copy) of a storage group. An LCR copy is located on the same server as the original storage group. When an LCR copy is created, it is kept up to date through change propagation (log replay) technology.
• user_name is the name by which a user is known to Oracle Server and to other users. Every user name is associated with a password and both have to be entered to connect to an Oracle Target Database. This user must have Oracle SYSDBA or SYSOPER rights. • password must be the same as the password specified in the Oracle password file (orapwd), which is used for authentication of users performing database administration.
Microsoft Exchange Server A “client-server” messaging and a workgroup system that offers a transparent connection to many different communication systems. It provides users with an electronic mail system, individual and group scheduling, online forms, and workflow automation tools. It provides a developer with a platform on which to build custom information-sharing and messaging-service applications.
offline redo log See archived redo log. online backup A backup performed while a database application remains available for use. The database is placed into a special backup mode of operation for the time period that the backup application requires access to the original data objects. During this period, the database is fully operational, but there may be a small performance impact and log files may grow very quickly.
• COPY - The mirrored pair is currently re-synchronizing. Data is transferred from one disk to the other. The disks do not contain the same data. • PAIR - The mirrored pair is completely synchronized and both disks (the primary volume and the mirrored volume) contain identical data. • SUSPENDED - The link between the mirrored disks is suspended. That means that both disks are accessed and updated independently.
public folder store (Microsoft Exchange Server specific term) The part of the Information Store that maintains information in public folders. A public folder store consists of a binary rich-text .edb file and a streaming native internet content .stm file.
replica (ZDB specific term) An image, at a particular point in time, of the data in source volumes that contain user-specified backup objects. Depending on the hardware or software with which it is created, the image may be an independent exact duplicate (clone) of the storage blocks at the physical disk level (for example, a split mirror or snapclone), or a virtual copy (for example, a snapshot).
SAPDBA (SAP R/3 specific term) An SAP R/3 user interface that integrates the BRBACKUP, BRARCHIVE, and BRRESTORE tools. Scheduler A function that controls when and how often automatic backups occur. By setting up a schedule, you automate the start of backups. secondary volume (S-VOL) (HP StorageWorks Disk Array XP specific term) secondary volumes, or S-VOLs, are XP LDEVs that act as a secondary BC mirror of another LDEV (a P-VOL).
shared disks A Windows disk on another system that has been made available to other users on the network. SMBF The Session Messages Binary Files (SMBF) part of the IDB stores session messages generated during backup and restore sessions. One binary file is created per session. The files are grouped by year and month. snapshot (HP StorageWorks EVA specific term) A form of replica produced using snapshot creation techniques.
(the mirror is split) and a split mirror replica of the source volumes at the time of the split remains in the target volumes. See also split mirror. 220 SSE Agent (HP StorageWorks Disk Array XP specific term) An Application Recovery Manager software module that executes all tasks required for a split mirror backup integration. It communicates with the HP StorageWorks Disk Array XP storing system using the RAID Manager XP utility.
tablespace A part of a database structure. Each database is logically divided into one or more tablespaces. Each tablespace has data files or raw volumes exclusively associated with it. 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 Windows desktop session and Windows-based programs running on the server.
transportable snapshot (Microsoft VSS specific term) A shadow copy that is created on the application system and can be presented to the backup system. See also Microsoft Volume Shadow Copy Service (VSS). unattended operation See lights-out operation.
Virtual disks are the entities that are replicated using the HP StorageWorks Enterprise Virtual Array snapshot functionality. See also source volume and target volume. virtual server A virtual machine in a cluster environment defined in a domain by a network IP name and address. Its address is cached by the cluster software and mapped to the cluster node that is currently running the virtual server resources. This way all requests for a particular virtual server are cached by a specific cluster node.
used in operating systems as a means of specifying more than one file by name. 224 Windows Registry A centralized database used by Windows to store configuration information for the operating system and the installed applications. WINS server A system running Windows Internet Name Service software that resolves Windows networking computer names to IP addresses. writer (Microsoft VSS specific term) A process that initiates change of data on the original volume.
Index A advantages, 28 Oracle integration, 87 VSS integration, 26, 28 architecture, 30 VSS integration, 26 audience, 15 B backing up VSS backup flow, 29 backing up Oracle backup templates, 106 backing up SAP R/3 backup options, 172 backing up VSS scheduling backups, 58 backing up Oracle, 116 - 119 backup options, 114 backup types, 88 backup specifications, creating, 106 concepts, 88 - 93 scheduling backups, 117 starting backups, 118 - 119 starting backups, using CLI, 118 starting backups, using GUI, 118 wi
backup flow, Oracle integration ZDB session flow, 91 - 93 backup objects, 52 backup options SAP R/3 integration, 172 backup specifications creating, 47 backup specifications, creating Oracle integration, 106 SAP R/3 integration, 166 backup specifications, modifying SAP R/3 integration, 172 backup specifications, ownership Oracle integration, 96 backup specifications, scheduling VSS integration, 58 backup templates Oracle integration, 106 backup types, 27 Oracle integration, 88 SAP R/3 integration, 165 VSS i
Disk Array XP with VSS configuting, 40 document conventions, 18 related documentation, 15 documentation HP website, 15 providing feedback, 21 E EVA replica creation and reuse, 46 snapshot types, 45 EVA with VSS configuting, 38 examples SAP R/3 integration, starting interactive backups, 174 examples, scheduling backups SAP R/3 integration, 172 Exchange Replication Service, 56 F finding users Oracle integration, 96 H help obtaining, 20 HP technical support, 20 I Informix backup backup specifications, crea
Microsoft Exchange Server configuring writer, 42 Exchange Server 2007 writer concepts, 32 storage groups, 56, 57 writer recovery specifics, 65 Microsoft Exchange Server 2007 writer backup specifics, 56 writer recovery specifics, 66 modifying backup specifications SAP R/3 integration, 172 monitoring sessions Oracle integration, 132 SAP R/3 integration, 184 O omnirc variables, 197 - 200 Oracle backup backup types, 88 scheduling backups, 117 Oracle configuration example, CLI, 103 Oracle integration advantages
related documentation, 15 replica creation and reuse EVA, 46 restore, 60 concepts, 32 instant recovery procedure, 69 Oracle integration, 119 problems, 84 procedure, 69 troubleshooting, 84 restore flow, 32 restore types Oracle integration, 88 restoring VSS restore flow, 32 restoring Oracle restore types, 88 restoring SAP R/3 instant recovery, 176 restoring Oracle, 119 restoring SAP R/3, 176 - 183 restoring SAP R/3 database recovery, 176 restoring VSS, 60 instant recovery, 68 running backups, 59 running backu
starting backups, Oracle integration using CLI, 118 using GUI, 118 starting backups, Oracle integration, 118 - 119 storage groups, 56, 57 Subscriber's Choice, HP, 21 T technical support HP, 20 technical support service locator website, 21 third-party backup software Oracle, 116 transportable backup, 51 transportable VSS backup, 30, 48 troubleshooting backup, 80 checks and verifications, 79 instant recovery, 84 restore, 84 troubleshooting SAP R/3 verifying backups, 189 troubleshooting Oracle, 134 - 137 trou
VSS integration prerequisites, 33 advantages, 28 architecture, 26, 30 backup, 44 - 59 checking configuration, 43 configuration, 37 - 44 - 44 configuring, 37, 41 instant recovery, 32 limitations, 34 prerequisites, 33 restore, 32 troubleshooting, 78 - 85 VSS provider configuring, 41 VSS restore, 60 instant recovery, 68 instant recovery procedure, 69 restore flow, 32 Z ZDB concepts, 26 ZDB flow SAP R/3 integration, 141 ZDB session flow Oracle integration, 91 - 93 zero downtime backup, 26 W websites HP Subscr
