Skip to main content

backup/validation/corruption?

Thread needs solution

I use home edition 2011. Recently it started having problems. This is under Windows 7/ultimate. Most of my work is on the C: drive, I have a D: drive and two external USB drives, G: and H: I back up full copies of my C: drive to G: nightly and to my D: drive and to my H: drive on a weekly basis. Previously, all was working perfectly. Now I find that if I do a validation on my G: drive as part of the backup process that it shows the backup is corrupted. If I simply do a backup and when it is completed then do a validation, there is no problem. When I run a backup on the D: and/or the H: drive if I do a validation as part of the backup operation, there is no problem; only on the G: drive and only if the validation is part of the backup process. I have reformatted the G: drive and it makes no difference. Anybody have an idea of what is going on or a suggestions?

Thank you.

Ross

0 Users found this helpful

Ross,
I have been watching your post but no responses which shows its uniqueness for the issue.

Maybe a little info would help.
Laptop or desktop?
How usb connected? hub or direct to computer. If desktop, try using rear connectors
Is a network involved with the backups?
Does the problem backup have its own backup task?
Does each of your backups have their own tasks?

Generally speaking, these are the rules I follow.
1. Target disk assigned it own unique individual drive letter such as either x or yo or z. This prevents interference by the insertion of a camera or flash drive, printer, etc.
2. Each backup has its own task and each task points to its own empty storage folder or sub-folder off one backup folder. NO mixing of backups files from other tasks.
3. usb cable plugged direct into computer or at test if a hub can be used without issues.
4. Occasional checking for disk and file errors on both the source and target.
5. No editing of any kind to the backup task. Set it once and and leave it alone. If correction needed, create a new task pointing to a new folder.
6. Use backup scheme of custom/diff. Do 6 dif and keep x number of chains (your choice of number of dif or inc and chains.)

I follow each item of your advice except for the last: I am making a full backup of my C: drive onto my G: (external USB drive), my J: (external USB drive) and my D: drive (internal IDE drive). Only the backup to the G: drive is problematic. Yet the problem does not appear if I let the backup a complete and then run a manual validation (although it does not show "completed and validated" as it does for the other two backups – is merely shows "completed")

As for the uniqueness of my problem: I always prided myself on being unique! :-)