pitchford
asked on
Backup to Disk to Tape
All, we've been suffering from the following error message on some of our duplicate to tape jobs. Our backups are configured to backup to disk (on a Data Domain device) then archive to tape every day. We have about 15 jobs that backup to disk to tape and only 5 failed last night. It seems to always fail on the same duplicate jobs; the back to disk is successful. The backup to tape writes some data to tape before failing; for example one B2D job is 178 GB however the duplicate job failed after just 73 GB. Error code E0000602. I also have one job that failed with E0009444 and one that failed with E00084D4.
Backup Exec 2010 R3 fully patched running on Windows 2008 R2 Standard with 12 GB RAM.
Job ended: Tuesday, October 18, 2011 at 3:19:51 AM
Completed status: Failed
Final error: 0xe0000602 - A query for media on which the data set being read is continued was unsuccessful. Ensure that all media in the family have been inventoried and cataloged.
Final error category: Backup Media Errors
For additional information regarding this error refer to link V-79-57344-1538
Errors
Click an error below to locate it in the job log
DuplicateThe query for media sequence number 79 of this media family was unsuccessful.
Ensure that all media in the family have been inventoried and cataloged.
V-79-57344-65072 - The connection to target system has been lost. Backup set canceled.
Thank you!
Backup Exec 2010 R3 fully patched running on Windows 2008 R2 Standard with 12 GB RAM.
Job ended: Tuesday, October 18, 2011 at 3:19:51 AM
Completed status: Failed
Final error: 0xe0000602 - A query for media on which the data set being read is continued was unsuccessful. Ensure that all media in the family have been inventoried and cataloged.
Final error category: Backup Media Errors
For additional information regarding this error refer to link V-79-57344-1538
Errors
Click an error below to locate it in the job log
DuplicateThe query for media sequence number 79 of this media family was unsuccessful.
Ensure that all media in the family have been inventoried and cataloged.
V-79-57344-65072 - The connection to target system has been lost. Backup set canceled.
Thank you!
What's the data retention policy on the disk staging media set, if it's too short then you may overwrite the media before you do the duplicate job.
Have you checked all the system logs on both source and target machines, and also the network error counters?
ASKER
Retention is 2 weeks on our daily which is what we're working with here.
There are no known errors. Everything appears clean. The B2D routine is successful, just the dupe failed.
Thanks
There are no known errors. Everything appears clean. The B2D routine is successful, just the dupe failed.
Thanks
ASKER
I don't think this has anything to do with it, but this is the only error I've seen and I wouldn't suspect this as causing the error (but I figured I'd supply the information).
Our Data Domain is configured with 2 copper NICs in a round-robin. The switch is reporting port flapping for the Data Domain.
Our Data Domain is configured with 2 copper NICs in a round-robin. The switch is reporting port flapping for the Data Domain.
That could absolutely be causing the problem... backup applications have a rather limited period that they'll retry jobs after an error condition. After that, it's job over, and you have to restart the job from the beginning.
I'd figure out why you've got NIC problems... maybe just a cable swap will clear it up? Or perhaps changing ports on your switch? If not, can you change the NIC setup so they are independent, and see if this problem goes away?
I'd figure out why you've got NIC problems... maybe just a cable swap will clear it up? Or perhaps changing ports on your switch? If not, can you change the NIC setup so they are independent, and see if this problem goes away?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Issue is a bug reported by Symantec.
Just noticed the Smantec article mentions policy based jobs, gave up on those and started manualy created jobs instead a while back. Not so elegant but much more reliable.