VEEAM -Certified Engineer (VMCE8)

Standard ✘ All editions ✘ Enterprise Plus ✘ Enterprise and Enterprise Plus ✔ Free ✔

Instant VM Recovery only works from newest restore point. ✘ Migration to production after Instant VM Recovery allows to change disk type. ✘ Instant VM Recovery is only available in paid editions. ✘ Instant VM Recovery allows a VM to be fully booted and all applications up and running in as little as 2minutes ✔ After migration to production has completed the Instant VM Recovery, VM is automatically no longerpublished. ✔

After comitting failback, the failback protective snapshot that saves the pre-failback state of a VM replica is deleted. After commiting failback, replication activities for the VM which you failed back are NOT resumedautomatically. When you undo failover, the VM replica is reverted to its pre-failover state, powered off and all changesthat have taken place since the VM replica was powered on are deleted. After undoing failover has completed, you will need to reconfigure the replica job before it will startagain. It is only possible to failover one VM at a time.

Yes, all file systems are fully supported. ✘ Yes, but a support case will have to be opened. ✘ No, this is not supported. ✘ Yes, but you need to install 3rd party tool Portlock Explorer. ✔ Yes, but it requires manual work ✔

Veeam Explorer for Exchange supports Microsoft Exchange 2007, 2010 and 2013. ✘ When you run the Exchange Items Restore wizard on a VM backed up using VSS, the ese.dll file is added automatically ✘ Veeam Explorer for Exchange is only available for paid editions. ✘ The Extensible Storage Engine DLL file can be found on the Microsoft Exchange Server distribution CDat X:\Setup\ServerRoles\Bin\ese.dll ✔ Veeam Explorer for Exchange requires a special dynamic link library - ese.dll - otherwise it can onlyexport folders/items to .PST files. ✔

RESTful API is an optional feature. ✘ Only XML format is currently supported for RESTful API for resource representation. ✘ Users with Portal User role can access VMs from their restore scope in VMs and/or Files tab andgenerate reports as permitted by their settings. ✘ Restore scope can be customized if you have Enterprise Edition. ✔ Users with Restore Operator role can access VMs from their restore scope in VMs and/or Files tab, aswell as reports for these VMs; they can also perform restore operations as permitted by their settings. ✔

To see a list of available commands use: Get-VBRCommands The PowerShell Snap-In is an optional component. The PowerShell Snap-In is installed by default. The PowerShell Snap-In is available for all editions. A PowerShell script could be run as a post-job activity.

Continuously ✘ Daily ✘ Every minute ✘ Hourly ✔ Every 5 minutes ✔

No, for Hyper-V hosts a proprietary filtering mechanism is used. ✘ Yes, but only for gen 2 virtual machines using VHDX. ✘ Yes, Veeam Backup & Replication installs a file system filter driver on every host. ✘ Yes, Hyper-V has built-in Change Block Tracking just like vSphere has. ✔

New compression settings are applied at the next run of the job. Previously created backup files are not affected. ✘ New compression settings are not applied until an active full backup has been performed. Previously created backup files are re-processed. ✘ New compression settings are applied at the next run of the job. Previously created backup files are re-processed. ✘ It is not possible to change compression level after first backup has been run. ✔ New compression settings are not applied until an active full backup has been performed. Previouslycreated backup files are not affected. ✔