"VM is backup server - not a parallel task" - but it's not!

[mdiver]

With a replication job consisting of a single large VM we see:

"Waiting for completion of other tasks (VM is backup server - not a parallel task)"

Therefore CBT is getting switched of and VBR is waiting for other tasks to finish first.
Because of the lack of CBT the backup is pretty slow as it has to crawl every bit and byte.

Which is the actual trigger for this behavior? The VBR is actually a physical machine here. The proxy is an Ubuntu hot-add proxy.

Thanks,
Mike

[foggy]

Hi Mike, do you mean the job mistakenly detects the VM as a backup server while it is not a backup server? Do you have a support case open for this?

[PetrM]

Hi Mike,

Any chance to use another virtual proxy for HotAdd? Perhaps, it would allow you to circumvent the issue while our support team is looking into it.

Thanks!

[mdiver]

It's just a small PoC on a trial license. But I opened a case though (02203478).
Actually we ARE using a hot-add proxy (linux) already. VBR server is acting as backup server and repo only.
The VM has NO role in VBR.

Both jobs - backup and replication - state the same thing -> "VM is backup server".

I wonder what exactly is the trigger for VBR to assume it to be the VBR itself.

The one thing special here: the physical box that now IS the VBR (from freshly installed W2016) USED to be the server (W2012) that now became the VM (P2V) to be backed up.
Both fully independent Windows installations. No upgrade whatsover. Might a hardware ID being transported into the VM be the reason?

Thanks,
Mike

[foggy]

Chances are it still has some components installed from the previous life, support will be able to check.

[mdiver]

Case was solved together with support. The VM carried the same vmx uuid.bios value because of P2V.
This seems to be the indicator for VBR that it must be the VBR server itself inside.

Had to be changed manually within the vmx file.
Afterwards CBT gets enabled properly and the VM gets backed up at full speed.