Reclam job fails. Error -2241

[fgl]

Ok another new problem for VDR. Over the weekend for the first time the reclaiming job failed with a error -2241 (destination index invalid/damaged). The recatalog job is now taking like 100 times longer than before. The integrity job was running for 49 hours and was still at 1% before I got fed up and force reboot the VDR appliance and now it just starts all over again with the same problem with the reclaim, recatalog, and integrity job. It looks like I may have to start from scratch AGAIN with new datastore, new vdr, etc... What a waste of 4 months worth of backups. In case I don't ever reply again it's because I either got fired or I commited sucide.

[TedCrilly]

I have had similar issue resolved by treating it as a linux disk problem, i.e running fsck on the volume and resolving any filesystem level problems before trying to resolve database level ones (treating the VDR store as a database). Worth a shot instead of losing work. Also, try keeping a backup of the Store on an external drive or something every few weeks.

[admin]

fgl, is your backup destination a CIFS share or VMDK? If it's CIFS, make you have a clean, fast path from the VDR host to whatever is hosting your destination share. It's possible if you're having transient network problems, VDR may think the destination is partially damaged even though it was a network error that caused it not to be able to read the data. If it's a VMDK, is it a locally attached disk? SAN? NFS?