β05-03-2010 08:50 AM
I have Backup Exec 9.1 on a windows server.
I have two jobs being canceled.
There is no reason given for why the jobs are being canceled.
One based on the size of the backup byte count "seems" to be backing everything up. They are just files. When I open the Job log it gives and error but opens listing the files etc that were backed up. eg.
======================================================================
Job server: BACKUP
Job name: Public Images [14A] Monthly
Job started: May 1, 2010 at 9:00:01 PM
Job type: Backup
Job Log: BEX18016.xml
======================================================================
Drive and media information from media mount:
Drive Name: AppsE_Public_M-T_[12A] + Images Monthly [14A]
Media Label: B2D005289
Media GUID: {5885C0D8-720B-469A-8495-27AE80B28F9A}
Overwrite Protected Until: 02/05/2010 1:14:00 AM
Appendable Until: 31/12/9999 12:00:00 AM
Targeted Media Set Name: Monthly Public Folder Backup
======================================================================
Media operation - append.
Software compression enabled.
======================================================================
NTSERVEROFO: Started for device: "\\NTSERVER\D:". Advanced Open File Option used: Veritas Volume Snapshot Provider (VSP).
Network control connection is established between 10.1.0.3:2227 <--> 10.1.0.19:10000
Network data connection is established between 10.1.0.3:2230 <--> 10.1.0.19:1895
\\NTSERVER\D: Data
Family Name: ">BACKUP >Public Images [14A] Monthly >12/4/2006 >10:38:38 AM"
Backup of "\\NTSERVER\D: Data"
Backup set #41 on storage media #136
Backup set description: "Public Images [14A] Monthly"
Backup Type: FULL - Back Up Files - Reset Archive Bit
Backup started on 01/05/2010 at 9:00:56 PM.
Directory \
Directory \Public
Directory \Public\IMAGES
READ THIS ON WHERE TO PUT PICTURES.txt
2082 02/12/2009 2:43 PM
Shortcut to Opening.wmv.lnk
730 18/12/2007 2:57 PM
The opening.wmv 63405786 18/12/2007 1:17 PM
Thumbs.db <HS> 13312 13/07/2009 2:08 PM
Directory \Public\IMAGES\100th Anniversary
IMGP3109.JPG 239754 09/10/2008 4:53 PM
IMGP3110.JPG 240243 09/10/2008 4:53 PM
IMGP3111.JPG 236953 09/10/2008 4:53 PM
... etc
The second is an Exchange Info Store Backup.
It "Says" in the Job Summary Information that 0 files directories etc where backed up. But then in the Job log, which displays an error when I open it , eventually says
======================================================================
Job server: BACKUP
Job name: Exchange [7A] Backup -Full Storage Group
Job started: May 1, 2010 at 10:37:12 PM
Job type: Backup
Job Log: BEX18019.xml
======================================================================
β05-03-2010 08:57 AM
β05-03-2010 09:10 AM
β05-03-2010 11:40 AM
β05-03-2010 11:52 AM
This is Possible but if the backup exec Job engine did terminate. Wouldnt that mean that all subsequent jobs would have the same error, or at least fail? However other jobs did not fail? eg here is the list of jobs. At least one was successfull 1 1/2 hours later.
---------------------------------
Starting with the latest
2:00 AM Failed
1:00 AM Successful
11:50 PM Failed
10:37 PM Canceled
9:00 PM Sucessful
9:00 PM Canceled
9:00 PM Successfull
--------------------------------
Please advise.
β05-03-2010 10:07 PM
β05-04-2010 09:32 AM
β05-04-2010 11:11 PM
From the events, the hardware (Backup to disk folder in this case) seems to throwing the errors. You can try the following:
1) Run a disk defragment operation and the Windows Error Checking Utility (CHKDSK /F) on the disk where the Backup to disk is residing.
2) Confirm disk compression is not enabled on the hard disk/s.
3) Check if there are any Disk Controller related errors in the System Log.
4) If possible, copy the data to some other disk, format the disk in question and recreate the Backup to Disk folder on that. Then try the backup.
5) Try creating a new B2D on a separate disk and check the result.
About the error logging/reporting, the job log is ideally just an indicator of the problem. It would not give you a detailed report. Also, in your case, because of the job engine service terminating, it could not completely write the log. However, the events in the Application log are posted by Backup Exec components itself and they are posted as and when they occur and do not wait for the job to complete. Thus, you may find the events but no error in the job log. This is how you can effectively use the job log, Alerts tab and Event logs for troubleshooting an issue with Backup Exec. Next step would be debugging which should be ideally handled by a Symantec Support engineer.
Let me know if the above steps do not help or if you have any queries.
β05-06-2010 12:44 PM