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

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. For

more information on local client installation, refer to the Data Protector Installation Guide (see the For

more information section).

After all clients have been installed, the Microsoft Hyper-V virtual IP address must be imported. Client

import can be done using the Data Protector GUI. In the Clients scoping pane, right-click the Clients

subfolder. In the pop-up menu, select Import Client option. After specifying the name of the virtual IP

address, change the type of client to Hyper-V (see

Figure 42). This virtual IP address should be used

whenever Microsoft Hyper-V backup specification is created.

Figure 42: Importing Microsoft Hyper-V virtual IP address

In earlier Data Protector versions, Hyper-V backups are configured using MS Virtual Shadow Copy

Writers folder. Due to backward-compatibility reasons, this is also supported in Data Protector 6.2,

but it is not recommended. However, there are some use cases where this integration should be used.

Refer to the Data Protector 6.20 Integration Guide for Virtual Environments for more details. In Data

Protector 6.2, a dedicated agent has been developed for protection of virtual environments. This

agent is part of Virtual Environment Integration. This agent should be used for backup of virtual

machines running on Microsoft Hyper-V setup. The Virtual Environment Integration must be installed

on servers running Windows OS. For this integration to operate, a SAN connection is not required.

Additionally, 3PAR VSS Provider must be installed and configured on all Hyper-V servers and on the

backup host also.