HP Application Recovery Manager software A.06.
Legal and notice information © Copyright 2008 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents About this guide ................................................................... 9 Intended audience ............................................................................................... 9 Documentation set ............................................................................................... 9 Guides ........................................................................................................ 9 Online help ..........................................................
Snapclone ........................................................................................... 29 Local replication integrating with HP-UX LVM mirroring ..................................... 31 3 Using Application Recovery Manager for ZDB and instant recovery ............................................................................ 33 Application Recovery Manager cells .................................................................... 33 Cell components .........................................
Freezing operation of the application or database ................................................. Creating a replica ............................................................................................. Replicating the data objects ......................................................................... Mounting the replica on the backup system ........................................................... Recording session information ................................................................
Figures 1 Application Recovery Manager graphical user interface ....................... 14 2 Zero downtime backup and instant recovery concept ............................ 18 3 Disk virtualization with RAID ............................................................. 22 4 Split mirror replication ...................................................................... 24 5 Creating a standard snapshot ........................................................... 26 6 Creating a vsnap ..........................
25 LVM mirroring configuration in a cluster .............................................. 67 26 BC snapshot configuration 1 ............................................................. 69 27 BC snapshot configuration 2 ............................................................. 70 28 BC snapshot configuration 3 ............................................................. 70 29 Supported LVM mirroring configuration 1 ...........................................
Tables 1 Documentation map ......................................................................... 11 2 Document conventions ...................................................................... 12 3 Disk arrays integrating with Application Recovery Manager .................. 39 4 Disk arrays integrating with Application Recovery Manager ..................
About this guide This guide describes zero downtime backup and instant recovery concepts and how these are used within Application Recovery Manager. Intended audience This guide is intended for users interested in understanding the concepts of the Application Recovery Manager zero downtime backup and instant recovery capabilities and who wish to improve backup strategies for high-availability systems.
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.
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. Documentation map Abbreviations The guide titles are all preceded by the words “HP Application Recovery Manager software”. Map The following table shows where to find information of different kinds.
X Support matrices X X X X X Supported configurations Troubleshooting CLI reference X Concepts guide X Product announcements Installation guide X Integration guide Requirements Administrator's guide X Getting started Online Help Recommendations X X X X X Document conventions and symbols Table 2 Document conventions Convention Element Blue text: Table 2 on page 12 Cross-reference links and e-mail addresses Blue, underlined text: http://www.hp.
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. Refer to the online Help for information about the Application Recovery Manager graphical user interface.
Figure 1 Application Recovery Manager graphical user interface General Information General information about Application Recovery Manager can be found at http:// www.hp.com/go/apprm. HP technical support For worldwide technical support information, see the HP support website: http://www.hp.
• Detailed questions Subscription service HP recommends that you register your product at the Subscriber's Choice for Business website: http://www.hp.com/go/e-updates After registering, you will receive e-mail notification of product enhancements, new driver versions, firmware updates, and other product resources. HP websites For additional information, see the following HP websites: • • • • • http://www.hp.com http://www.hp.com/go/software http://www.hp.com/service_locator http://www.hp.
About this guide
1 Overview Introduction Zero downtime backup (ZDB) and instant recovery (IR) have two great advantages over other backup and restore techniques: • Minimal downtime or impact on the application system during backup • Short restore times (minutes instead of hours) The growing requirement for data security for mission critical applications, together with the increasing sophistication of Storage Area Network (SAN) environments, has resulted in a rapid expansion in the use of large disk arrays containing RAID te
The first can cause major disruption to the application’s operation. The second can produce many large transaction log files, putting extra load on the application system. Zero downtime backup (ZDB) uses disk array technology to minimize the disruption. In very general terms, a copy or replica of the data is created or maintained on a disk array. This is very fast and has little impact on the application’s performance.
After the replica is created, the database returns to normal operation. Any subsequent backup operations are performed on the replica, leaving the database online and unaffected. In both cases, the effect on the application is limited to the period during which the replica is created, much less than with standard tape backup techniques.
the replica are restored directly to their original locations. Because the restore is performed internally within the array, it runs at very high speed. Once the restore is completed, the sections of the database/filesystem concerned are returned to their states at the time the replica was created and the application system can be re-enabled. Depending on the application/database concerned, this may be all that is required.
2 Replication techniques Disk array basics The replication techniques available depend on the type of disk array and the firmware/software installed. Disk arrays support disk virtualization techniques, which enable the creation of virtual disks, logical volumes, and so on. An array of physical disks is configured in such a way that it appears as one large block of data storage. This can then be divided into a number of virtual storage blocks, which are presented to the host/operating system.
Figure 3 Disk virtualization with RAID Various RAID levels are available, providing different levels of data redundancy, speed, and access time. In some cases, it is possible to adjust the balance between these attributes according to the amount of free storage available. RAID systems operate by distributing data across the physical disks and presenting them to the host as logical units, which, in turn, can be regarded as the physical disks considered in the previous disk virtualization illustration.
• data security The following sections discuss methods of replication within each of these two local replication. Local replication In local replication, data is replicated within the same disk array, that is, source and target volumes are both on the same array. There are two techniques: • Split mirror • Snapshot Advantages of local replication • The processes are fast. • Disruption to the application or filesystem involved is minimized.
Figure 4 Split mirror replication When a mirror is first created, data in it is synchronized until it is identical to that in the source volumes. During normal application usage, the mirror volumes are kept synchronized with the source volumes. Any updates to the source volumes are also applied to the mirror volumes. When a replica of the data at a fixed point in time is required for an administrative task (such as backup): 1.
Because there is a separate physical copy of data, there is a higher likelihood that these target volumes will remain intact and available, if the array hardware experiences a partial failure that impacts the source volumes. Snapshot replication Snapshot replicas are created at a particular instant and are immediately available for use. Unlike split mirror replicas, no data is copied initially, but rather, a duplicate of the original storage is created through virtualization.
Standard snapshot Figure 5 Creating a standard snapshot 1. At time T0, storage capacity equal to that taken up by the source volumes concerned is allocated on the array for the target volumes. No data is copied from the source storage blocks. Instead, pointers are mapped to the storage blocks holding the original data and the copy is completely virtual. From a host’s perspective, however, a complete replica of the source volumes at time T0 exists in the target volumes and it is ready for use. 2.
• The standard snapshot is not an independent duplicate of the original data. (It is however possible that in time, every single storage block in the source volume has been updated and therefore copied.) • Adequate space is guaranteed for the snapshot, even if all the data in the source volumes changes. • It is space-inefficient. Enough space is always reserved for all the data to be changed, though normally only part is used.
Figure 6 Creating a vsnap 1. At time T0, only pointers are copied to the target, as for a standard snapshot, but no space is reserved for the target volumes. The snapshot takes up no storage space other than that required for the pointers. 2. After snapshot creation, if T0 source data needs to be updated, “copy-on-write” is used, as in standard snapshots. Storage space is required only for the changed data. 3. As with standard snapshots, the snapshot is now partly real and partly virtual.
As with standard snapshots, when a backup system accesses the snapshot, it reads disk blocks from both the source volumes and the replica. Consequently both the application and the backup systems disk resources are used, which can result in the application performance degradation in cases where the array is excessively loaded. Snapclone Snapclone starts as a standard snapshot and ends up as a complete duplicate (or clone), similar to a split mirror replica.
1. Containers of the same size as the source volumes are allocated on the disk array if they do not exist yet. 2. Write cache policy on the source volumes is set to the write-through mode, so that all data in the cache is written to physical disks. 3. A background process starts to copy all unchanged data from source storage blocks to target storage blocks. At this point, the write cache policy automatically reverts to write back mode. 4.
Local replication integrating with HP-UX LVM mirroring Local replication integrating with HP-UX LVM mirroring is a specific integration, which reduces the amount of storage which needs to be replicated in order to get a complete version. Advantages of local replication integrating with LVM mirroring • Disk space usage is reduced by making a copy of part of the total disks used.
Replication techniques
3 Using Application Recovery Manager for ZDB and instant recovery Application Recovery Manager cells Application Recovery Manager uses the concept of the managed cell.
are both directly attached. The tape library or other tape device is optional and is used only by third-party backup software. Cell components For a typical Application Recovery Manager cell, operational software components should be installed on the hardware as shown in the following figure: Figure 9 Location of software components for ZDB+IR Cell Manager The Cell Manager is the main system in the cell.
The IDB contains information about backup details such as, backup durations and session IDs • Runs core Application Recovery Manager software • Runs Session Managers that start and stop backup and restore sessions and write session information to the IDB You can manage the Cell Manager from any system on the network on which the Application Recovery Manager graphical user interface (GUI) is installed.
Backup system It is the system to which a replica is presented after it is created, so it is the system by which the replica can be accessed for subsequent processing, whether or not the data contained in it is to be backed up to tape. It also performs various checks and administration functions. The backup system must have a relevant Application Recovery Manager ZDB Agent installed. In some cases, it may also require an Application Integration Agent.
User interfaces You can use either the Application Recovery Manager graphical user interface (GUI) or command-line interface (CLI) to perform ZDB+IR operations. GUI The GUI enables you to administer your ZDB environment from a single system. You can: • Create backup specifications for ZDB, schedule them, and start ZDB sessions. • Monitor active operations. • In the Instant Recovery context, browse for sessions marked for instant recovery, define necessary options, and start an instant recovery session.
Figure 10 Application Recovery Manager GUI CLI You can use the CLI to perform most ZDB+IR operations available in the GUI, but some administration tasks can only be done using the CLI: • Querying, synchronizing, and purging the ZDB database • Checking the consistency of the ZDB database 38 Using Application Recovery Manager for ZDB and instant recovery
• Manually deleting a replica or replica set when it is no longer needed, together with information on it stored in the ZDB database • Excluding or including replicas from use with Application Recovery Manager. • EVA only: Setting disk group pairs. For details on available commands, see the HP Application Recovery Manager software command line interface reference.
Figure 11 Example BC XP configuration For further examples of XP configurations, see “Supported HP StorageWorks Disk Array XP configurations” on page 60 Local replication integrating with LVM mirroring The Application Recovery Manager XP integration supports HP-UX Logical Volume Manager mirroring (LVM mirroring) in configurations where one logical volume on one physical disk (LDEV) is mirrored onto a logical volume on another physical disk (LDEV).
Figure 12 Example LVM mirroring configuration XP HP StorageWorks Enterprise Virtual Array The Application Recovery Manager EVA integration supports the creation of standard snapshots, vsnaps, and snapclones. For further examples of EVA configurations, see Appendix A on page 59. EVA storage presentation EVA uses virtualization technology, which organizes physical disks into disk groups. Each disk group is a storage pool from which virtual disks are allocated.
Local replication For local replication, the HP StorageWorks Business Copy (BC) EVA configuration is used. This enables you to create replicas to be used for instant recovery purposes (note that only snapclones can be used for instant recovery). With this, large replica sets can be used, the number of members being limited primarily by the available space on the array. The maximum number of standard snapshots and vsnaps is limited by the EVA storage system.
Figure 13 Example LVM mirroring configuration EVA Application integrations Application Recovery Manager supports integration of supported disk arrays with the following database applications and replication types (online or offline): • • • • Oracle—online and offline backup SAP R/3—online and offline backup Microsoft SQL Server—online backup Microsoft Exchange Server—online backup Microsoft Exchange Server and Microsoft SQL Server are supported through the VSS integration.
Application data consistency A simple ZDB of logical volumes or disks guarantees only filesystem consistency, but not application data consistency. After an instant recovery of such a backup, the database may not recover properly. For supported integrations, Application Recovery Manager ensures that the application is set in to backup mode (online backup) or shut down (offline backup), but you must back up transaction logs separately.
control the disk array(s) and the Application Recovery Manager Oracle and SAP integrations interact with the database applications. On Microsoft Windows, a new unified backup and restore interface — the Volume Shadow Copy Service (VSS) — coordinates the actors in the backup process. The VSS model provides a standardized interface to the applications (writers) and disk arrays (providers). The writers interact with the applications, providing a list of items that can be backed up.
Using Application Recovery Manager for ZDB and instant recovery
4 The replica life-cycle Overview This chapter describes the life-cycle of replicas, summarized in the following diagram. Figure 14 Replica life-cycle The path that a replica takes depends on how you specify backup and instant recovery options.
Creating replicas With both split mirror and snapshot replication techniques, the basic idea is the same: to produce copies or images of the storage volumes (source volumes) containing the specified data objects. These copies are created in other storage volumes (target volumes) on the same array, which can then be presented to a host system. In all cases, only complete source volumes on the array can be replicated.
After successful backup, details of the backup session are saved to the IDB. Replica sets A replica set is a collection of replicas created at different times using the same backup specification. Replica sets are normally used when creating replicas for instant recovery purposes. In Application Recovery Manager, the members of a set can undergo replica set rotation, either interactively or at times specified in the scheduler.
Instant recovery Instant recovery enables you to restore data objects to their states at a particular point in time. For details of the process, see “Instant recovery” on page 55. What happens to the replica afterwards depends on the array and the configuration: • XP: The replica becomes a mirror in synchronization with the recovered source. You can however configure the instant recovery so that the replica is retained afterwards.
5 ZDB session process ZDB process overview With conventional backup to tape, application operation is affected for the whole of the backup session, until the streaming of data to tape is complete. However, with Application Recovery Manager ZDB, application operation is only affected during the creation of a replica. The principle steps in a ZDB process are: 1. Locate the data objects for backup. See “Locating data objects” on page 51. 2. Freeze operation of the application database.
3. The application host is prepared, bringing data into a consistent state. For online backup, the database is quiesced. For offline backup, the database is brought offline. If the ZDB option Dismount application system is set ON, the filesystems involved are dismounted. Freezing operation of the application or database While a replica is being created, operation of the application or section of the database concerned must be frozen.
Creating a replica 1. A replica is created. 2. The application host is resumed. Any dismounted filesystem is remounted. In the case of an offline backup, the database can be put back online and normal operation started again. In the case of an online backup, transaction log files and cached information from the replica creation period are applied to the database. 3. The backup host environment is prepared for the replica’s disks and data. New devices are detected by scanning.
Recording session information At this stage, created replicas can be recycled for the next session. If instant recovery has been enabled, additional IR session information is stored in the IDB, and the replicas retained in case IR is required. Writing session information to the IDB ZDB session information is written to the IDB throughout the session, including information on data objects available for restore, as well as array specific information about the replica used for instant recovery purposes.
6 Instant recovery and other restore techniques from ZDB sessions Overview With instant recovery, you restore complete replicas, at high speed, with minimum impact on the application system. All volumes containing the data objects specified in the backup specification are returned to their states at a specific point in time. After a ZDB session, you can view the associated restore sessions in the Instant Recovery GUI context. Alternatively, you can use the Application Recovery Manager CLI.
During instant recovery, data in the source volumes is replaced by or copied from that in the target volumes internally within the array. This makes the restore very fast. Even though individual backup objects may be specified in the backup specification, it is generally not possible to restore just those individual backup objects; only a complete session can be selected for restore and, hence, only the complete replica can be restored.
3. Optionally (except with VSS integration), perform a preview of the instant recovery session to provide an extra level of security. 4. Start the instant recovery. Application Recovery Manager then: 1. Starts processes on the application and backup systems. 2. Extracts the session information from the IDB and the array-specific information associated with the session from the ZDB database. 3.
Instant recovery and LVM mirroring Instant recovery is supported for ZDB sessions produced on HP-UX systems with an LVM mirroring plus BC XP or BC EVA configurations. However, it is necessary to perform additional manual steps. For information, see the HP Application Recovery Manager software administrator's guide. Instant recovery in a cluster Instant recovery is supported for an application or a filesystem running in a cluster environment on the application system.
A Supported configurations Introduction This appendix gives you information on the configurations supported on different disk arrays.
With all configurations, application and backup data can be spread across multiple disk arrays of the same type. Note that each configuration has a specific behavioral pattern imposing specific requirements on the control functions to guarantee backup and recovery functionality. Supported HP StorageWorks Disk Array XP configurations Local replication configurations Figures Figure 16 on page 61 through Figure 18 on page 62 are examples of supported local replication configurations on XP.
Figure 16 BC XP configuration 1 Figure 17 BC XP configuration 2 Concepts guide 61
Figure 18 BC XP configuration 3 Single-Host (BC1) configuration The following figure shows a single-host configuration, also called BC1 configuration: 62 Supported configurations
Figure 19 BC1 XP configuration Cascading configurations With the Application Recovery Manager XP integration, you can create two additional copies for each first-level mirror by using a cascading configuration. However, only first-level mirrors (to a maximum of three) are supported for instant recovery purposes. This means you can configure the integration to use cascading, but the additional second-level mirrors (up to six) can only be used for purposes other than ZDB+IR.
Figure 20 Cascading configuration Local replication configurations with HP-UX LVM mirroring Figures Figure 21 on page 65 through Figure 25 on page 67 are examples of supported LVM mirroring configurations on XP: 64 Supported configurations
Figure 21 LVM mirroring configuration 1 NOTE: The Application Recovery Manager design requires that either all devices in the PV1 columns have an XP mirror or all of the devices in the PV2 columns have an XP mirror. Mirrors of a logical volume must be fully hosted by physical volumes belonging to the same physical volume group. The physical extents of a mirror must be fully allocated from the physical volumes from the same array.
Figure 22 LVM mirroring configuration 2 Figure 23 LVM mirroring configuration 3 66 Supported configurations
Figure 24 LVM mirroring configuration 4 Figure 25 LVM mirroring configuration in a cluster Concepts guide 67
Supported HP StorageWorks Enterprise Virtual Array configurations Local replication configurations For local replication, BC EVA configuration is used. A separate backup system needs to be connected to a disk array. After the replicas are created, Application Recovery Manager scans for new disks on the backup system, creates device files (on UNIX), and performs all other necessary steps to mount the filesystems on the backup system so that it can access the replicated data.
Figure 26 BC snapshot configuration 1 Concepts guide 69
Figure 27 BC snapshot configuration 2 Figure 28 BC snapshot configuration 3 Local replication configurations with HP-UX LVM mirroring 70 Supported configurations
It is recommended to group the physical volumes of a volume group into physical volume groups (PVGs) and specify the PVG-strict policy for the mirror creation. With that, the mirrors of one logical volume will belong to different PVGs, which helps avoid certain situations, such as mirroring a logical volume onto the same disk.
Replicas are only created for those storage volumes that are found in that PVG. Later, these replicas are presented to the backup system for further backup of the selected backup objects. Both PVG-1 and PVG-2 satisfy the mirror selection rules. However, as SMI-S Agent always attempts to select a secondary mirror, it will choose PVG-2 for the BC pair replication. Figure 30 Supported LVM mirroring configuration 2 Only selected logical volumes are included in a backup specification.
Figure 31 LVM mirroring configuration 3 Some of the secondary mirror members are hosted by the primary mirror array, so they cannot be replication candidates. The primary mirror set is therefore selected for the BC pair replication. For more information about LVM mirroring and mirror selection rules, see the HP Application Recovery Manager software administrator's guide.
Supported configurations
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. 76 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. 80 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. 82 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. 84 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. 94 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. user account (Application Recovery Manager user account) You can use Application Recovery Manager only if you have an Application Recovery Manager user account, which restricts unauthorized access to Application Recovery Manager and to backed up data.
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. 98 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 Application Integration Agent, 35 Application integrations VSS, 44 Application Recovery Manager cell, 33 - 39 ZDB database, 36 application systems, 35 backup systems, 36 Cell Manager, 34 components, 34 Installation Server, 35 application systems, 35 audience, 9 B backup specifications, 48 backup systems, 36 BC configuration EVA, 42, 68 XP, 39 BC1 configuration XP, 62 Business Copy configuration See BC C cascading configuration XP, 63 Cell Manager, 34 clusters instant recovery, 58 configurations B
disk arrays, introduction, 21 - 22 RAID technology, 21 storage volumes, 21 disk arrays, supported ZDB techniques, 59 disk arrays, supported configurations, 39 EVA, 41 XP, 60 disk virtualization, 17, 21 document conventions, 12 related documentation, 9 documentation HP website, 9 providing feedback, 15 E Enterprise Virtual Array See EVA EVA, configurations BC, 42 EVA, backup local replication, 42, 68 local replication integrating with LVM mirroring, 42 remote plus local replication using LVM mirroring, 70 E
O offline backup, 18, 52 online backup hot-backup mode, 52 online backup, 18, 52 hot-backup mode, 18 Oracle integration, 43 R RAID technology, 21 related documentation, 9 replica sets, 49 rotation, 49 replicas creating, 19, 48, 53 deleting, 50 introduction, 19 lifecycle, 47 using, 49 replication local, 23 - 30 scheduling, 49 techniques, 22 restore from ZDB, 19 restore from ZDB, 55 instant recovery, 55 - 58 roll forward, 44, 55 S SAP R/3 integration, 43 scheduling replication, 49 single-host configuration,
W websites HP Subscriber's Choice for Business, 15 HP , 15 product manuals, 9 X XP, configurations BC, 39 LVM mirroring, 64 XP, backup, 39 local replication, 39 local replication integrating with LVM mirroring, 40 local replication, 60 - 64 local replication using LVM mirroring, 64 - 67 XP, configurations BC1, 62 cascading, 63 XP, restore, 50 instant recovery, 55 Z ZDB Agent, 35 ZDB database, 36, 54 ZDB, backup process, 51 - 54 creating replicas, 53 freezing database applications, 52 locating data objects
