If you are comfortable and understand the implications, you can go ahead and run the following command on each host in the clusters that you plan on installing the I/O filter onto: esxcli software acceptance set -level CommunitySupported I highly encourage you to check out the VMware Manage the Acceptance Levels of Hosts and VIBs documentation. It is crucial to understand what this setting is, as well as what the impact (from a support standpoint) is if you make the change.

If you don’t change this setting, you’ll receive an error message: “Illegal acceptance level ‘partner’, required: ‘community'”. However, there is a caveat that your hosts need to be set to have a VIB acceptance level of Community (the default is “partner”). From there Veeam will push out the filters to the hosts. This will launch an install wizard which allows you to select which cluster(s) you want to install the filter onto. You can accomplish this by going to Inventory –> Virtual Infrastructure –> vCenter Servers –> vCenter (in my case, ), and clicking on “Manage I/O Filter”. I n order to leverage these filters, the ESXi hosts in your datacenter need to be prepped. What is worth noting though is that vSphere 7.x supports VAIO (this is not to say that Veeam v11 is vSphere 7 certified). I’ve previously covered the tech behind CDP, which leverages VMware’s VAIO (vSphere APIs for I/O Filtering), so I won’t get into that portion. Additionally, there is the chance that some functionality may still change before GA. This will be visible in some spots as terms such as may be visible. Please note that the experience below as well as the screenshots are based off of the version 11 beta 2 code. I most recently wrote about it again last year, when we got another preview of the tech at the Veeam Vanguard Summit.Īlas, with 2020 unfolding how it has, some welcome news is here: CDP will be a part of Veeam v11! Since I’ve been literally talking about this feature for years, I’m pretty excited to share what I’ve seen with it. stability or performance issues were deemed unsatisfactory by Veeam’s internal QA process). Over the course of time, the release date has slipped a few times, but largely for good reason (e.g. Anyone who is a Veeam user is likely well aware of Veeam’s “upcoming” CDP (Continuous Data Protection) it has been somewhat notorious as it was announced way back at VeeamON 2017 in New Orleans.