Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

Compeleted with Exceptions; but no exceptions

Updated: 23 May 2010 | 3 comments
cmara@tgo.ca's picture
0 0 Votes
Login to vote

I have a Backup Exec running that is continuously returning the error "Completed with Exceptions", but there are no additional comments that would indicate what the exceptions are.  The notification email gives a little more: "(Server: "SQL1") (Job: "Mon-Thurs Backup") The job completed successfully.  However, the following conditions were encountered:

A snapshot operation required by this job was unsuccessful. Check the job log and the Windows Event Viewer for additional information."; but that is all that I can find.

According to the log, every device was backed up and verified; and this is the entry in the windows event viewer: "The job completed successfully.  However, the following conditions were encountered:

A snapshot operation required by this job was unsuccessful. Check the job log and the Windows Event Viewer for additional information."

How do I figure out which snaphot(s) are giving me grief?

** I have rebuilt the job (new job with the same devices and properties) but I received the same error last night.

Thanks

Comments

CraigV's picture
07
Aug
2009
0 Votes 0
Login to vote

I'd start with checking that

I'd start with checking that your agents are all in working order.
From Backup Exec itself it'll be easy to push out the agents again.
DId you perhaps update your CMS at any time?

If you find this is a solution, please mark it as such.

OneManITShop's picture
07
Aug
2009
0 Votes 0
Login to vote

agent been reinstalled

as part of the troubleshooting of this problem
all patches been installed

----------------------
OneManITShop
read my blog at OneManITShop.blogspot.com

Gilly-Bhoy's picture
07
Aug
2009
0 Votes 0
Login to vote

Reply

Run
vssadmin list writers
from a command prompt on TS2.tgo.ca
If any of the writers are in an error state a reboot of the server may resolve it.

Regards,
Gilly

**Please mark as solution if indeed it is**