1 of 11

FAILOVER SCENARIO

Partial Failover

Partial failover is necessary when your DC (on-premises site) is still up and running but only one (or a subset) of your servers, applications, or virtual machines (VMs) is experiencing problems.
In this scenario, a complete site failover is unnecessary. Partial failover allows you to run the corrupted systems at the DR site (HI GIO cloud) while the rest of your functional systems keep running on your DC site (on-premises site).

Full Failover

Disaster scenarios almost always strike unexpectedly. In a disaster event, it is critical to restore the infrastructure of your business as soon as possible before any significant damage is done.
Failover and failback can help ensure that your business continues functioning properly, even if the DC site is affected by a disaster.

ENVIRONMENT

Architecture Diagram

DC site has an issue - full failover

FAILOVER

Guideline

Step 1: Create a protection job (from on-premises site)

Procedure

Step 1: Log in to vCenter, Expand Menu > Click on Cloud Provider DR and Migration

Step 2: Click on Outgoing Replications > New Protection

Step 3: Enter credential of Organization > LOGIN

Step 4: On Source VMs windows:

- Enable Group VMs to a single vApp.

- Select APP1 & DB1.

- Click NEXT

Step 5: On vApp Settings

- Enter vApp name: vAPP1

- Set: start wait time

- Click NEXT

Step 6: Select destination VDC & storage policy > NEXT

Step 7: Select SLA profile > NEXT

Step 8: Review > FINISH

Step 9: Expectation result

Confirm the Replication is started. You can monitor the % progress here

Replication state completed. Confirm that:

- Replication state = healthy,

Step 2: Configure the Network Settings for On-Premises to Cloud Replications

Overview

Before running the replicated VM's Recovery, we must configure a Failover Network on APP1.

Procedure

Step 1: Log in to HI GIO Availability.

Step 2: Select Incoming Replications > select vAPP1 > ALL ACTIONS > Recovery settings.

Step 3: In the Recovery settings window > click the Nics tab > vAPP1

Step 4: Assign a network that fits with HI GIO's network > APPLY

Step 3P - Partial failover VMs (VM - APP1) from on-premise site to HI GIO site

Overview

Use this step when your primary infrastructure (on-premise) is running well. After this step:

- Workload is on the HI GIO cloud site.

- Source workload is powered off.

Step 3F - Full failover vAPP1 (VM - APP1 & VM - DB1) from on-premise site to HI GIO

Overview

If the protected site (on-premises) is unavailable. In the HI GIO cloud, you can perform a workload disaster recovery operation (full failover)

Procedure

Step 1: Log on to the HI GIO portal.

Step 2: Expand More > Click on Availability ()

Step 3:

Validate - vAPP1 (VM APP1 & DB1)

In this scenario, on-premise has issues: network, hardware host, and storage… that make it not available.

Procedure

Step 1: Log on to the HI GIO portal: select vAPP1 > Virtual machines.

Step 2: Confirm that 02 VMs, APP1 & DB1, were migrated to HI GIO and are running.

Step 4: Reverse replication of the VM from HI GIO Cloud to On-Premises

Overview

After the on-premises site has recovered from the issue and is available, we can migrate the workload (APP1, DB1) from the HI GIO cloud back to on-premises by reversing the replication.

Step 5: Migrate the VMs back from HI GIO Cloud to On-Premises

Overview

Since the VM is successfully replicated from Cloud to On-Prem, we will migrate the VM APP1, DB1 from HI GIO Cloud back to On-Prem.

Procedure

Step 1: Log on to the HI GIO portal.

Step 2: Expand More > Click on Availability ()

Step 3:

Step 6: Reprotect the VMs from On-Premises to HI GIO Cloud

Overview

After migrating over the workload to On-Premises, we can reverse the replication and reprotect it back to the HI GIO Cloud site.

Once reprotect is successful, this will show as outgoing replication from On-Premises to the Cloud.

FAQs

You can find the protected jobs on the jobs on-premises site.

After creating the protection job\reverse job on HI GIO cloud (by provider account), you cannot see these jobs on-premises site.

Solution: Change the owner of these jobs to a tenant organization

Virtual Machine disk consolidation is needed.

Migrating back VMs from HI GIO cloud to on-premises made VMs warn - virtual machine disk consolidation is needed.

Solution: consolidate for VMs

The issue with the Windows server - lost trust relationship after migrating VM to HI GIO cloud or migrating back to on-premises.

Solution: Follow this guide to resolve it
Tip. You can configure the maximum computer password age using the Domain member: Maximum machine account password age policy under Computer Configuration-> Windows Settings-> Security Settings-> Local Policies-> Security Options. A computer password lifetime may last from 0 to 999 days (30 days by default);