Update 4 Backup Warning - Failed to build target multi-home info

[DeadEyedJacks]

After updating Veeam Backup and Replication 9.5 from update 3a to update 4
Now receiving this warning for some VMs on some jobs.

"Failed to build target multi-home info for VM"

Any ideas what this means ?

Jobs are NetApp Data OnTap Snapshots and SnapMirrors
NetApp version 9.3 with version flexible SnapMirrors

[veremin]

Have not seen this issue previously, can you please open a support ticket and provide its number here (so we can investigate it internally)? Thanks!

[foggy]

The affected VMs have disks on multiple VMFS datastores (support for such VMs in snapshot-only jobs was added in U4) and info for some of the disks on the target side cannot be collected for some reason. Please open a case to investigate. Thanks!

[DeadEyedJacks]

Case #03379173 was created

Yes Foggy, you're correct VMs with warning have multiple VMDKs spread across VMFS datastores.

NB Support for this is primary reason why we've upgraded so quickly.

[DeadEyedJacks]

OK, we established that this warning was due to the service account been used having insufficient permissions on the secondary NetApp controller.

Restore from NetApp Snapshot for multi-disk VMs on the primary controller have been tested and are working OK.

Thanks

[Gostev]

Great! Thanks for coming back to post the solution, and I'm happy that your quick upgrade to Update 4 will now start paying off

[Dino]

i am having the same issue. I started a job that creates a Netapp Snapshot on the primary storage system and initiates a snapmirror to the secondary storage system. The job is a SQL Server with application consistency. What do you mean the service account being uses has insufficient permissions to the secondary storage? The service account i am using doesn't have access to the primary storage. The service account is a windows domain account, while the account used to connect to the Netapp controllers is a Local Netapp account

[Dino]

Anyone have an update. Your solution was unclear to me?

[DeadEyedJacks]

Hi,
"Failed to build target multi-home info" seems to mean "Veeam can't find one or more protected VMs on the destination SnapMirror at the secondary site"

Our initial problem was with insufficient permissions for the NetApp service account we use for Veeam.
Once that was resolved we still see this error periodically when VMs have been moved between datastore clusters and / or when SnapMirrors are lagging behind.
Hope that helps

[orb]

I had this reason for a space problem on the destination (snapvault). The snapvault destinations were busy in 'Quiescing'. The log returned the correct error, not this strange cryptic message

Oli
.

[foggy]

Indeed, logs typically contain more details on what's happening than the high-level UI message.