this happened 3-month ago.
we've the NetBackup Services set to start using domain account. after some windows server 2016 updates, the services failed to start automatically after reboot and we had to go and manually start them after each reboot.
how can we fix this?
error from system log:
-The NetBackup Compatibility Service service was unable to log on as domain\username with the currently configured password due to the following error: There are currently no logon servers available to service the logon request. To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC).
-The NetBackup Compatibility Service service failed to start due to the following error: The service did not start due to a logon failure.
-The NetBackup Database Manager service depends on the NetBackup Client Service service which failed to start because of the following error: The service did not start due to a logon failure.
well, there is not so many things that can be solved here from NetBackup side.Check the core problem with your AD admin:
There are currently no logon servers available to service the logon request.
Is there a reason why Compatibility and Client Services are running under a Domain account? Usually Local System account is enough for all Master Server services.
thanks Michal for your reply.
usually if the service is set to "delayed start" this work but dependant services does not.
can we put all the netbackup services to delayed start? will that cause issue?
"supported" is not probably the best word, better is that it is not necessary.
It is also a default install option.
Sometimes it is required to use domain account, but it is rather on clients (not Master/Media Servers) and for special reasons - usually when permissions for some database agent operations are needed. Or when a filesystem agent needs to backup network drives.
And I have never used domain account for NetBackup Master Server services.