I started to install VMware vCloud Director in my new lab, as I want to be ready to test the upcoming Veeam Cloud Connect Replication v10, with its native support for this cloud management platform. One of the requirements of vCloud Director is NSX, so I started with its installation. As I hit some errors in the “NSX Host Preparation” step, I learned how to fix them manually and how to automate a bit VIB deployments.
In my job, I have to learn a lot about multiple topics of IT. Especially in the virtualization market, many people are usually well prepared when it comes to infrastructure, servers and storage, but I found out that the weakest point is many times networking. There are some topics that are obscure for many, like Layer2 vs Layer3, BGP, Spanning Tree, but there is one topic that is really important even for infrastructure guys, yet it’s almost unknown to them: Latency.
During Veeam replication jobs, your vCenter triggers the VM MAC conflict alarm. This happens because when a VM replica is created, it has the same MAC address and UUID as the original VM. This situation is totally expected because a newly created replica is an absolute copy of the original VM with exactly the same properties. This doesn’t create any issue, since the replicated virtual machine is not powered on, but more importantly because vCenter changes both replica’s MAC address and UUID. So, the issue is gone after a few moments, but the alarm remains in the console and it may be annoying. So, here’s how you can suppress the alarm.
Last week, during the VeeamON 2017 conference, one of the announcements has been a completely new product, called VeeamPN (Veeam Powered Network), a solution to easily create virtual private networks betweens multiple public clouds, remote locations and roaming users. Even if the main use case of the solution is to ease the access to Azure virtual machines, I’ve found another interesting use case that I’m sure the service providers running Veeam Cloud Connect will like.
I’m working on some heavy lab tests in these weeks, plus I’m travelling a bit more than usual, so my blogging activity has slowed down a bit. As I’m catching up on the news I read around, I found two different articles that can give to all of us a good perception about two things about the public cloud, or the so called “hyper-scalers”. They have insanely massive resources, but as insane as they are, they are not infinite.
Since Veeam Backup & Replication 9.5 became available and people are using the ReFS blockclone API, one of the most common questions has always been “how much space I’m saving? Is there any way to measure it”. Finally, there’s a way to answer to this question!
Veeam Agent for Windows 2.0 is today available as a public beta, and it’s soon to be officially released. One of the most awaited features is for sure the possibility to send backups over the Internet to Veeam Cloud Connect, and the feedback we’ve seen during the public beta period has been great so far. There’s actually however one limit in v2: users can only choose one destination for their backups. So, if you want to consume Cloud Connect, this is going to be your only traget and you will have no local backups, and viceversa. Two different policies cannot be configured in the interface, but this doesn’t mean it cannot be done!
Veeam Agents, both for Windows and for Linux, have the possibility to send backups to a Veeam Backup & Replication server. This is a great feature, but sometimes customers don’t even have anymore any virtualized workload to protect, so they find a hard time to justify the deployment of Veeam Backup & Replication to only protect physical workloads. There’s a solution to this however, and it doesn’t cost anything to users.