Backups using VMM tags fail after V10 upgrade

[cookiejc]

Hi, we have just upgraded to V10 to find all our backups are failing with the following error:

28/02/2020 18:14:31 :: Task failed. Failed to expand object "VMM TAG NAME". Error: Object reference not set to an instance of an object.


This appears to be an issue with Veeam enumerating VMs within a defined TAG

We have logged a Sev 1 case: 04034492 to simply be told this is a known issue and "suggest we add the entire SCVMM into the backup job instead"

This is not a solution as it would target servers which we do not want backed up. The tags are there to define backup policies and priority etc

The other alternative suggested makes no sense to me at all "As an alternative on the Hyper-V side, you can work around this by deleting or deploy/deleting all VMs from the Library. "

Can anyone help?!

[HannesK]

Hello,
yes, it's the issue #4 described here

EDIT: hotfix was sent to you (was not ready when I answered initially)

Adding the VMs on an alternative way is currently a workaround. Instead of adding the full SCVMM, I would try to get the tag information from SCVMM with powershell and then add the machines with powershell to the jobs. I suggest to test with a small job, whether it causes full backups.

Or you could go back to 9.5U4 - as you could not do any backups anyway. That should not be a big deal, just restore the old configuration backup to U4 https://helpcenter.veeam.com/docs/backu ... ml?ver=100

Best regards,
Hannes

[rosen]

Hello,

Can this SCVMM fix be publicaly available, so everione can use it, or it is available only to paid subscriptions?

Thnaks

[HannesK]

[/quote] or it is available only to paid subscriptions?[/quote]
correct. but it will be included in future updates.

actually I'm surprised that a SCVMM might use community edition