Évaluations - , GPA:
(
)
)
Fabricant : HP
Taille : 1.12 mb
Nom Fichier :
Langue d'enseignement: 
Le document est chargé, s'il vous plaît patienter
 |
Le document est chargé, s'il vous plaît patienter
Par ce dispositif a également d'autres instructions :
Facilité d'utilisation
10 Special Notes
•
If a single virtual machine sits on two datastores and two virtual volumes, it is recommended
to include both virtual volumes in the same Remote Copy group.
•
In a disaster recovery scenario, when Remote Copy links are down, the Remote Copy group
status could still be Started. A failover attempt will not be successful until the Remote Group
status becomes Stopped.
•
HP 3PAR SRA configuration will not be deleted in the Windows registry when the HP 3PAR
SRA package is uninstalled.
•
If a virtual machine sits on a spanned datastore, all virtual volumes used for the spanned
datastore need to be included in a single Remote Copy group.
•
SRM might potentially time out if multiple test failover or recovery operations are run
simultaneously. Rerun the operation if the time out issue occurs. Alternatively, the time out issue
might be avoided if the operations are run sequentially.
•
If an ESX(i) host has both FC and iSCSI definitions created on the HP 3PAR Storage system
and vCenter Server also has both FC and iSCSI software adapter configured, per the vCenter
Server's request, LUNs will be exposed to both host definitions in the event of failover. However,
if only one host definition is presented on the HP 3PAR Storage system (either FC or iSCSI),
HP 3PAR SRA will only expose LUNs to whichever is defined on the HP 3PAR Storage system.
•
It is strongly recommended to configure one protected group per Remote Copy group.
•
If multiple Remote Copy groups are included in one protected group, it is recommended to
set the same sync time on all of the periodic Remote Copy groups.
•
Remote Copy group reserves .r for naming. Do not include the reserved naming in your
Remote Copy group name.
•
SRM_RO_
SRM_TARGETBK_RO_
SRA.
•
SRM might potentially run into a virtual volume promote operation during re-protect. If this
occurs, retry the re-protect operation.
•
HP 3PAR SRA can handle virtual volumes or virtual volume set exposed to host set. However,
it does not support it. In the event of failover, LUNs will be exposed to the ESX(i) host(s) as
individual LUNs and not a set. If the virtual volumes were exposed to the host set, LUNs will
be exposed to individual host as oppose as to a host set.
•
If virtual volumes are from a virtual volume set with multiple VMs created, be sure to include
all virtual volumes in a single HP 3PAR Remote Copy group and in the same protection group.
Otherwise there is a potential of losing connectivity to the VMs if virtual volumes are included
in more than one HP 3PAR Remote Copy group and not all Remote Copy groups are included
in the protection group.
•
If virtual volumes are part of a virtual volume set, LUNs exposed to the ESX(i) host that do not
have HP 3PAR Remote Copy configured and are not managed by SRM will lose the connectivity
of the LUNs.
•
HP 3PAR SRA can coexist with a Synchronous Long Distance Remote Copy group with HP
3PAR OS version 3.1.1 or above.
•
Devices on the protected storage system should be read-only after prepareFailover and
optionally take snapshots of the source devices for restoration if needed. The way to make a
device read-only to meet SRM's specification before failover is to remove VLUN exposure so
that no one has access to it. Remote Copy will internally manage the snapshot taking in case
something goes wrong during the failover process. In addition, HP 3PAR SRA will also take
26
Special Notes
...