tag based backup, guest file indexing and credentials

[pirx]

Our backups are based on vSphere tags. It's simple, each VM in a cluster gets a tag based on the last digit in its hostname (0-9). So each VM has a tag like clusterxx_0...clusterxx_9. With this the jobs are somewhat dynamically balanced as new VMs are created or old ones are deleted. Now I wanted to test guest file indexing and I can't see how to define different credential based of OS. I created a test job based on a tag and value "true", set the "Guest OS credentials" to my windows credentials (this option seems to be mandatory). Then I added Win/Linux credentials in "Customized OS credentials...".

First of all, if I then click on test, Veeam tests the credentials of _all_ known VMs with the two guest OS tags. Not only the ones in the job.

For the Linux VM I get an error: "20.04.2022 17:21:08 :: Red Hat Enterprise Linux 8 guest OS requires Linux credentials"

What am I doing wrong? I also tried a combination of guest OS tag and the other tag (at least no all VMs are tested then).

[Andreas Neufert]

I would start checking authentication on a 1:1 base. Add a single linux system to a job and check guest processing.

- If you use Linux username and password, check that the /etc/ssh/sshd_config has the passwordauthentication yes set
- In any case check with Putty from the backup server if you can login with the credentials that you use.

If this is successfull, try to use the guest processing with the single VM.

If this works, add a new tag for just that VM and process it.

Somewhere in this step you will face an issue I guess. Please share then here and we can give more tips.

As well maybe open a support ticket to upload logs so that we can check this.

[Andreas Neufert]

For the scope of the test button. The scope of the job is not clear at that point in time, so it will always check the full selected containers.

[pirx]

I've already a job with only 3 VMs in it. A Windows, Linux and appliance. I know that the credential are right for the OS's but they are not used. Somehow Veeam always uses one type of credential for all tagged VMs in the jobs. And I can't remove the <Default> credentials for object "True" (that's Category IndexTest -> value True). I think this is always used and the other non-default for Linux/Windows not.

[Andreas Neufert]

Thanks for this clarification. I asked the field as well to contact you. Beside this let me find someone with a test environment to see if we can reproduce it here.

[HannesK]

Hello,
hard to say what's wrong without support case number... I think I did the same as you did and it's working fine for me.

The Guest OS Credentials user "azureadmin" is wrong for both my Windows and Linux machines. Taking this account would always fail. So I defined the account for the Linux tag and Windows tag and it works fine for me.

the settings (same result if I use the AND tag combination)


and here the result


Best regards,
Hannes

[pirx]

I just noticed that the affected VM does not have a tag from byGuestOSType category. It seems our VeeamOne has a problem, there are a lot of VMs missing VeeamOne tags or Windows VMs that have the byGuestOSType tag "Other" even though VeeamOne shows them correctly as Windows Server 2016 in the details. I've to create a case for that.