HP Data Protector 6.2 software integration with HP 3PAR Storage System

9
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. Be aware that the size of the protected LUN is not just the amount of data
that is stored on the LUN, but the size of the provisioned virtual volume.
On-line Extension for ONE Windows / Linux system is a server-based license. You need as many of
these licenses as the number of application servers that are protected. It is not required to have a
license for standalone backup server.
Setup of 3PAR Storage System Components
To prepare a 3PAR Storage System for integration with Data Protector, the following steps must be
performed:
• Export source volumes to the application server
• Install and configure Microsoft MPIO with 3PAR
• Install and configure the 3PAR VSS Provider
All examples have been performed using FC SAN connection. No example has been done using
iSCSI SAN.
Export source volumes to the application server
Prior to starting with exporting of source Virtual Volumes to the application, ensure that the following
has been correctly configured:
• All application and backup servers have been properly zoned with the 3PAR Storage System
• Host objects for all application and backup systems have been created and configured. When
configuring host objects, make sure that the right Personas are set (see
Figure 8):
– For Windows 2008 based systems use second Persona:
Generic-AULA
– For Windows 2008 R2 based systems use first Persona:
Generic
If the application host is running as a Guest OS in either Microsoft Hyper-V or VMware EXS
environment, and the LUNs are accessed from the Guest OS as Pass through (Hyper-V) Raw Disk
Mapped (VMware) disk, the above rules also apply to that host.
If the virtual volume is going to be used by either an application running in a MS cluster or as a
Clustered Shared Volume, it has to be exported to all clients that are part of the cluster or that are
configured as the Hyper-V server.