This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Failover testing is an essential component in disaster recovery planning. You can use the Disaster Recovery wizard to perform non-disruptive testing of your disaster recovery system. During a test failover operation, all the steps are the same as for failover. However, instead of starting after they are recovered to the DR site, the VMs and vApps are placed in a paused state. At the end of test failover, the wizard automatically removes all VMs, vApps, and storage recreated on the DR site.
After initial DR configuration, verify that failover works correctly by performing a test failover. We recommend you also do a test failover after you make significant configuration changes in a DR-enabled pool.
To perform a test failover of VMs and vApps to a secondary site:
In XenCenter, select the secondary pool, and on the Pool menu, click Disaster Recovery to open the Disaster Recovery wizard.
Select Test Failover and then click Next.
If you use Fibre Channel shared storage with LUN mirroring to replicate the data to the secondary site, break mirroring before you attempt to recover data. This action gives the secondary site Read/Write access.
Select the storage repositories (SRs) containing the pool metadata for the VMs and vApps that you want to recover. By default, the list on this wizard page shows all SRs that are currently attached within the pool. To scan for more SRs, choose Find Storage Repositories and then select the storage type to scan for:
- To scan for all the available Hardware HBA SRs, select Find Hardware HBA SRs.
- To scan for software iSCSI SRs, select Find Software iSCSI SRs and then enter the target host, IQN, and LUN details in the dialog box.
When you have selected the required SRs in the wizard, click Next to continue.
Select the VMs and vApps that you want to recover.
Click Next to progress to the next wizard page and begin failover prechecks.
Before beginning the test failover process, the wizard performs pre-checks. For example, the checks ensure all the storage required by the selected VMs and vApps is available.
- Check that storage is available. If any storage is missing, you can click Attach SR on this page to find and attach the relevant SR.
- Check that HA is not enabled on the target DR pool. To avoid having the same VMs running on both the primary and DR pools, disable high availability on the secondary pool. This action ensures that high availability does not automatically start the recovered VMs and vApps after recovery. To disable high availability on the secondary pool, click Disable HA on this page. (If the wizard disables high availability at this point, it is enabled again automatically at the end of the test failover process.)
Resolve any issues on the pre-checks page, and then click Failover to begin the test failover.
A progress page is displayed showing whether recovery was successful for each VM and vApp. Failover can take some time depending on the number of VMs and vApps you are recovering. The following actions occur during this process:
- Metadata for the VMs and vApps is recovered from the replicated storage
- VMs and vApps are re-created in the DR pool
- SRs containing the virtual disks are attached to the re-created VMs
- The recovered VMs are placed in a paused state. The VMs are not started on the secondary site during a test failover.
After you are satisfied that the test failover was performed successfully, click Next in the wizard to have the wizard clean up on the DR site:
- VMs and vApps that were recovered during the test failover are removed.
- Storage that was recovered during the test failover is detached.
- If the wizard disabled high availability on the DR pool at the prechecks stage to allow the test failover to take place, it is enabled again.
The progress of the cleanup process is displayed in the wizard.
Click Finish to close the wizard.
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select Do Not Agree to exit.