We're often experiencing failed backups, they fail with an error "V-79-57344-34108 - An unexpected error occurred when cleaning up snapshot volumes. Confirm that all snapped volumes are correctly resynchronized with the original volumes".
These failures don't have any particular pattern, one can fail, the next it's backed up or two can fail and then the job is successful. One thing for sure: after server restart the next backup always succeeds, but restarting the server is not an option.
vssadmin list writers output says the writers state is stable with no errors.
Can someone advise on this?
Thanks in advance!
Could you give a bit more information on your environment?
Version of Backup Exec
Type of files the failing job is backing up
OS of the Media server
OS of the remote server
Backup Exec version in 13.0 rev. 5204 (64 bit).
Where can I find info about type of files failing? The only error I get in the log file is "V-79-57344-34108 - An unexpected error occurred when cleaning up snapshot volumes. Confirm that all snapped volumes are correctly resynchronized with the original volumes."
Both OSs are Windows Server 2008 R2.
Today I have a third day in a row of failed backup. Right now the job is just hanging, no bytes counting, so I'll have no other choise as to cancel the backup.
The statistics shown is as follows:
There could be orphaned snapshots. You need to go to the VM and manually delete the snapshots.
Also, try taking a snapshot from the VM. If there is an error, you would need to correct this from the VM before proceeding with another backup.
Check for any utility or maintenance jobs that could be interfering with the backups.
Try recreating one of the jobs to see if that helps
Exclude any virus scans from the Backup Exec processes
and if possible try to schedule a time to run Live Updates and then push out the RAWs out to the remote servers
Other things you can try are
1) disabling and enabling the shadow copy on the affected volume. This will get rid of previous volume snapshots.
2) increase the space allowed for shadow copy.
3) move the shadow copy to another volume
If you don't know how to do any of these, search the Web, in particular the Microsoft site.