In my previous post, I explained how to automatically add all the different managed server to a Veeam Cloud Connect installation. The servers are now all listed in the Console, but still no role has been assigned to them. That’s what we will do together in this post.
Everytime I receive a new version of Veeam Backup & Replication, with inside also a new Veeam Cloud Connect, I try to install it as soon as possible in my personal lab to test it. My lab is a bit complex, because it uses a dozen virtual machines, spread over multiple VLAN connected via a firewall that only allows the minimum amount of TCP/UDP ports; this is done on purpose to simulate as much as possible a real Veeam Cloud Connect installation, so that everything I test is good also for our Service Providers which I work with. This is a good thing, but it also means that each time there’s a new version of the software, especially Beta versions which don’t allow in-place upgrades, I need to uninstall and re-install everything.
This is an insanely boring and error-proned task, and because of this I recently automated almost the entire process. In this first post, I’ll show you how to add all the managed servers to the Console and install the base components.
In my previous post I explained step by step how a service provider can configure Veeam Cloud Connect Replication to allow for more than 9 internal networks. In this second part of the post, we’ll see how a tenant can replicate his virtual machines in this specific scenario, and how they can configure pfSense to allow the multiple communications between the replicated VMs and Internet.
Veeam Cloud Connect Replication does not only manage virtual machine replication, but also offers a complete networking solution to easily publish failed over virtual machines in case of a disaster. This has always proved to be a tremendous feature of the solution. There are however some specific use cases where the Network Extension Appliance (NEA) may be better replaced with a different solution. One of the use cases is when a tenant needs to have more than 9 virtual networks to publish his virtual machines.
Veeam Cloud Connect reference architecture, the book that I wrote two years ago, is now available as an online book that you can read or download as pdf, mobi or epub.
I recently received this request from one of our service providers: “Is there a way to trace the failover actions in Veeam Cloud Connect, so that I can figure out the consumption of the virtual environment?”. As I never tried before to figure out this one myself, I thought it was time to hit the […]
In the previous post of this series, we registered a remote Veeam Backup & Replication and started to monitor it. VAC can do a lot of things, but when monitoring and the operations that can be done via VAC are not enough, it’s time to learn what other options are available. Remote Access Console: the […]
If you are trying to connect to a remote tenant using Veeam Remote Access Console, and you face the error “”This tenant does not allow managing any of their backup servers remotely”, there are a couple of firewall ports you need to open. Learn here which ones.