Remote Copy - HP StoreVirtual 4000 Release Note

Networking
In rare situations, creating a bond may result in an event notice
Due to timing issues in the software, after you create a new bond, the event notice NIC
Motherboard:Port2=down may appear. You can safely ignore this event. To verify that the
bond was created correctly, check the status of the bond by navigating to the storage system
Network category and select the TCP/IP tab.
HP LeftHand Recovery Manager
The CLI must be installed on the same system where the HP LeftHand Recovery Manager is installed
for auto-mount policy-related commands to work properly
To use related CLI commands, ensure that the CLI is installed on the same system where the
Recovery Manager is installed.
The Auto-Mount Policy window in the Recovery Manager does not indicate if the policy is added
for a volume set
The Recovery Manager can only provide volume set information on snapshots, not volumes.
The Windows Application Event log continuously fills with error messages if the auto-mount service
failed to mount a snapshot when the server is not found in the management group
1. In the Recovery Manager, pause the Auto-Mount policy until the server is added to the
management group.
2. In the CMC, add a server to the management group that contains the snapshot.
3. In the Recovery Manager, start the policy.
The Recovery Manager documentation for version 10.0 does not list the current supported versions
of SAN/iQ and Windows
The Recovery Manager documentation (Online Help and Deployment Guide) was not updated
for 10.0. Therefore, the "Supported version of Microsoft Windows Server" and "Supported
versions of SAN/iQ" lists do not include Microsoft Windows Server 2012 Datacenter and SAN/iQ
version 10.0, respectively. However, both of these versions are supported with Recovery Manager.
The Recovery Manager documentation will be updated in the next release.

Remote Copy

While cross–version Remote Copy is occurring from 10.0 to 8.5 management groups, if copying
halts because the cluster is full, the CMC displays the "See Alarms Window" error message,
although the 8.5 management group does not have the Alarms window
The version 9.x and greater Alarms and Events feature is not compatible with pre-9.x versions of
software. Review the Alarms window for version 9.x or later management groups. If you are
operating in a mixed SAN environment with management groups earlier than version 9.x, also
review the Alerts window.
Snapshots
Application-managed snapshots will not work if the Windows server running VirtualCenter Server
is not in the domain
The following workarounds apply to all supported versions of Microsoft Windows. The Windows
server computer name and full computer name must be the same for the workarounds to work.
Do one of the following:
◦
Create a domain and join the management computer to the domain
◦
Change the Pegasus server service logon:
18 Workarounds