- Service Provider
- Posts: 63
- Liked: 1 time
- Joined: Mar 22, 2010 8:43 am
- Full Name: Andrew Singleton
We encountered an issue with the replication task on Monday, one of the domain controllers was rebooting as part of a scheduled restart.
The replica job was then unable to authenticate against the VC. The error generated is below.
Checking "ESXSERVER.domain" host license level Failed to login to "VC" by SOAP, port 443, user "DOMAIN\USername", proxy srv: port:0 Exception has been thrown by the target of an invocation. Cannot complete login due to an incorrect user name or password.
We have a secondary domain controller which was available for authentication, should veeam not have authenticated against the other DC?
DC1 - reboots 11pm
Replica job 1 - starts 23:00:19
Replica job 2 - starts 23:00:19
The next entry in the job log is :
Status Success Start time 17/05/2010 23:10:46 Details
Total VMs 0 End time 17/05/2010 23:11:06 There are no objects to backup
Processed VMs 0 Duration 0:00:20
Successful VMs 0 Total size 0.00 KB
Failed VMs 0 Processed size 0.00 KB
VMs in progress 0 Processing rate 0 KB/s
The primary DC was back online at ~23:03
The next job ran successfully at 1AM (2 hour schedule)
- SVP, Product Management
- Posts: 27831
- Liked: 4774 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
Generally, if AD has no issues, this issue should not happen assuming vCenter implements Microsoft recommendations on working with AD, and uses serverless bind instead of specifying exact DC to connect to, and "sticking" to it.