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)

Step 1: Log on to the HI GIO portal.

Step 2: Expand More > Click on Availability ()

Step 3: Click on Incoming Replications > Check the checkbox for VM APP1 > Expand ALL ACTIONS > Click on Failover

Step 4: Configure Recovery Settings for Failover

- Instances handing after recovery: Default.

- Power Settings: Power on recovered vApps.

- Network Settings: Apply preconfigured network settings on migrating.

Click NEXT

Step 5: Configure Recovery Instance for Failover

Click SELECT LATEST FOR EVERY VM > NEXT

Step 6: Review and FINISH

Step 7: Expectation result:

Failover in Progress: In the Detailed Status, you will notice Failover in Progress with % progress.

Failover successfully: This process will take a couple of minutes. Please be patient.

After the failover task finishes, the failed over workload runs in the HI GIO cloud.

Confirm that all VMs in vAPP1:

- Recovery State = Failed-Over.

- Replication Type = On-Premise Protection

- Overall health = Green

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

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 3: Change default gateway for APP1 & DB1 (on-prem network is problem)

Logon APP1 & DB1 by admin local > change default gateway and validate that APP1 & DB1 can be reachable.

Step 4: Point domain name to APP1 (public DNS record if needed).

Step 5: Access to APP1 via the internet (in my case, I used a public IP).

Last updated 6 months ago