Before running the replicated VM's Recovery, we must configure a Failover Network on APP1.
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
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.
Step 1: Log on to the HI GIO portal.
Step 2: Expand More > Click on Availability ()
Step 3: Click on Outgoing Replications > Check the checkbox for vAPP1 > Expand ALL ACTIONS > Click on Migrate
Step 4: Configure Migrate Settings. Leave the Defaults and Click on NEXT
Step 5: Review the Migration Settings and click on FINISH
Migration in Progress
Migration to on-premises is Completed Successfully. Confirm that:
- Recovery state = Failed-Back
- Replication type = On-Premise Protection
Confirm VMs migrated back to On-premises.
VM APP1-xxxx, DB-xxxx now show up in the vCenter's inventory
Login to APP1 & DB1 by local account > change the IP address to fit with the on-premise site (in my case, I just changed the default gateway to .1) and validate the application.
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,
Confirm the Replication Status from HI GIO Cloud:
Log in to HI GIO Availability > Incoming Replications, select INSTANCES.
Confirm the vAPP1:
- Replication state = Healthy
- Overall Health = Green
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);
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.
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:
- Recovery State = Failed-Over.
- Replication Type = On-Premise Protection
- Overall health = Green
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).
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.
Step 1: Log on to the HI GIO portal.
Step 2: Expand More > Click on Availability ()
Step 3: Click on Outgoing Replications >Check the checkbox for vAPP1 > Expand ALL ACTIONS
Step 4: Click on Reverse
Step 5: Click on REVERSE
The reverse from On-Premises to HI GIO Cloud Is In Progress
Reverse from On-Premises to Cloud Completed Successfully. Outgoing Replications is empty now.
Since the replication is configured from On-Premises to Cloud, we will view Incoming Replications.
Select Incoming Replications. Here, you will notice VM APP1-xxxx is replicated back from On-Premises to Cloud, and the Replication type is On-Premise Protection.
Verify replication status from the On-Premises site
Expand Menu > Click on Cloud Provider DR and Migration.
Click on Outgoing Replications.
Confirm VM APP1-xxxx & DB1-xxxx is replicated back from On-Premises to Cloud and Replication type is Protection.
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 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 Migrate
Step 4: Configure Recovery Settings for Migrate
- Instances handing after recovery: Default.
- Power Settings: Power on recovered vApps.
- Network Settings: Apply preconfigured network settings on migrate (configured in step2)
- Click NEXT
Step 5: Review and click FINISH
Step 6: Expectation result:
Failover in Progress: You will notice Migrate in Progress with % progress in the Detailed Status.
Once the migration task is completed, confirm on
STATUS, VM:
Step 1: Log on to the HI GIO portal: select vAPP1 > Virtual machines.
Step 2: Confirm that VM APP1 was migrated to HI GIO and powered on.
Step 3:
- Recovery state = Failed-Over,
- Replication Type = On-Premise Protection,
- Overall health = Green.
DB1:
- Recovery state = Not stated,
- Replication Type = On-Premise Protection,
- Overall health = Green.
Migrate completed successfully. The workload is running in the HI GIO cloud, and the workload is no longer protected.
Step 4: Expectation result:
The VM APP1 is running on the HI GIO site now. The VM is no longer protected.
The VM APP1 is power off on-premises - automatic by vCDA.
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 1: Log on to the HI GIO portal.
Step 2: Expand More > Click on Availability ()
Step 3: Click Incoming Replications > Check the checkbox for vAPP1 > Expand ALL ACTIONS > Click on Reverse.
You can also select individual VMs in this step.
Step 4: Confirm Reverse Replication from HI GIO Cloud to on-prem. Click REVERSE.
Step 5: Expectation result:
Reverse Replication is in progress. You can monitor the progress of the Reverse task in the Last changed section and replicate the state.
Reverse Replication is Completed. Here, APP1 & DB1 are replicated back to On-Prem, and the Recovery State is Reversed.
