As discussed in my introduction post about vCloud Availability for Cloud-to-Cloud DR (vCAv-C2C), I am going to do a high-level write-up of my installation/deployment process for this new vCD site-to-site replication and migration solution.
While this write-up does cover the deployment methodology, a production state will need to be rationalized inclusive of certificates, ports, and firewall rules that will be required.
Below are the high-level steps I took for deployment. VMware’s documentation does go in a different order, but this is the way I rationalized it along with a combined role (all-in-one appliance).
High-Level Steps for Installation and Setup:
- Download OVF and deploy at each respective site
- Configure vCAv-C2C Replication Manager
- Configure vCAv-C2C Replicator
- Pair Replication Manager with Replicator
- Configure vCAv-C2C Replication Service/Manager
- Configure vCAv-C2C Availability Portal
Again, my high-level architecture –
- Let’s grab the OVF (remember, we only need one for vCAv-C2C), and deploy it to my management cluster –
- We can see it’s the new Cloud to Cloud appliance –
- As we discussed before, the team has done a great job of simplifying the deployment of vCAv-C2C to a simple and single OVF for all of the roles required for Cloud to Cloud. We can see the drop-down for each respective role. For my deployment, we will be selecting a combined since this is a lab environment.
- We now have to put in the required network configuration while enabling SSH (this is not a mandated requirement, but nice to have in my lab environment). One thing to note – the root password is temporary. When we get into the initial portal configuration, it will prompt us to change it to a new password from a security perspective.
- Final screen to complete the deployment –
- Alright, initial appliance deployment is done! Now off to the configuration.
Configure vCAv-C2C Replication Manager
- For the initial configuration, we will want to open a browser to “https://Appliance-IP-address:8044” or in my case, https://vcav-repmgr-01a.corp.local:8044 –
- Let’s click on the Configuration Portal link and now set the new password after a successful login with the password we set in the OVF deployment –
- We can see we have a red x where the lookup service is missing. This is for us to point to the resource vCenter (remember, resource and management vCenters must be in the same SSO domain at each site).
- Let’s go to Configuration -> Set lookup service and put in the lookup service FQDN and we should see a successful message.
- Back to the diagnostics tab, we can now see the lookup service is green!
- Now, the next step is correctly set up the replication instance and then come back to the Replication Manager for pairing.
Configure vCAv-C2C Replicator
- Open a browser to “https://Appliance-IP-address:8043” or in my case, https://vcav-repmgr-01a.corp.local:8043 –
- Change password –
- Set lookup service – again, I am using a consolidated vCenter instance for resource and management so this is pretty straightforward –
- Now, back to the Replication Manager for pairing.
Pair Replication Manager with Replicator
- On the Replication Manager, let’s go to Replicators -> New replicator while giving the full FQDN along with the password (remember, new password!) and SSO credentials –
- Accept the cert and we should see the success message shortly.
- Now, let’s click on Show all managers and we can see the replication instance is now registered –
- While from the replication instance, we can see the replication manager also configured –
- Excellent! Now, off to the Replication Service Manager
Configure vCAv-C2C Replication Service/Manager
- Open a browser to “https://Appliance-IP-address:8046” or in my case, https://vcav-repmgr-01a.corp.local:8046 – this time, I used the new password as it seems to have propagated to the other roles.
- Now, we get a nice clean wizard for the setup.
- Let’s put in the Site information, this is going to be my SiteA.
- Next, lookup service again with accepting the certificate –
- Now, we are going to point it to the Replication Manager we previously setup. This is on port 8044, so let’s put that full FQDN along with port 8044 –
- Now, we get to setup vCloud Director. I used the manual configuration here to verify everything was good to go.
- Finally, we get a summary screen to show the stated configuration –
- Excellent! All green and expanding out the Manager data shows our registered replication instance too. Very slick interface.
- Now, off to the Availability Portal configuration as the last setup step.
Configure vCAv-C2C Availability Portal
- Home stretch for the first site installation and configuration – let’s open a browser to “https://Appliance-IP-address:5480” or in my case, https://vcav-repmgr-01a.corp.local:5480
- I am prompted for vApp Replication Manager / vCD Connection information. By default, I did see a “127.0.0.1:8046” but decided to change it to the FQDN of my combined instance. Put in the vCD credentials (administrator@system) and hit connect to get a successful message –
- Now, click Test to verify everything is operational from a vCD perspective –
- We will be using the defaults for the database, but you are prompted to select a custom database if you so desire –
- Alright, final step. Here’s where we can change the port for user access (remember, this is what will be publicly facing) along with the certificate. I am staying with the defaults for my installation.
- Now, we are ready to hit the Start Service button. Running…
- Now, we get a nice, simple portal that’s used to verify all of our services are operational
Wow, a very streamlined process that was very intuitive while using a sleek and simple interface.
I am going to check to verify my org user can log into the portal…
Before I can have the paired sites and start testing workload migration, I need to go set up my SiteB vCloud Director instance and deploy the combined appliance. On the next blog post, we will go through the Site pairing process and do a migration/replication.