Yeah, the "staging drive" was what I was now
testing. But then I need something "restartable" to copy the backup to an
offsite location. Besides rsync, what can you think of that can simply
perform a directory sync?
The problem with the backup-partitioning is that it
would be very easy to start missing files and directories as they're created,
unless we can come-up with some creative scripting with the
--include/exclude's. If I explicitly define the dirs under the root of our
main "share", then if someone creates a new directory at the root, it'll never
get backed-up.
Can I use the regexp's to define which of the
top-level dirs to include (and then include ALL files and folders recursively
beneath those)? In other words, only use the include/exclude regexp to
determine the top-level, and NOT to filter anything else? If so, this
could be a way forward...just do alphabetical ranges of folders and then one to
do any files (not folders) resting directly at the root.
-AJ
----- Original Message -----
Sent: Tuesday, March 11, 2008 12:54
PM
Subject: Re: [Duplicity-talk] ftp and
short filenames prob
Sorry, duplicity is not your solution, for
now. It does retry on error
and will recover from most errors, but it
does not have a restart
capability. That's going to take some
redesign.
Your best bet if you want to use duplicity is to
partition the backup
into multiple directory trees so that if you have to
restart, you only
lose the time for the portion in that tree.
Drives are cheap enough now that using a drive to
stage your backup is
quite reasonable and offers advantages over slow
off-site backup since
you have a local copy for quick restore. You
can then rsync that drive
to the remote site.
...Ken