HP Insight Recovery 6.3 User Guide

NOTE: For information on storage setup of cross technology logical servers (logical servers
capable of being VC hosted or VM hosted), refer to Dynamic workload movement with BladeSystem
Matrix: Fluid movement between physical and virtual resources for flexibility and cost-effective
recovery available at: http:// www.hp.com/go/insightrecovery
NOTE: For a list of supported storage, refer to the HP Insight Software 6.3 Support Matrix
available at: http://www.hp.com/go/insightdynamics/docs
NOTE: When Continuous Access XP storage replication is used, HP Insight Recovery depends
on the Cluster Extension for XP command line interface (CLI) to manage storage replication
(Continuous Access EVA storage replication does not require the installation of cluster extension
software). The Cluster Extension For XP CLI must be installed on a standalone Windows system.
Cluster Extension for XP depends on Raid Manager XP to manage XP storage replication. Raid
Manager instances and Raid manager configuration files must be configured to manage various
device groups that are configured in HP Insight Recovery. For more information, refer to:
• HP StorageWorks XP Cluster Extension Software documentation available at: http://
h20000.www2.hp.com - click on Manuals, then go to Storage –> Storage Software –> Storage
Replication Software –> HP StorageWorks XP Cluster Extension Software.
• HP StorageWorks XP RAID Manager documentation available at: http://
h20000.www2.hp.com - click on Manuals, then go to Storage –> Storage Software –> Storage
Device Management Software –> HP StorageWorks XP RAID Manager Software.
NOTE: With HP StorageWorks Continuous Access EVA storage replication, when an asynchronous
replication group is used in a recovery group and a recovery group failover occurs, a full copy of
the new source vDisks is automatically duplicated on the new destination vDisks. If a failure occurs
in the middle of this full copy operation, the data on the new destination vDisks could be corrupted.
To protect the new destination vDisks, you must make EVA Command View settings enabling
auto-suspend to prevent the automatic full copy operation. You will also need to backup the data
on the new destination vDisks, then manually resume the full copy. Alternatively, for a planned
failover, you can backup data on the source vDisks, before performing the failover.
NOTE: If the password for a Storage Management Server is changed, take the following actions
to refresh the Storage Management Server password on the CMS and in the HP Insight Recovery
configuration:
1. Discover the Storage Management Server with the changed password.
2. Go to the HP Insight Recovery user interface Storage Management Servers tab.
3. Select the Storage Management Server that has the changed password, and click on Edit.
4. Check the Refresh SIM Password box and click Save.
NOTE: Hyper-V virtual machines in clustered environments must be stored on cluster shared
volumes created from LUNs on EVA disk arrays.
Primary Site logical server setup
You must ensure that logical servers selected for DR protection at the Primary Site meet the following
requirements:
• The storage associated with these logical servers must be SAN based.
• If the logical servers you plan to protect with HP Insight Recovery at the Primary Site have not
been activated, and an operating system and applications have not been installed, these steps
must be completed before you can configure these logical servers for DR protection. Logical
servers that meet these conditions will appear in the Available LS(s) list in the Primary Site
configuration GUI, even if they are deactivated after they have been activated for the first
time.
Primary Site logical server setup 11