v. 5.0.1.198 - HOTADD failing over to network mode

[antivir]

Hello.

Target VM: Windows 2003 Server R2, two disks: 10 Gb and 3 Gb
VBR: Clear Windows 2003 R2.


1. I make snapshoot and install 5.0.0.179
-Backing up (VA mode, via vCenter, root credentials for hosts)

5 of 5 files processed

Total VM size: 13,00 GB
Processed size: 13,00 GB
Processing rate: 33 MB/s
Backup mode: HOTADD/NBD with changed block tracking
Start time: 14.12.2010 19:47:16
End time: 14.12.2010 19:54:04
Duration: 0:06:47

Everything is ok

2. Revert Snapshot and install 5.0.1.198
-Backing up (VA mode, via vCenter, root credentials for hosts)

Total VM size: 13,00 GB
Processed size: 13,00 GB
Processing rate: 29 MB/s
Backup mode: HOTADD/NBD with changed block tracking
Start time: 15.12.2010 12:11:03
End time: 15.12.2010 12:18:36
Duration: 0:07:33

Backing up object "[MSA2-700GB] antivir/antivir.vmdk"
Hot add is not supported for this disk, failing over to network mode...

Backing up object "[MSA2-700GB] antivir/antivir_1.vmdk"
Hot add is not supported for this disk, failing over to network mode...

[Bunce]

I think the logging has been expanded in 5.01 - it was probably failing over to network mode before but you didn't know.

Verify the hot-add pre-requisites (note there are some in the faq that are not in the documentation).

different block sizes on veeam vm storage compared to vm being backed up is am easy one to miss and isn't checked/ presented in the veeam gui.

[Gostev]

Bunce is 100% correct, 5.0 simply did not notify about failover happening (you could only see that from full log), and this is documented as a resolved issue in the Release Notes document for 5.0.1...

Yes, the FAQ topic provides a link to list of all known limitations which may cause hotadd not being available for specific VM or disk, so this should help if you decide to troubleshoot this yourself, otherwise you may just contact our support of you need any help. Thanks!