VMware vCloud Availability for Cloud-to-Cloud DR – Pairing and Usability (1 of 2)

As a continuation of my vCloud Availability for Cloud-to-Cloud DR (vCAv-C2C) series, we will be covering the initial pairing and usage of C2C in this blog post.

Blog Post – what is vCloud Availability for Cloud-to-Cloud DR? 

Blog Post – vCloud Availability for Cloud-to-Cloud DR – Installation and Setup

I will break this post into the following sections and into two blog posts:

  1. Part 1:
    1. The pairing of the two vCD/vCAv sites
    2. Logging into the vCAv Portal and Portal Overview
    3. Provider view of the vCAv Portal
  2. Part 2:
    1. Initial authentication between the two sites
    2. Migrating a workload in the same site
    3. Protecting a workload between two sites
    4. Testing the protected workload
    5. Edit Options
    6. Failing Over

The pairing of the two vCD/vCAv Sites

  1. First, the Provider must set up an association between the two vCAv sites before the tenant can authenticate within the vCAv portal.
  2. This is done in the Replication Manager portal – point your browser to https://<vcav-rep-mgr>:8046, authenticate, and click on Sites -> New site
  3. We then assign a Site name, the full URL of the respective peer replication manager, and the appliance password. Within my setup, I did this on both sites, SiteA and SiteB. 
  4. Once we hit OK, you will receive a Task succeeded message – 
  5. Now, if we click on the Sites subsection, we can now see our local site along with our newly peered site. From SiteA and SiteB, I can see each respective site. 
  6. Complete! Now we are ready to log into the vCAv Portal.

Logging into the vCAv Portal and Portal Overview

  1. Point your browser to the fully qualified domain name along with port 8443 – this is the default port the portal runs (can be changed). 
  2. Logging in is very similar to vCAv-DR2C – you utilize the username@org-name parameter. For my SiteA, I have an “Org1” while my SiteB is “Org2” – for SiteA, I am logging in as org1admin@org1 with the appropriate password.
  3. Once authenticated, I get the very clean interface that shows the Cloud Topology. We haven’t started any replications/migrations yet, so I don’t have any ingress/egress traffic yet.  
  4. On the home page, you get a very clear view of the topology, workload statistics, and even the Organization VDC status. I thought this was a very efficient use of current oVDC utilization along with what’s being used within each oVDC. 
  5. Under the DR Workloads tab, we would be able to see incoming and outgoing protected workloads. Since we haven’t set up any yet, nothing to show yet. 
  6. Paired Clouds shows available vCD/vCAv instances and their authentication status. Since the Provider paired with SiteB, we have it available but it shows unauthenticated. We still need to authenticate with the appropriate credentials that reside on SiteB. 
  7. Last of all, Tasks will show any previous or current tasks and the event log. This will show logs for any connected site, so very easy to see exactly is going on between the paired sites. 
  8. For those of you that have used vCAv-DR2C, this is very similar to that experience with a few minor enhancements. The learning curve is very minimal and we will go through a few test scenarios.

Provider view of the vCAv Portal

  1. The development team did a great job from a provider view on providing very useful information.
  2. First of all, we get to see a current status ticker that shows state of the vCAv environment. I thought this was extremely useful and intuitive to gain an operational understanding of the health of the current environment. 
  3. I didn’t mention this in the previous portal post, but this is also available there too. You can expand and see the details of the current replications/migrations between sites. This is done by clicking the carrot icon in the top right corner. 
  4. If you scroll down also, you get to see the pVDC view of the current environment with a resource utilization rollup. Very similar experience to what we see now in vCD 9.1 Multi-Site. 
  5. Under the Orgs tab, we get to see the current organization and any registered vApps and current status. 
  6. One very nice item is that shield/checkmark icon. If we click that, we can actually impersonate the organization admin and assist with any tasks that the organization may be having trouble with. All done through this single interface! 
  7. I won’t cover DR Workloads as it’s the same as the tenant view, but just a macro-rollup of all protected workloads. However, under Administration, we get to see Configuration and Registration. From here, we can actually register other components to monitor from this dashboard along with resource threshold display. Very nice! 

Onto the next post, where we will review migrations and protection operations. Thanks!


5 thoughts on “VMware vCloud Availability for Cloud-to-Cloud DR – Pairing and Usability (1 of 2)”

  1. Great post !
    Is it possible to replicate from an org vDC to another ? I have always an error : Unable to find suitable replicator from site ‘vcdlab’.

    1. Hi Jul, thanks for reaching out. Yes, you can do intra-.org VDC migrations in the same vCD instance. Does your destination org VDC reside in a separate pVDC/vCenter? You need to have a replication instance registered for any resource vCenter instance.

  2. Hi i have similare issue in vcav3 cloud to cloud , both site have identical configuration but still have this error Unable to find suitable replicator from site “A”

    1. This is typically related to the URL endpoint. Are you using 8048 and the replicator is attached to the cloud replication manager? Please do open an SR for further assistance.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.