HP Data Protector 6.2 software integration with HP 3PAR Storage System Zero Downtime Backup solution Technical white paper Table of contents Executive summary............................................................................................................................... 2 Audience ............................................................................................................................................ 2 Concepts ..............................................................
Executive summary This white paper provides detailed information on how to integrate HP Data Protector software with HP 3PAR Storage Systems. The solution is based on Data Protector Zero Downtime Backup concept. The 3PAR InServ version mentioned and tested here is 2.3.1. The Data Protector version is 6.2.
VSS Writer Each application or service that is running on Windows and wants to integrate with VSS framework has to provide a VSS Writer specific for that application or service. The writer is responsible to quiesce (pause) the application’s data and make it suitable for a make shadow copy/replica and backup operation. At the same time, the application continues to be available to the user.
providers, the operating system does not need to maintain the point-in-time view of the replica. This job is off-loaded to the disk array that takes care that the replica maintains the same data during its lifetime. HP 3PAR Storage System provides the VSS Hardware Provider (HWP). Solution Description This solution is based on HP Data Protector 6.2 using Zero Downtime Backup and HP 3PAR Storage System.
• 3PAR InForm Management Console is installed on one of the servers and manages the HP 3PAR Storage System. Once the backup session is started, Data Protector will resolve the volumes involved in the backup. During this phase, Data Protector finds out on which storage volumes the selected objects are located. Finally, it requests the creation of a snapshot for each of those volumes by using 3PAR Hardware Provider. This copy is a replica or a virtual copy snapshot in 3PAR terms.
At this point, the snapshot is visible on the backup host and data can be read and streamed to the tape device by the Data Protector Media Agent. In Figure 5, the backup to tape is shown by the red line between the snapshot volume, the backup host and the tape drive.
Figure 6: Virtual Copies are kept after backup Preparing the environment Data Protector Setup Data Protector Cell Server can be installed on either Windows or UNIX servers. The MS Volume Shadow Copy Integration module must be installed on the application and backup servers (see Figure 7). In addition, the Media Agent must be installed on each server that can act as the backup server. However, the application server can also be the backup server at the same time.
Figure 7: Data Protector Components available for installation 8
Licensing Data Protector MS Volume Shadow Integration requires at least one terabyte (1 TB) of the following licenses to be available: Windows Zero Downtime Backup for 1 TB Windows zero downtime backup license is a terabyte-based license. The terabyte-amount of this license must be equal to, or higher than, the sum of disks to be protected by the integration in the whole Data Protector Cell.
Figure 8: 3PAR Storage System Host Object Configuration Installation and configuration of Windows Multipath I/O Feature (MPIO) HP 3PAR supports native Windows 2008 and Windows 2008 R2 MPIO. To configure MPIO for 3PAR Storage System, several steps must be performed: • Install Windows MPIO Feature using Server Manager (see Figure 9). • Start disk rescan using the Disk Management tool. At this point, you should be able to see all VLUNs that are exported to the server.
• The VLUNs are now ready to be used on the system.
Figure 11: Add 3PAR Virtual Volumes to the list of supported MPIO Devices Install and configure 3PAR VSS Provider Prior to installing 3PAR VSS Provider, the following software must be installed on the server: • Microsoft .NET Framework 3.5 • 3PAR InForm CLI 3PAR VSS Provider installer will first install Visual C++ Runtime Libraries. After these libraries are installed, installer will start with the provider installation and configuration.
Figure 12: Installation and configuration of 3PAR VSS Provider The installation process will check if the provided credentials are valid.
Figure 13: Credential and license check at the end of 3PAR VSS Provider installation Note 3PAR VSS Provider must be installed on both application and backup host. To verify that installation was successful, execute following command: C:\Users\administrator.TIC>vssadmin list providers vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool (C) Copyright 2001-2005 Microsoft Corp.
Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5} Version: 1.0.0.7 If installation was successful, 3PAR VSS Provider should be listed in the command output. Additional 3PAR InServ Storage Systems can be configured with 3PAR VSS Provider using the following CLI command: C:\Program Files\3par\HWPRV>ProvCfg.exe InServ -sys par002.hp.com -user DP -pass myPassword -sockssl on Success. Configuration for InServ Storage System has been created successfully.
Figure 14: Copy Space Settings For an up-to-date list of supported environments, operating systems and applications, see the Data Protector VSS Integration Support matrix listed in the For more information section. Configuring Data Protector Backup Specifications VSS based backups must be configured using MS Volume Shadow Copy Integration.
Figure 15: Configuring MS Volume Shadow Copy transportable backup On the next wizard window, it is possible to select several options that are specific to the Volume Shadow Copy Integration (see Figure 16): • Application system: server on which the application, in our case, file system, resides. • Backup system: server from which streaming to media will be performed. On this server, in addition to the MS Volume Shadow Copy Integration, the Media Agent component must be installed (see Figure 7).
Figure 16: MS Virtual Shadow Copy Integration options Figure 17: Replica management Settings 18
Figure 18: Mount option settings • Directory where replicas will be mounted is calculated from the combination of root mount point value and the additionally specified mount paths. In case that root directory is c:\mnt and that user specifies Hostname + session ID option, mount directory for the source volume that was mounted on F:\ drive letter on application host tpc200.zdbe14.test and replica was made in session with the ID 2011/04/12-3, will look like following: C:\mnt\tpc200.zdbe14.
sure that the file systems all reside on the 3PAR Storage System. If the file system does not reside on the disk array, the backup session will fail. In the next wizard window, it is possible to specify the media drive where the backup should be stream to. Ensure that the selected backup device is configured to be accessed from the backup host. If this is not the case, the data will be transferred over the LAN to the server from where backup device/drive is accessible.
Figure 20: Select components to be restored. There are two restore modes available: • Restore components will restore the whole data that was backed up on the selected file system • Restore files to temporary location gives you the possibility to restore single files to either the original destination or to any other server or location (see Figure 21). To specify alternative server or location where selected files should be restored, use the Options tab.
Figure 21: Select single files to be restored. Figure 22: Select the backup from which data should be restored. An example of the file system restore-session report can be found in Appendix B: in File System Restore section. File System restore from virtual copy In case the virtual copy still exists, it is possible to restore the whole LUN on which the file system exists by promoting the virtual copy to the source virtual volume.
C:\Users\administrator.ZDBE14>"c:\Program Files\OmniBack\bin\omnidbvss.exe" -list session Session Key IR Disk-Only Barlist Name =============================================================================== [0] 2011/04/12-1:tpc200 FALSE FALSE FStest [1] 2011/04/12-2:tpc200 FALSE FALSE FStest [2] 2011/04/12-3:tpc200 FALSE FALSE FStest C:\Users\administrator.
Number of Mount Points: 1 Mount points: C:\restore\tpc200.zdbe14.test\2011-04-12-3\F\ [Normal] From: OB2BAR_VSSBAR@tpc200.zdbe14.test "MSVSSW" Putting backup disks into read-only mode. Time: 4/12/2011 12:50:26 PM [Normal] From: OB2BAR_VDSA@tpc200.zdbe14.
Figure 23: Content of virtual copy is available on the application system. Microsoft SQL backup Microsoft SQL Server provides support for creating snapshots from SQL Server data using VSS by providing SQL writer. Starting with MS SQL version 2005, SQL writer is included in the MS SQL installation. To check if the writer is properly installed and if it is in the proper, stable state, execute following command on the server where MS SQL Server is running: C:\>vssadmin list writers vssadmin 1.
To create a Microsoft SQL backup specification, use the same procedure as for the file system backup specification creation. The only difference is in the selection of components to be backed up. In the list of available writers, under SqlServerWriter, select components that you would like to backup in this backup specification. You can select either the whole MS SQL instance or specific database (see Figure 24).
Figure 25: Select Microsoft SQL Writer components to be restored. Restore to any point-in-time from media To be able to restore MS SQL database to any point-in-time, the following is required: • All transaction log backups must be available from the time when the full VSS based backup was taken until the desired time at which the database should be recovered.
Disk-Only: FALSE Component Name =============================================================================== [0] /SqlServerWriter(SQL Server 2008 R2:SQLWriter)/TPC193/DB1_3PAR Storage ID =============================================================================== [0] DP-1-Volume-Basic-100000-ffd00000-{72a912c8-0000-0000-0000000000000000}:tpc193.tic.dp [1] DP-1-Volume-Basic-100000-ffd00000-{72a912c9-0000-0000-0000000000000000}:tpc193.tic.
[Normal] From: OB2BAR_VSSBAR@tpc193.tic.dp "MSVSSW" Saving writer configuration. Time: 4/18/2011 9:22:21 PM [Normal] From: RSM@ita030.deu.hp.com "" Time: 4/18/2011 9:25:32 PM OB2BAR application on "tpc193.tic.dp" disconnected. [Normal] From: RMA@tpc194.tic.dp "FL194_Writer0" Time: 4/18/2011 9:22:49 PM Unloading medium to slot C:\FL1\10394b8254dac5491551665009a.fd from device FL194_Writer0 [Normal] From: RMA@tpc194.tic.
Figure 27: Restore of MS SQL transaction log 30
Figure 28: Select option to leave database in the restore mode in order to be able to restore additional transaction logs An example of the restore-session output of transaction logs can be found in the Appendix B: Microsoft SQL Server Transaction Log Restore section. Microsoft SQL restore from virtual copy In situations that virtual copies/snapshots are still available, it is possible to restore the database data by promoting virtual copies to its parents.
• In cases where MS SQL is running in the MS cluster, put all involved disks in the maintenance mode. • Retrieve disk signature from all disks (use diskpart detail disk CLI) • Unmount all involved disks and put them in offline mode. • Remove all presentations from all virtual LUNs (un-export virtual LUNs) from all hosts. • Promote all virtual copies to the parent LUN. Note that you have to promote the read-only (marked with ro) virtual copy (see Figure 29).
[Normal] From: OB2BAR_VSSBAR@tpc193.tic.dp "MSVSSW" Gathering Existing Writer Metadata. Time: 4/19/2011 1:14:59 AM [Normal] From: OB2BAR_VSSBAR@tpc193.tic.dp "MSVSSW" Gathering Backed Up Writer Metadata. Time: 4/19/2011 1:15:01 AM [Normal] From: OB2BAR_VSSBAR@tpc193.tic.dp "MSVSSW" Checking writer configuration. Time: 4/19/2011 1:15:01 AM [Normal] From: OB2BAR_VSSBAR@tpc193.tic.dp "MSVSSW" Performing Pre-Restore phase. Time: 4/19/2011 1:15:01 AM [Normal] From: OB2BAR_VSSBAR@tpc193.tic.
integration for backup of Exchange 2010 has been introduced. However, this integration is based on the Data Protector MS Volume Shadow Copy Service Integration. It is highly recommended to use this integration for backup of Exchange 2010. To use this integration, you are required to install Data Protector’s MS Exchange Server 2010 Integration on all Exchange 2010 servers (see Figure 7). In addition, MS Volume Shadow Copy Integration has to be installed on all these servers.
Figure 31: Microsoft Exchange 2010 DAG setup with 3PAR Storage System Figure 32 shows how the configuration appears in the Exchange Management Console. Figure 32: Microsoft Exchange 2010 Management Console view of the setup Before starting to create a backup specification, ensure that Exchange 2010 writers on all servers are configured and are in a stable state. The following command can be used to check the state of the writers. C:\Users\administrator.ZDBE14>vssadmin list writers vssadmin 1.
Writer Instance Id: {92c255ce-7a79-42a8-b6f0-df6350d3d057} State: [1] Stable Last error: No error . . . . Writer name: 'Microsoft Exchange Writer' Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7} Writer Instance Id: {e6e7deda-42f6-47bd-b022-40e3eea7627b} State: [1] Stable Last error: No error C:\Users\administrator.ZDBE14> Note that there are two writers available on the system.
Figure 33: Microsoft Exchange 2010 backup specification In the next wizard window, specify the DAG’s name or the physical name of the Exchange server (see Figure 34). In cases where the DAG name is entered, Data Protector provides a server-independent database view as shown in (see Figure 35). For backup host, select the server that has the local access to the drives that will be used for the backup. All other options can be set in the same way as it was described in the File System backup section.
Figure 34: Configuring VSS transportable backup options In the following window, a list of all available databases is shown (see Figure 35). Select the database(s) to be backed up and go to the next window. Figure 35: Select databases to be backed up In the next wizard window (see Figure 36), it is possible to set the policies on which server the copy of the database(s) will be backed up.
Figure 36: Select a backup policy The next step is to specify the media to be used for the backup. In the next window (see Figure 37), it is possible to specify application-specific options such as: • Pre-exec and Post-exec executables that will be started before and after the backup is done. These executables will be started at the node where the DAG Virtual IP address is pointing to at the time of the backup. • Consistency check options.
Figure 37: Microsoft Exchange Server 2010 Specific Options The remaining scheduling options have been described previously in the File System backup section. After creation of backup specification is done, start the backup. An example of the Exchange 2010 Server backup-session report can be found in Appendix B: Microsoft Exchange 2010 Backup section. The same backup specification can be used for backup of logs.
Figure 38: List of Microsoft Exchange 2010 servers that can be restored Figure 39: Restore options for Microsoft Exchange Server 2010 when failed database exists As soon as the database to be restored is selected, a window with the restore options will pop up (see Figure 39). Data Protector runs a discovery of the selected Microsoft Exchange 2010 database before this window is presented (this may take several minutes).
• Restore to a point-in-time, see Figure 40 • Restore to a new mailbox database, see Figure 40 (this can also be used for single mail recovery using the recovery database) • Restore files to a temporary location Figure 40: Additional restore options for Microsoft Exchange Server 2010 database Now you are ready to start the restore process of a failed database.
C:\Users\Administrator.TIC>vssadmin list writers vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool (C) Copyright 2001-2005 Microsoft Corp. Waiting for responses. These may be delayed if a shadow copy is being prepared. … Writer name: 'Microsoft Hyper-V VSS Writer' Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de} Writer Instance Id: {1ef504da-5a9f-4259-b995-a40cfbe0b7b5} State: [1] Stable Last error: No error … C:\Users\Administrator.
Installation and configuration Data Protector MS Volume Shadow Copy Integration agent must be installed on each of the servers that are part of the Hyper-V cluster (see Figure 7). Installation must be done in the same way as with a Microsoft Failover Cluster aware installation. Currently, this is not possible with the push installation from Data Protector’s GUI. Instead, installation of agents must be done locally on each server.
Note Servers that are part of the Microsoft Hyper-V setup cannot be used as backup hosts due to Microsoft Hyper-V limitations. In order to successfully complete the replica creation, it is required to enable automatic mounting of new volumes on all Hyper-V servers. To enable automatic mounting, run the following command: C:\Users\Administrator.
Figure 44: Select virtual machines to be backed up An example of the Microsoft Hyper-V backup-session report can be found in Appendix B: Microsoft Hyper-V Backup section. Microsoft Hyper-V R2 restore from media To restore a virtual machine that is running on Microsoft Hyper-V, under the Virtual Environment subfolder in Restore scoping pane, select the system under which Microsoft Hyper-V is running (see Figure 45). Under Source tab, select the virtual machine that you want to restore.
Figure 46: Select options for virtual machine restore. Note Before starting the restore session, ensure that the virtual machine that is about to be restored, is deleted or exported from the Microsoft Hyper-V. An example of the Microsoft Hyper-V restore-session report can be found in Appendix B: Microsoft Hyper-V Restore section. After the restore session is completed, the virtual machine is restored and brought online.
Appendix A: Command Line Interface List available Data Protector licenses CLI used to list available Data Protector licenses: C:\Program Files\OmniBack\bin>omnicc Licensing mode License server : Local : vmw35030.zdbe14.test Category Number of Licenses ... On-line Extension for ONE Windows / Linux system 20 ... Windows Zero Downtime Backup for 1 TB ...
Script used for manual MS SQL database restore The following is the script used for the manual MS SQL database restore: C:\>type "C:\Program Files\OmniBack\bin\SQL_man_restore.bat" @echo off echo delete this file as soon as restore finished > c:\deleteWhenFinished.txt echo Executing vss manual restore echo ======================================================================= echo Please start restore of SQL server files now! echo Delete file C:\deleteWhenFinished.
Appendix B: Session Outputs File System Backup The following is a sample of the file system backup-session report with the session id 2011/04/12-3: [Normal] From: BSM@vmw35030.zdbe14.test "FStest" Backup session 2011/04/12-3 started. Time: 4/12/2011 2:47:25 AM [Normal] From: BSM@vmw35030.zdbe14.test "FStest" Time: 4/12/2011 2:47:28 AM OB2BAR application on "tpc200.zdbe14.test" successfully started. [Normal] From: OB2BAR_VSSBAR@tpc200.zdbe14.test "MSVSSW" Performing Full Transportable Backup.
[Normal] From: OB2BAR_VSSBAR@tpc201.zdbe14.test "MSVSSW" Time: 4/12/2011 2:48:03 AM Disk Backup of '/Filesystem/F' completed successfully. [Normal] From: BMA@tpc201.zdbe14.test "HP:Ultrium 4-SCSI_4_tpc200" AM STARTING Media Agent "HP:Ultrium 4-SCSI_4_tpc200" Time: 4/12/2011 2:48:06 [Normal] From: BMA@tpc201.zdbe14.test "HP:Ultrium 4-SCSI_4_tpc200" AM By: UMA@tpc200.zdbe14.test@scsi4:0:0:0 Loading medium from slot 21 to device Tape3:0:2:4C Time: 4/12/2011 2:48:12 [Normal] From: OB2BAR_VSSBAR@tpc201.
OB2BAR application on "tpc200.zdbe14.test" disconnected. [Normal] From: BMA@tpc201.zdbe14.test "HP:Ultrium 4-SCSI_4_tpc200" AM Tape3:0:2:4C Medium header verification completed, 0 errors found. Time: 4/12/2011 2:50:37 [Normal] From: BMA@tpc201.zdbe14.test "HP:Ultrium 4-SCSI_4_tpc200" AM By: UMA@tpc200.zdbe14.test@scsi4:0:0:0 Unloading medium to slot 21 from device Tape3:0:2:4C Time: 4/12/2011 2:50:39 [Normal] From: BMA@tpc201.zdbe14.
Unloading medium to slot 21 from device Tape3:0:0:4C [Normal] From: RMA@tpc200.zdbe14.
Source volume: Originating host: Service host: Creation time: Creation date: Provider ID: \\?\Volume{42d09a48-5fdd-11e0-a41d-001cc4db0318}\ tpc193.tic.dp tpc193.tic.dp 5:07:05 PM Monday, April 18, 2011 {5F466535-9C6C-4B33-BE9F-8F3147381CF5} [Normal] From: OB2BAR_VSSBAR@tpc194.tic.
[Normal] From: OB2BAR_VSSBAR@tpc194.tic.dp "MSVSSW" Proceeding with Tape Backup. Time: 4/18/2011 5:08:06 PM [Normal] From: OB2BAR_VSSBAR_COMP@tpc194.tic.dp "MSVSSW" Time: 4/18/2011 5:08:06 PM Starting OB2BAR Backup: tpc193.tic.dp:/SqlServerWriter(SQL Server 2008 R2:SQLWriter)/TPC193/DB1_3PAR "MSVSSW" [Normal] From: OB2BAR_VSSBAR_COMP@tpc194.tic.dp "MSVSSW" Time: 4/18/2011 5:08:08 PM Completed OB2BAR Backup: tpc193.tic.
============================================================================ Session completed successfully! ============================================================================ Microsoft SQL Server Transaction Log Restore The following is a sample of the Microsoft SQL Server restorep-session report with the session id 2011/04/18-41 where only transaction logs are being restored: [Normal] From: RSM@ita030.deu.hp.com "" Time: 4/18/2011 9:31:25 PM Restore session 2011/04/18-41 started.
[Normal] From: OB2BAR_Main@tpc193.tic.dp "(DEFAULT)" Time: 4/18/2011 9:28:58 PM Database statistics: -------------------------------------------------------------1. DB1_3PAR 1 MB 1 min (379 Mb/h) -------------------------------------------------------------[Normal] From: RSM@ita030.deu.hp.com "" Time: 4/18/2011 9:32:08 PM OB2BAR application on "tpc193.tic.dp" disconnected. [Normal] From: RMA@tpc194.tic.
[Normal] From: OB2BAR_VSSBAR@tpc202.zdbe14.test "MS Exchange 2010 Server" Time: 4/29/2011 4:09:37 PM Volume 'C:\mnt\Exchange\3par\DB1\data\' was successfully added to Shadow Copy Set with the following provider: Provider type: Hardware Provider name: 3PAR VSS Provider Provider version: 1.6.2.3 [Normal] From: OB2BAR_VSSBAR@tpc202.zdbe14.
Storage ID: DP-1-Volume-Basic-100000-ffd00000-{b37d4faa-00000000-0000-000000000000} Software VDS Provider: Microsoft Virtual Disk Service Basic Provider Number of Disks: 1 Number of Mount Points: 0 Device Path: \\?\SCSI#Disk&Ven_3PARdata&Prod_VV#7&120fcb3&0&000003#{53f56307-b6bf-11d0-94f2-00a0c91efb8b} Disk GUID: {B37D4FAA-0000-0000-0000-000000000000} Disk Address: Port3Path0Target0Lun3 [Normal] From: OB2BAR_VDSA@tpc200.zdbe14.
Completed OB2BAR Backup: tpc202.zdbe14.test:/Microsoft Exchange Writer(Exchange Information Store)/Microsoft Information Store/33d5875e-c049-47d7-887d-20b465e807d9/Logs "MSVSSW-APP" [Normal] From: BMA@tpc200.zdbe14.test "HP:Ultrium 4-SCSI_1_tpc200" PM Tape0:0:0:1C Medium header verification completed, 0 errors found. Time: 4/29/2011 5:11:24 [Normal] From: BMA@tpc200.zdbe14.test "HP:Ultrium 4-SCSI_1_tpc200" PM By: UMA@tpc200.zdbe14.
The volume with properties was put into read-only mode: Storage ID: DP-1-Volume-Basic-100000-ffd00000-{b37d4faa-00000000-0000-000000000000} Number of Mount Points: 1 Mount points: C:\mnt\tpc202.zdbe14.test\2011-04-29-2\C\mnt\Exchange\3par\DB1\data\ [Normal] From: OB2BAR_VSSBAR@tpc200.zdbe14.test "MS Exchange 2010 Server" 5:16:18 PM Putting backup disks into read-only mode. Time: 4/29/2011 [Normal] From: OB2BAR_VDSA@tpc200.zdbe14.
Session completed successfully! ============================================================================ Microsoft Exchange 2010 Restore The following is an example of an Exchange 2010 restore session output: [Normal] From: RSM@vmw35030.zdbe14.test "" Time: 5/2/2011 10:55:45 AM Restore session 2011/05/02-1 started. [Normal] From: OB2BAR_E2010_BAR@tpc200.zdbe14.test "MS Exchange 2010 Server" 10:56:03 AM Analyzing MS Exchange Server 2010 environment.
[Normal] From: RMA@tpc201.zdbe14.test "HP:Ultrium 4-SCSI_1_tpc200" AM By: UMA@tpc200.zdbe14.test@scsi4:0:0:0 Loading medium from slot 3 to device Tape1:0:2:1C Time: 5/2/2011 10:57:55 [Normal] From: OB2BAR_VSSBAR_COMP@tpc201.zdbe14.test "MS Exchange 2010 Server" Time: 5/2/2011 10:58:11 AM Starting OB2BAR Restore: tpc202.zdbe14.
Microsoft Hyper-V Backup The following is an example of a backup- session output from a backup of one virtual, vmOn3PAR, machine running on Microsoft Hyper-V: [Normal] From: BSM@tpc040.tic.dp "3PAR" Time: 4/29/2011 4:35:32 PM Backup session 2011/04/29-1 started. [Normal] From: BSM@tpc040.tic.dp "3PAR" Time: 4/29/2011 4:35:34 PM OB2BAR application on "tpc040.tic.dp" successfully started. [Normal] From: OB2BAR_VEPA_BAR@tpc040.tic.dp "HyperV" Performing Hyper-V backup.
Storage ID: DP-1-Volume-Basic-100000-ffd00000-{bf400d5a-00000000-0000-000000000000} Software VDS Provider: Microsoft Virtual Disk Service Basic Provider Number of Disks: 1 Number of Mount Points: 0 Device Path: \\?\scsi#disk&ven_3pardata&prod_vv#5&1124384d&0&000103#{53f56307-b6bf-11d0-94f200a0c91efb8b} Disk GUID: {BF400D5A-0000-0000-0000-000000000000} Disk Address: Port3Path0Target1Lun3 [Normal] From: OB2BAR_VSSBAR@tpc040.tic.
Disk GUID: Disk Address: {BF400D5A-0000-0000-0000-000000000000} Port3Path0Target1Lun3 [Normal] From: OB2BAR_VSSBAR@tpc048.tic.dp "HyperV" Backup completed. Time: 4/29/2011 4:47:30 PM [Normal] From: OB2BAR_VEPA_BAR@tpc040.tic.dp "HyperV" VSS finished successfully. Time: 4/29/2011 4:42:22 PM [Normal] From: OB2BAR_VEPA_BAR@tpc040.tic.dp "HyperV" Time: 4/29/2011 4:42:22 PM Starting OB2BAR Backup: dl380er.tic.
[Normal] From: OB2BAR_VSSBAR@tpc049.tic.dp "HyperV" Loading Backup Metadata from VSS db. Time: 4/29/2011 6:18:31 PM [Normal] From: OB2BAR_VSSBAR@tpc049.tic.dp "HyperV" Connecting to Volume Shadow Copy Service. Time: 4/29/2011 6:18:31 PM [Normal] From: OB2BAR_VSSBAR@tpc049.tic.dp "HyperV" Gathering Existing Writer Metadata. Time: 4/29/2011 6:18:31 PM [Normal] From: OB2BAR_VSSBAR@tpc049.tic.dp "HyperV" Gathering Backed Up Writer Metadata. Time: 4/29/2011 6:18:39 PM [Normal] From: OB2BAR_VSSBAR@tpc049.
For more information To read more about HP Data Protector, go to http://www.hp.com/go/dataprotector To access the following documents, an HP-Passport login is required: HP Data Protector 6.20 Integration Guide for Microsoft Volume Shadow Copy Service HP Data Protector 6.20 VSS integration support matrix HP Data Protector 6.20 Command Line Interface Reference HP Data Protector 6.20 Integration Guide for Microsoft Application HP Data Protector 6.20 Installation and Licensing Guide HP Data Protector 6.
