Forum Discussion
- mikeviennaLevel 3Hi,
Since you wrote "after restarting" what did you did/changed before that reboot?
I'm not a win user but running "services.msc" and then look at the netbackup services.
Check via properties the start type should be set to automatically start the services on startup.
And you can use "msconfig.exe" I think that tool also relates to autostarting in some ways - NicolaiModerator
also check the event log, maybe there is something preventing Netbackup services to start during boot.
- AndriiPushkarovLevel 5
This server has not been rebooted before. This is a new server.
Temporarily configured start Netbackup services through Task Scheduler after system startup.
- NicolaiModerator
You wrote "After restarting the media server, the Netbackup services do not start automatically."
but is now saying "This server has not been rebooted before" ??
I am starting to be a bit puzzled.
During media server installation, Netbackup will set it services to be started during boot. Check with services.msc
If you by hand wand to restart Netbackup services use bpup and bpdown
- AndriiPushkarovLevel 5
Sorry for the confusion.
There was a question from mikevienna:
“Since you wrote "after restarting" what did you did/changed before that reboot?”;
answer to this question:
“this server has not been rebooted before”
This server is newly created. His story has just begun
Now about the problem.
Obviously, there are reasons why the Netbackup services do not start automatically after the media server's operating system starts.
I tried using "Delayed Start" for services. It turned out successfully.
But I don’t know if it will always be correct and in the right sequence to start services in this way?
- mikeviennaLevel 3I forgot to mention that you should look at the events (run eventvwr)..
- AndriiPushkarovLevel 5
By default, the launch of some Netbackup services is set to “Automatic”.
In this case, the Event Log present error is: A timeout was reached (30000 milliseconds) while waiting for the NetBackup Anomaly Detection Management Service service to connect.
As I already wrote, the launch of “Automatic” services was reconfigured to “Automatic (Delayed Start)”.
In this case, the services start without an error message.
- admin_bkp007Level 5
Go to console NBU Devices/Media Server right click in your media server MM Device Daemon restart and check your event viewer.
- AndriiPushkarovLevel 5
Thanks for your interest in the issue.
I did MM Device Daemon restart.
The event viewer has the following message:
”The NetBackup Device Manager service entered the stopped state”;
“The NetBackup Device Manager service entered the running state”.
As for the future work of this media server: the launch of "Automatic" services has been reconfigured to "Automatic (Delayed Start)".
Such start of services does not lead to errors.
As confirmation, Veritas recommends running services like this for a master server: https://www.veritas.com/support/en_US/article.100047659
Related Content
- 11 years ago
- 12 years ago
- 10 years ago