Wednesday, 24 April 2013

Symantec Backup eVault Error: Possible Causes

Ref. Backup exec verison: Symantec Backup Exec 2010 R3 v13.0Rev.520464bit.
1. Check the version of beremote.exe (C:\Program Files\Symantec\Backup Exec\beremote.exe) on both backup exec server and on enterprise vault server (C:\Program Files\SYMANTEC\BACKUP EXEC\RAWS\beremote.exe).  If differs, must be the SAME version.
Check if there is enough storage space on backup exec server
3. Make sure that the backup exec remote agent services are running on both SQL nodes.
4. DB Permissions needs to be checked. The backup service account needs to have db ownership rights on all the enterprise vault related databases.
Try considering redeployment of BE remote from symantec console to the destination server.
if for any reason the above deployment fails, consider manual re-installation of Symantec Backup exec remote agents:
(agent location)
32bit: C:\Program Files\Symantec\Backup Exec\Agents\RAWS32
64bit: C:\Program Files\Symantec\Backup Exec\Agents\RAWSX64
5. Enable troubleshooting: Click SGMon.exe (C:\Program Files\Symantec\Backup Exec\SGMon.exe) from backup exec server. Capture the following check lists:- JobEngine,RAWS; Backup exec server;Device and Media;Third Party debug output and then click start capturing debug output.
6. Run the backup schedule again. try to expand the enterprise vault backup selections again until the error pops up. 
You might get a tip to find out the error cause from the SGMon capture screen.