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 recovers VMs and vApps to a secondary site in the event of disaster at your primary site. To fail over your critical VMs and vApps, use the Disaster Recovery wizard.
The Disaster Recovery wizard does not control any storage array functionality. Disable duplication (mirroring) of the metadata storage and the storage used by the VMs to be restarted before you attempt failover to your recovery site.
To fail over 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 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. Use the Power state after recovery option to specify whether you want the wizard to start the recovered VMs and vApps immediately. Alternatively, you can wait and start the VMs and vApps manually after failover is complete.
Click Next to progress to the next wizard page and begin failover prechecks.
The wizard performs pre-checks before starting failover. For example, the wizard ensures all the storage required by the selected VMs and vApps is available. If any storage is missing at this point, you can click Attach SR on this page to find and attach the relevant SR.
Resolve any issues on the prechecks page, and then click Failover to begin the recovery process.
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. During this process, the following actions occur:
- Metadata for the VMs and vApps is exported from the replicated storage
- VMs and vApps are re-created in the primary pool
- SRs containing the virtual disks are attached to the re-created VMs
- VMs are started, if specified
When the failover is complete, click Next to see the summary report.
- Click Finish on the summary report page to close the wizard.
After your primary site is available again, you can return the VMs and vApps to that site. To complete this process, follow the Disaster Recovery wizard again, but instead select the Failback option. For more information, see Failback.
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.