Backup Exec Device and media service is stuck in starting state
Check the TN below then and make sure each of your services are started up with the correct account:
https://www.veritas.com/support/en_US/article.TECH67215
Full SQL is fine for the BEDB.
Thanks!
BE is designed to run on a server which is part of a domain. You can have the media server in a workgroup, but you would encounter a lot of problems with your backups due to lack of permissions.
All the BE services must run under a domain admin account, except for the BE remote agent service which is run under a local admin account.
Your best bet is to include the media server in a domain and run the BE services using a domain admin account. See the document below for the rights required by the BESA.
http://www.veritas.com/docs/000028683
Larry, the backup exec is just now installed and I ve not been able to successfully log into the backup exec and hence no storage is created or added at this point
I would use the BE Service manager (servicesmgr.exe, or another method) to set the BE services to manual. This allows you to torubleshoot BE separate from the server booting.
Once the server is booted and BE services are stell stopped:
- check Windows Device Manager for any issues
- start SGmon.exe and enable logging for pvlsvr
- start tracer.exe and enable logging
- Use BE Service manager to start the BE services
- Look for errors or issues in SGmon or tracer
You may need to open a tech support case for full log analysis.
Since this is a fresh install, maybe it is just that something wonky happened during the install, so you may want to try and un-install, reboot and re-install of BE
For the issue you see, I don't think that the servioce account matters. Using a domain account is certainly the best way to go when you want the BE server to interact with other servers, but it isn't needed to get services started locally.
Even if things (sources/targets) aren't configured in BE yet, the Device and Media Service does some exploring of your server to see what devices are out there. What are your intended backup destinations? If you have anything "optional" connected, you may want to disconnect it during troubleshooting to help isolate issues.
