revjim.net

Imagine for a moment, if you will, the following scenario. A series of events, that, one by one and only in a particular order, add up to headache and destruction.

Imagine if every night all of the files from one directory are copied to a directory on a remote server using a piece of software that you paid for designed to perform exactly that function. Now imagine if the remote disk was full and you didn't know it. Imagine also if the backup software you're using is too stupid to realize that it's full. Now, imagine if that same stupid backup software decides that it should mark that file as copied despite the fact that the file didn't successfully copy. Now imagine if the next day when the backup runs again and notices the previously copied (but not really) file is no longer in the remote folder and, therefore, believes the file has been deleted and, therefore, deletes it from the source folder.

To boil it all down, essentially, what is happening is that, with a backup running nightly, every file you edit, move, or create (i.e. the new, and therefore most likely most important, stuff) will be deleted two days after editing it.

Now, imagine the directory you're bothering to back up happens to be your directory full of photographs.

Yeah.

I still don't know the full extent of what is missing.

I'm heartbroken.

(And whatever you do, for the love of God, don't use SyncBackSE.)