On Sun, Feb 14, 2010 at 01:39:23PM -0800, Craig Barratt wrote:
> If you want to try the two fixes, here's a patch against 3.2.0beta1
> (note: I haven't tested this yet - just did this sitting on a plane).
>
> Craig
>
> --- bin/BackupPC_dump 2010-01-24 17:30:43.0 -0800
> +++ bin/BackupPC_d
John writes:
> The reason for the current layout is to allow the existing critical
> backups to complete even if it takes days to backup the newer shares
> (filesystems). So it's a temporary thing, but I could see somebody
> wanting to put /home first to prioritize it's backup over say /.
> Is the
On Fri, Feb 12, 2010 at 01:44:56PM -0800, Craig Barratt wrote:
> John writes:
>
> > 2010-02-12 18:34:33 unexpected repeated share name / skipped
>
> It's a bug (also reported by Tim Connors) that I meant to fix
> in 3.2.0beta1 but somehow overlooked.
>
> As a workaround, try putting "/" first in
John writes:
> 2010-02-12 18:34:33 unexpected repeated share name / skipped
It's a bug (also reported by Tim Connors) that I meant to fix
in 3.2.0beta1 but somehow overlooked.
As a workaround, try putting "/" first in the list.
Craig
--
Hi all. I am backing up a system with the following pc/host.pl file:
$Conf{RsyncShareName} = [
'/etc',
'/var/bak',
'/var/log',
'/usr/local',
'/home/opssvn/backups',
'/home/svn/backups',
'/',
'/usr',
'/home',
'/var',
'/boot',
];
and here is what the backup log looks like:
2010-02-12
