A couple of weeks ago I presented to a customer Veeam's integration with AWS services, specifically the Direct Restore to EC2 feature. He was really interested, but he also immediately thought about possible large scenarios of this feature. This solution is not a Disaster Recovery technology, since a machine is not replicated into EC2, ready to be powered on, but it's rather a backup that is uploaded and then imported into EC2. But still, massive migrations or the creation of dev/test environments from a production copy were really nice use cases.
Automated Veeam Cloud Connect deployment 5: Replication services for vCloud Director
In chapter 3 of this blog series, I showed you how to connect a vCloud Director to Veeam Backup & Replication. Before Veeam Backup & Replication 9.5 Update 4, the main usage of vCloud Director was to make backups of vCloud VMs. But now with Update 4, we can use vCloud Director as a target for Cloud Connect replicas.
Automated Veeam Cloud Connect deployment 4: Create new tenants
In the first three posts of this series I've showed you how to automate the building of a Veeam Cloud Connect environment. Now that the environment is ready, today we'll automate also the onboarding of new customers.
Automated Veeam Cloud Connect deployment: 3 – connect to VMware virtual environment
In the previous posts we completed the automatic configuration of the Veeam Cloud Connect environment. In this third post of this short series, we will add additional resources in order to offer replication services. In fact, all the Cloud Connect components are now successfully deployed, so Backup services can already be offered, but to offer also replication services we need to connect our environment to the virtualized platform. Historically, Veeam Cloud Connect supported VMware vSphere and Microsoft Hyper-V, but since the soon-to-come 9.5 Update 4 will also add support for VMware vCloud Director, we will see how to add both to the infrastructure.
Replication in Veeam Cloud Connect with more than 9 networks
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.
Configure Veeam Cloud Connect Replication with more than ten networks
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.
Tracing Veeam Cloud Connect replica failover in Windows Event Viewer
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 […]
Is Veeam replication compatible with VMware NSX?
Recently I’ve been asked by a colleague if Veeam Backup & Replication supports VMware NSX. The answer to me was pretty clear, since Veeam works at the vSphere layer and what is sees are “just” portgroups, regardless if they are simple, distributed, or NSX virtual wires. Nonetheless, I decided to do a quick test to prove it.