Skip to main content

Bug/Bad Feature in r16386

Thread needs solution

Hello,

this is just a report of bad behaviour of 16386, which might help someone who encounters the same problem:

 

Two days ago we began to update our storage node servers to 16386 and shortly after that we started to get reports from Acronis users that their backup plans are failing.

All errors were the same: The credentials for location "XY" are not specified (which is not true)

Updating the credentials in backup plan settings didn't help and we tried many more options (new backup plans, services restarts, repairing Acronis installation, re-attaching whole Locations, etc.).
Weird thing was that it wasn't happening on all updated servers, only on most. There's literally no difference between individual storage node servers (all are Windows Server 2016, VMs with identical configuration, identical software and updates installed), but eventually we found out the source of this problem.

The only difference between backup plans that are working after the update and those that aren't, is domain in the user name.

16386 requires user name (in backup plan settings) to contain domain name (if it's domain account). Up until now it wasn't necessary. And it's still not necessary when browsing the Location, for example (there I can enter user name without domain and it loads, no problem)

If the user accessing location is domain one, it needs to be set as "[DomainName]\[UserName]" in backup plan credentials.

 

So, it's solvable, but annoying as hell as we have over 1800 backup plans (40+ storage node servers) and most of them have this problem and thus need to have their credentials manually updated, one-by-one. :-/
Fun times, thanks.

 

 

Lukas

0 Users found this helpful

Hello Brose!

Thanks for discovering this!

For that many plans I'd take a shot at requesting a custom fix from Acronis, if you have active support.

-- Peter

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 0
Comments: 2016

Hello Lukas,

thank you for posting on Acronis forums!

Please check whether the machines with this error were in the domain. If they were not in a domain and a backup plan is run by the Agent which is in the domain, then you will see this error message.

There could be various reasons of this error message: another Agent (machine which runs this backup plan) is selected or the Agent has been migrated to another domain.