Hyper-V 2016 VMs with non-snapshottable disk such as disks connected via in-guest iSCSI initiator can now be processed by backup and replication jobs, with unsupported disks skipped and their content not included in a backup or replica. If you’d rather prefer the job to fail on such VMs (legacy behavior), create HyperVIgnoreNonSnapshottableDisks (DWORD) value under HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication registry key on the backup server.
spgsit5upport wrote:So basically 2016 is still unusable, right?
I am on 2012 R2 where at least I can have shared vmdx backed up in crash consistent mode (for backup & as workaround for DR - due to ne replication possible)
I simply can not move to 2016 in that case!
Users browsing this forum: PTide and 5 guests