cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to back up following v.10 upgrade

Philippe_Heinri
Level 2
Following upgrade to v.10, unable to perform backups.

All jobs submitted result in "No Communication" being shown for "Job Status", but:

1. Test Runs end up as "Successful" in Job History after a few minutes

2. Inventory jobs quickly return error message indicating the job failed because "The Backup Exec job engine system service is not responding". Jobs then ends up in the Job History with status "Recovered". However, if application is exited and re-launched, same jobs now shows as "Successful".

3. Backup jobs behave like Inventory jobs, except on re-launching application, jobs are shown in Job Log as "Cancelled".

Windows Event Log shows '33152' Adamm Mover Errors (ERROR=ERROR_BUSY).

All BE Services are started and running OK.

Server is W2K SP4, and is a Secondary server on a BE SAN Storage configuration. Primary server and two other Secondaries are running just fine. BE 9.1 worked OK before upgrade (except unable to run any SPs of HFs).
3 REPLIES 3

ashwin_pawar
Level 6
Repair Backupexec installation:
Repairing VERITAS Backup Exec (tm) 9.x and 10.0 for Windows Servers
http://support.veritas.com/docs/253199

Once the repair is done,


Repair Backupexec database.
Repair backupexec database
How to run a database repair in VERITAS Backup Exec (tm) 9.x for Windows Servers when the original database is found to be inconsistent
http://support.veritas.com/docs/265180


I hope it helps.

Philippe_Heinri
Level 2
Have installed, uninstalled, repaired, re-installed, etc numerous times (between 4 and 8 times). Same result.

Have run repair on the database using beutility.exe from the SAN Shared Storage primary server. No change.

Support case is with Veritas, will post outcome.

Ameet_Thakkar
Level 6
We would appreciate if you could post a query to our Email support at http://support.veritas.com/

Please attach the following logs so that we can help you troubleshoot the problem.


1] All the related job logs in HTML format.
Refer to the following technote to create them in HTML format:

URL - http://seer.support.veritas.com/docs/251970.htm


2]BEDIAG.FAX file. (For Backup Exec server and remote server)
Refer to the following technotes to create the BEDIAG.FAX files.
- Local server URL - http://seer.support.veritas.com/docs/251779.htm


- for Remote server URL - http://seer.support.veritas.com/docs/192302.htm

(This technote is applicable to Backup Exec v9.x/10.x)


3] Event ID's (System and Application logs) in ".evt" format on Backup Exec server and remote server.


4] SGMON.LOG file - The SGMON.EXE file located by default in \Program
Files\VERITAS\Backup Exec\NT folder. Start sgmon.exe just before starting
the backup job, this helps us see the sequence of events. Refer to the
following technote:

URL - http://seer.support.veritas.com/docs/190979.htm


5] System information file from the related systems in ".NFO" format using
the WINMSD.EXE utility.

6] Relevant screen shots of error message encountered if any (in .jpg format)

7] Bkupinst.log and MSDE_BKUPEXEC.log file located in WINNT folder.



How to locate the logs generated during the installation of VERITAS Backup Exec (tm) 9.x/10.x

http://seer.support.veritas.com/docs/268722.htm


Please send requested information in single zip file.
============