Site Pairing and Failover Workflows from Cloud to Cloud using vCloud Availability

In this exercise, we will learn to -

  • Configure Site Pairing from Cloud to Cloud and
  • Configure Failover Workflows from Cloud to Cloud using VMware Cloud Director Availability

Note that in the lab environment, we have already deployed and configured the VMware Cloud Availability appliances for each site, but we have not configured any site pairing yet. 

Login to RegionA vCenter (On-Premise)

Login to vCenter
  1. Start the Chrome Browser from the desktop. Click on RegionA in the bookmarks bar.
  2. Click on vcsa-01a Web Client. Verify the address as : https://vcsa-01a.corp.local/
  3. Enter Username: administrator@regiona.local
  4. Enter Password: VMware1!
  5. Click on LOGIN

Open RegionB vCenter

Login to vCenter
  1. Open a new tab on the browser.
  2. Click on RegionB
  3. Click on vcsa-01b Web Client. Verify the address as : https://vcsa-01b.corp.local/

Login to RegionB vCenter

Login to vCenter
  1. Enter Username: administrator@corp.local
  2. Enter Password: VMware1!
  3. Click on LOGIN

Open SiteA VMware Cloud Director Provider

Login to vCenter
  1. Open a new tab on the browser.
  2. Click on RegionA
  3. Click on VCD SiteA - Provider . Verify the address as : https://vcd-01a.corp.local/

Login to SiteA VMware Cloud Director Provider

Login to vCenter
  1. Username: administrator
  2. Password: VMware1!
  3. Click on SIGN IN

Open SiteB VMware Cloud Director Provider

  1. Open a new tab on the browser.
  2. Click on RegionB
  3. Click on VCD SiteB - Provider. Verify the address as : https://vcd-01b.corp.local/

Login to SiteB VMware Cloud Director Provider

  1. Username: administrator
  2. Password: VMware1!
  3. Click on SIGN IN

Open Tenant1-OVDC-B

First, we need to expand the resources in Tenant1-OVDC-B.

  1. Click Organization VDCs in the left-hand navigation bar
  2. Click the Tenant1-OVDC-B name in the main window

Note: if you already added resources in the previous module, you can skip ahead to Open Availability menu at SiteA Provider

Edit Allocation

  1. Click on Allocation
  2. Click Edit

Edit Allocation (cont'd.)

  1. Change CPU Allocation to 3 GHz
  2. Click Save

Open Availability menu at SiteA Provider

  1. Switch to tab Site A Provider
  2. Expand More and Click on Availability (Site A)

Review Topology and System Health at vCD SiteA

Login to vCloud Availability
  1. Topology: There are no sites paired and no Replications
  2. System health: Confirm there are green check marks and everything is healthy and green
  3. From the left panel, click Policies

Add a new Replication Policy

Replication policies are sets of rules that define and control the replication attributes on a VMware Cloud Director organization level. To control the replication settings allowed for replications on a VMware Cloud Director organization level, the service providers can create replication policies.

When configuring a protection or a migration, the New Replication wizard validates the replication attributes of the policy that is assigned to the organization. Lets add a new policy at SiteA Provider that will be validated while configuring replication.

  1. Click on + NEW to add a new Policy

Add a new Policy

Login to vCloud Availability

Just brief overview for each parameter in this wizard-

-Enter a unique, case-sensitive name for the replication policy.

-Select whether to allow custom SLA settings per replication or only to allow SLA profiles to set the SLA settings.

-Select whether to allow incoming and outgoing replications.

-If incoming replications are enabled, enter the maximum number of virtual machines replications.

-If incoming replications are enabled, enter the maximum number of point-in-time instances per replication.

-If incoming replications are enabled, enter the maximum number of stored instances per replication.

-Select whether to allow bandwidth throttling and if enabled enter the maximum throughput per VMware Cloud Director Availability On-Premises Appliance.

-If incoming replications are enabled, set the minimum allowed RPO by using the Recovery Point Objective (RPO)slider or by clicking the time ranges.

  1. Enter Policy name: T1-PolicyA
  2. Leave everything as default
  3. Click on CREATE

Confirm the Policy is created

  1. Confirm policy T1-PolicyA is created successfully

Assign the Policy

  1. Click on T1-PolicyA
  2. Click on ASSIGN

Assign the Policy (contd..)

  1. Check the checkbox Tenant1
  2. Click on ASSIGN

Confirm the Policy is assigned to Org

  1. Confirm T1-PolicyA is now assigned to 1 Org

Switch to SiteB Cloud Provider tab

  1. Switch to tab SiteB Provider
  2. Expand More
  3. Click on Availability (SiteB)

Verify/Create Replication Policy for SiteB

If you went through Module 2 before this module, you should already have a replication policy created and assigned. You can go to the next page.

If you do NOT already have a replication policy created and assigned, please use the steps you just completed for SiteA to create and assign a replication policy for SiteB.

Copy Public API Endpoint from SiteA Cloud Provider

Before we pair the 2 sites, we need the Public API Endpoint from SiteA

  1. Switch to SiteA Cloud Provider tab
  2. From left hand panel, click on Sites
  3. Copy Public API Endpoint: https://vcda-01a.corp.local:8048/

Configure New Pairing between Cloud Provider Sites

  1. Switch back to SiteB Cloud Provider
  2. Click on Sites
  3. Click on NEW PAIRING

Enter New Pairing details

Register new Remote Site Connection
  1. Enter Site name : SiteA
  2. Service Endpoint - Paste the Public API Endpoint url we copied from Site A cloud provider: https://vcda-01a.corp.local:8048/
  3. Click on PAIR

Note: the Site Name is case sensitive and must match the site name at the site being paired.

 

Accept the Server Certificate

Choose Hybrid Services
  1. Click on ACCEPT  to accept the SSL certificate from the paired site and you should be able to successfully pair the sites

 

Additional Action is Required to Complete the Pairing Between 2 Cloud Provider Sites

Local Gateway Parameters

To complete the pairing between 2 cloud provider sites, additional action is required. Click on OK

Copy Public API Endpoint from SiteB Cloud Provider

Before we complete pairing the 2 cloud sites, we need the Public API Endpoint from SiteB as well

  1. Click on Configuration from left-hand navigation bar
  2. Copy the Service Endpoint address using the icon https://vcda-01b.corp.local:h8048/

Switch to SiteA Cloud Provider

  1. Switch to tab SiteA Cloud Provider.
  2. Click on Sites
  3. Click on NEW PAIRING

Enter New Pairing details

Register new Connection
  1. Enter Site name : SiteB
  2. Service Endpoint - Paste the Public API Endpoint url we copied from Site B cloud provider: https://vcda-01b.corp.local:8048/
  3. Click on PAIR

Note: the Site Name is case sensitive and must match the site name at the site being paired.

Accept the Server Certificate

Choose Hybrid Services
  1. Click on ACCEPT  to accept the SSL certificate from the paired site and you should be able to successfully pair the sites

 

Login to SiteB to complete the pairing

L2 Concentrator Configuration

Once the pairing is completed, a login button appears allowing us to authenticate as our vCloud Director provider admin user (administrator@system) to the 2nd site. After successful authentication the 2 cloud provider sites should be paired and ready to run failover workflows.

  1. Select SiteB
  2. Click on LOGIN

Enter Login Credentials for SiteB

Ready to complete
  1. Enter Username: administrator@system
  2. Enter Password: VMware1!
  3. Click LOGIN

Confirm on vCD SiteA that the Pairing is complete

Confirm that the pairing to SiteB is Green and Healthy

Verify the Pairing at vCD SiteB

Verify Site Pairing

Before we confirm the pairing between the sites, we need to login to SiteA

  1. Switch to tab SiteB Cloud Provider
  2. Select Sites in the left-hand navigation bar
  3. Select the Cloud site SiteA
  4. Click on LOGIN

Enter Login Credentials for SiteA

Verify Site Pairing
  1. Enter Username: administrator@system
  2. Enter Password: VMware1!
  3. Click on LOGIN

 

Confirm the Pairing from SiteB to SiteA is successful

Confirm that the pairing to SiteA is Green and Healthy

System Monitoring at SiteB Cloud Provider

  1.  Click on System Monitoring

View Local and Remote Replicators at Cloud SiteB

Scroll down to the bottom of the page to view Local and Remote Replicator details.

  1. Here, you should see that both the Local (to the site you are logged into) and Remote Replicators are shown and connected
  2. The odd Address shown for the Remote replicator (boxed in red above) is correct since this is an internal address used to reach the remote replicator appliance via the Tunnel.

 

System Monitoring at Cloud SiteA

Similar to Cloud SiteB, we will now review the local and remote replicators configured at Cloud SiteA

  1. Switch back to tab SiteA Cloud Provider
  2. Click on System Monitoring 

View Local and Remote Replicators at Cloud SiteA

Scroll down to the bottom to the bottom of the page to view Local and Remote Replicator Services details.

  1. Here, you should see that both the Local (to the site you are logged in to) and Remote Replicators are shown and connected
  2. The odd Address shown for the Remote replicator (boxed in red above) is correct  this is an internal address used to reach the remote replicator appliance via the Tunnel.