In 2012 I wrote a blog post that became really popular: Installing VMware tools on Centos 6 via yum. Few years forward, and today the preferred tools are the open sourced ones available natively in many linux package managers. So, some may think to switch from one version to the other one for their existing virtual machines. That’s what I’ve done in some of my virtual machines, and here is the process.
CentOS is known for not using the latest versions of the Linux kernel. If you need up-to-date versions, you need to configure the OS to use different repositories.
If you have a large environment that is constantly changinh, you may want some automation to test VMs every day with Veeam SureBackup. Here’s a solution to do so.
Since Veeam announced the Scale-Out Backup Repository technology coming in Veeam Backup & Replication v9, I’ve been asked already multiple times to give some practical examples on how to leverage it. Let’s see together one interesting way to leverage the “performance” policy available in Scale-Out Backup Repository.
If you want to backup virtual machines running on an NFS storage in vSphere using virtual proxies, Veeam has a dedicated registry key to protect you from NFS locks.
Lately, different bugs involving VMware CBT in vSphere 6 have created some justified concerns among users. But there are ways to guarantee successful backups even in these conditions.
One of the features coming in Veeam Backup & Replication v9 is per-VM backup chains.This great addition was in between a general announcement related to other backup storage improvements; in case you missed it, here we go with a dedicated post, because this feature is going to be great!
When you have to deal with a large environment and several jobs in Veeam, automation via powershell is the only possible solution.