Brocade Communications Systems StorageWorks 4400 - Enterprise Virtual Array Uživatelský manuál Strana 33

  • Stažení
  • Přidat do mých příruček
  • Tisk
  • Strana
    / 38
  • Tabulka s obsahem
  • KNIHY
  • Hodnocené. / 5. Na základě hodnocení zákazníků
Zobrazit stránku 32
33
Failback considerations
Failback is the process of setting the replication environment back to its original state at the protected site
prior to failover. Configuring the failback process with Site Recovery Manager is a manual process that
occurs after failover and the steps vary with respect to the degree of failure at the protected site. For
example, the failover could have been due to an array failure or the loss of the entire data center. The
manual configuration of failback is important since the protected site could have completely different
hardware and/or SAN configuration after a disaster occurred. Using Site Recovery Manager, once
failback is configured it can be managed and automated like any planned Site Recovery Manager failover.
The recovery steps can differ based on the conditions of the last failover that occurred. If failback follows an
unplanned failover, a full data re-mirroring between the two sites may be required. This step usually takes
the most time in a failback scenario.
Failback scenario
The following failback scenario uses Site Recovery Manager as a failback mechanism to Site A after
executing at Site B, with recovery plan R1 in recovery mode. Follow these steps to copy the scenario used
in testing.
Note: If you are preparing failback after a planned failover, this step can be
skipped.
1. Establish appropriate array replication from Site B to Site A with Command View EVA. Include all Vdisks
assigned to the protected virtual machines (VMFS datastores and Raw Device Mapping).
a. Create or reconfigure DR groups between Site B and Site A, with Site B virtual disks as the
source and Site A as the destination.
b. Set host presentation for all target Vdisks to ESX host(s) at Site A.
c. Set DR group destination host access to None.
Using VMware Infrastructure Client with Site Recovery Manager Plugin
2. Delete recovery plan R1 at Site B.
3. If Site A still has protection group or groups P1 in recovery plan R1, delete protection group(s) P1 at Site
A.
4. If it is not already in place, use the VI Client at Site B to establish Site A as the secondary site for Site B.
(If Site A does not have Site Recovery Manager installed, install Site Recovery Manager and the HP EVA
Replication Adapter at Site A.)
5. Create protection group or groups P2 at Site B to add virtual machines that must failback to Site A.
6. At Site A, create a recovery plan R2 for the protection group or groups P2.
7. After the user has determined with Command View that the virtual machines Vdisks have been fully
replicated to Site A, execute recovery plan R2 at Site A in test mode.
8. If the test is successful, execute recovery plan R2 in recovery mode.
9. At this point, you may want to re-protect recovered virtual machines to Site B:
10. Delete recovery plan R2 at Site A.
11. Delete protection group(s) P2 at Site B.
12. Create protection group(s) P3 at Site A to protect recovered virtual machines
13. At Site B, create a recovery plan R3 for the protection group or groups P3.
Zobrazit stránku 32
1 2 ... 28 29 30 31 32 33 34 35 36 37 38

Komentáře k této Příručce

Žádné komentáře