On Sat, 24 Feb 2007 00:18:32 -0800
Craig Barratt wrote:
> David writes:
>
> > However, tonight I decided to decrease the max number of backups
> > saved and got the following messages:
> >
> >Error: No save due to errors
> >Error: SplitPath must be a valid executable path
>
> $Conf{Spli
On 24/02/07, Jason B <[EMAIL PROTECTED]> wrote:
> Incidentally, unrelated, but something that's been bugging me for a while:
> subsequent full backups hardlink to older ones that have the true copy of the
> file, correct? That means there is no meaningful way of deleting an older
> backup, as the p
Jason B wrote:
>> 3.) Rsync(d) full backups go to more trouble to determine what has changed,
>> meaning they're more expensive in terms of CPU time and disk I/O, but
>> they'll catch changes incrementals may have missed. That means they're
>> vital every now and then, supposing you wa
Jason B wrote:
> close to
> the same way as an incremental, except it's more useful, so to say?
>
> Incidentally, unrelated, but something that's been bugging me for a while:
> subsequent full backups hardlink to older ones that have the true copy of the
> file, correct? That means there is no
Hiya,
> Jason Hughes explained how to incrementally transfer such a structure using
> $Conf{BackupFilesExclude}. The important thing is that you need successful
Well, I'm glad to say the $Conf{BackupFilesExclude} method worked fine. I had
to do it quite a few times (did about 10GB at a time), so
David writes:
> However, tonight I decided to decrease the max number of backups saved
> and got the following messages:
>
>Error: No save due to errors
>Error: SplitPath must be a valid executable path
$Conf{SplitPath} doesn't point to a valid executable. That's
used for archive.
Go t
