Best practice for moving vSphere 5.1 to non-LDAP auth

[dgapinski]

Hello,

We are anticipating the eventual turning-off of non-encrypted LDAP for AD. This scheme is not supported in vSphere 5.1, and we're not going to upgrade, so we removed LDAP authentication from vSphere. It seems to me that we have 3 options for how to handle VM backup for the time being, until we decommission the VMs there:

1) change the Veeam auth to a vSphere local account
2) change the Veeam auth to a host local account
3) use the agent on each VM

I am tried #1 a couple days ago, but it looks like the job does not have access to vSphere, even using the local account. For today, I removed and re-added the vSphere server with the local account, to see if that will work instead.

My questions are, is there a reason option #1 might not work? Or would options #2 or #3 work better for some reason?
Thanks - stay safe!

[wishr]

Hi Dan,

I would for sure stick with the first option. As long as the supplied account has all the required permissions, there should not be any issues.

Thanks

[dgapinski]

OK, thanks Wishr. That is what I thought as well. Since changing the authentication on the server did not work, I ended up having to remove the job & server and re-add both. I will let you know if that works out tonight.

[dgapinski]

That worked out perfectly - once I removed the job and server and re-added them, it ran just like before.

Thanks for your thoughts Wishr.