Some time ago I decided to it would be smart to set up a mirror of my archive disk rather than include it in my regular backups. It wasn't :-(. When the archive disk became corrupt synctoy dutifully duplicated the corruption onto the mirrored disk. At least I think that is what happened. Bottom line - both the archive disk and its mirror are corrupt.
In an attempt to recover at least some of the archived Vegas projects I purchased Wondershare but I'm not having much luck with it. I can "recover" some VEG's, MTS's, JPG's, etc. but when I attempt to open them their respective application reports them as corrupt. For a few of the corrupt files I have a good copy stored elsewhere. When I compare the corrupt to the good copy they both have the same number of bytes and date, but when I open them in a hex editor the internals are different.
I am at a loss as to what caused the corruption. The three other HD's in that PC are ok so I doubt it was any type of malware. At this point I'm not very hopeful of recovering these archives, but am posting this just in case there is something I'm not considering here.
More importantly, how do I guard against this going forward? My archive workflow is that I accumulate archived projects on a removable HD. When it is filled I remove it and replace it with a new HD. I suppose I could set up a differential backup of the archive HD, and then blow it away when its archive HD is removed. Question: would a differential backup detect a file change even though the date and size of the file has remained the same (as happened with my corrupted files)? What would you do to guard against data loss while the archive HD is in the system?
/jerry
In an attempt to recover at least some of the archived Vegas projects I purchased Wondershare but I'm not having much luck with it. I can "recover" some VEG's, MTS's, JPG's, etc. but when I attempt to open them their respective application reports them as corrupt. For a few of the corrupt files I have a good copy stored elsewhere. When I compare the corrupt to the good copy they both have the same number of bytes and date, but when I open them in a hex editor the internals are different.
I am at a loss as to what caused the corruption. The three other HD's in that PC are ok so I doubt it was any type of malware. At this point I'm not very hopeful of recovering these archives, but am posting this just in case there is something I'm not considering here.
More importantly, how do I guard against this going forward? My archive workflow is that I accumulate archived projects on a removable HD. When it is filled I remove it and replace it with a new HD. I suppose I could set up a differential backup of the archive HD, and then blow it away when its archive HD is removed. Question: would a differential backup detect a file change even though the date and size of the file has remained the same (as happened with my corrupted files)? What would you do to guard against data loss while the archive HD is in the system?
/jerry