Page 1 HP Data Protector A.06.1 1 Integration guide for VMware Virtual Infrastructure, Sybase, Network Node Manager, and Network Data Management Protocol Server B6960-90160 Part number: B6960-90160 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 ..................23 Document conventions and symbols ..............25 Data Protector graphical user interface ..............26 General information ..................27 HP technical support ..................27 Subscription service ................... 28 HP websites ...................... 28 Documentation feedback ..................28 1 Integrating VMware Virtual Infrastructure and Data Protector ................
Page 4 Configuring VMware users ................38 Configuring clusters ..................38 ESX Server systems in a cluster ............... 38 Configuring backup proxy systems ..............39 Configuring VMware management clients ............39 Using the Data Protector GUI ..............40 Using the Data Protector CLI ..............42 Configuring virtual machines ................
Page 5 Using the Data Protector GUI ..............79 Using the Data Protector CLI ..............80 Restoring using the Data Protector GUI ............81 Restoring using the Data Protector CLI ............89 Recovering virtual machines manually ............92 Recovery after restoring outside of a datacenter ........92 Recovery after restoring to a datacenter ..........
Page 6 Monitoring sessions ..................145 Troubleshooting ....................145 Before you begin ..................146 Checks and verifications ................146 3 Integrating HP Network Node Manager and Data Protector ................. 149 Introduction ....................149 Integration concept ..................150 Configuring the integration ................150 Prerequisites .....................
Page 7 Media management ..................192 Troubleshooting ....................193 Before you begin ..................193 Problems ....................193 A Integrating Citrix XenServer and HP Data Protector .... 195 Introduction ....................195 Integration concepts ..................195 Types of backup ..................195 Online backup ................... 195 Offline backup ...................
Page 8 Backup using the integration ................204 Updating configuration script DPxen_config.py for backup ......205 Example backup configurations ............206 Creating a backup specification ..............207 Restore using the integration ................209 Updating configuration script DPxen_config.py for restore ......209 Example restore configurations ............. 210 Specifying a restore ..................
Page 9 Figures Data Protector graphical user interface ..........27 VirtualCenter environment ..............32 Migration of virtual machines ............34 Standalone ESX Server environment ........... 35 Configuring a VirtualCenter Server system ........... 41 Configuring virtual machines ............. 44 Snapshot tree .................. 51 Full backup (disabled mode) .............
Page 10 Restore options (VCBfile) ..............85 Conversion – Specify Source ............. 95 Conversion – Specify Destination 1 ............ 96 Conversion – Specify Destination 2 ............ 97 Conversion – View/Edit Options ............98 Conversion – Ready to Complete ............99 Recovery completed ............... 100 Virtual Infrastructure Client ..............
Page 11 Example of a list of Sybase databases ..........142 Restoring a database from a specific session ........143 Creating a database device ............144 Creating an empty database ............144 Scheduling a backup specification ........... 154 Data Protector NDMP Server integration architecture ......164 The NDMP environment configuration ..........
Page 12 Tables Edition history ................. 15 Document conventions ..............25 VMware users ................. 38 Virtual machine options ..............44 Backup method overview ..............50 Legend ................... 53 Backup types .................. 66 Disk space requirements ..............67 VMware backup options ..............72 What must be backed up ..............
Page 13 NDMP variables for NetApp NAS device ......... 189 NDMP variables for Celerra NAS device .......... 189 Approximate disk consumption by file history swap files ..... 192 Integration guide for VMware Virtual Infrastructure, Sybase, Network Node Manager, and Network Data Management Protocol Server...
Page 15: 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 16 Publication history...
Page 17: 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 18 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 19 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 20: 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 21: 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 22: 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 23: 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 Integration guide for VMware Virtual Infrastructure, Sybase, Network Node Manager, and Network Data Management Protocol Server...
Page 24 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 25: Document Conventions And Symbols
Document conventions and symbols Table 2 Document conventions Convention Element Blue text: Table 2 on page 25 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 26: 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 27: 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 28: 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 29: Integrating Vmware Virtual Infrastructure And Data Protector
VCBfile backup method, see the latest support matrices at http:/ /www.hp.com/support/manuals. This method is not supported for virtual machines running on ESXi Server systems. This method requires a Windows system with the VMware Consolidated Backup software installed (backup proxy system).
Page 30: Integration Concepts
VMware Integration component installed. This chapter provides information specific to the VMware Virtual Infrastructure integration. For limitations, see the HP Data Protector product announcements, software notes, and references. For general Data Protector procedures and options, see the online Help.
Page 31: Virtualcenter Environment
systems in your environment, each managing its own set of ESX Server and/or ESXi Server systems. VirtualCenter environment In a VirtualCenter environment, Data Protector communicates with the VMware Virtual Infrastructure through the VirtualCenter Server system. All backup and restore requests are sent there.
Page 32: Virtualcenter Environment
Figure 2 VirtualCenter environment ESX Server or ESXi VMware platform capable of hosting multiple virtual machines. Server system Virtual machine. Virtualized x86 or x64 PC environment, in which a guest operating system and associated application software can run. Datacenter An organizational unit that consists of one or more ESX Server and/or ESXi Server systems and the related storage for virtual machines (datastores).
Page 33 Migration of virtual machines In a VirtualCenter environment, Data Protector supports migration of virtual machines between ESX Server and/or ESXi Server systems that belong to the same datacenter. Virtual machines migrate from one ESX Server or ESXi Server system to another for various reasons: •...
Page 34: Migration Of Virtual Machines
Figure 3 Migration of virtual machines Whatever the reason for the migration, you do not need to create a new backup specification afterwards. Data Protector will automatically find the migrated virtual machines and back them up. Data Protector does not support migration of virtual machines between ESX Server and/or ESXi Server systems that belong to different datacenters.
Page 35: Standalone Esx Server Environment
Standalone ESX Server environment In a standalone ESX Server environment, Data Protector communicates with the VMware Virtual Infrastructure through an ESX Server system. All backup and restore requests are sent there. In one session, you can back up virtual machines from only one datacenter (ESX Server system).
Page 36: Data Protector Components
Data Protector components Data Protector Cell Manager The Data Protector Cell Manager can be installed on a virtual machine, VirtualCenter Server system, backup proxy system, or a separate system outside the VMware Virtual Infrastructure environment. Data Protector VMware Integration component The Data Protector VMware Integration component must be installed on the following clients: •...
Page 37: Configuring The Integration
VMware documentation. • Ensure that you have correctly installed Data Protector. On how to install Data Protector in various architectures, see the HP Data Protector installation and licensing guide. • For limitations, see “Limitations and recommendations” in the HP Data Protector product announcements, software notes, and references.
Page 38: Configuring Vmware Users
Configuring VMware users Identify or configure the following users: Table 3 VMware users VirtualCenter users For each VirtualCenter Server system, identify the Windows operating system user who administers the (VirtualCenter environment) VirtualCenter Server. ESX Server users For each standalone ESX Server system, identify an operating system user who has read, write, and (standalone ESX Server execute permissions on the related datastores.
Page 39: Configuring Backup Proxy Systems
Configuring backup proxy systems If your virtual machines reside on iSCSI datastores, restart the Data Protector Inet service on the related backup proxy system under a network domain user account that has read-write permissions for the following directories: • C:\Program Files •...
Page 40: Using The Data Protector Gui
on the Cell Manager. The file is named VMwareManagementClient%_OB2_GLOBAL. NOTE: Before the information is saved, Data Protector first tests the connection. If the connection fails, the information is not saved in the configuration file, leaving the previous login information (if it exists) in the configuration file intact. •...
Page 41: Configuring A Virtualcenter Server System
Figure 5 Configuring a VirtualCenter Server system Select either Integrated security or Standard security. If you select Standard security, specify the following: • Username and Password: Specify an operating system user account that has the following VMware Virtual Infrastructure privileges: •...
Page 42: Using The Data Protector Cli
• Port: Optionally, change the TCP port number of the Virtual Infrastructure web service server. Default: 443 (SSL–encrypted HTTP), 80 (unencrypted HTTP). By default, the HTTP/S (SSL–encrypted HTTP) is used. To switch to unencrypted HTTP, configure the VMware management client to allow HTTP connections and set the Data Protector omnirc variable OB2_VMWARE_HTTP to 1.
Page 43: Configuring Virtual Machines
[-webroot WebServiceRoot] [-port WebServicePort] The message *RETVAL*0 indicates successful configuration. For option description, see the util_vmware.exe man page or the HP Data Protector command line interface reference. Configuring virtual machines For each virtual machine, specify details on how to perform various backup methods: •...
Page 44: Configuring Virtual Machines
specification, right-click the client system at the top or any of the virtual machines listed below and click Configure Virtual Machines. Figure 6 Configuring virtual machines In the Configure Virtual Machine(s) dialog box, specify the following options: Table 4 Virtual machine options Configure Select whether you want to specify common virtual machine settings virtual...
Page 45 Use common Available only if a virtual machine is selected. settings for Select this option to apply the common virtual machine selected VM settings for the selected virtual machine. Default: ON Use default Available only if Common VM Settings is selected. settings Select this option to set default values for the common virtual machine settings.
Page 46: Using The Data Protector Cli
The values { 0 | 1 | 2} represent Disabled, Single, and Mixed snapshot handling modes respectively. For details, see the util_vmware.exe man page or the HP Data Protector command line interface reference. To change virtual machine specific settings back to common virtual machine settings, run: util_vmware.exe –config –instance DatacenterPath –vm VMpath...
Page 47: Checking The Configuration Of Vmware Clients
TIP: You can join the options for configuring virtual machines and the options for configuring the VMware management client in the same command line. Example Suppose you want to set Integrated security for the VirtualCenter Server system virtualcenter2.company.com. In addition, you want to specify Single snapshot handling mode and use the backup proxy system proxy2.company.com for the virtual machine /vm/myfolder/myvm that belongs to the datacenter/Mydatacenters/Datacenter1.
Page 48: Backup
Standalone ESX Server system: /opt/omni/lbin Run: util_vmware.exe –chkconf [–instance DatacenterPath] For option description, see the util_vmware.exe man page or the HP Data Protector command line interface reference. Backup Using the Data Protector VMware integration, you can back up the following VMware objects: •...
Page 49: Virtual Machines
Virtual machines Virtual machines can be backed up using the Snapshot, Suspend, or VCBimage backup method. A virtual machine backup contains the following files: Virtual machine configuration file. vmdk Virtual machine disk files. There are two types: metadata files and binary extent files.
Page 50: Snapshot Method
• Snapshot (see “Snapshot method” on page 50) • Suspend (see “Suspend method” on page 60) • VCBimage (see “VCBimage method” on page 61) • VCBfile (see “VCBfile method” on page 63) Table 5 Backup method overview Supported backup types Backs up Needs a How is backup...
Page 51: Snapshot Tree
a description that contains the product name and a timestamp. Therefore, avoid using this label for snapshots that you create for other purposes. Figure 7 Snapshot tree Existing virtual machine snapshots reduce the overall performance of a virtual machine. For this reason, Data Protector removes DP snapshots once they are no longer needed. The number of DP snapshots that remain on the snapshot tree depends on the selected snapshot handling mode and backup type.
Page 52 IMPORTANT: A backup chain gets broken if you do any of the following operations: • Delete a snapshot • Revert to a snapshot • Create a non-Data Protector snapshot • Change snapshot handling mode • Add a new virtual machine disk or rename an existing one •...
Page 53: Full Backup (Disabled Mode)
Figure 8 Full backup (disabled mode) Table 6 Legend Boxes denoted by Ti show how the virtual machine snapshot tree changes in time. Virtual The rectangle denoted by Virtual machine base represents the virtual machine base machine base or the last non-Data Protector created virtual machine delta file on the active branch.
Page 54 DP snapshot A rectangle denoted by DP snapshot represents a process (snapshot operation triggered by Data Protector). This process closes the current active state to become a read-only file. At the same time, it creates a new delta file, which becomes the active state. The active state is denoted by round corners.
Page 55: Differential Backup (Single Mode)
Figure 9 Differential backup (single mode) DP snapshot1 remains on the snapshot tree to track changes made since the last full Integration guide for VMware Virtual Infrastructure, Sybase, Network Node Manager, and Network Data Management Protocol Server...
Page 56 backup. A backup chain consisting of a full backup that is followed by incremental sessions progresses in the same way, with the exception that, at the end of an incremental session, DP snapshot1 is removed instead of DP Snapshot2 (see Figure 10).
Page 57: Incremental Backup (Single Mode)
Figure 10 Incremental backup (single mode) DP snapshot2 remains on the snapshot tree to track changes made since the last Integration guide for VMware Virtual Infrastructure, Sybase, Network Node Manager, and Network Data Management Protocol Server...
Page 58 incremental backup. Snapshot mode: mixed A full backup in the Mixed mode progresses in the same way as a full backup in the Single mode (you end up with one DP snapshot). A subsequent differential or incremental backup progresses in the same way as a differential or incremental backup in the Single mode, with the exception that no DP snapshot is removed at the end (you end up with two DP snapshots).
Page 59: Incremental Backup (Mixed Mode)
Figure 1 1 Incremental backup (mixed mode) Integration guide for VMware Virtual Infrastructure, Sybase, Network Node Manager, and Network Data Management Protocol Server...
Page 60: Suspend Method
Figure 12 Incremental backup (mixed mode) DP snapshot1 and DP snapshot3 remain on the snapshot tree to track changes made since the last full and the last backup respectively. A subsequent differential backup progresses in the same way as an incremental session described in Figure 1 1 on page 59, with the following exceptions:...
Page 61: Vcbimage Method
Using this method, you can run full, incremental, and differential backups. Data Protector uses the file modification time as an incremental or differential backup criterion. It means that only the files with the modification time changed since the last (full) backup are backed up. Figure 13 Snapshot and Suspend backup methods VCBimage method For the VCBimage backup method, you need to have at least one backup proxy...
Page 62 machine snapshot to put the virtual machine into a consistent state. Once mounted, the virtual machine is copied (exported) to the backup proxy local disk. NOTE: Depending on virtual machine disk sizes, the copy operation can be very time–consuming. It may take longer than the default Data Protector Session Manager timeout, which is 10 minutes.
Page 63: Vcbimage Backup Method
Figure 14 VCBimage backup method Integration guide for VMware Virtual Infrastructure, Sybase, Network Node Manager, and Network Data Management Protocol Server...
Page 64: Vcbfile Method
VCBfile method For the VCBfile backup method, you need to have at least one backup proxy system configured in your environment. A backup proxy system is a Windows system that has the VMware Consolidated Backup (VCB) software installed. For details on the VCB software, see the VMware documentation.
Page 65: Backup Types
Figure 15 VCBfile method Backup types Integration guide for VMware Virtual Infrastructure, Sybase, Network Node Manager, and Network Data Management Protocol Server...
Page 66: Considerations
The integration provides the following backup types: Table 7 Backup types Full Snapshot and Suspend: Backs up the complete virtual machine, including the virtual machine snapshot tree and the virtual machine memory file (if specified). VCBimage: Backs up the complete virtual machine. The virtual machine snapshot tree and the virtual machine memory file are not included.
Page 67: Disk Space Requirements
can be safely performed (whether enough disk space is available). If not, the backup of that particular virtual machine or filesystem is skipped. Table 8 Disk space requirements Backup Required disk space on Explanation method datastores Snapshot After a snapshot is created, changes The sum of the sizes of all the made to the virtual machine disks are virtual machine disks, plus the...
Page 68: Creating Backup Specifications
• Concurrent sessions: Backup sessions that use the same devices or back up the same datacenter cannot run concurrently. If multiple sessions are started, one session waits for the other to complete. Creating backup specifications Create a backup specification using the Data Protector Manager. In the Context List, click Backup.
Page 69: Selecting Vmware Objects (Snapshot, Suspend, Vcbimage)
Snapshot, Suspend, and VCBimage backup methods: Select virtual machines or individual virtual machine disks that you want to back up. Figure 16 Selecting VMware objects (Snapshot, Suspend, VCBimage) VCBfile backup method: Right-click a virtual machine and click Mount filesystem to mount virtual machine filesystems. This may take some time. Then, select the files and folders that you want to back up.
Page 70: Selecting Vmware Objects (Vcbfile)
Figure 17 Selecting VMware objects (VCBfile) NOTE: The following note applies to all backup methods: if you select the client system at the top, all virtual machines in the datacenter will be selected for backup, including the virtual machines that you create after the backup specification is saved.
Page 71: Application Specific Options
Set backup options. For information on application specific backup options, see Table 9 on page 72. Figure 18 Application specific options Click Next. Optionally, schedule the backup. See “Scheduling backup specifications” on page 72. Click Next. Save the backup specification, specifying a name and a backup specification group.
Page 72: Modifying Backup Specifications
TIP: Preview your backup specification before using it for real. See “Previewing backup sessions” on page 73. Table 9 VMware backup options Options Description Pre-exec, Post-exec The command specified here is run by vmware_bar.exe on the VMware management client before the backup (pre-exec) or after it (post-exec).
Page 73: Previewing Backup Sessions
Under Recurring, select Weekly. Under Time options, select 8:00. Under Recurring Options, select Mon, Tue, Wed, Thu, and Fri. See Figure 19 on page 73. Under Session options, select Differential from the Backup type drop-down list. Click OK. Repeat Step 1 Step 2 to schedule differential backups at 13:00 and 18:00.
Page 74: Using The Data Protector Cli
Specify the Backup type and Network load. Click OK. The message Session completed successfully is displayed at the end of a successful preview. Using the Data Protector CLI Log in to the VMware management client under a user account that is configured as described in “Configuring VMware users”...
Page 75: Using The Data Protector Cli
VMwareMode is one of the following backup types: full|incr|diff The default is full. For ListOptions, see the omnib man page or the HP Data Protector command line interface reference. Examples To start a full backup using the backup specification snapshot2, run:...
Page 76: Preparing For Disaster Recovery
Oracle type. In Application database, type the name of the VirtualCenter configuration database. Continue with the backup specification creation as described in the HP Data Protector integration guide for Oracle and SAP. Start a backup using the newly created backup specification.
Page 77: Restore
Restore You can restore virtual machines and filesystems of virtual machines using the Data Protector GUI or CLI. Restore of virtual machines Virtual machines backed up with the Snapshot, Suspend, or VCBimage method can be restored in two ways, depending on what you select in the Application database restore option.
Page 78: Application Database: None (Restore Files To Client)
IMPORTANT: Since the Data Protector VMware Integration component cannot be installed on ESXi Server systems, virtual machines backed up from ESXi Server systems can be restored back to the original ESXi Server systems only if there is an ESX Server system (with the VMware Integration component installed) in the same datacenter, having access to the virtual machine datastores.
Page 79: Considerations
Considerations • Restore chain: When you restore a virtual machine from an incremental or differential Snapshot or Suspend session, Data Protector automatically restores the complete backup chain, starting with the last full backup, which is then followed by the last differential and all subsequent incremental backups (if they exist) up to the selected session.
Page 80: Using The Data Protector Cli
Figure 20 Backup object information TIP: To view the messages displayed during the session, click the Messages tab. Using the Data Protector CLI Log in to the VMware management client under a user account that is configured as described in “Configuring VMware users”...
Page 81: Restoring Using The Data Protector Gui
-vmware BackupObjectName -session SessionID -catalog Here is one example of a backup object name: gabriel.company.com::/%2FElDatacentro/0/%2Fvm%2Fharbour For details, see the omnidb man page or the HP Data Protector command line interface reference. Restoring using the Data Protector GUI In the Context List, click Restore.
Page 82 In the Source page, Data Protector displays VMware objects that were backed up with the method specified in Backup method. To display VMware objects that were backed up with a different method, change Backup method. NOTE: VMware objects that were created using different backup methods cannot be restored in the same session.
Page 83: Selecting Vmware Objects For Restore (Snapshot, Suspend, Vcbimage)
Figure 21 Selecting VMware objects for restore (Snapshot, Suspend, VCBimage) Figure 22 Selecting VMware objects for restore (VCBfile) Integration guide for VMware Virtual Infrastructure, Sybase, Network Node Manager, and Network Data Management Protocol Server...
Page 84: Restore Options (Snapshot, Suspend, Vcbimage)
In the Options page, specify the VMware restore options. For details, see Table on page 86. Figure 23 Restore options (Snapshot, Suspend, VCBimage) Integrating VMware Virtual Infrastructure and Data Protector...
Page 85: Restore Options (Vcbfile)
Figure 24 Restore options (VCBfile) IMPORTANT: If you restore from a Snapshot backup in which individual virtual machine disks were backed up, clear the option Register virtual machines if needed. Otherwise, the restore fails. Whenever you restore with the option Register virtual machines if needed cleared, you need to manually recover the virtual machine after the session completes.
Page 86: Vmware Restore Options
In the Start Restore Session dialog box, click Next. Specify Report level and Network load. Click Finish to start the restore. The message Session completed successfully is displayed at the end of a successful session. Table 1 1 VMware restore options GUI/CLI option Description Restore client/...
Page 87 GUI/CLI option Description Application database/ Specifies the datacenter that the virtual machines are restored to. By default, the virtual machines are restored -newinstance to the original datacenter. Change the default only in the case of a disaster recovery when the new datacenter does not have the same name as the original one.
Page 88 GUI/CLI option Description Power-on virtual machines after This option is applicable only if Register virtual machines restore/ if needed is selected. Select this option to put the newly-restored virtual machines online when the session -poweron completes. This option is not available if None (restore files to client) is selected in Application database or if you restore from a VCBfile backup.
Page 89: Restoring Using The Data Protector Cli
GUI/CLI option Description Target hosts for restore/ This option is available only if you restore from a VCBfile backup. -target Specifies where to restore filesystems of virtual machines. The target system can be any Windows system (physical or virtual). Restoring using the Data Protector CLI Log in to the VMware management client under a user account that is configured as described in “Configuring VMware...
Page 90 -all [-exclude VMFolder [-exclude VMFolder...]] | —vmfolder VMFolder [-exclude VMFolder [-exclude VMFolder...]] | —vm VM For description of all the options, see the omnir man page or the HP Data Protector command line interface reference. Example (Restoring virtual machines to a datacenter) Suppose you want to restore the virtual machine /vm/machineA and the individual disks (scsi0:0 and scsi0:1) of the virtual machine /vm/machineB.
Page 91 to the datacenter /MyDatacenter managed by the VirtualCenter Server system Virtualcenter.company.com. The virtual machines were backed up with the Suspend backup method. You want to restore them to the original location, using the backup session 2008/07/14–1. If, in this session, virtual machine memory files were also backed up, you want to restore them as well.
Page 92: Recovering Virtual Machines Manually
MachineB.company.com. The virtual machines were backed up from the datacenter /MyDatacenter that was managed by the VirtualCenter Server system VirtualCenter.company.com. You want to restore from the last backup session. Run: omnir -vmware -barhost VirtualCenter.company.com –instance /MyDatacenter –method VCBfile -vmfolder /MyVirtualMachines –exclude /MyVirtualMachines/MachineA –target computer1.company.com –vm /MyVirtualMachines2/MachineB –target MachineB.company.com –file “C/Documents and Settings”...
Page 93 Display the content of the restored directory C:\tmp\FreeBSD 8.0 beta2 i386: catalog_2009_07_17_0002 FreeBSD 8.0 beta2 i386.vmdk_2009_07_17_0002 FreeBSD 8.0 beta2 i386.vmx_2009_07_17_0002 scsi0-0-0-FreeBSD 8.0 beta2 i386-flat.vmdk_2009_07_17_0002 Delete the backup session IDs appended at the end of the filenames: catalog FreeBSD 8.0 beta2 i386.vmdk FreeBSD 8.0 beta2 i386.vmx scsi0-0-0-FreeBSD 8.0 beta2 i386-flat.vmdk Integration guide for VMware Virtual Infrastructure, Sybase, Network Node Manager,...
Page 94 Open the catalog file with a text editor: catalog version= esx-3.0 state= poweredOn display_name= "FreeBSD 8.0 beta2 i386" uuid= "503d98d9-cad4-5c0e-9132-b35de35b900d" disk.scsi0:0.filename= "scsi0-0-0-FreeBSD 8.0 beta2 i386.vmdk" disk.scsi0:0.diskname= "[Storage_VmWare_all] FreeBSD 8.0 beta2 i386/FreeBSD 8.0 beta2 i386.vmdk" config.vmx= "[Storage_VmWare_all] FreeBSD 8.0 beta2 i386/FreeBSD 8.0 beta2 i386.vmx"...
Page 95: Conversion - Specify Source
In the Specify Source page, select Backup image or third-party virtual machine for the source type and \\droid\tmp\FreeBSD 8.0 beta2 i386\FreeBSD 8.0 beta2 i386.vmx for the virtual machine. Figure 25 Conversion – Specify Source Click Next. Integration guide for VMware Virtual Infrastructure, Sybase, Network Node Manager, and Network Data Management Protocol Server...
Page 96: Conversion – Specify Destination 1
In the Specify Destination (Destination Type) page, provide the login information for the VirtualCenter Server system. Figure 26 Conversion – Specify Destination 1 Click Next. Integrating VMware Virtual Infrastructure and Data Protector...
Page 97: Conversion – Specify Destination 2
In the Specify Destination (Host/Resource) page, specify the destination ESXi Server system srsen.company.com. Figure 27 Conversion – Specify Destination 2 Click Next. Integration guide for VMware Virtual Infrastructure, Sybase, Network Node Manager, and Network Data Management Protocol Server...
Page 98: Conversion - View/Edit Options
In the View/Edit Options page, modify the options (optional). Figure 28 Conversion – View/Edit Options Click Next. Integrating VMware Virtual Infrastructure and Data Protector...
Page 99: Conversion - Ready To Complete
1 1. In the Ready to Complete page, review your selection and click Finish. Figure 29 Conversion – Ready to Complete Integration guide for VMware Virtual Infrastructure, Sybase, Network Node Manager, and Network Data Management Protocol Server...
Page 100: Recovery After Restoring To A Datacenter
After a while, the VMware Converter informs you about the successful recovery. Figure 30 Recovery completed Recovery after restoring to a datacenter The following procedure enables you to import restored virtual machine disks into a new or an existing virtual machine. Use this procedure if you have restored individual virtual machine disks or virtual machines to the original ESX Server or ESXi Server system (Application database: datacenter), however, without selecting the option Register virtual machines if needed.
Page 101: Virtual Machine Information
• VCBimage: No preparatory steps are required. Linking virtual machine disk files The procedure for linking virtual machine disk files is described using the following example: Table 12 Virtual machine information Virtual machine helios • scsi0:0 (1.2 GB) base metadata file: helios.vmdk base extent file: helios-flat.vmdk Virtual machine disks...
Page 102 Display the content of the restored directory /vmfs/volumes/storage2/helios/: helios_1-000001-delta.vmdk.2008_09_10_0003 helios_1-000001.vmdk.2008_09_10_0003 helios_1-000002-delta.vmdk.2008_09_10_0004 helios_1-000002.vmdk.2008_09_10_0004 helios_1-flat.vmdk.2008_09_10_0001 helios_1.vmdk.2008_09_10_0001 helios.nvram.2008_09_10_0001 helios.nvram.2008_09_10_0003 helios.nvram.2008_09_10_0004 helios-Snapshot1.vmsn.2008_09_10_0001 helios-Snapshot4.vmsn.2008_09_10_0003 helios-Snapshot5.vmsn.2008_09_10_0004 helios.vmsd.2008_09_10_0001 helios.vmsd.2008_09_10_0003 helios.vmsd.2008_09_10_0004 helios.vmx.2008_09_10_0001 helios.vmx.2008_09_10_0003 helios.vmx.2008_09_10_0004 helios.vmxf.2008_09_10_0001 helios.vmxf.2008_09_10_0003 helios.vmxf.2008_09_10_0004 Identify the scsi1:2 metadata files: helios_1.vmdk.2008_09_10_0001 helios_1-000001.vmdk.2008_09_10_0003 helios_1-000002.vmdk.2008_09_10_0004 Identify the corresponding extent files: helios_1-flat.vmdk.2008_09_10_0001 helios_1-000001-delta.vmdk.2008_09_10_0003 helios_1-000002-delta.vmdk.2008_09_10_0004...
Page 103 Open the base metadata file helios_1.vmdk.2008_09_10_0001: # Disk DescriptorFile version=1 CID=d0fb6c81 parentCID=ffffffff createType="vmfs" # Extent description RW 2097152 VMFS "helios_1-flat.vmdk" # The Disk Data Base #DDB ddb.virtualHWVersion = "4" ddb.geometry.cylinders = "512" ddb.geometry.heads = "128" ddb.geometry.sectors = "32" ddb.adapterType = "lsilogic" Change the extent file name helios_1-flat.vmdk to helios_1-flat.vmdk.2008_09_10_0001.
Page 104 Open the snapshot metadata file helios_1-000002.vmdk.2008_09_10_0004: # Disk DescriptorFile version=1 CID=d0fb6c81 parentCID=d0fb6c81 createType="vmfsSparse" parentFileNameHint="helios_1-000001.vmdk" # Extent description RW 2097152 VMFSSPARSE "helios_1-000002-delta.vmdk" # The Disk Data Base #DDB Change the parent metadata file name helios_1-000001.vmdk to helios_1-000001.vmdk.2008_09_10_0003. Change the extent file name helios_1-000002-delta.vmdk to helios_1-000002-delta.vmdk.2008_09_10_0004.
Page 105: Virtual Infrastructure Client
Open the Virtual Infrastructure Client. Figure 31 Virtual Infrastructure Client Right-click the virtual machine galaxy and click Edit Settings. Integration guide for VMware Virtual Infrastructure, Sybase, Network Node Manager, and Network Data Management Protocol Server...
Page 106: Virtual Machine Properties
In the Virtual Machine Properties dialog box, select Hard Disk 1 and click Add. Figure 32 Virtual machine properties In the Select Device Type page of the Add Hardware wizard, select Hard disk and click Next. In the Select a Disk page of the Add Hardware wizard, select Use an existing virtual disk and click Next.
Page 107: Browsing Datastores
In the Browse Datastores dialog box, browse to /vmfs/volumes/storage2/helios, select helios_1_recovered.vmdk and click Open. Figure 33 Browsing datastores In the Advanced Options page of the Add Hardware wizard, select a Virtual Device Node for the new disk and click Next. Integration guide for VMware Virtual Infrastructure, Sybase, Network Node Manager, and Network Data Management Protocol Server...
Page 108: Restoring Using Another Device
In the Ready to Complete page of the Add Hardware wizard, review your selection and click Finish. Figure 34 Add hardware summary Restoring using another device You can restore using a device other than that used for backup. For details, see the online Help index: “restore, selecting devices for”.
Page 109: Monitoring Sessions
To monitor a session, see the online Help index: “viewing currently running sessions”. Troubleshooting This section lists general checks and verifications, plus problems you might encounter when using the VMware integration. For general Data Protector troubleshooting information, see the HP Data Protector troubleshooting guide. Before you begin •...
Page 110: Checks And Verifications
Checks and verifications If your configuration, backup, or restore failed: • Examine system errors reported in the debug.log located in: VirtualCenter Server system: Data_Protector_home\log. Standalone ESX Server system: /opt/omni/log. • Check if you can do a filesystem backup and restore on the problematic client. For information, see the online Help.
Page 111 Problem Suspend backup fails with the error “insufficient resources to satisfy failover level” This error may occur if your ESX Server systems are configured in a high availability cluster and one of the ESX Server systems fails. Consequently, the virtual machines from the failed system migrate elsewhere.
Page 112 Action Do not change the restore destination. Changes are allowed only in case of a disaster recovery when the newly configured VirtualCenter systems, ESX Server systems, or datacenters have different names than the original ones. Problem Backup fails if a VM filesystem is still mounted If not enough time passes between unmounting and mounting of a VM (mount point), the vcbMounter will report that it cannot create a directory, although the directory has been removed:...
Page 113: Integrating Sybase Server And Data Protector
2 Integrating Sybase Server and Data Protector Introduction This chapter explains how to configure and use the Data Protector Sybase Adaptive Server (Sybase Server) integration. It describes concepts and methods you need to understand to back up and restore Sybase databases. Data Protector offers interactive and scheduled backups of the following types: Table 13 Backup types Full...
Page 114: Sybase Integration Architecture
Sybase Server isql utility. Figure 35 on page 114 shows the architecture of the Data Protector Sybase integration. Figure 35 Sybase integration architecture Table 14 Legend Data Protector Session Manager: Backup Session Manager during backup and Restore Session Manager during restore. Sybase Backup Server Application Programming Interface.
Page 115: Data Protector Cli Commands
The isql utility sends backup and restore commands (issued through the Data Protector GUI or CLI, or the Sybase isql command line interface) to Sybase Backup Server, initiating data transfer between Sybase databases and Data Protector media. While Sybase Backup Server is responsible for read/write operations to disk, Data Protector manages devices and media used for backup and restore.
Page 116: Prerequisites
Prerequisites • Ensure that you have correctly installed and configured Sybase Server. • For supported versions, platforms, devices, and other information, see the HP Data Protector product announcements, software notes, and references or http://www.hp.com/support/manuals. • For information on the Sybase Server, see the Adaptive Server Enterprise System Administration Guide and Adaptive Server Enterprise Installation and Configuration Guide.
Page 117: Configuring Sybase Instances
Configuring Sybase instances Provide Data Protector with Sybase instance configuration parameters: • Pathname of the Sybase Server home directory • Pathname of the Sybase isql utility • Sybase instance name • Sybase instance user • Password of the Sybase instance user •...
Page 118: Specifying The Sybase Instance
In Client, select the Sybase Server system. In a cluster environment, select the virtual server. In Application database, type the Sybase instance name. UNIX only: Type sybase in both Username and Group/Domain name. This user becomes the backup owner. Figure 36 Specifying the Sybase instance Click Next.
Page 119: Configuring A Sybase Instance (Windows)
In the Configure Sybase dialog box, review and, if necessary, correct the configuration parameters that are filled in automatically. On Windows, all configuration parameters are determined automatically. On UNIX, you need to set the Sybase Server home directory, and username and password of the Sybase instance user that has the Sybase rights to back up and restore databases.
Page 120: Using The Data Protector Cli
Figure 38 Configuring a Sybase instance (UNIX) Click OK. The Sybase instance is configured. Exit the GUI or proceed with creating the backup specification at Step 6 on page 123. Using the Data Protector CLI Run: Windows: perl -I..\lib\perl util_sybase.pl -CONFIG Sybase_instance Sybase_home isql_path Sybase_user Sybase_password Sybase_ASE Sybase_OCS UNIX: util_sybase.pl -CONFIG Sybase_instance Sybase_home...
Page 121: Checking The Configuration
Name of the Sybase instance. Sybase_instance Pathname of the Sybase Server home directory. Sybase_home Pathname of the Sybase isql command. isql_path Sybase instance user with the Sybase right to back Sybase_user up and restore databases. Password of the Sybase instance user. Sybase_password Name of the Sybase Sybase_ASE directory.
Page 122: Using The Data Protector Cli
Using the Data Protector CLI Run: Windows: perl -I..\lib\perl util_sybase.pl -CHKCONF Sybase_instance_name UNIX: util_sybase.pl -CHKCONF Sybase_instance_name Backup The Data Protector Sybase integration provides online backup of the following types: Table 15 Backup types Full Backs up all selected Sybase databases and transaction logs. Backs up changes made to the transaction logs since the last backup Trans of any type.
Page 123: Selecting Backup Objects
In the Scoping Pane, expand Backup Specifications, right-click Sybase Server, and click Add Backup. In the Create New Backup dialog box, click OK. In Client, select the Sybase Server system. In a cluster environment, select the virtual server. In Application database, type the Sybase instance name. UNIX only: Type sybase in both Username and Group/Domain name.
Page 124: Pre- And Post-Exec Commands (Windows)
Select devices to use for the backup. To specify device options, right-click the device and click Properties. Click Next. Set backup options. For information on application specific options, see Table on page 127. Figure 40 Pre- and post-exec commands (Windows) Integrating Sybase Server and Data Protector...
Page 125: Pre- And Post-Exec Commands (Unix)
Figure 41 Pre- and post-exec commands (UNIX) Click Next. Optionally, schedule the backup. For more information, see “Scheduling backup specifications” on page 127. Click Next. Integration guide for VMware Virtual Infrastructure, Sybase, Network Node Manager, and Network Data Management Protocol Server...
Page 126: Specifying The Number Of Concurrent Streams
View the properties of objects selected for backup. If you have selected only specific databases, not the whole instance, you can specify the number of concurrent data streams for backing up a particular database: right-click the database and click Properties. This option is equivalent to Sybase dump striping.
Page 127: Modifying Backup Specifications
TIP: Preview your backup specification before using it for real. See “Previewing backup sessions” on page 128. Table 16 Sybase backup options Specify a command that will be started by ob2sybase.exe Pre-exec, (Windows) or ob2sybase.pl (UNIX) on the Sybase Server system Post-exec before the backup of every selected database (pre-exec) or after it (post-exec).
Page 128: Previewing Backup Sessions
Figure 43 Scheduling a backup specification Previewing backup sessions Preview the backup session to test it. Use the Data Protector GUI or CLI. Using the Data Protector GUI In the Context List, click Backup. In the Scoping Pane, expand Backup Specifications and then Sybase Server. Right-click the backup specification you want to preview and click Preview Backup.
Page 129: Using The Data Protector Cli
Using the Data Protector CLI Run: omnib -sybase_list backup_specification_name -test_bar Figure 44 Example of previewing a backup What happens during the preview? The following are tested: • Communication between the Sybase instance and Data Protector • The syntax of the backup specification •...
Page 130: Starting Backup Sessions
Starting backup sessions Interactive backups are run on demand. They are useful for urgent backups or for restarting failed backups. Start a backup in any of the following ways: • Use the Data Protector GUI. • Use the Data Protector CLI. •...
Page 131: Integration Guide For Vmware Virtual Infrastructure, Sybase, Network Node Manager
Using Sybase commands To start a database backup from the client where the database is located, using the Sybase isql utility: Check if the devices to be used contain formatted (initialized) media with enough free space. Verify the backup options in the Data Protector Sybase backup specification. Log in to the Sybase Server system as user sybase.
Page 132: Localized Database Names
Localized database names If the names of backed up objects contain characters that cannot be displayed using the current language group (on Windows) or code page (on UNIX): Set the encoding used on the terminal to UTF-8. Windows only : Set the environment variable OB2_CLI_UTF8 to 1. When gathering information for restore, redirect the output of the syb_tool or omnidb command to a text file.
Page 133: Integration Guide For Vmware Virtual Infrastructure, Sybase, Network Node Manager
Using the Data Protector syb_tool command The Data Protector syb_tool command returns the exact Sybase load command needed for restore. The syntax of the syb_tool command is: syb_tool database Sybase_instance -date YYYY/MM/DD.hh:mm:ss [ -new_db new_database [ -new_server new_Sybase_instance ] [ -file file [ -media Parameter description Database to be restored.
Page 134: Running The Syb_Tool Command
syb_tool database1 audi -date 1999/06/01.12:00:00 -media Figure 45 on page 134. Figure 45 Running the syb_tool command Example 2 To get the load command that restores database1 of the Sybase instance sherlock from the first backup performed after 12.00 noon on June 1, 1999, to get the necessary media, and to record the load command to the file c:/tmp/isqlfile (Windows), run: syb_tool database1 sherlock -date 1999/06/01.12:00:00 -file...
Page 135: The Load Command For Restore To A Different Database
syb_tool database1 audi -date 1999/06/01.12:00:00 -new_db database2 -media Figure 47 The load command for restore to a different database Example 4 To get the load command that restores database1 of the Sybase instance audi to the Sybase instance toplarna, run: syb_tool database1 audi -date 1999/06/01.12:00:00 -new_server toplarna -file /tmp/isql -media Integration guide for VMware Virtual Infrastructure, Sybase, Network Node Manager,...
Page 136: The Load Command For Restore To A Different Server
Figure 48 The load command for restore to a different server Example 5 To get the load command that restores database1 of the Sybase instance audi from the first backup performed after 14:28 on July 7, 1999, and to record the load command to the file /tmp/dudule, run: syb_tool database1 audi -date 1999/07/07.14:28:00 -file /tmp/dudule...
Page 137: Loading Transaction Logs From Multiple Backups
Figure 49 Loading transaction logs from multiple backups Using the standard Data Protector CLI commands Integration guide for VMware Virtual Infrastructure, Sybase, Network Node Manager, and Network Data Management Protocol Server...
Page 138: Example Of A List Of Backed Up Sybase Databases
Get a list of backed up Sybase databases: omnidb -sybase Figure 50 Example of a list of backed up Sybase databases Integrating Sybase Server and Data Protector...
Page 139: Restoring Using The Sybase Isql Command
Get a list of backup sessions for a specific object, including the session ID: omnidb -sybase "object_name" Figure 51 Example of a list of backup sessions for a specific object IMPORTANT: For object copies, use the object's backup ID (which equals the object's backup session ID).
Page 140 Run the Sybase isql utility: isql -SSybase_instance -USybase_user -PSybase_password [-i input_file -J utf8] Parameter description Sybase instance name. Sybase_instance Sybase instance user. Sybase_user Password of the Sybase instance user. Sybase_password The file to which the load parameter was input_file saved. See also “Localized database names”...
Page 141 If you did not provide the load command in a file, type the desired load command in the first line. To run the command(s), type go in the last line and press Enter. The syntax of the Sybase load command is: load {database|transaction} new_database from "ob2syb::version[::database[::Sybase_instance]]"...
Page 142: Restore Examples
TIP: To list all Sybase databases of a particular Sybase instance, run: Windows: perl -I..\lib\perl util_sybase.pl -OBJS0 Sybase_instance_name UNIX: util_sybase.pl -OBJS0 Sybase_instance_name Figure 53 Example of a list of Sybase databases Restore examples Example 1 To restore the database database2 from the backup session 1999/06/09-2, run: 1>load database database2 from "ob2syb::1999/06/09-2"...
Page 143: Restoring A Database From A Specific Session
Figure 54 Restoring a database from a specific session Example 2 To restore the latest version of the database Sybdata to a new database, named Sybdata1: Integration guide for VMware Virtual Infrastructure, Sybase, Network Node Manager, and Network Data Management Protocol Server...
Page 144: Creating A Database Device
Create a database device. See Figure 55 on page 144. Figure 55 Creating a database device Create an empty database, named Sybdata1. See Figure 56 on page 144. Figure 56 Creating an empty database Restore Sybdata to Sybdata1 by running: 1>load database Sybdata1 from "ob2syb::latest version::Sybdata"...
Page 145: Restoring Using Another Device
On how to monitor a session, see the online Help index: “viewing currently running sessions”. Troubleshooting This section lists general checks and verifications. For general Data Protector troubleshooting information, see the HP Data Protector troubleshooting guide. Integration guide for VMware Virtual Infrastructure, Sybase, Network Node Manager, and Network Data Management Protocol Server...
Page 146: Before You Begin
Ensure that the latest official Data Protector patches are installed. See the online Help index: “patches” on how to verify this. • See the HP Data Protector product announcements, software notes, and references for general Data Protector limitations, as well as recognized issues and workarounds.
Page 147 Create a Sybase backup specification to back up to a null or file device. If the backup succeeds, then the problem is probably related to devices. For information on troubleshooting devices, see the HP Data Protector troubleshooting guide. If the test succeeds, start a backup directly from the Sybase Server. See “Using...
Page 148 Integrating Sybase Server and Data Protector...
Page 149: Integrating Hp Network Node Manager And Data Protector
Node Manager and Data Protector Introduction This chapter explains how to configure and use the Data Protector HP Network Node Manager (NNM) integration. It describes concepts and methods you need to understand to back up and restore the NNM database.
Page 150: Integration Concept
Remove the files manually to free the disk space. The NNM Perl compiler is used for NNMpre.ovpl and NNMpost.ovpl. While HP Network Node Manager is responsible for read/write operations to disk, Data Protector reads from and writes to devices and manages media.
Page 151: Before You Begin
• Ensure that you have correctly installed Data Protector. On how to install the Data Protector NNM integration in various architectures, see the HP Data Protector installation and licensing guide. Every NNM system you intend to back up from or restore to must have the Data Protector HP Network Node Manager Backup Integration and Disk Agent components installed.
Page 152: Creating Backup Specifications
Select the appropriate client and directories to be backed up from the client. Click Next. Select devices to use for the backup. To specify device options, right-click the device and click Properties. Click Next. Integrating HP Network Node Manager and Data Protector...
Page 153: Modifying Backup Specifications
Set backup options. IMPORTANT: If you have selected the NNM template, do not change the default pre- and post-exec options. If you have selected a different template, specify exactly the same pre-exec and post-exec scripts as specified in the NNM template. Click Next.
Page 154: Starting Backup Sessions
Use the Data Protector GUI. In the Context List, click Backup. In the Scoping Pane, expand Backup Specifications and then Filesystem. Right-click the backup specification you want to start and click Start Backup. Integrating HP Network Node Manager and Data Protector...
Page 155: Restore
They are only informational. Message [Warning] From: session_owner Time: mm/dd/yy hr:mn:sc [error code] path\HP OpenView\NNM\bin\tcl7.5.dll Cannot preserve time attributes: ([5] Access is denied.). Integration guide for VMware Virtual Infrastructure, Sybase, Network Node Manager,...
Page 156: Troubleshooting
Description The embedded database file referenced in this message has already been backed up as part of the pre-exec script. Its default location is in the path\HP OpenView\NNM\databases\analysis\default\backup directory, which is specified in the solid.ini file. After the restore, copy the backed up solid.db file from that directory to the active path\HP OpenView\NNM\databases\analysis\default directory.
Page 157: Before You Begin
For general Data Protector troubleshooting information, see the HP Data Protector troubleshooting guide. Before you begin • Ensure that the latest official Data Protector patches are installed. See the online Help index: “patches” on how to verify this. • See the HP Data Protector product announcements, software notes, and references for general Data Protector limitations, as well as recognized issues and workarounds.
Page 158 Problem Wrong number of arguments On Windows, Data Protector reports: Wrong number of arguments. Please specify pre or post backup. "NNMScript.exe pre" for pre-exec script "NNMScript.exe post" for post-backup script. Integrating HP Network Node Manager and Data Protector...
Page 159 Couldn’t find HP Network Node Manager key On Windows, Data Protector reports: Couldn’t find HP Network Node Manager key in registry. Action Ensure that NNM is installed on the target client and that the registry key HP Network Node Manager exists under HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\OpenView. Problem Couldn’t find the HP Network Node Manager PathName...
Page 160 Ensure that the NNM Perl compiler has not been removed and paths for Data Protector and NNM in the registry are correct. Problem Execution of NNM_perl_compiler_path Data_Protector_home\bin\*.ovpl failed On Windows, NNM reports: Integrating HP Network Node Manager and Data Protector...
Page 161 Execution of NNM_perl_compiler_path Data_Protector_home\bin\*.ovpl failed. Action Ensure that path\HP OpenView\NNM\bin is in the PATH and scripts are in the Data_Protector_home\bin directory. Otherwise, the command that starts NNMpre.ovpl or NNMpost.ovpl fails. Integration guide for VMware Virtual Infrastructure, Sybase, Network Node Manager,...
Page 162 Integrating HP Network Node Manager and Data Protector...
Page 163: Integrating Ndmp Server And Data Protector
• Full • Inc1 For information on these backup types, see the HP Data Protector concepts guide. The Data Protector NDMP Server integration offers two restore types: • Standard filesystem restore • Direct access restore This chapter provides information specific to the Data Protector NDMP Server integration.
Page 164: Data Protector Ndmp Server Integration Architecture
interfaces, the NDMP Server. Figure 58 on page 164 shows the architecture of the integration. Figure 58 Data Protector NDMP Server integration architecture Legend Session Manager Data Protector Session Manager: Backup Session Manager during backup and Restore Session Manager during restore. No Data Protector Disk Agents are involved in the session because the whole functionality is already implemented within the NDMP Media Agent.
Page 165: The Ndmp Environment Configuration
Data Protector supports two different NDMP Server types: • NetApp NAS device (NetApp) • Celerra NAS device (Celerra) In a typical environment (Figure 59 on page 165), the NDMP Server system and the Data Protector client with the NDMP Media Agent installed (NDMP client) are connected to the LAN.
Page 166: Configuring The Integration
Prerequisites • Ensure that you have correctly installed and configured NDMP Server. • For supported versions, platforms, devices, and other information, see the HP Data Protector product announcements, software notes, and references or http://www.hp.com/support/manuals. • For information on installing, configuring, and using NDMP Server, see the NDMP Server documentation.
Page 167: Specifying An Ndmp Server System
In Name, type the name of the NDMP Server system you want to import and select NDMP Server. Figure 60 Specifying an NDMP Server system Click Next. Integration guide for VMware Virtual Infrastructure, Sybase, Network Node Manager, and Network Data Management Protocol Server...
Page 168: Creating Media Pools
In NDMP Type, select the NAS device type. In Port, specify the TCP/IP port number of the NDMP Server. The default number is 10000. Provide the NDMP Server system user account that will be used by Data Protector to connect to the NDMP Server system. This user must have permission to read from and write to the NDMP media.
Page 169: Configuring Ndmp Devices
The NDMP media pool can only be used by devices using the NDMP data format (NDMP devices). Limitations • A medium cannot be used by different NMDP Server types. Consequently, data that was backed up from one NDMP Server type cannot be restored to another NDMP Server type.
Page 170: Library Configuration-I
Figure 62 Library configuration—I Integrating NDMP Server and Data Protector...
Page 171: Configuring Tape Libraries
If library robotics or drives are connected to the NDMP Server system, they can be controlled only by an NDMP client. Library drives can be shared between multiple NDMP Server systems and general Media Agent clients, and with other applications. For more information, see the HP Data Protector concepts guide. Limitations •...
Page 172: Configuring A Library
Type a name for the device. Optionally, describe the device. See Figure on page 172. In Device Type, select SCSI Library. In Interface Type, select the NAS device used. In Client, select the NDMP client that will control the library through the NDMP Server.
Page 173 Specify library robotics’ SCSI address and drive handling. For information, see “Network appliance configuration” on page 176 and “EMC Celerra configuration” on page 177. Click Next. Specify slots to be used by Data Protector. Click Next. Select the media type used in the library. Click Next.
Page 174: Configuring Standalone Devices
1 1. Click Yes to create another drive or NO to finish. On how to configure a tape library with robotics connected to a Data Protector NDMP or General Media Agent client and drives connected to the NDMP Server system, see the online Help index: “configuring SCSI libraries”. Then configure the drives as described in Step 8 on page 173 through...
Page 175: Configuring A Standalone Device
Type a name for the device. Optionally, describe the device. In Device Type, select Standalone. In Data Format, select the NAS device used. In Client, select the NDMP client that will control the device through the NDMP Server. In NDMP Server, select the NDMP Server system to which the standalone device is connected.
Page 176: Network Appliance Configuration
Specify the media pool. To specify advanced device options, click Advanced. For information on supported block sizes, see Table 24 on page 178. NOTE: Multiplexing data steams is not supported by NDMP Server, limiting device concurrency to 1. Click Finish. Network appliance configuration Before you begin •...
Page 177: Emc Celerra Configuration
Example The output for a DLT 4000 drive is: nrst0m - no rewind device, format is:42500 bpi 6.0GB Library robotics To get the SCSI address of the library robotics connected to the NDMP Server system, run: sysconfig -m on the NDMP Server system. The SCSI address consists of two parts. See Table on page 177.
Page 178: Block Size
Example Table 23 on page 178 for an example list of SCSI devices. c2t2l0 and c2t3l0 are the SCSI addresses of the drives in the tape library and c2t0l0 is the SCSI address of the library robotics. Table 23 Example of a list of SCSI devices Name SCSI address Device...
Page 179: Backup
NOTE: Although the Data Protector media formatting completes successfully, that does not guarantee that the NAS device supports the set block size, and backup may still fail. Limitations • The device used for restore must have the same or greater block size than the one that was used for backup.
Page 180: Before You Begin
• Once you have selected a directory, you cannot exclude any subdirectories or files from backup. Specifically, the following options are not supported: • Data Protector GUI: the Trees/Filters set of options: Trees, Excludes, Skips, and Onlys. • Data Protector omnib command: -trees, -exclude, -skip, and -only. Before you begin •...
Page 181: Selecting A Backup Template
Select a template. In Backup type, select Data mover backup. In Sub type, select NDMP-NetApp or NDMP-Celerra. See Figure 66 on page 181. Figure 66 Selecting a backup template Click OK. Integration guide for VMware Virtual Infrastructure, Sybase, Network Node Manager, and Network Data Management Protocol Server...
Page 182: Specifying The Ndmp Server Mountpoints For Backup (Unix)
Select the NDMP Server system you want to back up and click Add/Remove. In the Add/Remove Disk Mount Points dialog box, specify the filesystem mountpoints you want to back up: type the pathname of each directory in New mount point and click Add. See Figure 67 on page 182.
Page 183 Set backup options. Click Next. Optionally, schedule the backup. Click Next. Integration guide for VMware Virtual Infrastructure, Sybase, Network Node Manager, and Network Data Management Protocol Server...
Page 184: Specifying Advanced Netapp Options
Review the summary of the backup specification To specify the NDMP NetApp options for a specific backup object, right-click the object, click Properties, and click the NDMP tab. For each object, you can specify a new user account that will override the user account specified in the Import NDMP Host dialog box, provided that the access rights are properly set on the NetApp or Celerra NAS device system.
Page 185: Modifying Backup Specifications
Save the backup specification, specifying a name and a backup specification group. TIP: Preview backup session for your backup specification before using it. For details, see the online Help index: “previewing a backup”. Modifying backup specifications To modify your backup specification, click its name in the Scoping Pane of the Backup context, then click the appropriate tab, and apply the changes.
Page 186: Restoring Using The Data Protector Gui
Restoring using the Data Protector GUI In the Context List, select Restore. In the Scoping Pane, expand Filesystem, expand the client with the data you want to restore, and then click the object that has the data. In the Source page, browse for and select the objects you want to restore. In the Destination page, specify restore destination for every selected object.
Page 187: Direct Access Restore
Click Finish to start the restore. Direct access restore Direct access restore is an optimized data recovery operation. Backed up data is accessed directly, in the middle of a tape. This is achieved by partitioning backed up data into segments during backup and recording their start addresses.
Page 188: Selecting Ndmp Server Data For Direct Access Restore
Figure 70 Selecting NDMP Server Data for direct access restore Limitations • NetApp : • Direct access restore of files is supported on ONTAP v6.1.x and higher. • Direct access restore of directories is supported on ONTAP v6.4.x and higher. If you select both a directory and individual files from another directory and start the restore, only the selected files are restored.
Page 189: Restoring Using Another Device
Restoring using another device You can restore using a device other than that used for backup. For more information, see online Help. NDMP environment variables Set the NDMP environment variables for NetApp and Celerra NAS devices using the Data Protector GUI. See Figure 68 on page 184 and Figure 69...
Page 190: The Ndmp Specific Omnirc File Variables
Variable Value Function Restore collision policy for localization. MI/MD/MM NOTE: You can also set some NDMP environment variables using the omnirc file. For more information, see “The NDMP specific omnirc file variables” on page 190. The NDMP specific omnirc file variables On how to set the omnirc variables, see the online Help index: “omnirc options”.
Page 191 When set to 1, the NDMP Media Agent uses system physical memory only. When set to 0, the NDMP Media Agent stores part of the catalog in file history swap files. Set the variable to 0 whenever the number of files in the backup specification exceeds 5 millions.
Page 192: Media Management
Example Windows: C:\tmp, 32, 1024; D:\tmp\tmp_1, 10, 1024 UNIX: /tmp, 10, 1024; /var/tmp, 5, 60 When the files in the first directory are full, the integration writes data to the files in the next specified directory. If the allocated disk space is used up during the backup, the backup fails.
Page 193: Troubleshooting
For more information, see online Help. Troubleshooting This section lists problems you might encounter when using the Data Protector NDMP Server integration. For general Data Protector troubleshooting information, see the HP Data Protector troubleshooting guide. Before you begin • Ensure that the latest official Data Protector patches are installed. See the online Help index: “patches”...
Page 194 Action Ensure that the drive used for importing NMDP media is connected to an NDMP Server system. Problem A tape remains in the drive after a successful drive scan Action Eject the tape manually and set the OB2SCTLMOVETIMEOUT omnirc file variable on the NDMP client to a higher value (for example, 360000 or higher).
Page 195: A Integrating Citrix Xenserver And Hp Data Protector
Data Protector functionality, enables online and offline backup and restore of Virtual Machines hosted on a Citrix XenServer. For the supported version of Citrix XenServer for your version of Data Protector, refer to the HP Data Protector A.06.1x Virtualization support matrix.
Page 196: Offline Backup
Export the snapshot to the temporary backup folder as an .xva file. Delete the snapshot. After the script has finished, the contents of the temporary backup folder are backed up to the backup device using standard Data Protector functionality. Integrating Citrix XenServer and HP Data Protector...
Page 197: Offline Backup
Offline backup The process used by the integration script for an offline backup is as follows: If the virtual machine to be backed up is running, stop it. Export the virtual machine to the temporary backup folder as an .xva file. If the virtual machine was running before the backup, restart it.
Page 198: Restore Processes
When the restore option is set to true, the MAC of the old virtual machine is preserved Integrating Citrix XenServer and HP Data Protector...
Page 199: Restore Considerations
NOTE: The file type of the backup file for offline backup is the same as that for online backup, but it is possible to differentiate between offline and online backups from the filename. Refer to “Specifying a restore” on page 212 Restore considerations When a restore is performed, the original storage repositories used by the virtual machine are not known, so the user must specify in which storage repository the...
Page 200: Main Integration Components
During backup, virtual machines, or virtual machine disks, are exported to the Disk Agent host and backed up using Data Protector. The device used for the backup can be any device supported by Data Protector for file-system backup. Integrating Citrix XenServer and HP Data Protector...
Page 201: Installation Of The Integration
Figure 72) with the Data Protector Disk Agent installed and must be a member of a Data Protector Cell. For further details, refer to the HP Data Protector installation and licensing guide. The Data Protector Disk Agent must be installed first, since other software must be installed in specific Data Protector directories.
Page 202: Installation Of The Integration Scripts
For Data Protector A.06.1 1, on the Data Protector A.06.1 1 DVD–ROM in directory: • For Windows: DP611_WIN_OTHER\Windows_other\Xen_sup • For Linux: DP611_SOL_LINUX/Xen_sup • For other versions of Data Protector for which the integration is supported, as a download package: Go to http://www.hp.com/go/dataprotector Integrating Citrix XenServer and HP Data Protector...
Page 203 Click Patches and utilities. Select the Data Protector version with which you will be using the integration. Select Cross operating system (BIOS, Firmware, Diagnostics, etc.) In the Software-Solutions section, click Data Protector Release x.xx / Xen Server integration packet and download the package from the subsequent page.
Page 204: Integration Script Functions
Backup using the integration To produce a backup using the integration, you need to perform the following operations: Update the configuration script DPxen_config.py, or your own equivalent. Ensure that the temporary backup directory is empty. Integrating Citrix XenServer and HP Data Protector...
Page 205: Updating Configuration Script Dpxen_Config.py For Backup
Set up a Data Protector backup specification. Run the backup specification (or schedule it in the specification). These operations are described in this section. Updating configuration script DPxen_config.py for backup In the configuration file DPxen_config.py, or a configuration file with a name of your own, you can specify the following parameters required to perform the backup: Mode The type of backup to be used and whether all, or only specified virtual machines...
Page 206: Example Backup Configurations
= True sr = "" • Backup the virtual machines Debian and vm2 in hot mode, creating a debug file. Mode = "online" url = "http://tpc227.company.com" username = "user" password = "myPassword" Integrating Citrix XenServer and HP Data Protector...
Page 207: Creating A Backup Specification
vmName = ["Debian", "vm2"] debug = True sr = "" • Backup all the virtual machines present in the XenServer, without changing their power state. When the Mode selected is allOnline or allOffline, the value of the vmName parameter is ignored so its value is not important. In this example a debug file will not be created.
Page 208: Temporary Backup Folder Selection
Python25. Python must be installed in the correct location, as described in “Prerequisites” on page 201. NOTE: If the integration scripts have been installed on the Cell Manager, the full path must be given. For example, Data_Protector_home\bin\Python25. Integrating Citrix XenServer and HP Data Protector...
Page 209: Restore Using The Integration
• ScriptPath is the full path of the integration scripts, for example, Data_Protector_home\bin • ConfigFile is an optional parameter for specifying a configuration file with a name of your own. If this is omitted, the default configuration file DPxen_config.py is used. Click OK and then Next.
Page 210: Example Restore Configurations
Restore the Debian virtual machine, which was backed up using offline mode, into the default storage repository. Create a debug file. Mode = "offline" url = "http://tpc227.company.com" username = "user" password = "myPassword" vmName = ["Debian"] debug = False sr = "" Integrating Citrix XenServer and HP Data Protector...
Page 211 • Restore all the files backed up in the selected session into the default storage repository. The backup was performed in offline mode. Create a debug file. Mode = "allOffline" url = "http://tpc227.company.com" username = "user" password = "myPassword" vmName = [] debug = True sr = ""...
Page 212: Specifying A Restore
• offline or allOffline: servername_vmName.xva • online or allOnline: servername_vmName_Snapshot.xva Check the file format, to decide the mode of restore required, (it must be equivalent to the type of backup). See Figure Integrating Citrix XenServer and HP Data Protector...
Page 213: Selection Of Files To Restore
Figure 76 Selection of files to restore IMPORTANT: The Source tab shows the contents of the temporary backup folder when the backup session was performed. It does not show the current contents of the folder. It is important to ensure that the temporary backup folder is empty before performing a restore.
Page 214: Notes On Restore
For the latest snapshot support with your XenServer version, refer to the XenServer documentation. Integrating Citrix XenServer and HP Data Protector...
Page 215: Further Information
Before performing a backup, ensure that there is enough space on the Disk Agent host. If there is not enough space, the backup will fail. Further information For further information, refer to http://www.hp.com/go/dataprotector. Integration guide for VMware Virtual Infrastructure, Sybase, Network Node Manager, and Network Data Management Protocol Server...
Page 216 Integrating Citrix XenServer and HP Data Protector...
Page 217: 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 218 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 219 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 220 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 221: Backup Types
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 222 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 223 (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 224 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 225 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 226 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 227 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 228 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 229 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 230 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 231 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 232 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 233 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 234 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 235 (HP StorageWorks Disk Array XP specific term) HP StorageWorks Disk Array XP allows up to three mirror copies of a primary Integration guide for VMware Virtual Infrastructure, Sybase, Network Node Manager,...
Page 236 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 237 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 238 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 239 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 240 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 241 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 242 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 243 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 244 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 245 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 246 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 247 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 248 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 249 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 250 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 251 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 252 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 253 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 254 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 255 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 256 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 257 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 258 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 259 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 260 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 261 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. Integration guide for VMware Virtual Infrastructure, Sybase, Network Node Manager,...
Page 262 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 263 (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 264 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 265 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 266 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 267 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 268 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 269 (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 270 (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 271 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 272 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 273 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 274 Glossary...
Page 275: Index
Index backing up Sybase, 122 - 131 backup options, 127 architecture backup specifications, creating, 122 NDMP integration, 164 backup specifications, modifying, 127 Sybase integration, 114 database objects backup, 122 VMware integration, 31 full backups, 113, 122 audience, 17 scheduling backups, 127 scheduling backups, example, 127 starting...
Page 276 backup specification configuring NDMP, 166 - 179 XenServer integration, 207 configuring NDMP devices, 169 backup specifications, creating creating media pools, 168 integration, 152 importing NDMP Servers, 166 backup specifications, modifying configuring NNM, 150 - 151 integration, 153 configuring Sybase backup specifications, creating checking configuration, 121 NDMP...
Page 277 full backups monitoring sessions integration, 151 integration, 155 Sybase integration, 113, 122 Sybase integration, 145 VMware integration, 66 VMware integration, 109 help NDMP configuration obtaining, 27 configuring NDMP devices, 169 creating media pools, 168 technical support, 27 importing NDMP Servers, 166 NDMP integration concepts, 163 introduction, 163...
Page 278 NNM integration restore concepts, 150 XenServer integration, 209 introduction, 149 restore options monitoring sessions, 155 VMware integration, 89 backup, 151 - 155 restore from offline backup backup specifications, creating, 152 XenServer integration, 197 backup specifications, modifying, 153 restore from online backup backup templates, 152 XenServer...
Page 279 113, 122 integration, 154 troubleshooting NDMP, 193 - 194 Sybase integration, 130 troubleshooting NNM, 156 Subscriber's Choice, HP, 28 troubleshooting Sybase, 145 - 147 Sybase backup troubleshooting VMware, 109 - 112 database objects backup, 122 Sybase integration concepts, 113...
Page 280 37 - 48 restore, 77 - 109 troubleshooting, 109 - 112 VMware restore, 77 - 109 restore options, 89 using another device, 108 websites HP Subscriber's Choice for Business, , 28 product manuals, 17 XenServer integration concepts, 195 offline backup, 196 online...

HP Data Protector A.06.11 Integration Manual

Publication History

About this Guide

Integrating Vmware Virtual Infrastructure and Data Protector

Integrating Sybase Server and Data Protector

Integrating HP Network Node Manager and Data Protector

Integrating NDMP Server and Data Protector

A Integrating Citrix Xenserver and HP Data Protector

Quick Links

Troubleshooting

Related Manuals for HP Data Protector A.06.11

Summary of Contents for HP Data Protector A.06.11