Individual Credentials on VMWare Tagged VMs

[stevil]

Hi all,

I'm starting to use VMware tags to backup groups of VM's. When it comes to 'application aware' options it looks like I can only specify one option for the tag I've selected. Is there a way of drilling down into those tagged VM's? Is it a case of adding the VM into the list manually to change it's options so it overrides the tag setting?

Thanks.

[dellock6]

Hi Steve,
I tested it now and probably the issue is that, when you use the "add" button to add additional credentials, even if you are using tags, the view in the pop-up is again the default host and clusters, where you see the selected tag but you cannot further expand it. If you switch again to "VMs and Tags" then you can expand the selected tag and see all the VMs that have that tag and that will then be processed by that job.

Hope it helps,
Luca

[sandrola]

Hi Luca
i have a similar issue with Veeam Backup & Replication 9.5 on vSphere. I have some VM tagged to two Tags (Domain and standalone). All VM are only reached via VIX. Credentials are also defined. During the Job configuration i can select under "credentials" the right credentials for the related Tag. The test is also positive, all VM can be reached via VIX with the related credentials. To finish the Job setup I must choose a credential from the dropdown in the "Guest processing" step. Wich one should be selected? I tried with booth ^, but no success (see next paragraph).

During the backup I have a strange behavior, the non-domain VM cannot be backed up due to a wrong credentials (in the log the right credential is NOT tried, only the Veeam default and the Domain Credential).
If I define new tags in VMware, and I add these tags to two of the VM (one Domain and one non-Domain), with the same settings (pick up the stored credentials) the Job works fine.

My Questions:
1. Why is the Test ok and job not?
2. Is something in the DB that can/must be cleaned up?

many Thanks
Sandro

[sandrola]

Hi All

I have found the issue that caused the weird behavior: the Vsphere folder where the VM resides was tagged itself with the Domain-VM Tag. This take precedence on the VM Tag and force the backup to use the "wrong" credentials.

[dellock6]

Thanks for posting your findings, appreciated!

[Regnor]

I'm currently creating backup jobs for a high amount of VMs which need different credentials; all jobs using vCenter Tags.
It's nice to have dynamic jobs with tags, but it only works well if all the VMs are in the same domain.
So wouldn't it make more sense to make the guest OS credentials independent of the backup job? If the credentials were globally defined a VM could move from one job to another without the need to set the credentials.

[dellock6]

I totally agree credentials should be a property of the VM, not the job.

[Regnor]

Perhaps we can count that as a feature request

By the way what would happen if a VM has two tags with different credentials in a single job?