Tenant Self Service Site Workflows from Cloud to Cloud using vCloud Availability

In this exercise, we will learn the following workflows  -

  • Configure Tenant driven Failover Workflows from Cloud to Cloud using VMware Cloud Director Availability. 

Open new browser to Login as Tenant

Fleet Deployed and Tunnel is Up
  1. Click on 3 dots at the top right corner to open Chrome in Incognito mode. We will login as Tenant in Incognito mode so the other Chrome browser tabs can remain open logged in as Administrator.
  2. Click on New incognito window

 

Open Tenant Site A

Fleet Deployed and Tunnel is Up
  1. In the bookmarks bar, open the folder named Region A
  2. Click on VCD SiteA - Tenant1

 

Login as Tenant at Site A

Fleet Deployed and Tunnel is Up
  1. Enter Username t1admin
  2. Enter Password VMware1!
  3. Click on SIGN IN

 

Open Tenant Site B

Fleet Deployed and Tunnel is Up
  1. Click on Region B
  2. Click on VCD SiteB - Tenant1

 

Login as Tenant at Site B

Fleet Deployed and Tunnel is Up
  1. Enter Username t1admin
  2. Enter Password VMware1!
  3. Click on SIGN IN

 

Open Availability menu at SiteB Tenant

Fleet Deployed and Tunnel is Up
  1. Expand More
  2. Click on Availability (SiteB)

 

Configure New Replication as Tenant from Cloud SiteB to Cloud SiteA

Fleet Deployed and Tunnel is Up

We will now configure replication from Cloud Provider SiteB to Cloud Provider SiteA as Tenant

  1. From left panel, Click on Outgoing Replications to Cloud
  2. Click on icon for New Protection

 

Provide credentials to manage replication at SiteA

Fleet Deployed and Tunnel is Up
  1. Enter Username t1admin@tenant1
  2. Enter Pass VMware1!

 

New Outgoing Replication - Cloud vApps and VMs

Fleet Deployed and Tunnel is Up
  1. Check the checkbox for VM  tenant1-photon-01b
  2. Click on NEXT

 

New Outgoing Replication -  Destination VDC and Storage policy

Fleet Deployed and Tunnel is Up
  1. Review the defaults and Click on NEXT

New Outgoing Replication - Configure Settings

Fleet Deployed and Tunnel is Up

Here's brief overview of the parameters -

SLA Profile - The premise of a SLA Profile is to provide a grouping of target settings when protecting a workload. This minimizes the amount of time spent configuring for protection. Think of this as a logical grouping construct which is a single selection to protect a workload. One does not need to think about what settings to configure. A SLA Profile consists of the following:

  • Target Recovery Point Objective (target being the key word here)
  • Retention Policy for Point in Time Instances
  • Ability to Quiesce or Compress Replication Traffic
  • Time select of the synchronization.

Just select SLA profile, and done. You can either use default or custom created SLA profile. SLA profiles are optional and only pertain to protections. They are not utilized for migrations at this time.

Target recovery point objective (RPO) -The RPO is the longest tolerable timeframe of data loss. For example, with one hour RPO the recovered virtual machine can have no more than one hour of data lost. Shorter RPO intervals, ensure less data loss during recovery, at the expense of consuming more network bandwidth to keep the replica up to date.

Retention Policy- Maximum number of retained snapshots per single virtual machine replication within an organization.

Delay start synchronization

  • To schedule the start of the replication, select this option and enter the local date and time to start the replication.
  • To start the replication when the wizard finishes, leave this option deselected.

Exclude disks - To exclude some hard disks of the virtual machines from replicating to the destination site, select this option.

Configure Seed VMs -For each new replication that you configure, an initial full synchronization operation is performed. During this operation, vCloud Availability copies the whole data from the source vApp or VM to a datastore in the target site. Due to the size of the vApp or VM or to the network bandwidth, an initial full synchronization might take a long time.

To reduce the initial synchronization time, you copy the source vApp or VM to the target site by using removable media, failover of a previous replication, or other means of data transfer. Then, in the target site, configure a replication that uses the vApp or VM copy as a replication seed.

When a replication uses a seed vApp or VM, vCloud Availability does not copy the whole source vApp or VM data to the target site. Instead, vCloud Availability copies only the different data blocks between the source vApp or VM and the seed and reuses the seed data in the target site as a basis for replication.

We do not have Seed VM available at the target site for this exercise

  1. Leave everything as Default and Click Next

 

Ready to Complete the Replication

Fleet Deployed and Tunnel is Up
  1. Review the replication details and click on FINISH

 

Replication in Progress

Fleet Deployed and Tunnel is Up

Review the replication details, it is in progress

Replication is Completed

Fleet Deployed and Tunnel is Up

Verify the Replication status, it may take few minutes to complete. Review the details and Confirm:

  1. Replication state is Healthy
  2. Replication type is Protection
  3. Overall health is Green

 Note: In case you see Unexpected vCloud Director error during replication, please retry. Due to the nested environment in Hands On Lab, sometimes the error is seen, in real world it should work seamlessly.  

Verify Replication Status at SiteA Tenant

Fleet Deployed and Tunnel is Up
  1. Switch to tab Cloud Site A
  2. Expand More
  3. Click on Availability (SiteA)

 

Verify Incoming Cloud vApp/VM Replication Status at SiteA Tenant

Fleet Deployed and Tunnel is Up
  1. You can notice Incoming VM replication status as Green
  2. From left panel, click on Incoming Replication from Cloud

 

Confirm Incoming Cloud vApp/VM Replication Status at SiteA Tenant

Fleet Deployed and Tunnel is Up

Confirm the Replication State is Healthy and Overall health is Green

 

Switch to Cloud SiteB Tenant to configure network for Replicated VM

Fleet Deployed and Tunnel is Up
  1. Switch back to SiteB Tenant
  2. In the upper right-hand corner, click on  vAPP

Configure Networks for Replicated VM

Fleet Deployed and Tunnel is Up

Before we can run Recovery of the replicated VM in Cloud, we need to configure a Test/Failover Network. This Network would be connected to the Recovered VM.

For the cloud to cloud replications, VMware Cloud Director Availability replicates all the types of source vApp networks in the target cloud site: Isolated, bridged (direct) and fenced (NAT-routed) networks. VMware Cloud Director Availability replicates the source networks settings like: IP pools, NAT routes, firewall rules, and DNS settings, in the target site.

  1. Check the checkbox for VM tenant1-photon-01b
  2. Expand ALL ACTIONS
  3. Click on Network Settings

 

Configure Network Settings for Replicated VM

Fleet Deployed and Tunnel is Up

In this screen, we can configure the target networks to be used for migration/failover as well as test failovers. For this lab, we will just configure the Migrate/Failover network.

  1. In the dropdown for connect to target org VDC network, select Tenant1-OVDC-A-OrgNet-Rtd
  2. Set IP Mode to Static - IP Pool
  3. Click on APPLY

 

Run Failover to Cloud SiteA

Fleet Deployed and Tunnel is Up

Now that the VM is successfully replicated in Cloud, we will run Failover workflow such that VM will now run in Cloud SiteA

  1. Check the checkbox for VM tenant1-photon-01b
  2. Expand ALL ACTIONS
  3. Click on FAILOVER

Failover in Cloud - Recovery Settings

Fleet Deployed and Tunnel is Up

Brief overview of the parameters on this page

Consolidate VM disks - Enable for a better performance of the recovered virtual machines at the expense of the failover task taking longer to complete.

Power on recovered vApps - Select to power on the virtual machines on the destination site after the task completes.

Network settings
-
Apply preconfigured network settings on failover will assign the network configured during the virtual machine replication.
-Connect all VMs to network will allow you select a target network on the fly during a failover

  1. Because we already configured a target network, leave the default setting and click NEXT

 

Failover - Recovery Instance

Fleet Deployed and Tunnel is Up
  1. Select the latest available Instance and click on NEXT

 

Ready to Complete the Failover Settings

Fleet Deployed and Tunnel is Up
  1. Review the Failover Settings and Click on FINISH

 

Failover to Cloud SiteA is in Progress

Fleet Deployed and Tunnel is Up
  1. In the Detailed Status, you will notice Failover in Progress.
  2. Recovery State is updated to Fail-Over

 

Failover completed successfully

Fleet Deployed and Tunnel is Up

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

  1. Replication State is Healthy
  2. Recovery State shows Failed-Over.
  3. Overall health is Green

Note: In case you see Unexpected vCloud Director error during failover, please retry. Due to the nested environment in Hands On Lab, sometimes the error is seen, in real world it should work seamlessly.  

Verify Failover is successful at Cloud Provider SiteA

Fleet Deployed and Tunnel is Up

Lets confirm that Failover is completed successfully from Cloud Provider SiteA

  1. Switch to SiteA Tenant  
  2. Click on Incoming Replications from Cloud
  3. Replication State is Healthy
  4. Recovery State shows Failed-Over.
  5. Overall health is Green

Note: In case you see Unexpected vCloud Director error during failover, please retry. Due to the nested environment in Hands On Lab, sometimes the error is seen, in real world it should work seamlessly.  

Verify Failed-Over VM is now running in SiteA

Fleet Deployed and Tunnel is Up
  1. Switch back to Chrome browser vCenter SiteA
  2. On the left panel expand RegionB01
  3. Expand RegionB01-COMP01
  4. Expand vCD-RegionB01
  5. Expand Tenant1-OVDC-B
  6. Verify VM tenant1-photon-01b-xxxx is now powered on in SiteA inventory

Congratulations!! You completed the Tenant driven Pairing and Recovery Workflows between the Cloud Provider Sites.