# Full Site Failover

Full site failover involves engaging the whole DRaaS environment in the event the production is completely unavailable. 

Ideally, a Cloud Failover Plan is created in advance which pre-configures the failover scenario and networking settings, and allows engagement of DR for the whole environment from the production Veeam B\&R server (if available), the Hosted Network VSPC portal (see [VSPC Overview](https://kb.hostednetwork.com.au/support/services/cloud/backup-as-a-service/tenant-management-via-vspc/vspc-overview) in the BaaS section for information on VSPC), or manually via the vCloud Director portal (VMware only) if required.

{% hint style="warning" %}
Manual booting of VMs in DR environment via portal is only possible for VMware replicas via the vCloud Director portal.

For Hyper-V, failover can be initiated from the production Veeam B\&R server (if available) or the Hosted Network VSPC portal (if a failover plan is pre-created).

For manual booting of Hyper-V machines, assistance is required from Hosted Network support
{% endhint %}

## Creating Failover Plans

* Launch the Failover Plan wizard from the Veeam Backup and Replication Console via the Failover Plan button in the ribbon<br>

  <div align="left"><figure><img src="https://3953723498-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LYYiX2aEcPAPdzrvDc4%2Fuploads%2FTQcXyuYQpOKWVsObPoNX%2Fimage.png?alt=media&#x26;token=f4d104b5-9f10-4c69-a749-f4938b757899" alt="" width="563"><figcaption></figcaption></figure></div>
* Select Cloud Connect (vCloud) or (Hyper-V) depending on your production infrastructure and give the plan a name<br>

  <div align="left"><figure><img src="https://3953723498-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LYYiX2aEcPAPdzrvDc4%2Fuploads%2Ft6v1MTDHGAnJUhnvzwjn%2Fimage.png?alt=media&#x26;token=5714821b-47e0-46e2-ae00-1de435be2efa" alt="" width="518"><figcaption></figcaption></figure></div>
* Add the VMs you wish to include in the plan<br>

  <div align="left"><figure><img src="https://3953723498-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LYYiX2aEcPAPdzrvDc4%2Fuploads%2FvxKA6GYuhrjEhNM9HKdv%2Fimage.png?alt=media&#x26;token=406ae76d-c100-4e9f-80a8-c184f26c5b85" alt="" width="563"><figcaption></figcaption></figure></div>
* Click Next and Finish

## Performing Full Site Failover

Once a failover plan has been created, initiating full site failover can be completed via the following methods depending on the situation:

### Veeam B\&R server

If the on-prem Veeam server is still available and connected to the internet, this is the easiest method for starting a failover plan. This method is frequently used for DR testing, however often during a real DR event, the Veeam server is not a viable option.

* From the Veeam B\&R console, select **Replicas > Failover Plans** from the navigation tree<br>

  <div align="left"><figure><img src="https://3953723498-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LYYiX2aEcPAPdzrvDc4%2Fuploads%2FxCWcXzLqNOXrXEg29ZKS%2Fimage.png?alt=media&#x26;token=8fc0b603-8a2e-44e8-8f7f-5cef817158c7" alt="" width="166"><figcaption></figcaption></figure></div>
* Right click the failover plan you wish to use and select **Start** ('Start to' can also be used to use a previous restore point if required)<br>

  <div align="left"><figure><img src="https://3953723498-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LYYiX2aEcPAPdzrvDc4%2Fuploads%2Ff2RSWCGdNGK0tvfN4nyN%2Fimage.png?alt=media&#x26;token=30f72af0-66a3-4c4f-90f4-40d11c6a99db" alt="" width="270"><figcaption></figcaption></figure></div>
* The VMs included in the failover plan will be started according to the settings used in the failover plan

### Hosted Network VSPC portal

In the event the on-prem Veeam server is not accessible or not able to communicate with the Hosted Network cloud, failover plans can be initiated from the VSPC portal

* Login to the VSPC Portal (<https://vac.mhn.net.au:1280>) using your reseller account
* Select **Failover Plans** from the navigation menu<br>

  <div align="left"><figure><img src="https://3953723498-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LYYiX2aEcPAPdzrvDc4%2Fuploads%2F8vab4SzMUKiMEcppm4Sx%2Fimage.png?alt=media&#x26;token=ae48146c-0851-47b3-8f57-fcf60cc09650" alt="" width="563"><figcaption></figcaption></figure></div>
* Right click the failover plan and select **Start**<br>

  <div align="left"><figure><img src="https://3953723498-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LYYiX2aEcPAPdzrvDc4%2Fuploads%2FfKHIVM7gtETfo0XeP74Y%2Fimage.png?alt=media&#x26;token=e64b0618-4615-493f-9556-3923e8a77552" alt="" width="369"><figcaption></figcaption></figure></div>
* The VMs included in the failover plan will be started according to the settings used in the failover plan

### Manually booting replicas (VMware only)

In the event the on-prem Veeam server is not accessible and it's not possible to start a failover plan from the VSPC portal (or a failover plan was not created in advance), for VMware based replicas it is possible to login to the VMware vCloud Director portal and manually start the replica VMs.

Please see the next section on [Accessing replica VMs](https://kb.hostednetwork.com.au/support/services/cloud/disaster-recovery-as-a-service/failover/accessing-replica-vms)