Migrating Veeam to a new Windows domain

Good morning,

I switched to a new Windows domain last night and things went fairly smoothly.  The only remaining issue is the Veeam B&R server, where it refers to the old domain.  I tried to add a new VMWare vSphere infrastructure entry and hit a snag.  The login failed.  I'm not sure if this is an issue with Veeam or with vCenter server, or something else.

Running vCenter Server 6.7 and Veeam B&R 9.5.

Any suggestions?



Login failure
Ben ConnerCTO, SAS developerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
The account you are using configured in Veeam, does it have the correct permissions, and have you tested that account when logging into the Web Client (vCenter) with that account and password ?

It looks like the account you are using does not have correct permissions, wrong account/username combo etc

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Ben ConnerCTO, SAS developerAuthor Commented:
Ah.  I thought it was to log in to the Windows server, not the vSphere Center server.  I don't have that configured yet to use the Windows domain for logins.  

Using a vCenter server account worked fine.

It looks like both the old and new entries have the same VMs under them.  Is it safe now to remove the obsoleted domain entry?


Sebastian TalmonSystem Engineer Datacenter SolutionsCommented:
If you move to a new vCenter, all VMs will get new IDs - and you have to reconfigure all your backup jobs.

Although your jobs list the VMs with their name, all entries reference the old vCenter and VM ID

Veeam also have a Migration Utility to assist you with that:
Sebastian TalmonSystem Engineer Datacenter SolutionsCommented:
I would recommend that you continue to use local vCenter accounts for your connection to vCenter, so backup/restore is still possible if your domain controllers are down (maybe add a veeam@vsphere.local account with admin permissions so you can differentiate your own tasks from Veeam tasks in the recent tasks/events)
Ben ConnerCTO, SAS developerAuthor Commented:
Thanks, Sebastian.  Good idea.  That's what I went to after Andrew's comment.  Once it works I tend not to change it without good reason.

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.