Obsolescence Announcement
Frequently Asked Questions
HP Application Recovery Manager 6.0x Version Obsolescence Announcement Frequently Asked Questions
On June 1, 2008, HP announced the version maturity and end of support dates for HP Application Recovery Manager (AppRM) version 6.0x. This document provides you with answers to frequently asked questions regarding this announcement. Product related questions Question Answer Question Answer
When is HP discontinuing this HP Application Recovery Manager 6.0x product? Effective June 1, 2008, HP is discontinuing HP Application Recovery Manager version 6.0x. Please refer to the customer letter for the end of support date. What version of HP Application Recovery Manager is currently available and what upgrade plans do you have for the product, if any? The latest version of HP Application Recovery Manager is version 6.1. Please check www.hp.com/go/software (Products -> Products A-Z -> Application Recovery Manager) or otherwise check with your local HP sales representative or HP software business partner for the latest information. Why is HP discontinuing this HP Application Recovery Manager 6.0x product? This is in accordance with the HP Software Supported Version Policy 4.2. Definitions of terms are documented in the HP Software product version obsolescence guidelines When is the last date I can order HP Application Recovery Manager 6.0x? HP Application Recovery Manager 6.0x will no longer be available for purchase from June 1, 2008. Whom can I contact if I have more questions with regards to this product discontinuance? You have several options available to you: Contact your local HP sales representative or your local HP software business partner: h20229.www2.hp.com/buy/index.html Web Self Solve: www.hp.com/go/hpsoftwaresupport/

Question Answer

Question Answer Question Answer

*5992-4842*

HP Technical Support: www.hp.com/go/hpsoftwaresupport/casemanager/submitcase
What are the hardware requirements to upgrade to HP Application Recovery Manager version 6.1? Hardware requirements will vary depending on your operating system, please review the appropriate Release Notes, Installation Guide, and/or Migration Guide or otherwise contact your local HP sales representative or HP software business partner for further assistance. Where can I find upgrade information for the HP Application Recovery Manager product? Information on upgrading from prior versions to Application Recovery Manager version 6.1 is included in the Application Recovery Manager version 6.1 product documentation. In addition to this, your local HP sales representative or HP software business partner can help you get this information. I plan to upgrade my HP Application Recovery Manager version 6.0x environment using in-house technical resources. Where do I get all the required software? You can request the HP Application Recovery Manager version 6.1 media by sending or faxing in your pull letter you have received or by requesting or downloading the software via Software Update Manager (SUM). In case you do not have this information; please contact your local HP contract administration representative or your HP Software Services Integrator (SVI) partner to provide you with the HP Application Recovery Manager version 6.1 media. The release to be requested is labeled APRM61.
Support contract related questions Question Answer
What is the end of support date? The End of Support date is November 30, 2009. As of this date all customer support activities will cease, this includes: Telephone support Security Rule updates Product upgrades Are there any other key dates I need to be aware of? Please see Customer Letter, page 1 for the key dates. What are my discontinuance options? Customers have the option to continue using HP Application Recovery Manager 6.0. HP will stop providing Support for this product on November 30, 2009. SelfHelp Support will continue to be available through November 30, 2011. Customers are encouraged to begin reviewing their business requirements for Application Recovery Manager. Customers are also encouraged to contact their local HP sales representative or HP software business partner for help in determining migration options that meet your business needs. How does this affect my HP Application Recovery Manager support contract? Upon the End of Support date of HP Application Recovery Manager version 6.0x, your support contract will automatically be updated to reflect HP Application Recovery Manager version 6.1 product numbers. In case you havent upgraded to HP Application Recovery Manager version 6.1 by this date, you can continue to get Self-Help Support for HP Application Recovery Manager version 6.0x until October 31, 2011.

Question Answer Question

Can I get a support contract for technical support only, without having to pay for upgrades? No, support contracts include both technical support and software updates. Should there be a defect with a version of HP Application Recovery Manager for which no defect fixing is done anymore, can I pay for a fix to be implemented on my request? HP may choose to offer defect fixes at a premium price, depending on available resources. If I am on a support contract, what will I be entitled to? You should have received a letter or electronic notification from HP to inform you about the availability of HP Application Recovery Manager version 6.1 for support customers, what license(s) you were entitled to under your support contract and how to sign up for it. Your local HP sales and support representatives or your HP software business partner can help provide information and assistance to enable your upgrade to be easy and successful. When I upgrade from HP Application Recovery Manager version 6.0x to HP Application Recovery Manager version 6.1, can I continue my existing support contracts until they expire? Yes, you can continue using your existing support contract. When I upgrade from HP Application Recovery Manager version 6.0x to HP Application Recovery Manager version 6.1, can I expect the same support pricing compared to HP Application Recovery Manager version 6.0x? Not necessarily. Each product support price is determined independently.

Answer Question Answer

Question

Answer Question

What migration services are available to help me upgrade?
HP Consulting & Integration or HP Software Business Partners can provide migration assistance as a services engagement. In addition, the product provides documentation for the migration process.

For more information

For more information on Application Recovery Manager and HP Software services, contact any of our worldwide sales offices or visit our worldwide websites on the Internet at: www.hp.com/go/software www.hp.com/go/hpsoftwaresupport/ www.hp.com/go/hpsoftwaresupport/support-lifecycle
Copyright 2008 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. For more information, go to www.managementsoftware.hp.com 5/2008. Printed in the U.S.

Migration from HP Application Recovery Manager to HP Data Protector
Summary.....3 Application Recovery Manager and Data Protector key differences..3 Before reading on....3 General limitations and workarounds....4 Missing command options....4 IDB backups.....4 Container Support....4 Oracle restore options....4 Backup system-related options....5 SAP environments....5 Migration process overview....5 Recommended upgrade path....6 Upgrade the Cell Manager.....6 Upgrading an HP-UX Cell Manager....6 Upgrading a Windows Cell Manager....7 What happens after a Cell Manager is upgraded...8 Upgrade the Installation Server...8 Upgrade clients....8 Upgrading clients by push installation....9 Upgrading clients locally.....9 Add additional agents.....11 Configure the devices....12 Modify backup specifications...12 VSS backup specifications....12 Oracle backup specifications....12 SAP backup specifications...13 Modify schedules.....13 SAP environments....14 SAP non-compliance mode...14 SAP-compliance mode....14 Host selection.....14 Oracle instant client support....15 SAP instant recovery options....15 Using a third-party backint utility...16 Mismatch in environmental variables...17 Troubleshooting.....18 BRBackup fails creating copy of the control file...18 Copy of control file already exists....18 Backup fails to get database configuration....19 For more information....20

Summary

This document is for users who have HP Application Recovery Manager (AppRM) installed and wish to upgrade to HP Data Protector. If during the upgrade process, you find that any configuration is not working as expected, you are recommended to get assistance from Data Protector support. It is also recommended that you read this document completely before starting the upgrade process in order to understand the benefits and limitations of upgrading the existing AppRM setup to Data Protector.
Application Recovery Manager and Data Protector key differences
HP Application Recovery Manager (AppRM) is a solution for backup and recovery of business application data designed to improve the time to recovery from an outage. AppRM automates restoration of application databases such as Oracle, SAP, Exchange and Microsoft SQL in the event of failure or corruption, and allows you to restore data to the moment before the outage. HP Data Protector is backup and disaster-recovery software that not only offers functionality similar to AppRM but also tape backup and Disaster Recovery solutions. Data Protector offers comprehensive backup and restore functionality specifically tailored for enterprise-wide and distributed environments. It provides reliable data protection and high accessibility for your fastgrowing business data. Data Protector can be used in environments ranging from a single system to thousands of systems on several sites. Due to the network component concept of Data Protector, elements of the backup infrastructure can be placed in the topology according to user requirements. The numerous backup options and alternatives to setting up a backup infrastructure allow the implementation of virtually any configuration you want. Additionally, Data Protector enables you to perform backup to a large number of backup devices simultaneously. It also supports high-end devices in very large libraries and the new drives capable of performing hardware-based AES encryption. Overall, setups supported with AppRM are also supported by Data Protector. As an added advantage, after the upgrade, you can make use of tape backups to safely store the data in a media vault if needed.

Before reading on

This guide assumes: you have a working AppRM setup which you want to migrate (upgrade) to Data Protector, you understand the functionality and administration of AppRM and Data Protector. To obtain this knowledge, the Administrator and Installation guides of AppRM and the Concepts and Installation guides of Data Protector are recommended. Before you start, as a safety measure, take the following actions related to your existing AppRM setup:
1. Copy the license file located in AppRM_home\config\server\cell\lic.dat (on Windows Cell
Manager) or /etc/opt/omni/server/cell/lic.dat (on HP-UX Cell Manager). Although your license for AppRM will continue to work for Data Protector, it is advisable to make a copy of the license file and store it in a different location. If you are using HP StorageWorks XP Array in your AppRM setup, then contact local HP sales representative or HP support to convert the licenses.

2. Note down details of the backup specification. You will need details of the backed-up data,
especially your SAP setups, and their schedules in case you are required to recreate the backup specifications. Before starting the upgrade, consider the following: What data is backed up.
How often the data is backed up. When you have a suitable time window to perform the upgrade.
3. Check if any backup sessions are excluded for instant recovery by executing omnidbsmis list
session excluded. If you find any such sessions, include them by issuing omnidbsmis include session <session ID>. Further information regarding this is given later in this document.
4. You may need the following information in case the upgrade does not work well, and you
have to recreate the setup: Credentials of the CommandView servers. Credentials of application servers, including database administrator passwords and location of the database configuration files.
General limitations and workarounds

Missing command options

In general all the commands present in AppRM are also present in Data Protector. However, in AppRM the command omnidbsmis has two options, include and exclude. These are used to indicate if the replicas generated in a particular session should be included in instant recovery or not. A supplementary option lists these excluded sessions by using omnidbsmis list session excluded. These options are not supported for the same command (omnidbsmis) in Data Protector 6.11. Because of these options, the excluded sessions do not show up in the instant recovery context, so if you have any excluded sessions from AppRM, it is advisable to include them before starting the upgrade in order to have all the sessions available for instant recovery. Note: These options will be available in upcoming releases of Data Protector.

IDB backups

AppRM provides a tool, dbtool.pl, for performing AppRM internal database (IDB) backups. This tool is not present in Data Protector. In Data Protector, IDB backups can be done using standard DP backup. For more information regarding Data Protector IDB backups, see Data Protector Online Help.

Container Support

AppRM uses EVA snapclone container functionality to improve the speed of the backups and restore, and to minimize the impact on the application using the original vdisks. This also allows a better opportunity for space planning and usage. Once a set of replicas is in use, the storage allocation is static. There is no need to wait for a disk to be fully deleted to free space for the next backup. Note: Data Protector 6.11 does not offer container support, but it will be available in upcoming releases of Data Protector.

Oracle restore options

In AppRM, since tape backup was missing, Oracle archive logs are backed up using a third-party application, for which the location is not known to AppRM. After instant recovery of the database, these backed-up logs can be used for database recovery. It is possible to use an RMAN script to use these logs. In AppRM, this script location can be specified during the restore in the Oracle restore GUI:

Figure 1:

Oracle restore options in AppRM
These options are missing in Oracle because they are not needed. But in the case of Data Protector, since it can also back up the archive logs, the location is known and hence these options are not needed.
Backup system-related options
In AppRM, after presenting snapshots to the backup system, it is possible to leave these snapshots mounted for additional operations, such as tape backup. This is achieved by an option in SMISA or SSEA backup:

Figure 2:

Backup system options in AppRM
These options are not present in SMISA backups in Data Protector 6.11. However you can start tape backup on the backup host by selecting disk+tape backup as shown in Figure 17:.

SAP environments

Since many changes are necessary in the SAP integration, they are described in SAP environments on page 14.
Migration process overview
The migration process can be summarized as follows: Upgrade the Cell Manager and install additional agents Upgrade the Installation Server Upgrade the clients Add additional agents to the clients Configure the devices Reconfigure the backup specifications and schedules These steps are described in this document in detail along with the limitations and solutions which are seen after the migration.

Recommended upgrade path

The recommended upgrade path from AppRM 6.1 is to Data Protector 6.11 and later versions. Although you can upgrade to Data Protector 6.10 in a similar way, it is better to upgrade to the latest version of Data Protector.

Upgrade the Cell Manager

On the AppRM Cell Manager, copy or mount the installation media or insert the Data Protector DVD to start the upgrade.
Upgrading an HP-UX Cell Manager
Execute the script omnisetup.sh from the LOCAL_INSTALL directory of the installation source. When it is executed, the installation detects the product as Data Protector 6.1 instead of AppRM 6.10, but the upgrade still works as expected.
root@CM_host:/<DVD_ROM>/LOCAL_INSTALL#./omnisetup.sh Data Protector version A.06.10 found Cell Manager detected. Installation Server detected. Client detected, installed packets: cc docs. ======= 10/01/09 19:11:46 METDST BEGIN swinstall SESSION (non-interactive) (jobid=CM_host-0085) * Session started for user "root@CM_host". * Beginning Selection * Target connection succeeded for "CM_host:/". * Source: /<DVD_ROM>/hpux_pa/DP_DEPOT/DP_A0611_UX11x.sd_depot * Targets: CM_host:/ * Software selections: + B6960MA,r=A.06.11,a=HP-UX_B.11.11_32/64,v=HP DATA-PROTECTOR.OMNI-CC,r=A.06.11,a=HPUX_B.11.11_32/64,v=HP,fr=A.06.11,fa=HP-UX_B.11.11_32/64 DATA-PROTECTOR.OMNI-CORE,r=A.06.11,a=HPUX_B.11.11_32/64,v=HP,fr=A.06.11,fa=HP-UX_B.11.11_32/64 DATA-PROTECTOR.OMNI-CS,r=A.06.11,a=HPUX_B.11.11_32/64,v=HP,fr=A.06.11,fa=HP-UX_B.11.11_32/64 DATA-PROTECTOR.OMNI-DA,r=A.06.11,a=HPUX_B.11.11_32/64,v=HP,fr=A.06.11,fa=HP-UX_B.11.11_32/64 DATA-PROTECTOR.OMNI-DOCS,r=A.06.11,a=HPUX_B.11.11_32/64,v=HP,fr=A.06.11,fa=HP-UX_B.11.11_32/64 DATA-PROTECTOR.OMNI-JAVAGUI,r=A.06.11,a=HPUX_B.11.11_32/64,v=HP,fr=A.06.11,fa=HP-UX_B.11.11_32/64 DATA-PROTECTOR.OMNI-MA,r=A.06.11,a=HPUX_B.11.11_32/64,v=HP,fr=A.06.11,fa=HP-UX_B.11.11_32/64 * A "+" indicates an automatic selection due to dependency or the automatic selection of a patch or reference bundle. * Selection succeeded.

You can see from this that, on HP-UX, the installer automatically selects additional Disk Agent and Media Agent components. After the Cell Manager is upgraded, the Installation Server upgrade (if installed on the same system) is started automatically.
Installing Data Protector A.06.11 Installation Server.
It is followed by similar messages as in the Cell Manager installation, listing all the individual components selected for upgrade. There is an additional message at the end:
* "CM_host:/": installed. * "CM_host:/": installed. 1 filesets have the selected revision already 1 bundles have the selected revision already
This message appears for the core packet, which is upgraded during Cell Manager installation, so you can ignore it.
Upgrading a Windows Cell Manager
On Windows the installer detects that AppRM is installed and prompts you to upgrade it. However, there are a couple of differences in the normal setup procedure:
1. On a Windows system, the installer upgrades all the agents found on the system. So if you run
the installer on a Cell Manager system, it will upgrade the Cell Manager, and if it is installed on the Installation Server, the Installation Server is updated.
2. When run on a Windows Cell Manager, the installer does not select any additional agents
automatically (in a standard Cell Manager installation, Disk Agent and Media Agent are normally preselected). It is always advisable to install at least a Disk Agent on the Cell Manager system, in order to perform Data Protector IDB backups.

Figure 3:

Selection of Disk Agent during Data Protector Cell Manager installation
3. Similarly, it is also advisable to select a Media Agent during the upgrade process. There are
several reasons for this, which are described later in this document.

Figure 4:

Selecting a Media Agent during Data Protector Cell Manager installation
What happens after a Cell Manager is upgraded
After the upgrade of a Cell Manager, the following have been achieved: The Cell Manager binaries and Installation Server depots are migrated to Data Protector. All the backup specifications which were created in AppRM are transferred to Data Protector backup specifications under appropriate types. All the credentials, such as application integration passwords, and CV login information, are retained as they are, so they will continue to work as they are. The contents of the AppRM IDB (session information, objects) are migrated to the Data Protector IDB. The customized omnirc files are retained as they were in your earlier setup, but a new template file is present in the Data Protector home directory.

Upgrade the Installation Server
The next task is to upgrade any additional Installation Servers present in your setup. This upgrade is similar to Cell Manager upgrade. See Upgrading an HP-UX Cell Manager on page 6 or Upgrading a Windows Cell Manager on page 7 for guidance.

Upgrade clients

After the Installation Server is upgraded, you need to upgrade the clients. Clients and user details that were present in the AppRM setup are also present in the new Data Protector cell. However, you need to upgrade all the clients to install the new Data Protector
binaries on them. You can do this through push installation, that is, by selecting the clients in the Data Protector GUI and choosing to upgrade them, or by upgrading them locally.
Upgrading clients by push installation
In the Data Protector Clients context, select the clients to be upgraded, right-click and select Upgrade.

Figure 5:

Pushing the upgrade in Data Protector
Note: If the AppRM INET process (or service) runs under any local user account, the upgrade does not work. The installation session terminates with an error: [Critical] <client.domain.com> [110:1026] Lost connection to client client.domain.com: [10054] Connection reset by peer In such a case, change the ownership of the AppRM INET process (or service) temporarily to the local system account before performing the upgrade. You can switch the ownership back when the upgrade is completed.
Upgrading clients locally
If an installed client does not have connectivity to the Data Protector Installation Server, or the Installation Server is not suitable for remote client installation (for example, a Windows client in an HP-UX-only environment), you can install the client locally. Similar to the Cell Manager upgrade, copy or mount the installation media on the client or insert the Data Protector DVD to start the upgrade. On Windows systems, the Data Protector installer detects the components installed on the system and upgrades them.

Figure 6:

Upgrading the client locally on Windows
Note: You can see in the picture above that the only installed components are marked for reinstallation (upgrade). You should also select additional components, such as at least an additional Disk Agent and optionally Media Agent during this process. On HP-UX systems, run the omnisetup.sh script from the LOCAL_INSTALL directory of the installation mediium. This script detects the existing installation (as in the Cell Manager upgrade, the existing AppRM installation is detected as a Data Protector 6.10 installation). When run without any options, the script lists all the components present on the system and upgrades them to Data Protector 6.11. No additional agents are selected or upgraded in this process. To install a Disk Agent and Media Agent additionally on the system, run the omnisetup.sh script with install da, ma options in order to install these components on the clients. A typical output of an upgrade session of an AppRM client where the user interface, Oracle, SAP and SSEA agents are upgraded, and a Disk and Media Agent are newly installed is as follows:

root@client:/<DVD>/LOCAL_INSTALL#./omnisetup.sh -install da,ma Data Protector version A.06.10 found Client detected, installed packets: cc sap oracle8 ssea Packets going to be (re)installed: omnicf integ cc da ma oracle8 sap ssea Unpacking selected packets from CD, please wait (5-10 minutes). Unpacking complete! Installing Core (omnicf). Installing Core of Integrations (integ). Installing User Interface (cc). Installing Disk Agent (da).
Installing Media Agent (ma). Installing Oracle Integration (oracle8). Installing SAP R/3 Integration (sap). Installing HP StorageWorks Disk Array XP Agent (ssea). Importing client to cellmanager.domain.com. Import host successful. Installation/Upgrade session finished.

Add additional agents

Since AppRM does not have a Disk Agent concept, there are no Disk Agents installed at the time of the upgrade. Additionally, since AppRM is a disk-only backup solution, it does not use any devices for backup. A typical AppRM setup does not have a Media Agent installed, so at the time of upgrading the clients either remotely or locally, it is not installed unless you specifically selected it. The procedures above describe how you can install a Disk or Media Agent when performing the upgrade on the Cell Manager or the clients during local upgrade. To install a Disk or Media Agent on any other system, you can push the components to any of the client in the cell. To do this:
1. Go to the Clients context in the Data Protector GUI, select the desired client and select Add

components.

Figure 7:
Adding components remotely in Data Protector
2. On the next screen, confirm the client selection and click Next. A list of available components
is shown. Select Disk Agent and Media Agent.

Figure 8:

Select Disk and Media Agent

Configure the devices

AppRM backup specifications do not have any target device selected in them. This causes an issue for Data Protector as all the backup specifications except VSS backups expected to use a target device. So, after installing a Media Agent in your cell, the next step is to create and configure devices that can be used as target devices for the backup specifications. Refer to the Data Protector online documentation and online help for details of how to configure the devices. Note: If the environment does not have any physical devices, you can configure file libraries or file devices.

Modify backup specifications
At this stage, you have all the systems including Cell Manager, Installation Servers and Clients upgraded to the latest release of Data Protector. Additionally the clients and Cell Managers also have Disk Agents installed on them. Some of the clients should also have Media Agents installed on them with at least one device configured in your Data Protector cell. To make sure that all the backups work flawlessly, you need to make some additional changes to the setup.
VSS backup specifications
There are no changes required in already configured VSS backups. These backups work as they used to work in AppRM when started interactively or through schedules. If needed, you can select a destination device for them, but it is not necessary.
Oracle backup specifications
Oracle backups take place when started interactively and in disk only mode. However, since Data Protector backup specifications are expected to use target devices, you will not be able to save the changes made to the backup specification unless the target devices are selected. To select target devices after the devices are configured, select the newly created devices as targets for your backup specifications. If you change a backup specification is changed without adding a target device, you will see the following error when saving the backup specification:

Figure 9:

No target device selected
To avoid this error, make sure all Oracle backup specifications have devices selected in them.
SAP backup specifications
Because SAP backups are implemented completely differently, you need to delete the SAP backup specifications created in AppRM, reconfigure the SAP instance and then recreate the backup specifications in Data Protector to back up the SAP database. If you try to open the existing backup specifications, the source database can neither be expanded nor selected, and although the database was properly configured in AppRM, you will see the following error message.
Figure 10: SAP backup error in Data Protector
Additional SAP-related limitations and workarounds are described later in this document.

Modify schedules

After migrating to AppRM, scheduled Oracle backups fail because of the missing destination device. To enable the backups to run successfully, you should add the target devices to the backup specification. However, depending on the backup policy of your organization, you can then choose whether to use the selected device or not. In Data Protector you can schedule a tapeless backup by selecting disk only backup. This option is available in the Data Protector scheduler, and can be selected for new schedules. Since you cannot add this option to existing schedules, you will have to recreate the existing schedules.

Figure 11: Disk only option for schedules in Data Protector
When you select the To Disk option, it appears in the schedules screen as seen below:
Figure 12: Disk only option for schedules in Data Protector
As described above, you need to reconfigure SAP instances and recreate the backup specifications and schedules when the environment is upgraded to Data Protector. To reconfigure the SAP environment and create the backup specifications, see the Data Protector zero downtime backup integration guide.

SAP non-compliance mode

If you are using AppRM in noncompliance mode to backup your SAP environment, then you can configure the Data Protector backups in the same way you configured your AppRM backups.

SAP-compliance mode

Note that both AppRM and Data Protector can perform SAP-compliant backups using the splitint interface. There are however some differences as to how the backups are configured. Host selection In AppRM, after selecting the application host and backup host, you have an option to select the host on which the SAP BR*Tools (brbackup) should be started. According to the SAP-compliance mode, these tools should be started on the backup host, which can be selected at this stage.
Figure 13: SAP client selection in AppRM
However, in Data Protector, when you specify the application host and backup host for a snapshot backup, no such selection appears. The backup is always configured on the application host. SAP-compliance mode is selected in Data Protector by setting the OB2_MIRROR_COMP environment variable. The Data Protector documentation describes how to set up this variable. For saving the options for SAP BR*Tools (brbackup) on the backup host, Data Protector uses the environmental variable from the application host, SAPBACKUP. Hence make sure that it points to a directory that is reachable from both the hosts using the same path e.g. \\backuphost\share\sapbackup\, which is the location of the SAPBACKUP directory (share) on the backup host. In the case of Windows, set the following registry entry to specify this location: HKEY_LOCAL_MACHINE\SOFTWARE\SAP\<SID>\Environment\SAPBACKUP On HP-UX, you can mount the directory sapbackup from the application host to the backup host at the same location. To configure the SAP integration and create new SAP-compliant backup specifications, see the Data Protector zero downtime backup integration guide. Oracle instant client support In AppRM, when using SAP compliance mode it is possible to use an Oracle instant client at a customized location on the backup host. There is a provision to enter the location of the Oracle SQL*Plus binaries while configuring the integration:
Figure 14: Specifying SQL path in AppRM
However, since in Data Protector the integration is started by saving the application host options, this location is expected to be same on both hosts. As a result, a custom location of the Oracle installation on the backup host, where ORACLE_HOME is different that on the application host does not work. It is not necessary to install a database on the backup host; the Oracle binaries are sufficient. SAP instant recovery options In AppRM there are some restore-related options in the SAP restore context that are not present in Data Protector. In AppRM, you can specify which files can be preserved during the restore by creating and/or editing a list of files. By default, these are control files, log files and parameter

file. These files are moved away before the instant recovery and copied back in place for a rollforward of the database.
Figure 15: SAP restore options in AppRM
These options are not present in Data Protector 6.11. In Data Protector, these files must be manually copied away before starting the instant recovery. For further information regarding instant recovery of SAP systems, see the Data Protector zero downtime backup integration guide. Using a third-party backint utility Since AppRM does not offer tape backups, it is possible that your environment uses the backint interface from another vendor when using SAP compliance mode. However, Data Protector has a tape backup solution and also delivers a backint utility, so when you upgrade the existing AppRM setup and configure it to use Data Protector, you must use the backint utility provided by Data Protector. There is an option in the AppRM backup specification which allows you to start the third-party backint at the end of the session:
Figure 16: Option to start third party backint in AppRM
This option is not necessary in the case of Data Protector. You can achieve it by performing a disk only backup and a disk + tape backup:
Figure 17: Starting a disk only or disk + tape backup in Data Protector
Note: Using another vendors backint is currently not supported, but this functionality will be available in an upcoming release of Data Protector. Mismatch in environmental variables After configuring Data Protector for SAP-compliant backups, you may need to adjust the settings of the existing SAP installation. This includes setting SAPDATA_HOME and SAPBACKUP environment variables on both application and backup host. You should also change the backup_root_dir, stage_root_dir and compress_dir in the initSID.sap file on both the hosts to those mentioned below. In general, when you configure the following SAP-related environment variables, Data Protector backups should work in SAP-compliance mode. In the following description, the application host is the host on which the SAP application runs, and the backup host is that on which replicas/snapshots are mounted and tape backup takes place. On the application host: Environment variables SAPBACKUP=\\applicationhost.domain.com\sapbackup SAPDATA_HOME=<drive>\saphome\<SID> In initSID.sap backup_root_dir = \\applicationhost.domain.com\saphome\sapbackup stage_root_dir = \\applicationhost.domain.com\saphome\sapbackup compress_dir = \\applicationhost.domain.com\saphome\sapreorg On the backup host: Environment variable: SAPBACKUP=\\applicationhost.domain.com\saphome\sapbackup SAPDATA_HOME=\\applicationhost.domain.com\saphome Registry entries HKEY_LOCAL_MACHINE\SOFTWARE\SAP\APP\Environment\SAPBACKUP = \\applicationhost.domain.com\saphome\sapbackup HKEY_LOCAL_MACHINE\SOFTWARE\SAP\APP\Environment\SAPDATA_HOME = \\applicationhost.domain.com\saphome\

Note:The directory specified in SAPDATA_HOME in the above two examples (environment and registry) is the location where sapbackup and sapreorg directories exist, and not where the actual data files reside. In initSID.sap backup_root_dir = \\applicationhost.domain.com\saphome\sapbackup stage_root_dir = \\applicationhost.domain.com\saphome\sapbackup compress_dir = \\applicationhost.domain.com\saphome\sapreorg Note: In HP-UX environments, you can share the /mountpoint/saphome/sapbackup and /mountpoint/saphome/sapreorg directories from the application hosts to the backup hosts, thus eliminating the need of using the UNC paths of the application host.

Troubleshooting

BRBackup fails creating copy of the control file Problem At the time of backup, BRBACKUP requests Oracle to make a copy of the control file to the location specified in SAPBACKUP. If that location is not writable from Oracle, the backup fails with following error message:
BR0301E SQL error -1580 at location BrCtlCopy-1, SQL statement: '/* BRBACKUP */ ALTER DATABASE BACKUP CONTROLFILE TO '\\apphost.domain.com\saphome\sapbackup\CNTRLSID.DBF'' ORA-01580: error creating control backup file \\apphost.domain.com \saphome\sapbackup\CNTRLSID.DBF ORA-27040: file create error, unable to create file
Solution Check if the location \\backuphost.domain.com\saphome\sapbackup is writable from the application system. Also, check that the following SQL statement:
ALTER DATABASE BACKUP CONTROLFILE TO '\\apphost.domain.com \saphome\sapbackup\CNTRLSID.DB
can be executed from SQL*plus as a SAP user. If it works, the BRBACKUP session should also succeed without error. On Windows, this error can be resolved by running the Oracle processes under the Windows Domain account (instead of local system account). On HP-UX, checking the permission for the share where the control file copy is created could resolve the problem. Copy of control file already exists Problem There is also a possibility that the previous backup session or the SAP brbackup has not deleted the copy of the control file. In such cases the error message specifies this with an additional error message:
ORA-01580: error creating control backup file \\apphost.domain.com \saphome\sapbackup\CNTRLAPP.DBF ORA-27038: created file already exists OSD-04010: <create> option specified, file already exists BR0320E Copying of control file to \\apphost.domain.com \saphome\sapbackup\CNTRLSID.DBF failed BR0314E Collection of information on database files failed
Similarly, the following error message can also occur for the same reason:

BR0055I Start of database backup: bebmfgtk.qub 2009-10-01 23.03.52 BR0484I BRBACKUP log file: \\apphost.domain.com\saphome\sapbackup\bebmfgtk.qub BR0280I BRBACKUP time stamp: 2009-10-01 23.04.53 BR0641I Deletion of database file '\\apphost.domain.com\saphome\sapbackup\CNTRLSID.DBF' waiting for releasing it by Oracle.
Solution In such a case, manually delete the control file copy so that brbackup can create a new copy of the control file. Backup fails to get database configuration Problem Data Protector backup fails with the following or a similar error message:
[Critical] From: OB2BAR_OMNISAP@Apphost.domain.com "OMNISAP" Time: 9/30/2009 12:45:45 AM Cannot get ORA_NLS_CHARACTERSET parameter from the configuration
In the case of a SAP-compliant backup, util_sap.exe is started on the application host first. It reads all the options from the backup specification and environment and saves them in the location specified as SAPBACKUP. Then it starts util_sap.exe on the backup host where these options are read and the BR*Tools are started on the backup host. This error message occurs if the location where these options are written is not readable from the backup host. Solution Make sure that the location specified as SAPBACKUP in the environment is identical and accessible from both application and backup host.

For more information

www.hp.com/go/dataprotector
Copyright 2009 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation. UNIX is a registered trademark of The Open Group. 4AA2-9546ENA, October 2009