Not quite.Atomic wrote:Warrl -- that has me a bit concerned. If I'm understanding the method properly, the method archives the directory and presumes the target files still exist.
The method copies the directory, and compares the target file to the version of the target file that exists *in the previous backup*. If there is no previous backup, or if the file is new or altered, then it copies the file as well. Otherwise, the directory entry in the new backup will point at the same file as the previous backup.
Inherent in properly supporting multiple directory entries for a single file, the file remains for as long as there is at least one directory entry pointing at it. So deleting a file from one backup doesn't break other backups that point at it.If those files go away, then what?
If a file no longer exists in the source area, no further backups of it occur. However the old ones remain unless the directory entries pointing at them are deleted.
It certainly should be. Although I've had to restore files due to user or operator error VASTLY more often than due to failed hardware.Is the backup on another drive than the original?