Backup Exec Job Engine se bloque Sym BE 2012 SBS

[lucho84]

Bonjour,

J'ai un serveur Windows SBS 2011 avec Symantec BE SBS 2012 sur lequel j'ai de gros problème avec le service Backup Exec Job Engine qui se bloque durant la sauvegarde et où la seule solution est de killer le service!

Je n'ai malheureusement pas d'autres informations à donner dans la mesure où je n'ai pas d'évènements pouvant expliquer ce bloquage...

Je commence à constater le même problème sur un serveur Windows 2003 + Exchange 2007, or pour tout mes autres serveurs qui sont protégés avec du BE 2010 SBS ou même Quick Start pas le moindre problème!

Dans tout les cas le support de sauvegarde est un lecteur RD 1000 de chez Dell avec des cassettes donc pas de bande

Je précise que la version 2012 est à jour (pas de nouvelles update)...

Qu'en pensez vous?

[lmosla]

Hello lucho84,

Make sure that the BE processes have been excluded from any antivirus scans. 

Have you tried running a repair of the BEDB with BEUtility.exe.http://www.symantec.com/docs/TECH67239

[lucho84]

Hi

I test my Database with succes and i modify my antivirus for an exclusion global on my symantec folder.

I run on next 3 days my backup task and i tell you result.

Thanks

[lucho84]

Hi,

My task run 48hours ago, i have to kill Backup Exec Job Engine process by taskkill / PID xxx /F so BEUtility and exclusion in avast didn't resolve my problem!!

I despair...

Have you other solution?

Thanks

[VJware]

Would you pls confirm if SP4 and HF 217347 are installed or not for Backup Exec.

Secondly, is there any event id 1000 logged in the event viewer relating to Backup Exec ?

Try splitting the backup jobs as well to check where the backup hangs. Does it hang during the backup of the C:\ or during the backup of System State or during the backup of DBs such as SQL, Exchange ?

[lucho84]

I 've just look and i confirm have SP4 and HF 217347. In my event viewer i didn't have any id 1000 ralting BE.

In my  firts server i have 2 task :

- 1 daily backup of my server (Windows 2008 just domain client of my controller) where i save system state,C: partially and D: On this server i have just SQL server for my software (Sage) + data. This task saved and sent backup to my controller server (Windows 2003) by using agent of BE

- 1 daily backup of my controller domain (windows 2003). In this server i have Active Directory, DNS, IIS, Exchange 2007 (role + mailbox) + data of users (word, excel, pdf...). I have also SQL Server for BE and my manage antivirus (avast endpoint protection suite plus with small office console). Thi task sent backup to my RD1000 cartridge.

In my second server, i have 1 task

- 1 daily backup of my server Windows 2011 SBS. I used AD, DNS, IIS, Exchange 2010 + Sharepoint. I have 5 SQL DB (1 for WSUS, 1 for monitoring console of SBS, 1 for Avast, 1 for BE and 1 for sharepoint) + data of user. I sent backup to my RD1000. I exclude WSUS DB and BE DB of my job but same problem BE Job Engine hang when the task running.

I'll try to execute 1 task and i'll test that why hang BE Job Engine and i'll let you know.

Thanks

[lucho84]

Hello,

I tried to launch 1 of 2 tasks in my first server and BE Job Engine hangs again!

So the problem is not on the task because any task cause hangs of BE Job Engine.

Other ideas?

Thanks for helpfull

[VJware]

Would recommend to log a support case for an engineer to have a look @ your setup and figure out what's going wrong.

[lucho84 · Accepted solution]

Hi,

I would like report resolve for thi thread. I had just uninstall BE completely and re-install it... It works perfectly since 2 months on my 2 server.

So the problem are BE Job Engine unstable, It would have Symantec corrects this problem by an update.

Salut,

Après des heures de recherche, j'ai enfin trouvé la solution! Il suffit de déinstaller complétement et réinstaller BE et cela fonctionne parfaitement depuis 2 mois sur mes 2 serveurs.

Le problème est donc bien au niveau du service BE Job Engine qui est instable après 2 ans d'utilisation...

Donc merci à Symantec de corriger ce bug par une mise à jour car je suppose que ce service est identique sur la version 2014 donc même problème après 2 ans d'utilisation!