HP Application Recovery Manager software A.06.
Legal and notice information © Copyright 2006, 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 ................................................................ 9 About this guide ................................................................. 11 Intended audience ............................................................................................. 11 Documentation set ............................................................................................. 11 Guides .............................................................................................
2 Backup ...................................................................... 29 Introduction ................................................................................................ Snapshot types ..................................................................................... Replica creation and reuse .................................................................... Replica redundancy level .......................................................................
6 Backup ...................................................................... 71 Introduction ................................................................................................ Backup concepts .................................................................................. Creating backup specifications ..................................................................... Backup options ...........................................................................................
Cell Manager and client on the application system in a cluster ........................ Client on the application system in a cluster, Cell Manager not in a cluster ....... Instant recovery in a cluster ............................................................................... MC/ServiceGuard .................................................................................... Microsoft Cluster Server ............................................................................. ZDB omnirc variables ....
Figures 1 Application Recovery Manager graphical user interface ....................... 16 2 Checking the mirrors ........................................................................ 33 3 EVA backup options ......................................................................... 35 4 Selecting a session .......................................................................... 51 5 XP backup options ...........................................................................
Tables 1 Edition history ................................................................................... 9 2 Documentation map ......................................................................... 13 3 Document conventions ...................................................................... 14 4 Redundancy levels for snapshots ........................................................ 31 5 Client systems 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 T4395-96004 October 2006 Application Recovery Manager Release A.06.00 N/A March 2008 Application Recovery Manager Release A.06.
Publication history
About this guide This guide provides information about: • configuring a disk array integration • using Application Recovery Manager zero downtime backup (ZDB) integrations for backing up data Conceptual information can be found in the HP Application Recovery Manager software concepts guide.
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 14 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
Part I. HP StorageWorks Enterprise Virtual Array This part describes how to configure and perform a zero downtime backup and instant recovery using the Application Recovery Manager HP StorageWorks Enterprise Virtual Array integration.
1 Configuration and maintenance Overview This chapter describes configuration of the Application Recovery Manager HP StorageWorks Enterprise Virtual Array (EVA) integration. It also provides information on the ZDB database and on how to maintain the integration. Prerequisites • Install: EVA components: • HP StorageWorks Virtual Controller Software (VCS) and Command View (CV) EVA. See the VCS and SMI-S EVA Provider documentation for installation instructions.
• Make sure the same operating system (and its version) is installed on the application and backup systems. • Connect the application and backup systems to the same EVA through SAN. • Check if the backup system is listed inside Command View EVA. • Using Command View EVA, create source volumes and present them to the application system. Prerequisites on Windows systems • Disable the operating system option Automatic mounting of new volumes.
• • • • • • • • • • Time when the session was performed Name of the backup specification used in the session Name, ID, and WWN of the target volume created in the session Name and ID of the EVA storage system on which the target volume resides Target volume type (vsnap, standard snapshot, snapclone) ID of the source volume used in the session IR flag (indicating that the target volume can be used for instant recovery) Purge flag (indicating that the target volume is intended for deletion) RAID level of the
For more information about LVM mirroring configurations, see “ZDB in HP-UX LVM mirroring environments” on page 31 and the HP Application Recovery Manager software concepts guide. For more information about LVM mirroring, see the HP-UX Managing Systems and Workgroups manual. To configure the integration: • Provide the login information for SMI-S EVA Provider running on a management system. See “Setting the login information for SMI-S EVA Provider” on page 24. • If desired, set disk group pairs.
performance degradation, since different physical disks are used for read and write operations on source volumes and the replica. To set disk group pairs, use the omnidbsmis command. See the omnidbsmis man page for command syntax and examples of manipulating the disk group pairs configuration file. The file template is as follows. # # # # # # # # # # # # # # # # HP Application Recovery Manager software A.06.
different from the network hostname, use the omnirc variable EVA_HOSTNAMEALIASES to define the backup system object name. Cluster environment: If the backup system is a cluster virtual server, configure host objects using Command View in such a way that only one cluster node is configured in one host object. Additionally, set the variable EVA_HOSTNAMEALIASES to the appropriate host object on each cluster node. For more information on the variable, see “ZDB omnirc variables” on page 106.
correct or if the SMI–S provider is currently operational. It just compares the saved data against the actual setup. This may provide misleading results, if the CV EVA or CV EVA SMI-S environment is not operating properly. If you use the results for an actual cleanup, verify the configuration first. The option checks also the entries which should be purged. To check SMISDB for consistency, use the omnidbsmis command. See the omnidbsmis man page for command syntax.
However, the intended use time for these replicas may exceed the time that is allowed by the current active rotation scheme, in which Application Recovery Manager automatically recycles the oldest replica. In such cases, you can exclude a session (a replica) from use (the replica set rotation and possibility to perform instant recovery) and thus preserve all target volumes of the replica.
2 Backup Introduction This chapter describes configuring a filesystem and disk image ZDB sessions using the Application Recovery Manager GUI. You should be familiar with EVA concepts and procedures and basic Application Recovery Manager ZDB and instant recovery functionality. See the EVA-related documentation and the HP Application Recovery Manager software concepts guide.
backup-related problem and possible workarounds, see “Backup problems” on page 57. Snapshot types Application Recovery Manager supports the following snapshot types: • Snapshots with pre-allocation of disk space (standard snapshots). • Snapshots without pre-allocation of disk space (vsnaps or Virtually Capacity-Free Snapshots). • A full copy of the source volume (original virtual disk), independent of the original virtual disk (snapclones).
Replica redundancy level EVA supports creations of snapshots and snapclones which have different storage redundancy level (RAID) than their source storage volumes. Vraid1 consumes the most storage space, followed by Vraid5 and then Vraid0. Standard snapshots and vsnaps cannot be created with more space-consuming RAID level than their source volumes have.
the first mirror copy. If such a mirror copy does not exist, the first mirror copy is backed up. If the ZDB_LVM_PREFERRED_PVG omnirc variable is set, the mirror copy residing in the PVG specified in the variable is backed up, provided that this mirror copy does not have stale extents. Otherwise, another mirror copy is selected for backup according to the algorithm described above. For more information on the ZDB_LVM_PREFERRED_PVG omnirc variable, see “ZDB omnirc variables” on page 106.
Figure 2 Checking the mirrors Administrator's guide 33
Creating backup specifications IMPORTANT: Before you begin, consider all limitations regarding the EVA integration. For more information, see the HP Application Recovery Manager software product announcements, software notes, and references and the HP Application Recovery Manager software concepts guide. 1. In the Context List, select Backup. 2. In the Scoping Pane, expand Backup Specifications. Right-click Filesystem (for both filesystem and disk image backup) and click Add Backup.
3. Under Client systems, select Application system and Backup system. Specify options as follows: To enable instant recovery, select Track the replica for instant recovery under Replica management options. Consequently, Snapshot type is automatically set to Snapclone and cannot be changed. The maximum number for vsnaps and standard snapshots is limited by the target EVA storage system. The GUI does not limit the number of replicas rotated, but the session will fail if the array specific limit is exceeded.
Under Snapshot management options, select Snapshot type and Redundancy level. TIP: For Snapclone snapshot type, select Delay any operations by a maximum of n minutes if the snapclones are not fully created. In this case, any subsequent operations (for example, backup to tape with third-party backup software) starts when the cloning process finishes, but not later than after the specified number of minutes.
5. In the Backup Specification Options group box, click the Advanced tab and then HP StorageWorks EVA SMI-S to open the EVA backup options. You can specify the Stop/quiesce the application and Restart the application options and modify all other options, except Application system and Backup system (note that you can change them after you save the backup specification). See “Backup options” on page 39. In the Filesystem Options group box, click Advanced and specify filesystem options as desired.
7. Filesystem backup: You can modify options for the listed object by clicking the object and then Properties. For information on the Object Property, press F1. Disk image backup: a. Click Manual add to add disk image objects. b. Select Disk image object and click Next. c. Select the client and click Next. d. Specify General Object Options. For information on these options, press F1. e. In the Disk Image Object Options window, specify disk image sections.
For information on how to find current disk numbers (physical drive numbers), see the online Help index: “disk image backups”. f. Click Finish and then Next. 8. Save your backup specification. For information on starting and scheduling ZDB sessions, see Chapter 9 on page 91. Backup options The following tables describe EVA and ZDB related backup options.. Table 5 Client systems options Application system System on which the application runs.
Standard snapshot Snapclone (default) Redundancy level Creates snapshots with the pre-allocation of disk space. For more information on snapshot types, see the HP Application Recovery Manager software concepts guide. Creates a clone of the source volume. Select the redundancy level to be used for the target volumes. If you create vsnaps and standard snapshots, the selected redundancy level should be of the same or lower quality than the one used for the source volumes.
Note that if the filesystem on the application system is busy and cannot be dismounted, the backup session will fail. Default: not selected. Stop/quiesce the application Create a command which you can use as the Stop/quiesce the application option. The command must reside in /opt/omni/lbin (UNIX) or AppRM_home\bin (Windows) on the application system and you specify only the filename in the backup specification. This command is executed on the application system before replica creation.
Default: Windows: C:\mnt UNIX: /mnt NOTE: For SAP R/3 integration, the option is not applicable (mount points created are always the same as on the application system. Create the mount path with the attributes Available only if Use the same mount points as on the application system is not selected. This option allows discrete control over the created mount points. When Session ID is used in path creation, this guarantees unique mount points.
Leave the backup system enabled If this option is not selected, Application Recovery Manager dismounts filesystems, exports volume groups (HP-UX), and unpresents the target volumes on the backup system after each backup. If this option is selected, the filesystems remain mounted, the volume groups remain imported and active (HP-UX), and the target volumes remain presented.
Backup
3 Restore Introduction This chapter describes configuring and running a filesystem or disk image restore of the data backed up using the EVA integration. The sections describe restore procedures using the Application Recovery Manager GUI and CLI. Instant recovery Instant recovery restores data directly from a replica to source volumes. All data in the replica is restored, including filesystems or other objects which were not explicitly selected for backup.
Limitations • Instant recovery fails in the following situations: • The source volumes are not presented to the application system. • If the current configuration of the participating volume groups on UNIX or partitions on Windows is different from the volume group/partition configuration during the backup and recorded in the SMISDB. • After instant recovery, restored filesystems are mounted to the same mount points or drive letters on the application system as they were at the backup time.
Advantages • Restore is very fast, regardless of the amount of data that was backed up. • The old source volumes can be retained after restore. Disadvantages • It is not possible to perform another restore from the same backup. • If a replica to be restored belongs to a different disk group than its source volumes, the disk group of the replica becomes the disk group of the source volumes after instant recovery.
Copying replica data without retaining the source volume With this method, the source volumes to be replaced are first converted into a container and then reused for the creation of new snapclones from the replica. The procedure is the same as reusing the oldest replica in a replica set during backup. The old source volumes are not retained and if the restore session fails, the original application data residing on the source volumes is lost.
NOTE: During an instant recovery session you cannot perform a ZDB using the source volumes to which the data is being restored. Instant recovery using the GUI 1. In the Context List, select Instant Recovery.
2. Select the backup session (replica) from which you want to perform the recovery. This can be done by selecting: • Backup session ID and name (in the Scoping Pane, expand Restore Sessions and select the session) • Backup object type (filesystem, Disk Image, SAP R/3, ...) and backup session name and ID: a. In the Scoping Pane, expand Restore Objects. Backed up object types are displayed. b. Expand the object type you want to restore.
Figure 4 Selecting a session 3. In the Scoping Pane, click the backup session (replica) you want to restore. The application system and its mount points or drive letters representing source volumes backed up during the selected session are displayed. Note that on UNIX all logical volumes inside a volume group and on Windows all partitions on a disk were backed up and if you did not select them all, they are not displayed here. 4.
5. Specify instant recovery options (see “Instant recovery options” on page 52 or press F1 for information). 6. Select Start Restore Session to start instant recovery, or Start Preview Session to start the preview. Click OK. Instant recovery using the CLI 1. List all available ZDB sessions (identified by the session ID): omnidbsmis -list -session -ir From the output, select the backup session you want to restore. 2.
Application Recovery Manager GUI/CLI Function to disks in the original storage and then the disks are switched with the source volume disks. The old source volumes are retained. • With the Retain source for forensics option not selected, the source volumes are overwritten during the copy process. Even if the instant recovery fails, you may lose the data in the source volumes.
Application Recovery Manager GUI/CLI Function from the replica to the restore location. Since this process may impact the application system performance, you can wait for the copy to complete before session continues. You can influence the control of the process by omnirc variables. See “EVA specific variables” on page 107.
Application Recovery Manager GUI/CLI Function Force remove presentations from replica storage/ If this option is selected and any snapclone to be restored is presented to some other system than the backup system, the SMI-S Agent removes these presentations. If this option is not selected but presentations exist, instant recovery fails.
1. Reduce the mirrors using the lvreduce command. Only the mirror copy that was backed up should remain.
4 Troubleshooting Before you begin This chapter lists general checks and verifications plus problems you may encounter when using the EVA integration. For general Application Recovery Manager troubleshooting information, see the HP Application Recovery Manager software troubleshooting guide. • Ensure that the latest official Application Recovery Manager patches are installed. See the online Help index: “patches” on how to verify this.
SMI-S Agent is always started as an administrator’s process on the application and backup systems. Therefore, the user who starts it must be the member of admin or operator user groups. Action Using the GUI, check if the user is a member of admin or operator user groups. If not, add the user to one of these groups. In addition, ensure that administrators from both the application and backup systems belong to Application Recovery Manager admin or operator.
Action Ensure that no other processes use the filesystem to be dismounted. If Stop/quiesce the application was specified, check that it stops all processes using the filesystem. Problem On Windows, replica cannot be mounted to the target location on the backup system [Major] Filesystem \\.\Volume{9640da9a-6f36-11d7-bd7a-000347add7ba} could not be mounted to C:\mnt. ([145] The directory is not empty.).
1. On the backup system, set ZDB_VOLUMESCAN_RETRIES and ZDB_POST_RESCAN_DELAY omnirc variables to moderately higher values (defaults are 5 retries and 30 seconds delay time). 2. Restart the backup session. Problem Application Recovery Manager fails to delete a replica from the replica rotation set in a cluster environment A backup session reports the following major error and then normal message: [Major] Resolving of storage volume 'target_volume_ID' has failed. ... [Normal] Some disks are still in use.
Instant recovery problems Problem Instant recovery fails The problem may occur if the option Force remove presentations from replica storage is not selected and a snapclone from the selected replica is presented to some other system than backup system or the snapclone cannot be dismounted. Action Select the option Force remove presentations from replica storage and restart instant recovery.
Troubleshooting
Part II. HP StorageWorks Disk Array XP This part describes how to configure, perform a zero downtime backup, and an instant recovery using the Application Recovery Manager HP StorageWorks Disk Array XP integration.
5 Configuration and maintenance Introduction This chapter describes the configuration of the Application Recovery Manager HP StorageWorks Disk Array XP (XP) integration. It also provides information on the ZDB database and on how to maintain the integration. Prerequisites • Ensure that you have Business Copy (BC) XP microcode and license. • Install: XP components: • RAID Manager Library on the application and backup systems. See the RAID Manager Library documentation for installation instructions.
• Create pair relationships between both sets of LDEVs Prerequisites on Windows systems • Disable the operating system option Automatic mounting of new volumes. At Command Prompt, run: mountvol /N • Do not manually mount target volumes that have been created by Application Recovery Manager. Limitations • In a cluster environment, the backup system must not be in the same cluster with the application system. The backup system also cannot be virtual server of a cluster. It can only be a cluster node.
Objects and their mirror configurations during backup and restore sessions are kept in XPDB for replica set rotation and instant recovery. Only LDEV pairs recorded in XPDB can be used for instant recovery. XPDB resides on the Cell Manager in: • HP-UX: /var/opt/omni/server/db40/xpdb • Windows: AppRM_home\db40\xpdb Configuring the integration In a cluster environment, the backup system must not be in the same cluster with the application system. The backup system also cannot be virtual server of a cluster.
is started), Application Recovery Manager generates a list of command devices connected to every application and backup system in the cell. • Every command device is assigned an instance number (starting from 301) and the system (hostname) having access to it. If a command device can be accessed from more than one system, Application Recovery Manager recognizes that the command device is assigned to another system; such command device-hostname combination gets the next available instance number.
Use the omnidbxp command to: • • • • Set and change the exclude file Identify excluded LDEVs Reset the exclude file Delete the content of the exclude file See the HP Application Recovery Manager software command line interface reference or omnidbxp man page for command syntax and the examples of manipulating the exclude file. The file syntax and the example are given below: Syntax # HP Application Recovery Manager software A.06.
• XPDB information about a particular LDEV pair See the HP Application Recovery Manager software command line interface reference or the omnidbxp man page for command syntax and the examples.
6 Backup Introduction This chapter describes configuring filesystem and disk image ZDB using the Application Recovery Manager GUI. You should be familiar with XP concepts and procedures and basic Application Recovery Manager ZDB and instant recovery functionality. See the XP-related documentation and the HP Application Recovery Manager software concepts guide. Backup concepts XP backup consists of one phase (optionally two, if third–party backup software is used): 1.
Creating backup specifications IMPORTANT: Before you begin, consider all limitations regarding the XP integration. For more information, see the HP Application Recovery Manager software product announcements, software notes, and references and the HP Application Recovery Manager software concepts guide. 1. In the Context List, select Backup. 2. In the Scoping Pane, expand Backup Specifications. Right-click Filesystem (for both filesystem and disk image backup) and click Add Backup.
5. Under Backup Specification Options, click Advanced and then HP StorageWorks XP to open XP backup options. Here, you can specify Application system options, and modify all other options, except Application system and Backup system (note that you can change them after you save the backup specification). See “Backup options” on page 75. In the Filesystem Options group box, click Advanced and specify filesystem options as desired. For information, press F1. Figure 5 XP backup options 6.
7. Depending on the type of the backup: • Filesystem backup: Click Next. • Disk image backup: a. Click Manual add to add disk image objects. b. Select Disk image object and click Next. c. Optionally, enter the description for your object. Click Next. d. Specify General Object Options. For descriptions of these options, press F1. Click Next. e. In the Disk Image Object Options window, specify disk image sections.
Backup options The following tables describe XP and ZDB related filesystem backup options. Table 11 Client systems options Application Recovery Manager GUI Function Application system System on which the application runs. In cluster environments, specify the virtual server hostname (rather than the physical node hostname). Backup system System to which your data will be replicated.
If integrated applications (for example, Oracle) run on the filesystem, they control data consistency, so it is not necessary to dismount filesystems before the split. Note that if the filesystem on the application system is busy and cannot be dismounted, the backup session will fail. Default: not selected. Table 13 Replica management options Track the replica for instant recovery Select this option to enable instant recovery.
Select this option to mount the filesystems on the replica to the same mount points on the backup system as used on the application system. If the mount points are already in use, the session will fail. You can select the option Automatically dismount the filesystems at destination mount points to prevent this. On Windows, the drive letters must be available, or the session will fail. Default: not selected. Available only if Use the same mount points as on the application system is not selected.
c:\mnt\app.comp.com\2008–02–22–4\E\disk1 If Session ID is selected: c:\mnt\2008–02–22–4\E\disk1 If Session ID and hostname is selected: c:\mnt\2008–02–22–4\app.comp.com\E\disk1 NOTE: For SAP R/3 integration, the option is not applicable (mount points created are always the same as on the application system.
import the backup system volume groups and filesystem in read-only mode. For other tasks, read/write mode may be needed. Note that if this option is selected, the replica is open to modification while the backup system is online. Consequently, instant recovery from such a replica includes all potential modifications. Default: not selected. The chart below provides detailed backup flow according to the backup options selected.
Figure 6 Split mirror backup flow 80 Backup
7 Restore Introduction This chapter describes configuring and running a filesystem or disk image restore of the data backed up using the XP integration. The sections describe restore procedures using the Application Recovery Manager GUI and CLI. The data backed up in a ZDB session is stored on a disk array, or in case you are using third–party backup software, on backup media. Instant recovery Instant recovery restores data directly from a replica to source volumes, without involving a tape device.
IMPORTANT: After instant recovery, restored filesystems are mounted to the same mount points/drive letters as they were at the backup time. If these mount points/drive letters have other filesystems mounted, these filesystems are automatically dismounted before instant recovery, and the restored filesystems are mounted afterwards.
2. Select the backup session (replica) from which you want to perform the recovery. This can be done by selecting: • Backup session ID and name (in the Scoping Pane, expand Restore Sessions and select the session from a list of sessions) • Backup type (filesystem, Oracle, SAP R/3,...) and backup specification name and ID: a. In the Scoping Pane, expand Restore Objects. Backed up object types (Filesystem, Disk Image, SAP R/3, ...) are displayed. b. Expand the object type you want to restore.
Figure 7 Selecting a session 3. In the Scoping Pane, click the backup session you want to restore. The application system and its mount points/drive letters backed up during the selected session are displayed. 4. Select the application system and specify the instant recovery options (see “Instant recovery options” on page 85). 5. Click Restore to start instant recovery, or Preview to preview it (filesystem backup only). 6.
Instant recovery options Table 15 Instant recovery options Application Recovery Manager GUI/CLI Function Check the data configuration consistency/-check_config If this option is selected on UNIX, the current configuration of the participating volume groups is compared with the volume group configuration during the backup session kept in XPDB. If the configuration changed since then, the restore fails.
3. Extend the logical volume containing LVM mirroring disks (using the lvextend -m command) with the LVM mirror disk that was previously excluded from the logical volume. Instant recovery in a cluster For information on instant recovery with an application or filesystem running on MC/ServiceGuard or Microsoft Cluster Server, see “Instant recovery in a cluster” on page 104 for instructions.
8 Troubleshooting Before you begin This chapter lists general checks and verifications plus problems you may encounter when using the XP integration. For general Application Recovery Manager troubleshooting information, see the online Help index: “troubleshooting”. • Ensure that the latest official Application Recovery Manager patches are installed. See the online Help index: “patches” on how to verify this.
Action In the Stop/quiesce the application script, stop all processes using the filesystem. Use appropriate operating system tools or utilities to get a list of processes that are using the filesystem in order to identify any processes that lock the filesystem. For example, lsof on HP-UX. Problem On the backup system, mounting of a filesystem fails Action Check that the directory exists in which the mount points are created exists is writable.
Action 1. In the backup specification, specify an existing and configured LDEV/MU# on the backup system, or ensure that LDEV/MU# stated in the output is not set in the XP LDEV exclude file. 2. Restart the session. Problem In some initial configurations on windows, filesystems may not be resolved on the backup system. The filesystem does not show up at all, even with manual pair or split. Action Uninstall the XP disk from the device manager and rescan the system.
Troubleshooting
9 Running and scheduling ZDB sessions You run ZDB by scheduling a backup or starting an interactive backup session. Scheduling ZDB sessions To schedule a filesystem or disk image ZDB, create a new or modify an existing backup specification. For detailed steps, see the online Help index: “scheduling backups on specific dates and times”. For general information on scheduling, see the online Help index: “scheduled backups”.
Figure 8 Scheduling a ZDB Starting interactive ZDB sessions Prerequisites • In a Microsoft Cluster Service configuration, if a cluster resource disk is to be backed up, it should not be in a maintenance mode before the backup. NOTE: When running concurrent ZDB sessions using one or several application systems, consider the limitations described in the HP Application Recovery Manager software concepts guide. Using the GUI 1. In the Context List, select Backup. 2.
Using the CLI Run: omnib -datalist Name where Name is the backup specification name. See the omnib man page for details.
Running and scheduling ZDB sessions
10 Internal Database Maintenance Overview The IDB is an internal database, located on the Cell Manager that keeps information regarding which data is backed up, on which disks it resides, the result of backup and recovery sessions, and which disk arrays are configured. What is the IDB used for? The information stored in the IDB enables the following: • • • • Fast and convenient restore You are able to browse sessions to be restored. Backup management You can verify the result of backup sessions.
The internal databases and configuration must be backed up separately and not by using the Filesystem backup because Application Recovery Manager must be stopped before you can back up the internal databases and configuration and restarted after the successful backup. Application Recovery Manager offers the dbtool.pl utility to back up the database and configuration to a safe location.
1. Configure the backup location and backup behavior: Windows: cd AppRM_home\bin perl.exe dbtool.pl -config Root=backup_location SizeLimit=limitMB CountLimit=number_of_kept_backups HP-UX: cd /opt/omni/bin ./dbtool.pl -config Root=backup_location SizeLimit=limitMB CountLimit=number_of_kept_backups 2. To manually start the backup, run: Windows: perl.exe dbtool.pl -backup HP-UX: ./dbtool.pl —backup 3.
NOTE: In the Windows steps below, it is assumed that the perl.exe command is in the search path list for commands (defined by environment variable PATH). If not, specify the full pathname. 1. Change the directory: Windows: cd AppRM_home\bin HP-UX: cd /opt/omni/bin 2. Start the restore: Windows: perl.exe dbtool.pl -restore HP-UX: ./dbtool.pl —restore This will restore your latest backup of the IDB and configuration.
A Appendix Alternate paths support For systems with multiple host adapters and connections to a disk array, the alternate paths solution performs dynamic load balancing and monitors each path to ensure that I/O completes its transactions. If a path between a disk array and a server fails, alternate path software automatically switches to an alternate path, removing the failed path from I/O rotation without data loss. Switchover is transparent to applications, so they continue unaffected.
For more information on cluster support, see the HP Application Recovery Manager software product announcements, software notes, and references and the online Help index: “cluster”. Sections below discuss supported ZDB cluster configurations. Figures Figure 9 to Figure 12 illustrate Application Recovery Manager application backup configurations and scenarios.
Figure 9 Client on the application system in a cluster, Cell Manager in a cluster Cell Manager on the backup system in a cluster Scenarios • Cell Manager failover during backup: session is automatically restarted, provided the option Restart backup of all objects is set. • Cell Manager failover in between backups: session completes successfully. Install: • On the application system: application binaries, Application Recovery Manager integration software component, Application Recovery Manager ZDB agent.
• On the backup system on all cluster nodes on local disks: Application Recovery Manager integration software component, Application Recovery Manager ZDB agent. Figure 10 Cell Manager on the backup system in a cluster Cell Manager and client on the application system in a cluster Scenarios • Application or Application Recovery Manager failover during backup: session is restarted automatically. • Application or Application Recovery Manager failover in between backups: session completes successfully.
• On the backup system on local disks: Application Recovery Manager integration software component, Application Recovery Manager ZDB agent. • Configure Cell Manager cluster’s critical resources in the same cluster group as those for the application being backed up. Figure 11 Cell Manager and client on the application system in a cluster Client on the application system in a cluster, Cell Manager not in a cluster Scenarios • Application failover during backup: session fails and must be restarted manually.
Figure 12 Client on the application system in a cluster Instant recovery in a cluster With an application or filesystem running on MC/ServiceGuard or Microsoft Cluster Server on the application system, instant recovery requires some additional steps. Additionally, there are limitations regarding instant recovery on Microsoft Cluster Server. IMPORTANT: If HP-UX LVM mirroring is used, see also “Instant recovery and LVM mirroring” on page 85. MC/ServiceGuard 1.
2. In the shell script for starting, shutting down and monitoring the database, comment the lines that monitor application processes (by putting # at the beginning of the line). Oracle example #set -A MONITOR_PROCESSES ora_pmon_${SID_NAME} ora_dbw0_${SID_NAME} ora_ckpt_${SID_NAME} ora_smon_${SID_NAME} ora_lgwr_${SID_NAME} ora_reco_${SID_NAME} ora_arc0_${SID_NAME} This shuts down the application (database) running in the cluster without causing a failover. 3.
Microsoft Cluster Server Limitations • Instant recovery of a cluster quorum disk is not supported because the cluster service must never lose the connection with the quorum disk, which happens during instant recovery (when disks are unpresented). • In the configuration where a local disk is mounted to a cluster resource disk, instant recovery of a such disk is not supported. Considerations • In a Microsoft Cluster Server environment, disks are distinguished by their disk signature.
Common ZDB variables This section explains omnirc variables that can be set for all ZDB agents. ZDB_ALWAYS_POST_SCRIPT: By default, the command set by the Restart the application option is not executed if Stop/quiesce the application fails. If this variable = 1, the command set by Restart the application is always executed. Default: 0. ZDB_IR_VGCHANGE: On HP-UX platform, determines the mode in which replicated volume groups on the application system are activated after restore.
EVA_HOSTNAMEALIASES: Allows a given ID to match the EVA host objects. Default: no hostnames specified. To add more hostnames to the search, specify hostname object names for this variable.
ZDB_SMISA_LVM_MIRRORING_DISABLED: By using ZDB_SMISA_LVM_MIRRORING_DISABLED, you disable LVM mirroring and continue performing ZDB sessions in your older configurations, unsupported by LVM mirroring. Default: 0 (LVM mirroring enabled). Possible: 0|1. SMISA_BACKUPPREPARE_RETRY: Determines the number of SMI-S Agent queries checking for completion of container allocation or creation and setting write cache policy on the source volumes to the write-through mode during zero downtime backup sessions.
ZDB_BACKUP_VG_EXIST: On HP-UX platform, for systems configured with multiple HBAs and connections to a disk array, the alternate paths solution performs dynamic load balancing. By default, during preparation for backup and restore, Application Recovery Manager creates a volume group with the disk on the first HBA as the primary path. To disable volume group autoconfiguration on the backup host and load balance the data across multiple paths manually, set this variable to 1.
Default: 2 seconds. SSEA_SYNC_REPORT_RATE: During the disks’ resynchronization, XP Agent checks the mirrored disks’ status in intervals determined by SSEA_SYNC_SLEEP_TIME. SSEA_SYNC_REPORT_RATE determines the rate of displaying the mirrored disks status. For example, if SSEA_SYNC_SLEEP_TIME is 5 seconds and SSEA_SPLIT_REPORT_RATE is 2, the status is displayed for every second check (every 10 seconds). Default: 2.
Appendix
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. 114 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. 118 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. 120 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. 122 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. 132 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. 136 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 alternate paths, 99 audience, 11 automatic configuration of backup system EVA, 25 B backup EVA considerations, 29 EVA troubleshooting, 57 XP concepts, 71 backup options EVA, 39 XP, 75 backup overview XP, 71 backup considerations EVA, 29 backup overview EVA, 29 backup specification configuring on EVA, 34 configuring on XP, 72 C checks and verifications XP troubleshooting, 87 checks and verifications: EVA troubleshooting;, 57 cluster specifics instant recovery, 104 cluster configurations, 99 comman
E EVA automatic configuration of backup system, 25 backup options, 39 backup considerations, 29 backup overview, 29 checks and verifications, 57 configuration prerequisites, 23 configuring, 24 configuring backup specification, 34 general overview, 21 instant recovery, 45 instant recovery considerations, 45 instant recovery in a cluster, 56 instant recovery options, 55 instant recovery using CLI, 52 instant recovery prerequisites, 48 instant recovery using GUI, 49 maintaining, 26 prerequisites, 21 RAID level
O omnirc variables, 106 common ZDB, 107 EVA specific, 107 - 109 - 111 XP specific, 109 options backup, EVA, 39 backup, XP, 75 instant recovery, EVA, 55 instant recovery, XP, 85 P preparing environment LVM mirroring, EVA, 23 LVM mirroring, XP, 67 prerequisites EVA , 21 XP , 65 purging SMISDB, 27 PVG-strict mirroring, EVA, 23 PVG-strict mirroring, XP, 67 Q querying SMISDB, 26 XPDB, 69 R RAID level EVA, 31 related documentation, 11 replica creation and reuse EVA, 30 restore introduction EVA, 45 restore over
W websites HP Subscriber's Choice for Business, 17 HP , 17 product manuals, 11 X XP backup options, 75 backup overview, 71 backup concepts, 71 checks and verifications, 87 command devices, 67 configuration prerequisites, 67 configuring, 67 configuring backup specification, 72 general overview, 65 instant recovery, 81 instant recovery in a cluster, 86 instant recovery options, 85 instant recovery prerequisites, 82 instant recovery using GUI, 82 instant recovery using CLI, 84 LVM mirroring, 85 maintaining, 6
