1. Manuals
  2. Brands
  3. HP Manuals
  4. Software
  5. Data Protector A.06.11
  6. Recovery manual

HP Data Protector A.06.11 Recovery Manual

Disaster recovery guide
Hide thumbs Also See for Data Protector A.06.11:
Table of Contents

Advertisement

Quick Links

Download this manual See also: User Manual
HP Data Protector A.06.1 1

Disaster recovery guide

B6960-90154
Part number: B6960-90154
First edition: September 2009

Advertisement

Table of Contents
loading

Related Manuals for HP Data Protector A.06.11

Summary of Contents for HP Data Protector A.06.11

  • Page 1: Disaster Recovery Guide

    HP Data Protector A.06.1 1 Disaster recovery guide B6960-90154 Part number: B6960-90154 First edition: September 2009...
  • Page 2 Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services.

  • Page 3: Table Of Contents

    Integrations ..................17 Document conventions and symbols ..............19 Data Protector graphical user interface ..............20 General information ..................21 HP technical support ..................21 Subscription service ................... 22 HP websites ...................... 22 Documentation feedback ..................22 1 Introduction ..............23 Overview ......................
  • Page 4 Consistent and relevant backup ................34 Creating a consistent and relevant backup ............. 35 Encrypted backups ..................35 Updating and editing the system recovery data (SRD) ..........36 Updating using the SRD update wizard ............37 Updating using omnisrdupdate ..............37 Updating using a post-exec script ..............
  • Page 5 Updating the ASR diskettes using the CLI interface ......... 112 Unlocking volumes locked with Windows BitLocker Drive Encryption ....112 4 Disaster recovery for UNIX ..........115 Manual disaster recovery of an HP-UX client ............115 Overview ....................115 Using custom installation medium ..............116 Overview ..................
  • Page 6 Enhanced automated disaster recovery and one button disaster recovery ....142 Intel Itanium specifics ................. 146 Automated system recovery ................147 A Further information ............149 Move kill links on HP-UX 1 1.x ................149 Windows manual disaster recovery preparation template ........149 Glossary ................. 151 Index ................209...
  • Page 7 Figures Data Protector graphical user interface ..........21 Verifying the default block size ............58 WinFS options tab ................61 Verifying the default block size ............73 Windows Vista and Windows Server 2008 client backup options ..77 Verifying the Default Block Size ............89 Creating ASR set ................
  • Page 8 Tables Edition history ................... 9 Document conventions ..............19 Overview of disaster recovery methods ..........26 How to determine the filesystem type from the SRD File ......46 Example of the AMDR preparation template ........46...

  • Page 9: Publication History

    Guide updates may be issued between editions to correct errors or document product changes. To ensure that you receive updated or new editions, subscribe to the appropriate product support service. See your HP sales representative for details. Table 1 Edition history...
  • Page 10 Publication history...

  • Page 11: About This Guide

    Documentation & Help component on Windows or the OB2-DOCS component on UNIX. Once installed, the guides reside in the Data_Protector_home\docs directory on Windows and in the /opt/omni/doc/C directory on UNIX. You can find these documents from the Manuals page of the HP Business Support Center website: http://www.hp.com/support/manuals In the Storage section, click Storage Software and then select your product.
  • Page 12 This guide describes the integrations of Data Protector with Oracle, SAP R/3, and SAP DB/MaxDB. • HP Data Protector integration guide for IBM applications: Informix, DB2, and Lotus Notes/Domino This guide describes the integrations of Data Protector with the following IBM applications: Informix Server, IBM DB2, and Lotus Notes/Domino Server.
  • Page 13 HP Data Protector integration guide for HP Reporter This manual describes how to install, configure, and use the integration of Data Protector with HP Reporter. It is intended for backup administrators. It discusses how to use the application for Data Protector service management.

  • Page 14: Online Help

    • HP Data Protector product announcements, software notes, and references This guide gives a description of new features of HP Data Protector A.06.1 1. It also provides information on installation requirements, required patches, and limitations, as well as known issues and workarounds.

  • Page 15: Documentation Map

    Documentation map Abbreviations Abbreviations in the documentation map that follows are explained below. The guide titles are all preceded by the words “HP Data Protector”. Abbreviation Guide Command line interface reference Concepts Concepts guide Disaster recovery guide Getting started guide...

  • Page 16: Map

    Abbreviation Guide Install Installation and licensing guide MO GS Media Operations getting started guide MO RN Media Operations product announcements, software notes, and references MO UG Media Operations user guide MPE/iX MPE/iX system user guide Product announcements, software notes, and references Trouble Troubleshooting guide ZDB Admin...

  • Page 17: Integrations

    Integrations Look in these guides for details of the following integrations: Integration Guide HP Operations Manager for UNIX/for Windows IG-OMU, IG-OMW HP Performance Manager IG-PM/PA HP Performance Agent IG-PM/PA Disaster recovery guide...
  • Page 18 Integration Guide HP Reporter IG-R HP Service Information Portal IG-SIP HP StorageWorks Disk Array XP all ZDB HP StorageWorks Enterprise Virtual Array (EVA) all ZDB HP StorageWorks Virtual Array (VA) all ZDB IBM DB2 UDB IG-IBM Informix IG-IBM Lotus Notes/Domino...

  • Page 19: Document Conventions And Symbols

    Document conventions and symbols Table 2 Document conventions Convention Element Blue text: Table 2 on page 19 Cross-reference links and e-mail addresses Blue, underlined text: http://www.hp.com Website addresses Italic text Text emphasis • File and directory names • System output Monospace text •...

  • Page 20: Data Protector Graphical User Interface

    NOTE: Provides additional information. TIP: Provides helpful hints and shortcuts. Data Protector graphical user interface Data Protector provides a cross-platform (Windows and UNIX) graphical user interface. You can use the original Data Protector GUI (Windows only) or the Data Protector Java GUI. For information about the Data Protector graphical user interface, see the online Help.

  • Page 21: General Information

    General information General information about Data Protector can be found at http://www.hp.com/go/ dataprotector. HP technical support For worldwide technical support information, see the HP support website: http://www.hp.com/support Before contacting HP, collect the following information: • Product model names and numbers •...

  • Page 22: Subscription Service

    Subscription service HP recommends that you register your product at the Subscriber's Choice for Business website: http://www.hp.com/go/e-updates After registering, you will receive e-mail notification of product enhancements, new driver versions, firmware updates, and other product resources. HP websites For additional information, see the following HP websites: •...

  • Page 23: Introduction

    1 Introduction Overview This chapter provides a general overview of the disaster recovery process, explains the basic terms used in the Disaster Recovery guide and provides an overview of disaster recovery methods. A computer disaster refers to any event that renders a computer system unbootable, whether due to human error, hardware or software failure, virus, natural disaster, and so on.
  • Page 24 Hosting system is a working Data Protector client used for Disk Delivery Disaster Recovery with Disk Agent installed. Auxiliary disk is a bootable disk that has a minimal operating system with networking and Data Protector Disk Agent installed. It can be carried around and used to boot the target system in Phase 1 of Disk Delivery Disaster Recovery of UNIX clients.

  • Page 25: Disaster Recovery Process

    Online recovery is performed when Cell Manager is accessible. In this case most of Data Protector functionalities are available (Cell Manager runs the session, restore sessions are logged in the IDB, you can monitor the restore progress using GUI, and so on).

  • Page 26: Disaster Recovery Methods

    This section provides a general overview of disaster recovery methods. For a list of supported disaster recovery methods for a particular operating system, see the latest support matrices at http://www.hp.com/support/manuals. NOTE: Each disaster recovery method has limitations you should consider before implementation.
  • Page 27 Phase 0 Phase 1 Phase 2 Phase 3 Full client backup, Windows: Windows: Restore critical Restore user and IDB backup (Cell Connect a volumes using DDDR wizard, application data Manager only), replacement disk remove the replacement disk using the standard create auxiliary to a hosting from the hosting system and...

  • Page 28: Manual Disaster Recovery Method

    Phase 0 Phase 1 Phase 2 Phase 3 Full client backup, Boot the system Critical volumes are restored. Restore user and ASR diskettes with from the Windows Additional steps to perform application data an updated SRD installation advanced recovery tasks are using the standard file and DP medium and enter...

  • Page 29: Disaster Recovery Using Disk Delivery

    With manual recovery, it is important to collect the information regarding the storage structure, which is not kept in flat files (such as partition information, disk mirroring, and striping). Disaster recovery using disk delivery This method is supported on Windows and UNIX clients. On Windows clients, the disk of the affected system (or the replacement disk for the physically damaged disk) is temporarily connected to a hosting system.

  • Page 30: Automated System Recovery (Asr)

    IMPORTANT: You need to prepare a new OBDR boot tape after each hardware, software or configuration change. This also applies to any network configuration changes, such as change of IP address or DNS server. Automated System Recovery (ASR) Automated System Recovery (ASR) is an automated system on Windows systems, which reconfigures a disk to its original state (or resizes the partitions if the new disk is larger than the original disk) in the case of a disaster.

  • Page 31: Data Protector Integrations And Disaster Recovery

    Ensure that the database/application server has the required Data Protector client software installed and is configured for the database/application. Follow the procedures in the appropriate HP Data Protector integration guide. Start the restore. When the restore is complete, follow the instructions of the database/application vendor for any additional steps required to bring the database back online.
  • Page 32 Introduction...

  • Page 33: Planning And Preparing For A Disaster Recovery

    2 Planning and preparing for a disaster recovery In this chapter Carefully follow the instructions in this chapter to prepare for a disaster recovery and to ensure fast and efficient restore. Preparation does not depend on the disaster recovery method, however, it does include developing a detailed disaster recovery plan, performing consistent and relevant backups and updating the SRD file on Windows.

  • Page 34: Consistent And Relevant Backup

    Plan Planning must be prepared by IT administration and should include the following: • Determine the systems that need to be recovered as well as the time and level of recovery. Critical systems are all systems required for network to function properly (DNS servers, domain controllers, gateways, and so on), Cell Managers and Media Agent clients.

  • Page 35: Creating A Consistent And Relevant Backup

    On UNIX systems, some daemons or processes are active as soon as the system finishes booting, for various reasons (HP-UX example: License server at run level-2). Such an early process may even read the data into memory and write a “dirty flag” into some file while it runs.

  • Page 36: Updating And Editing The System Recovery Data (Srd)

    Data Protector A.06.1 1 introduces changes in the encryption model compared to Data Protector A.06.00. The encryption keys are stored on the Cell Manager so the disaster recovery client must either be connected to the Cell Manager to get the encryption key or you must provide the encryption key on a removable medium.

  • Page 37: Updating Using The Srd Update Wizard

    SRD. The SRD can be updated only on a Windows client. The name of the updated SRD file is recovery.srd. There are three different methods possible for updating the SRD file: • Update SRD File wizard • omnisrdupdate command as a standalone utility •...
  • Page 38 passed session_ID value. After the SRD is updated it will be saved back on the Cell Manager. This procedure will only succeed if all critical backup objects (as specified in the SRD file) were actually backed up during the specified session. To view which objects are considered as critical for the SRD update, open the SRD file in a text editor and find the objects section.

  • Page 39: Updating Using A Post-Exec Script

    store an updated copy of the SRD file on the floppy disk and in the SRDfiles share on computer with the hostname computer2, type omnisrdupdate -session 2002/05/02-5 -host computer.company.com -location a: -location \\computer2\SRDfiles Make sure that you have the write permission on that share. Updating using a post-exec script Another method to update the SRD is using the omnisrdupdate command as a backup post-exec script.
  • Page 40 IMPORTANT: You should restrict access to the SRD files due to security reasons. Planning and preparing for a disaster recovery...

  • Page 41: Disaster Recovery For Windows

    The following sections explain how to prepare and execute an Assisted Manual Disaster Recovery on Windows systems. For details on supported operating systems, refer to the HP Data Protector product announcements, software notes, and references. Overview The general procedure for Assisted Manual Disaster Recovery of a Windows client Phase 0 Perform a full client backup and an IDB backup (Cell Manager only).

  • Page 42: Requirements

    Phase 2 Execute the Data Protector drstart command that will install the DR OS and start the restore of critical volumes. The system must be restarted after the drstart command finishes. Additional steps are required if you are recovering a Cell Manager or performing advanced recovery tasks.
  • Page 43 CAUTION: It is too late to prepare for a disaster recovery once a disaster has occurred. See also “Planning” on page 33, for the general preparation procedure for all disaster recovery methods before completing the steps listed in this section. To recover from a disaster quickly and efficiently, consider the following steps and prepare your environment accordingly: You need a Windows bootable installation CD-ROM to enable your system to...
  • Page 44 Ensure that the following is true: • You should have a successful full client backup. See See the online Help index: “backup, Windows specific” and “backup, configuration”. • You should have a SRD file updated with information about backed up objects in the chosen successful backup session.
  • Page 45 For Windows systems running on a 32–bit platform, copy the contents of Data_Protector_program_data\Depot\DRSetupX86 (Windows Server 2008), Data_Protector_home\Depot\DRSetupX86 (other Windows systems), or \i386\tools\DRSetupX86 (Data Protector installation medium) onto three floppy disks (drsetup diskettes). For Windows systems running on the AMD64/Intel EM64T platform, copy the contents of Data_Protector_program_data\Depot\DRSetupX64 (Windows Server 2008), Data_Protector_home\Depot\DRSetupX64 (other Windows systems), or \i386\tools\DRSetupX64 (Data Protector installation medium)

  • Page 46: How To Determine The Filesystem Type From The Srd File

    In order to re-create disk partitions to their initial state prior to the disaster, record the following information for each partition (it will be needed during the recovery process): • partitions length and order • drive letters assigned to the partitions •...
  • Page 47 Windows Service Pack Windows SP3 TCP/IP properties IP address 3.55.61.61 default gateway 10.17.250.250 subnet mask 255.255.0.0 DNS order 1 1.17.3.108, 1 1.17.100.100 Medium label / Barcode number "andes - disaster recovery" / [000577] Partition information and 1st disk label order 1st partition length 31 MB 1st drive letter...

  • Page 48: Recovery

    Recovery Follow the procedure below to recover a Windows system using Assisted Manual Disaster Recovery. If you are performing advanced recovery tasks (such as disaster recovery of a Cell Manager or IIS), see also “Advanced recovery tasks” on page 96. Install the Windows system from the CD-ROM and install additional drivers if needed.
  • Page 49 Install TCP/IP protocol. If DHCP was not used before the disaster, configure the TCP/IP protocol as prior to the disaster by providing the following information: hostname of the affected client, its IP address, default gateway, subnet mask and DNS server. Make sure that the field labeled Primary DNS suffix of this computer contains your domain name.

  • Page 50: Disk Delivery Disaster Recovery Of A Windows Client

    If the recovery.srd file is saved in the same directory as dr1.cab and omnicab.ini files, drstart copies recovery.srd file to the %SystemRoot%\system32\OB2DR\bin directory and the omnidr utility is started automatically. Otherwise, enter the location of SRD file (recovery.srd) in the SRD Path field or browse for the file. Click Next. If multiple SRD files are found on the floppy disk, Data Protector will ask you to select an appropriate version of the SRD file.

  • Page 51: Overview

    Data Protector Any remaining partitions can be recovered by using the standard Data Protector recovery procedure. For details on supported operating systems, refer to the HP Data Protector product announcements, software notes, and references. TIP: This method is specially useful with hot swap hard disk drives, because you can disconnect a hard disk drive from a system and connect a new one while the power is still on and the system is operating.

  • Page 52: Requirements

    Requirements • The partitions have to be the same size or larger than the partitions on the failed disk. This way the information stored on the failed disk can be restored to the new one. Also, the type of filesystem format has to match (FAT, NTFS). •...

  • Page 53: Recovery

    In order to re-create disk partitions to their initial state prior to the disaster, record the following information for each partition (it will be needed during the recovery process): • partitions length and order • drive letters assigned to the partitions •...

  • Page 54: Enhanced Automated Disaster Recovery Of A Windows System

    Enhanced Automated Disaster Recovery of a Windows system Data Protector offers an enhanced disaster recovery procedure for the Windows Cell Manager and clients. For details on supported operating systems, refer to the HP Data Protector product announcements, software notes, and references. Disaster recovery for Windows...

  • Page 55: Overview

    EADR collects all relevant environment data automatically at backup time. During a full backup, data required for the temporary DR OS setup and configuration is packed in a single large DR OS image file and stored on the backup tape (and optionally on the Cell Manager) for each backed up client in the cell.

  • Page 56: Requirements

    The Data Protector Automatic Disaster Recovery component must be installed on clients for which you want to enable recovery using this method and on the system, where the DR CD ISO image will be prepared. See the HP Data Protector installation and licensing guide.
  • Page 57 • Replacement disks have to be attached to the same host bus adapter on the same bus. • The boot partition (on which the DR OS is installed) must be larger than 200 MB or disaster recovery will fail. If you enabled the Compress drive option to save disk space option on the original partition, you must have 400 MB free.

  • Page 58: Verifying The Default Block Size

    Figure 2 Verifying the default block size • A backup of all necessary data for disaster recovery may require a significant amount of free space. While normally 500 MB is enough, up to 1 GB may be required depending on the operating system. •...

  • Page 59: Limitations

    Automated Installation Kit (WAIK) 1.1 installed. Older versions of WAIK are not supported. • To back up the IIS configuration object residing on a Windows Vista or Windows Server 2008 system, install the IIS 6 Metabase Compatibility package. Limitations • Dynamic disks are not supported (including mirror set upgraded from Windows NT).

  • Page 60: The Dr Iso Image File

    • all nodes • administrative virtual server (defined by the administrator) • if Data Protector is configured as a cluster aware application, Cell Manager virtual server and IDB. “Restoring the Microsoft Cluster Server specifics” on page 96 for details. After you performed the backup, merge the P1S files for all nodes in the MSCS, so that P1S file of each node contains information on the shared cluster volumes configuration.

  • Page 61: Winfs Options Tab

    Figure 3 WinFS options tab To copy the DR image files only for particular clients in the backup specification, perform the following steps: In the Context List, select Backup. In the Scoping pane, expand the Backup Specifications and then Filesystem. Select the backup specification you will use for a full client backup.

  • Page 62: The Kb.cfg File

    If data residing on Windows Vista or Windows Server 2008 systems will be backed up, select also Detect NTFS hardlinks and Use Shadow Copy, and clear Allow Fallback. Saving the full DR image to the Cell Manager is useful if you plan to burn the disaster recovery CD on the Cell Manager, because it is much faster to obtain the DR image from the hard disk than to restore it from a backup medium.

  • Page 63: The Phase 1 Startup File (P1S)

    DR-ClientName-keys.csv (Windows Server 2008), Data_Protector_home\Config\Server\export\keys\ DR-ClientName-keys.csv (other Windows systems), or /var/opt/omni/server/export/keys/DR-ClientName-keys.csv (UNIX systems), where ClientName is the name of the client for which the image is being created. Ensure that you have the correct encryption key for each backup that is prepared for a disaster recovery.

  • Page 64: Preparing Dr Iso Image

    Preparing DR ISO image To prepare a DR ISO image, perform the following steps: In the Context List, select Restore. Click the Tasks navigation tab and select Disaster Recovery. From the drop down list, select the client you would like to prepare the DR ISO image for.

  • Page 65: Recovery

    Record the DR ISO image on a CD using a CD recording tool that supports the ISO9660 format. IMPORTANT: Perform a new backup and prepare a new DR CD after each hardware, software or configuration change. This also applies to any network configuration changes, such as change of IP address or DNS server.
  • Page 66 Unless you are performing an offline disaster recovery, add the account with the following properties to the Data Protector Admin user group on the Cell Manager, depending on the operating system of the target system: Windows Vista and Windows Server 2008 systems: •...
  • Page 67 Boot the client system from the disaster recovery CD of the original system. Ensure that no external USB disks (including USB flash drives) are connected to the system before you start the recovery procedure. Press F12 when the following message is displayed: To start recovery of the machine HOSTNAME press F12.
  • Page 68 On Windows Vista and Windows Server 2008 systems, the DR OS is loaded first into memory and then the scope menu is displayed. On other Windows systems, the scope selection menu is displayed at the beginning of the boot process. Select the scope of recovery and press Enter.
  • Page 69 Windows Vista and Windows Server 2008 systems: If the volumes are encrypted using BitLocker Drive Encryption, a menu will display, enabling you to unlock the encrypted drives. See “Unlocking volumes locked with Windows BitLocker Drive Encryption” on page 112. After you have selected the scope of the recovery, Data Protector sets up the DR OS directly to the hard disk.

  • Page 70: One Button Disaster Recovery Of A Windows System

    One Button Disaster Recovery (OBDR) is an automated Data Protector recovery method for Windows clients and Cell Manager, where user intervention is reduced to minimum. For details on supported operating systems, refer to the HP Data Protector product announcements, software notes, and references.

  • Page 71: Overview

    single large OBDR image file and stored on the backup tape. When a disaster occurs, OBDR device (backup device, capable of emulating CD-ROM) is used to boot the target system directly from the tape which contains the OBDR image file with disaster recovery information.

  • Page 72: Requirements

    For more information about supported systems, devices and media, please refer to the HP StorageWorks Tape Hardware Compatibility Table on the World Wide Web: http://www.hp.com/support/manuals. Also see the HP Data Protector product announcements, software notes, and references.

  • Page 73: Verifying The Default Block Size

    • During OBDR backup, the partition on which Data Protector is installed should have at least 200 MB of temporary free space. This space is required to create a temporary image. • All drivers, required for boot must be installed under the %SystemRoot% folder. •...

  • Page 74: Limitations

    • If the system which will be backed up is a Windows Vista or Windows Server 2008 system, the Windows Automated Installation Kit (WAIK) 1.1 must be installed on it. Older versions of WAIK are not supported. • To back up the IIS configuration object residing on a Windows Vista or Windows Server 2008 system, install the IIS 6 Metabase Compatibility package.

  • Page 75: Obdr Backup

    Create a media pool for DDS or LTO media with Non-appendable media usage policy (to ensure that this will be the only backup on tape) and Loose media allocation policy (because the tape is formatted during OBDR backup). In addition, select this media pool as a default media pool for the OBDR device.
  • Page 76 Select backup options. For more details on available options, see the online Help index: “backup options”. Windows Vista and Windows Server 2008 systems: Specify the WAIK options: • Windows Automated Installation Kit (WAIK) directory Once you enter the location, Data Protector saves it and uses it as the default selection in the GUI the next time an DR ISO image is created.

  • Page 77: Windows Vista And Windows Server 2008 Client Backup Options

    Figure 5 Windows Vista and Windows Server 2008 client backup options Click Next to proceed to the Scheduler page, which can be used to schedule the backup. See the online Help index: “scheduling backups on specific dates and times”. Disaster recovery guide...

  • Page 78: The Kb.cfg File

    Click Next to display the Backup Object Summary page, in which you can review the backup options. NOTE: In the Summary page, you cannot change a previously selected backup device or the order in which the backup specifications follow one another (move up and move down functionalities are not available).

  • Page 79: Preparing The Encryption Keys

    boot relevant hardware or application configurations. The default kb.cfg file already contains all files necessary for industry standard hardware configurations. Create and execute a test plan using the default version of the kb.cfg file. If the DR OS does not boot normally or cannot access network, then you may need to modify the file.
  • Page 80 The following is a step-by-step procedure for performing a One Button Disaster Recovery of a Windows system: Disaster recovery for Windows...
  • Page 81 Unless you are performing an offline disaster recovery, add the account with the following properties to the Data Protector Admin user group on the Cell Manager, depending on the operating system of the target system: Windows Vista and Windows Server 2008 systems: •...
  • Page 82 Insert the tape containing the image file and your backed up data into an OBDR device. Shut down the target system and power off the tape device. Ensure that no external USB disks (including USB flash drives) are connected to the system before you start the recovery procedure.
  • Page 83 On Windows Vista and Windows Server 2008 systems, the DR OS is loaded first into memory and then the scope menu is displayed. On other Windows systems, the scope selection menu is displayed at the beginning of the boot process. Select the scope of recovery and press Enter.
  • Page 84 in advance during the disaster recovery session, before they are restored in the Data Protector restore session. The option is selected by default. • Remove Boot Descriptor: Available only on Intel Itanium systems. Removes all Boot Descriptors left over by the disaster recovery processes. See “Intel Itanium specifics”...

  • Page 85: Automated System Recovery

    Data Protector will then reestablish the previous storage structure and restore all critical volumes. The temporary DR OS will be deleted after the first login, except for the following cases: • Minimal Recovery is selected. • You interrupted the Disaster Recovery wizard during the 10 seconds pause (after it had found the DR installation and the SRD file on the backup medium), and selected the Debugs option.

  • Page 86: Overview

    Data Protector then recovers the target system to the original system configuration and finally restores all user data. For details on supported operating systems, refer to the HP Data Protector product announcements, software notes, and references. IMPORTANT: Perform a full client backup after each hardware, software, or configuration change and update the ASR diskettes.

  • Page 87: Requirements

    Requirements • Data Protector Automatic Disaster Recovery component must be installed on systems for which you want to enable recovery using ASR. See the HP Data Protector installation and licensing guide. • If you are using a firewall, ports 1071 and 1073 must be open. ASR does not support the OB2PORTRANGE and OB2PORTRANGESPEC variables.

  • Page 88: Hard Disk Drives

    Floppy disk drives and CD-ROM drives must be connected to IDE or SCSI controllers. External devices such as USB or PCMCIA devices are not supported. However, ASR using the USB flash drive is supported on HP Integrity servers (IA-64 platform). For details, see the “Recovering Windows Server 2003 on HP Integrity servers”...

  • Page 89: Limitations

    Figure 6 Verifying the Default Block Size Limitations • Windows XP Home Edition does not support ASR. • Multiboot systems that do not use Microsoft's boot loader are not supported. • Internet Information Server (IIS) Database, Terminal Services Database, and Certificate Server Database are not restored automatically during Phase 2.

  • Page 90: Preparation

    • Only those local backup devices are supported, that can be installed by Windows during OS installation (no additional drivers are required). Preparation See also “Planning” on page 33, for the general preparation procedure for all disaster recovery methods before completing the steps listed in this section. See also “Advanced recovery tasks”...
  • Page 91 Perform a full client backup. Insert a diskette in the floppy disk drive. In the HP Data Protector Manager, switch to the Restore context. Click the Tasks navigation tab and select Disaster Recovery in the Scoping Pane. From the drop down list in the Results Area, select the client for which you would like to create an ASR set.

  • Page 92: Creating Asr Set

    Click Create Automated System Recovery set and then click Next. Figure 7 Creating ASR set Data Protector will obtain the ASR archive file from the Cell Manager. If it is not saved on the Cell Manager, the Disaster Recovery wizard will offer you to recover it from the backup medium.

  • Page 93: Local Devices

    or DNS server. In order to update the first diskette from the ASR set, repeat the whole procedure, but you do not have to select the Copy DR installation check box. This option copies the DR installation files (to a selected destination), which do not need to be updated.
  • Page 94 After restart, Disaster Recovery wizard pops-up and requires input for the DR installation source and SRD Path. DR installation and SRD file are both located on the first diskette of the ASR set (a:\). To modify other ASR settings, press any key to stop the wizard during the countdown and select the options.

  • Page 95: User Name For Asr

    Unless you are performing an offline disaster recovery, add the client’s local system account to the Data Protector Admin user group on the Cell Manager. See the online Help index: “users, Data Protector”. Enter the same information as in Figure 8 on page 95.

  • Page 96: Advanced Recovery Tasks

    This section provides explanation of the steps you will need to take if you want to perform disaster recovery of a Microsoft Cluster Server (MSCS). For concepts and general information please refer to the clustering section in the HP Data Protector concepts guide and see the online Help index: “cluster”.

  • Page 97: Disaster Recovery Of A Secondary Node

    Disaster Recovery. All specifics, limitations and requirements pertaining a particular disaster recovery method you are going to use also apply for the disaster recovery of a MSCS. For details on supported operating systems, refer to the HP Data Protector product announcements, software notes, and references .

  • Page 98: Disaster Recovery Of The Primary Node

    You can restore the MSCS database after all nodes have been recovered and have joined the cluster to ensure its coherency. The MSCS database is part of the CONFIGURATION on Windows. See online Help index: “restore of configuration objects”. Disaster recovery of the primary node In this case all nodes in the MSCS are unavailable and the cluster service is not running.
  • Page 99 Perform disaster recovery of the primary node (including the quorum disk). • Assisted Manual Disaster Recovery: All user and application data on the quorum disk will be restored automatically by the drstart command. (-full_clus option) • EADR and OBDR: When you are asked to select the scope of recovery, select Full with Shared Volumes to restore quorum disk.
  • Page 100 The quorum and IBD volumes are restored. All other volumes are left intact and are claimed by the recovered primary node if they are not corrupted. If they are corrupted you have to: a. disable the cluster service and cluster disk driver (the steps required to do so are described in MSDN Q176970) b.
  • Page 101 UNIX Cell Manager only: The mmerge.cmd command works only on Windows systems with Data Protector Automatic Disaster Recovery component installed. If you are using a UNIX Cell Manager, copy the P1S files to a Windows client which has Automatic Disaster Recovery component installed and merge the files. Rename the merged P1S files back to the original name and copy them back to the Cell Manager.

  • Page 102: Automated System Recovery On A Majority Node Set Cluster

    Example At the command prompt type clubar r c:\temp\ClusterDatabase force q: to restore a MSCS Database from c:\temp\ClusterDatabase. For more information on clubar usage and syntax, see the clubar.txt file located in the Data_Protector_home\bin\utilns. If the Data Protector shared disk on the Cell Manager is different from the quorum disk, it has to be restored as well.

  • Page 103: Restoring The Data Protector Cell Manager Specifics

    Set up the MNS cluster and install a Data Protector client in it. Note that it is not possible to install a Cell Manager on a MNS cluster, it is not supported. Perform a filesystem backup, configuration backup, and an IDB backpup. Create an ASR disk set.

  • Page 104: Enhanced Automated Disaster Recovery Specifics

    Using the Data Protector GUI, recycle the medium or media with the backup of the partitions that remain to be restored for enabling the medium or media to be imported in the IDB. For more information on recycling media, see the online Help index: “recycling media”.

  • Page 105: One Button Disaster Recovery Specifics

    about objects and media is stored, when IDB is not available. If the SRD file is saved only on the Cell Manager, it is not accessible if the Cell Manager fails. See “Preparation” on page 42. • If your backups are encrypted, you must save the encryption key to a removable medium before a disaster occurs.

  • Page 106: Automated System Recovery Specifics

    Automated System Recovery specifics An additional step is required in Phase 0 if you are recovering Windows Cell Manager using Automated System Recovery (ASR): • ASR diskette for the Cell Manager should be prepared in advance. IMPORTANT: Perform a new backup and update the ASR diskette after each hardware, software, or configuration change.

  • Page 107: Editing The Kb.cfg File

    If this fails, stop the IIS Admin Service and restore the %SystemRoot%\system32\inetsrv\MetaBase.bin file, using the overwrite option. NOTE: %SystemRoot%\system32\inetsrv is the default location of IIS Service. If you have installed the service into other location, use this location as a destination for restore of MetaBase.bin file.

  • Page 108: Recovery Using An Edited Srd File

    • Logical device or drive (library) name (-dev). • Device type (-devtype). Refer to the sanconf man page or HP Data Protector command line interface reference for possible -devtype option values. • Device SCSI address (-devaddr). Disaster recovery for Windows...
  • Page 109 StorageWorks Ultrium standalone device with the device name Ultrium_dagnja, connected to the MA host dagnja (Windows). However, for the disaster recovery you would like to use an HP StorageWorks Ultrium robotics library with the logical library name Autoldr_kerala with drive Ultrium_kerala connected to the MA client kerala (Linux).

  • Page 110: Amdr/Asr

    -dev "Ultrium_dagnja" -devaddr Tape4:1:0:1C -devtype 13 -devpolicy 1 -mahost dagnja.company.com with something like: -dev "Ultrium_kerala" -devaddr /dev/nst0 -devtype 13 -devpolicy 10 -devioctl /dev/sg1 -physloc " 2 -1" -storname "AutoLdr_kerala" -mahost kerala.company.com. The procedure on using the edited SRD file for disaster recovery is different for each disaster recovery method.

  • Page 111: Install Only Option In The Disaster Recovery Wizard

    When the Disaster Recovery wizard appears, press any key to stop the wizard during the countdown, select the Install only option and click Finish. This option will install only the temporary operating system to the target system and thus finish Phase 1 of disaster recovery. Phase 2 of disaster recovery will not start automatically if the Install only option is selected.

  • Page 112: Updating The Asr Diskettes Using The Cli Interface

    Updating the ASR diskettes using the CLI interface Data Protector does not offer a command line interface command to automatically create ASR diskettes. However, you can manually update the contents of the first diskette in the ASR set by running the omnisrdupdate command. Insert the first diskette from the ASR set in to the floppy disk drive and specify a:\ as the location, for example: omnisrdupdate -session 11/04/2005-1 -host computer1.com...
  • Page 113 Check if the volume containing the password (for example an USB flash drive) is listed in the search path. The message will resemble the following: Search dir(s): [a:\] [d:\] If the path is not listed: a. Enter search. A new menu will display. b.
  • Page 114 1 14 Disaster recovery for Windows...

  • Page 115: Disaster Recovery For Unix

    4 Disaster recovery for UNIX Manual disaster recovery of an HP-UX client This section explains the procedure that should be used to recover an HP-UX client from a disaster. The procedure is based on the Ignite-UX product; an application primary developed...

  • Page 116: Using Custom Installation Medium

    Create a Golden Image of a client system. Phase 1 and 2 Replace the faulty disk with a replacement disk. Boot the HP-UX client from the Ignite-UX server and configure the network. Install the Golden Image from the Ignite-UX server. Phase 3 Use the standard Data Protector restore procedure to restore user and application data.
  • Page 117 This command will create a gzipped file depot in the specified directory on the system defined with the –d and -s options. Make sure that your HP-UX client has granted a passwordless access to the target system (an entry in the .rhosts file with the name of the client system on the target system) otherwise the command will fail.
  • Page 118 IP addresses is equal to the number of parallel booting clients. After the above described procedure is completed, you have a Golden Image of an HP-UX client (with a specific hardware and software configuration), which can be used to recover any client of a similar layout.

  • Page 119: Recovery

    CD based on the created Golden Image. Please refer to the Ignite-UX Administration Guide for more information. Recovery To recover an HP-UX client by applying the Golden Image, which is located on a NFS share on your network, perform the following steps: On the Client System: Replace the faulty hardware.

  • Page 120: Using System Recovery Tools

    The usage of the system recovery tools, bundled with the Ignite-UX, enables you a fast and easy recovery from a disk failure. The recovery archive of system recovery tools includes only essential HP-UX directories. However, it is possible to include other files and directories (for example, additional volume groups or the Data Protector files and directories) in the archive to speed up the recovery process.

  • Page 121: Preparation

    Preparation The easiest way to create a recovery archive of an HP-UX client is to use the Ignite-UX GUI on the Ignite-UX server. All GUI commands can also be executed from the command line. Refer to the Ignite-UX administration guide for more information.

  • Page 122: Recovery

    The tape creation process will now begin. Check the status and log file on the Ignite-UX server by right clicking the client icon and selecting Client Status. NOTE: Ignite-UX recommends the usage of 90m DDS1 backup tapes to ensure that the tape will work with all DDS with any DDS drive. Creating an archive using make_net_recovery The procedure for creating a recovery archive using make_net_recovery is almost the same as using make_tape_recovery.
  • Page 123 Data Protector restore procedure. Recovery from the network To recover an HP-UX client from a disaster via the network, follow the instructions on how to perform recovery with a Golden Image. Make sure you have selected the desired archive for the installation.

  • Page 124: Disk Delivery Disaster Recovery Of A Unix Client

    The administrator has to ensure (before the disaster) that enough data has been collected to correctly format and partition the disk. For details on supported operating systems, refer to the HP Data Protector product announcements, software notes, and references.

  • Page 125: Limitations

    The kill links include the basic services that would otherwise be suspended by moving to run level 1, and they are needed for the backup. For an example, see “Move kill links on HP-UX 1.x” on page 149. Disaster recovery guide...
  • Page 126 Ensure that rpcd is configured on the system (configure the variable RPCD=1 within the file /etc/rc.config.d/dce). This prepares the system so that it enters the state of minimal activity. The state can be characterized as follows: • Init-1 (FS_mounted, hostname_set, date_set, syncer_running) •...
  • Page 127 • You may want to restrict network access to the system, so that no one can log on to the system while the backup is running (for example, on HP-UX, overwrite inetd.sec and use inetd -c).

  • Page 128: Recovery

    Additionally, the root volume group to be restored has to be created on the repaired disk (for example, using vgimport on HP-UX). It will not look like a root volume group during the restore process. This is because the OS from the auxiliary disk will be running.

  • Page 129: Manual Disaster Recovery Of A Unix Cell Manager

    Start the Data Protector GUI and open a connection to the Cell Manager. Import the system with the auxiliary disk into the cell. 1 1. Select the version from which you want to restore. First list all the required media for the restore and make sure they are available.

  • Page 130: Limitation

    Reboot the system. Limitation For details on supported operating systems, refer to the HP Data Protector product announcements, software notes, and references. This description does not cover the recovery of a cluster environment. Depending on the configuration of the cluster environment, additional steps and modification to the environment are necessary.
  • Page 131 Prerequisites You will need the following to successfully perform a disaster recovery: • Media containing the last valid known backup of the root partition of the Cell Manager and IDB. • A device connected to the Cell Manager. The following steps need to be performed to recover a Cell Manager: Replace the affected disk.
  • Page 132 Disaster recovery for UNIX...

  • Page 133: Troubleshooting Disaster Recovery

    See “The autodr.log file” on page 133 for information where to find the error messages. For general Data Protector troubleshooting information, see the HP Data Protector troubleshooting guide. Before you begin •...

  • Page 134: Debugging The Disaster Recovery Session

    them are relevant to you and indicate that an error has occurred. These error messages are usually logged at the end of the log file with a traceback appended. There are four types (levels) of messages in the autodr.log (note that they do not correspond to the same report levels for messages that are reported at the end of a backup session in the Data Protector GUI): •...

  • Page 135: Enabling Debugs During A Disaster Recovery Session

    In the Disaster Recovery Wizard, select the check box to the left of the Debugs button. Figure 10 Enabling debugs during a disaster recovery session To specify the debug options, such as the location where the debugs are saved, click Debugs. By default, the debugs are saved into the %SystemRoot%\system32\OB2DR\tmp directory.

  • Page 136: Setting Omnirc Options During Disaster Recovery On Windows

    NET USE X: \\SystemName\SharedFolderForDebugOutput Password /USER:Username Setting omnirc options during disaster recovery on Windows For general information on omnirc options, see the HP Data Protector troubleshooting guide. If you need to set an omnirc option during the disaster recovery on Windows (except...

  • Page 137: The Drm.cfg File

    When the Disaster Recovery Wizard appears, press any key to stop the wizard during the countdown. Figure 12 Disaster recovery wizard Click Cmd to start the command prompt. Run the following command: echo variable > %SystemRoot%\system32\OB2DR\omnirc where variable is the omnirc option exactly as it should be written in the omnirc file.

  • Page 138: General Problems

    The drm.cfg file contains several parameters that you can modify and which affect the disaster recovery process, along with a description of their impact. The drm.cfg file is available only for EADR and OBDR. To change the variables: Copy the template file drm.cfg.tmpl to drm.cfg. The template is created during an installation or upgrade in Data_Protector_home\bin\drim\config, with all variables set to their default values.
  • Page 139 After the computer is again in the proper domain, click OK in the Network window. Windows will force you to reboot the system. To update this new state with disaster recovery, you should perform all necessary procedures (collecting system data, backup) once more, as described in the “Preparing for a Disaster Recovery”...

  • Page 140: Assisted Manual Disaster Recovery

    Action Disable automatic collecting of data for the disaster recovery method that failed. This will allow Data Protector to collect data needed for other methods. Set the variable OB2_TURNOFF_COLLECTING to one of the following values: 0 Default setting, data collection is turned on for all automatic methods (EADR, OBDR, ASR).

  • Page 141: Disk Delivery Disaster Recovery

    Disk delivery disaster recovery Problem Cannot find physical location of drives selected for disk delivery When performing Disk Delivery Disaster Recovery, you may receive the following error message: Cannot find physical location of drives selected for disk delivery Objects will be restored when creating a partition on the new disk, if you select a drive letter that has not been used before.

  • Page 142: Enhanced Automated Disaster Recovery And One Button Disaster Recovery

    If you are performing a Disk Delivery disaster recovery, Data Protector first tries to connect to the original client where the backup device was attached (Media Agent client) in order to use the same device for restore. However, when you are performing Disk Delivery disaster recovery of the affected Media Agent client where the backup has been made, Data Protector will not be able to connect to it and will proceed with offline restore and search for a local device for the restore.
  • Page 143 If the problem persists, uninstall the Data Protector Automatic Disaster Recovery component (so that at least Manual Disaster Recovery and Disk Delivery Disaster Recovery will work) and contact technical support. Problem Some non-critical errors were detected When using EADR or OBDR, it is possible that you will receive the following error: Some non-critical errors were detected during the collecting of Automatic DR data.
  • Page 144 CAUTION: Editing the registry incorrectly can result in failed disaster recovery. Problem Auto logon does not work Action Sometimes auto logon does not work and you have to manually log on using the DRM$ADMIN account. Problem Computer stops responding Action Check if the CD/tape is readable.
  • Page 145 Action • Mount the volume with a drive letter and verify it with the chkdsk /v /f command or wait until the system is completely restored and then recreate the original mount point. • Manually reboot the system directly to MiniOS (do not reboot from the recovery CD).

  • Page 146: Intel Itanium Specifics

    Action To create the ISO image for your client, use a client that has the old version of the disaster recovery module. If possible, upgrade all Windows 2000 clients to the new version. Intel Itanium specifics Problem After a failed or aborted disaster recovery, Boot Descriptors may be left in EFI On Intel Itanium systems, after a failed or aborted disaster recovery session, Boot Descriptors (named DRM Temporary OS) may be left in the EFI environment.

  • Page 147: Automated System Recovery

    Automated system recovery Problem Network problems during ASR Network problems can be the cause of different problems during ASR. For example, the target system has two network adapters installed and one of them had been disabled when the disaster recovery backup was performed. During ASR, all devices are enabled by default.
  • Page 148 To install the network driver before starting the Disaster Recovery, use the New Hardware Wizard, which can be invoked with the following command: %SystemRoot%\system32\rundll32 shell32.dll,Control_RunDLL hdwwiz.cpl • You may use the default ASR (DHCP) network installation. Follow the normal ASR procedure and press F8 when the following text is displayed in the Disaster Recovery wizard: Press F8 in the next 5 seconds to skip network configuration...

  • Page 149: A Further Information

    A Further information Move kill links on HP-UX 1 1.x Proceed as shown below on the system which you want to back up to move some links: # The system will go from "run-level" 4 to "run-level 1" # retaining the inetd, networking, swagentd services up.
  • Page 150 Drivers Windows Service Pack TCP/IP properties IP address default gateway subnet mask DNS order Medium label / Barcode number Partition information and 1st disk label order 1st partition length 1st drive letter 1st filesystem 2nd disk label 2nd partition length 2nd drive letter 2nd filesystem 3rd disk label...

  • Page 151: Glossary

    Glossary access rights user rights. ACSLS (StorageTek specific term) The Automated Cartridge System Library Server (ACSLS) software that manages the Automated Cartridge System (ACS). Active Directory (Windows specific term) The directory service in a Windows network. It contains information about resources on the network and makes them accessible to users and applications.
  • Page 152 an archived redo log is determined by the mode the database is using: • ARCHIVELOG - The filled online redo log files are archived before they are reused. The database can be recovered if an instance or a disk fails. A “hot” backup can be performed only when the database is running in this mode.
  • Page 153 associated with managing data and disk and provides striping and mirroring capabilities to optimize performance. automigration (VLS specific term) The functionality that allows data backups to be first made to the VLS' virtual tapes and then migrated to physical tapes (one virtual tape emulating one physical tape) without using an intermediate backup application.
  • Page 154 located (drive on Windows and mount point on UNIX). For integration objects — backup stream identification, indicating the backed up database/application items. • Description: For filesystem objects — uniquely defines objects with identical client name and mount point. For integration objects —...
  • Page 155 See also BCV. (HP StorageWorks Disk Array XP specific term) The Business Copy XP allows to maintain internal copies of HP StorageWorks Disk Array XP LDEVs for purposes such as data backup or data duplication. The copies (secondary volumes or S-VOLs) can be...
  • Page 156 BC VA (HP StorageWorks Virtual Array specific term) Business Copy VA allows you to maintain internal copies of HP StorageWorks Virtual Array LUNs for data backup or data duplication within the same virtual array. The copies (child or Business Copy LUNs) can be used for various purposes, such as backup, data analysis or development.
  • Page 157 (HP StorageWorks Disk Array XP specific term) Continuous Access XP allows you to create and maintain remote copies of HP StorageWorks Disk Array XP LDEVs for purposes such as data duplication, backup, and disaster recovery. CA operations involve the main (primary) disk arrays and the remote (secondary) disk arrays.
  • Page 158 The Catalog Database is a part of the IDB that contains information about backup, restore, object copy, object consolidation, object verification, and media management sessions. Depending on the selected logging level, it also contains file names and file versions. This part of the database is always local to the cell.
  • Page 159 Change Log (Windows specific term) A module that can be queried to Provider determine which objects on a filesystem have been created, modified, or deleted. channel (Oracle specific term) An Oracle Recovery Manager resource allocation. Every allocated channel starts a new Oracle process, which performs backup, restore, and recovery actions.
  • Page 160 cluster-aware It is an application that supports the cluster Application application Programming Interface. Each cluster-aware application declares its own critical resources (disk volumes (on Microsoft Cluster Server), volume groups (on MC/ServiceGuard), application services, IP names and addresses, and so on). cluster continuous (Microsoft Exchange Server specific term) Cluster continuous replication...
  • Page 161 It provides database consistency information used for recovery. copy set (HP StorageWorks EVA specific term) A pair that consists of the source volumes on a local EVA and their replica on a remote EVA.
  • Page 162 Data Replication (HP StorageWorks EVA specific term) A logical grouping of (DR) group EVA virtual disks. It can contain up to eight copy sets provided they have common characteristics and share a common CA EVA log.
  • Page 163 Dbobject (Informix Server specific term) An Informix Server physical database object. It can be a blobspace, dbspace, or logical log file. DC directory The Detail Catalog (DC) directory contains DC binary files, which store information about file versions. It represents the DCBF part of the IDB, which occupies approximately 80% of the IDB.
  • Page 164 tape a little and resumes to write to the tape, and so on. In other words, if the data rate written to the tape is less or equal the data rate which can be delivered to the device by the computer system, then the device is streaming.
  • Page 165 Disk Agent A component needed on a client to back it up and restore it. The Disk Agent controls reading from and writing to a disk. During a backup session, the Disk Agent reads data from a disk and sends it to the Media Agent, which then moves it to the device.
  • Page 166 The Demilitarized Zone (DMZ) is a network inserted as a "neutral zone" between a company's private network (intranet) and the outside public network (Internet). It prevents outside users from getting direct access to company servers in the intranet. DNS server In the DNS client-server model, this is the server containing information about a portion of the DNS database that makes computer names available to client resolvers querying for name...
  • Page 167 dynamic client client backup with disk discovery. EMC Symmetrix Symmetrix Agent (SYMA). Agent (SYMA) (EMC Symmetrix specific term) emergency boot (Informix Server specific term) The Informix Server configuration file file ixbar.server_id that resides in the directory INFORMIXDIR/etc (on Windows) or INFORMIXDIR\etc (on UNIX).
  • Page 168 A failover can occur mostly because of software or hardware failures or maintenance on the primary node. failover (HP StorageWorks EVA specific term) An operation that reverses the roles of source and destination in CA+BC EVA configurations. See also CA+BC EVA.
  • Page 169 (HP StorageWorks Disk Array XP specific term) HP StorageWorks Disk Array XP allows up to three mirror copies of a primary Disaster recovery guide...
  • Page 170 volume and each of these copies can have additional two copies. The three mirror copies are called first-level mirrors. See also primary volume number. flash recovery (Oracle specific term) Flash recovery area is an Oracle 10g/1 1g area managed directory, filesystem, or Automatic Storage Management disk group that serves as a centralized storage area for files related to backup and recovery (recovery files).
  • Page 171 Data_Protector_program_data\Config\Server\Options (Windows Server 2008), Data_Protector_home\Config\Server\Options (other Windows systems), or /etc/opt/omni/server/options (HP-UX or Solaris systems). group (Microsoft Cluster Server specific term) A collection of resources (for example disk volumes, application services, IP names, and addresses) that are needed to run a specific cluster-aware applications.
  • Page 172 HP Operations Manager, extending the managed domain. Plug-In (SPI) Through the Data Protector integration, which is implemented as an HP Operations Manager SMART Plug-In, a user can have an arbitrary number of Data Protector Cell Managers monitored as an extension to HP Operations Manager.
  • Page 173 HP StorageWorks A logical partition of a physical disk within an HP StorageWorks Virtual Array LUN Virtual Array. LUNs are entities that can be replicated in the HP StorageWorks Business Copy VA configuration, or can be used as standalone entities.
  • Page 174 See also backup types. incremental An incremental mailbox backup backs up all the changes made mailbox backup to the mailbox after the last backup of any type. incremental1 An incremental1 mailbox backup backs up all the changes made mailbox backup to the mailbox after the last full backup.
  • Page 175 Information Store (Microsoft Exchange Server specific term) The Microsoft Exchange Server service that is responsible for storage management. Information Store in Microsoft Exchange Server manages two kinds of stores: mailbox stores and public folder stores. A mailbox store consists of mailboxes that belong to individual users.
  • Page 176 ISQL (Sybase specific term) A Sybase utility used to perform system administration tasks on Sybase SQL Server. Java GUI Client The Java GUI Client is a component of the Java GUI that contains only user interface related functionalities and requires connection to the Java GUI Server to function.
  • Page 177 library Also called autochanger, jukebox, autoloader, or exchanger. A library contains media in repository slots. Each slot holds one medium (for example, DDS/DAT). Media are moved between slots and drives by a robotic mechanism, allowing random access to media. The library can contain multiple drives. lights-out A backup or restore operation that takes place outside of normal operation or...
  • Page 178 An LCR copy is used for disaster recovery because you can switch to the LCR copy in a few seconds. If an LCR copy is used for backup and if it is located on a different disk than the original data, then the I/O load on a production database is minimal.
  • Page 179 login ID (Microsoft SQL Server specific term) The name a user uses to log on to Microsoft SQL Server. A login ID is valid if Microsoft SQL Server has an entry for that user in the system table syslogin. login information (Oracle and SAP R/3 specific term) The format of the login to the Oracle information is user_name/password@service, where:...
  • Page 180 A mailbox store consists of a binary rich-text .edb file and a streaming native internet content .stm file. Main Control Unit (HP StorageWorks Disk Array XP specific term) An HP (MCU) StorageWorks XP disk array that contains the primary volumes for the CA and BC configurations and acts as a master device.
  • Page 181 During a restore or object verification session, a Media Agent locates data on the backup medium and sends it to the Disk Agent for processing. For a restore sssion, the Disk Agent then writes the data to the disk. A Media Agent also manages the robotics control of a library.
  • Page 182 See also shadow copy, shadow copy provider, replica, and writer. mirror (EMC target volume. Symmetrix and HP StorageWorks Disk Array XP specific term) mirror rotation (HP replica set rotation. StorageWorks Disk Array XP specific term)
  • Page 183 The Data Protector Media Session Manager, which runs on the Cell Manager and controls media sessions, such as copying media. MU number (HP StorageWorks Disk Array XP specific term) Mirror Unit number. An integer number (0, 1 or 2), used to indicate a first-level mirror. See also first-level mirror.
  • Page 184 OBDR capable A device that can emulate a CD-ROM drive loaded with a device bootable disk and can thus be used as a backup or boot device for disaster recovery purposes. object backup object. object The process of merging a restore chain of a backup object, consolidation consisting of a full backup and at least one incremental backup, into a new, consolidated version of this object.
  • Page 185 object verification A process that verifies the data integrity of specified backup session objects or object versions and the ability of selected Data Protector network components to deliver them to a specified host. Object verification sessions can be run interactively, or as specified in automated post-backup, or scheduled specifications.
  • Page 186 online backup A backup performed while a database application remains available for use. The database is placed into a special backup mode of operation for the time period that the backup application requires access to the original data objects. During this period, the database is fully operational, but there may be a small performance impact and log files may grow very quickly.
  • Page 187 Oracle instance (Oracle specific term) Each installation of an Oracle database on one or more systems. One computer system can have several instances of a database running. ORACLE_SID (Oracle specific term) A unique name for an Oracle Server instance. To switch among Oracle Servers, specify the desired ORACLE_SID.
  • Page 188 IP names and addresses) that are needed to run a specific cluster-aware application. pair status (HP StorageWorks Disk Array XP specific term) A mirrored pair of disks can have various status values depending on the action performed on it. The three most important status values are: •...
  • Page 189 Windows and as shell scripts on UNIX. See also post-exec. primary volume (HP StorageWorks Disk Array XP specific term) Standard HP (P-VOL) StorageWorks Disk Array XP LDEVs that act as a primary volume for the CA and BC configurations. The P-VOL is located in the MCU.
  • Page 190 CA and BC applications. The commands communicate through a RAID Manager instance with the HP StorageWorks Disk Array XP Disk Control Unit. This instance translates the commands into a sequence of low level SCSI commands.
  • Page 191 Recovery Catalog (Oracle specific term) A set of Oracle tables and views that are used by Recovery Manager to store information about Oracle databases. This information is used by Recovery Manager to manage the backup, restore, and recovery of Oracle databases. The recovery catalog contains information about: •...
  • Page 192 Remote Control (HP StorageWorks Disk Array XP specific term) The Remote Unit (RCU) Control Unit (RCU) acts as a slave of an MCU in a CA configuration. In bidirectional configurations, the RCU can act as an MCU. Removable (Windows specific term) A Windows service used for managing...
  • Page 193 A process that copies data from backup media to a client. resync mode (HP StorageWorks Disk Array XP VSS provider specific term) One of two XP VSS hardware provider operation modes. When the XP provider is in the resync mode, the source volume (P-VOL) and its replica (S-VOL) are in the suspended mirror relationship after a backup.
  • Page 194 By setting up a schedule, you automate the start of backups. secondary volume (HP StorageWorks Disk Array XP specific term) secondary (S-VOL) volumes, or S-VOLs, are XP LDEVs that act as a secondary CA or BC mirror of another LDEV (a P-VOL). In the case of CA, S-VOLs can be used as failover devices in a MetroCluster configuration.
  • Page 195 One binary file is created per session. The files are grouped by year and month. snapshot (HP StorageWorks VA and HP StorageWorks EVA specific term) A form of replica produced using snapshot creation techniques. Disaster recovery guide...
  • Page 196 StorageWorks EVA specific term) snapshot creation (HP StorageWorks VA and HP StorageWorks EVA specific term) A replica creation technique, in which copies of source volumes are created using storage virtualization techniques. The replicas are considered to be created at one particular point in time, without pre-configuration, and are immediately available for use.
  • Page 197 (HP StorageWorks Disk Array XP specific term) split mirror (EMC Symmetrix and HP StorageWorks Disk Array XP specific creation term) A replica creation technique, in which a pre-configured set of target volumes (a mirror) is kept synchronized with a set of source volumes until the time at which a replica of the contents of the source volumes is required.
  • Page 198 SSE Agent (HP StorageWorks Disk Array XP specific term) A Data Protector software module that executes all tasks required for a split mirror backup integration. It communicates with the HP StorageWorks...
  • Page 199 management systems, file systems, or other objects may exist. The volume management systems, file systems are built on this storage. Typically, these can be created or exist within a storage system such as a disk array. switchover See failover. Sybase Backup (Sybase specific term) An industry-standard interface developed Server API for the exchange of backup and recovery information between...
  • Page 200 System Recovery file. Data file System State (Windows specific term) The System State data comprises the Registry, COM+ Class Registration database, system startup files, and the Certificate Services database (if the server is a certificate server). If the server is a domain controller, Active Directory services and the SYSVOL directory are also contained in the System State data.
  • Page 201 this system to the original system configuration. The difference between a faulty system and a target system is that a target system has all faulty hardware replaced. target volume (ZDB specific term) A storage volume to which data is replicated. Terminal Services (Windows specific term) Windows Terminal Services provide a multi-session environment that allows clients to access a virtual...
  • Page 202 database backups. By applying transaction log backups, you can recover the database to a specific point in time. transaction log Files that record transactions of the database modifications, and files provide fault tolerance in case of a database disaster. transaction logs (Data Protector specific term) Keep track of IDB changes.
  • Page 203 (CRC) option ON. Virtual Controller (HP StorageWorks EVA specific term) The firmware that manages Software (VCS) all aspects of storage system operation, including communication with Command View EVA through the HSV controllers.
  • Page 204 (HP StorageWorks EVA specific term) A unit of storage allocated from an HP StorageWorks Enterprise Virtual Array storage pool. Virtual disks are the entities that are replicated using the HP StorageWorks Enterprise Virtual Array snapshot functionality. See also...
  • Page 205 Copy Service Microsoft Volume Shadow Copy Service. VSS compliant (HP StorageWorks Disk Array XP VSS provider specific term) mode One of two XP VSS hardware provider operation modes. When the XP provider is in the VSS compliant mode, the source volume (P-VOL) and its replica (S-VOL) are in simplex, unpaired state after a backup.
  • Page 206 one or more characters, and the question mark (?) typically represents a single character. Wildcard characters are often used in operating systems as a means of specifying more than one file by name. Windows Data Protector allows you to back up Windows CONFIGURATION CONFIGURATION, including Windows Registry, user profiles, backup...
  • Page 207 information. The ZDB database is used for ZDB, instant recovery, and split mirror restore. See also zero downtime backup (ZDB). ZDB to disk (ZDB specific term) A form of zero downtime backup where the replica produced is kept on the disk array as a backup of the source volumes at a specific point in time.
  • Page 208 Glossary...

  • Page 209: Index

    Index boot partition, 23 bootable installation CD, 43 ASR, 30, 85 Assisted Manual Disaster Recovery drsetup diskettes, 45 Assisted Manual Disaster Recovery Cell Manager limitations, Windows, 42 Manual Disaster Recovery, UNIX, 130 overview, Windows, 41 Manual Disaster Recovery, preparation, Windows, 42 Windows, 103 procedure, Windows, 48...
  • Page 210 disaster, 23 encryption keys disaster recovery preparing, 62 preparing, 33 Enhanced Disaster Recovery disaster recovery CD ISO image, 55 recovered partitions, 31 disaster recovery methods Enhanced Automated Disaster Recovery Manual Disaster Recovery, Unix Cell disaster recovery CD ISO image, 30 Manager, 129 Enhanced Automated Disaster Recovery disaster recovery operating system (DR...
  • Page 211 limitations OBDR, 29, 70 Assisted Manual Disaster Recovery, omniSRDupdate Windows, 42 post-exec script, 37 Disk Delivery Disaster Recovery, standalone, 37 UNIX client, 125 One Button Disaster Recovery, 29 Enhanced Automated Disaster limitations, 52 Recovery, Windows client, 59 limitations, Windows client, 74 Manual Disaster Recovery, UNIX Cell overview, 51 Manager, 130...
  • Page 212 Assisted Manual Disaster Recovery, Subscriber's Choice, HP, 22 Windows, 42 system partition, 23 Automated System Recovery, 90 System Recovery Data (SRD), 36 Disk Delivery Disaster Recovery, system specific disaster recovery UNIX client, 125 methods, 28 Disk Delivery Disaster Recovery,...
  • Page 213 HP Subscriber's Choice for Business, , 22 product manuals, 11 Windows ASR, 85 Assisted Manual Disaster Recovery, Assisted Manual Disaster Recovery, client, 41 Automated System Recovery set, 90 BitLocker Drive Encryption, 112 Disk Delivery Disaster Recovery, client, 50 Enhanced Automated Disaster...

Table of Contents