HP XP P9000 Replication Manager Software 7.6.1-00 Configuration Guide

NOTE:
The following restrictions apply:
SQL Server cluster configurations are not supported on guest operating systems, except for a
limited subset of configurations
between
guest operating systems, which are supported only in
Replication Manager version 7.1 and later. However, note that in these configurations, you must
use disks that are directly connected to iSCSI, and the SQL version must be one of the following:
SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012.
The backup server cannot support a Windows Server Hyper-V environment if a pass-through
connection is used and the secondary volume is recognized dynamically (hidden). Backup using
VSS is not supported if a pass-through connection is used.
Hyper-V Live Migration
In addition to the notes provided in the Application Agent CLI and Windows Server 2008 Hyper-V
documentation, please note the following points when using the Application Agent CLI under a guest
OS intended for live migration:
Use a configuration where the command device is not connected directly to the database server;
be sure to use a virtual command device. For details about how to set up a virtual command
device, see the P9000 RAID Manager documentation.
While it is possible to use a configuration where the command device is connected directly to the
database server, you must perform operations on the host OS to disconnect the command device's
drive from the guest OS prior to live migration and reconnect it after completion. For details about
these disconnection and connection operations, see the Microsoft documentation related to Win-
dows Server 2008 Hyper-V.
Use a configuration where the system drive of the guest OS is positioned in the VHD format on
the drive managed as a cluster shared volume (CSV) by the WSFC of the host OS. Replication
Manager does not support configurations where the system drive of the guest OS is positioned
on a drive that is used as a normal physical disk resource of a WSFC.
Virtual memory required when running Application Agent on a virtual machine
of Windows Server Hyper-V
See Virtual memory for information on virtual memory requirements.
Application Agent installation location
By default, the Common-Agent-Component-installation-folder is defined as follows.
For Windows 32-bit edition:
%ProgramFiles%\HDVM\HBaseAgent\
For Windows 64-bit edition:
%ProgramFiles(x86)%\HDVM\HBaseAgent\
If Device Manager Agent is pre-installed separately,
Common-Agent-Component-installation-folder is defined as follows:
folder-specified-by-HDvM-Agent-installer\HBaseAgent
Configuration Guide 81