Backup Exec 2014 doesn't start after upgrade

[UFO]

Hello everyone!

Just did the upgrade from BE 2012 SP4 to BE 2014 SP1. The upgrade process has passed with no problems (no unsupported jobs or other similar stuff). But after physical server reboot the server is not working as expected:

1) Backup Exec Deduplication Engine service hungs with status "Starting"

2) Backup Exec 2014 Console doesn't start

3) Remote desktop connection for the server is not working (only through iLO does work)

4) Everything on the server seem to work slowly

Any ideas on how to fix this?

[ZeRoC00L]

Check: http://www.symantec.com/business/support/index?page=content&id=TECH200217

Also check the eventlog for messages.

[CraigV · Accepted solution]

...have you tried to repair the BEDB through BEutility.exe?

If your server doesn't respond on RDP, have you looked at the server logs to see what else could be going on?

Thanks!

[UFO]

Thank you for responces. After setting Delayed Start for all BE services all services are finally able (slowly) to start and the BE console is accessible, RDP too. But here's another problem. BE couldn't see the main storage device that is generally a shared folder on a physical storage. BE states that the storage is:"Offline. Unable to connect to the OpenStorage device.  Ensure that the network is properly configured between the device and the Backup Exec server ". This is for the updated CAS server. The MMS server which is on BE 2012 can access this storage.

[UFO]

UPDATE on this: we have opened a case with Support and the issue with the BE services was solved for now, and the OpenStorage device has been coonected successfully after that, Seems that these two issues were connected somehow.

But the main question remains the same: How to avoid this (slowly starting BE service) in the future? How to examine the environment to find the cause of that problem? Should I start a new thread on that?

[UFO]

Thank you. Yes we have tried. Also we havr tried to stop and start over the BE services using th BEutility.exe. Some combination of BEutility, Task Manager (End Process Tree) and other manipulations did help.