Thanks pkh and Colin, I've been using BE for 12 years, but since I don't often actually configure backups, I forget some of the niceties when I have to get back to it. Thanks for the refresh.
My questions center around my desire to make my offsite syncing feasible. I think, again, I was getting myself tied in knots since I only configure backups every three years or so. But after a good night's sleep, I think I have most of the cobwebs cleared. I was mistakenly thinking that the differential/incremental would actually overwrite the particular files affected in the full backup, which of course is preposterous, but I was getting a little bleary by that time. Obviously, a full with differentials will be my best DR setup.
The consideration, though, is with the syncing over a WAN connection. My full backup is 2.4 TB. Syncing that over even a 20MB link is not really feasible on a regular basis. I understand, Colin, your cautioning about depending upon a single base full backup, which had entered my mind. The problem, however, is that doing a new full backup creates backup files with new timestamps, even though many of the files may not have changed. So evry time I do a new full backup, I have to sync that full 2.4 TB. I was trying to avoid that, as it really isn't feasible. The reality is, I probably have way too many unchanging files that are in my "production" backup, that really should exist only in an archive. I would guess that maybe only 20% ofmy full backup is actually changing, at best. Any thoughts?
As far as archive vs modified time, were you referring to the actual backup time in saying that modified time is faster? What happens to the archive bit, then? Or does it just become irrelevant?
