vSphere 6.7 Update 1 and Veeam Compatibility Issues

Yesterday, Tuesday 16th October saw the much anticipated release of VMware’s vSphere 6.7 Update 1, however, shortly after the announcement a number of Veeam users decried the release due to compatibility issues with Veeam’s Backup & Replication suite. None other than Veeam’s Anton Gostev first announced the issue with the below tweet:

The very next day the Veeam team announced a workaround in the form of Veeam KB2784, as well as ‘out-of-the-box’ support being included with highly awaited (and much delayed) next release, Update 4.

Where the fault lies with such release/compatibility issues is not the goal of this post (which Twitter seems to be more focused on). However, with a high number of pros likely raising internal changes to upgrade their vCenter(s) and ESXi hosts, you’ll want to implement the Veeam workaround in-line with this upgrade, as well as a number of solid backup/restore tests.

Veeam Backup & Replication 9.5 Update 3a

In this article we’ll cover the simple process of applying the latest Veeam Backup & Replication 9.5 update, Update 3a (released July 2nd 2018), however, I’d first like to cover what’s new in Update 3a, and why you might like to upgrade.

Update 3a brings support for a host of new VMware and Microsoft features, as well as a substantial number of enhancements. With VMware vSphere 6.5 U2 and 6.7 now well into GA, the release of Update 3a is something most of us have been craving in order to obtain that final green light to upgrade our vSphere environments. From the Veeam Release Notes for Veeam Backup & Replication 9.5 Update 3a the enhancements and newly supported features are detailed below.

Continue reading → Veeam Backup & Replication 9.5 Update 3a

Veeam Exchange Explorer

Veeam Explorer for Microsoft Exchange – Configuring Application Impersonation

To restore an Exchange mailbox/folder/item via the Veeam Explorer for Exchange, the account connecting to the Exchange server will require Full Access to the mailbox in question. To perform such a restore (without having to give your entire backup admin teams Full Access to every mailbox in your estate), we will cover the process of granting Application Impersonation to your administrative staff. This procedure applies to both on premise Exchange and Office 365 and can be easily implemented via a few simple Exchange Management Shell commands.

Veeam Exchange Explorer

Veeam Explorer for Exchange - The account does not have permission to impersonate the requested user

Implementing Exchange Application Impersonation

After connecting to your Exchange Server, launch Exchange Management Shell and run the below command. This will configure Application Impersonation for a specific user.

New-ManagementRoleAssignment –Name:"<ASSIGNMENT_NAME>" –Role:ApplicationImpersonation –User:"<USERNAME>"

Implementing Exchange Application Impersonation

View Accounts Configured for Application Impersonation

Get-ManagementRoleAssignment -Role ApplicationImpersonation

View Exchange Application Impersonation

Removing an Account Configured for Application Impersonation

Remove-ManagementRoleAssignment -Identity "<ASSIGNMENT_NAME>"

Remove Exchange Application Impersonation

Reference