For a project I’m working on these weeks, I’ve been asked to demonstrate how an external system (a Cloud Management Platform, an Automation tool, else) can automatically create backups for some specific virtual machines without interacting with the Veeam console. This blog post will show you how, using vSphere Moref IDs.
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.
I’ve waited a week after VMworld ended in San Francisco before writing this post: there were too many blog posts from every blogger trying to cover any new announcement like a newspaper, and with the addition of news collected directly from the Expo Floor, sessions I’ve attended and other sources, the amount of info to digest required a bit of time. This post is not a recap of the event, just the things that I’ve seen and I found interesting. If something is not here, it may be that I’ve missed it rather than don’t liking it.
With the new release of vCenter Server Appliance (VCSA) 5.5, VMware has made a huge step forward in order to make the appliance a real choice not only for test and small business environments, but also for medium and large ones. Specifically, the new limit of 100 hosts and 3000…