|Subject:||Re: [rdiff-backup-users] rdiff-backup limit time range|
|Date:||Thu, 15 Aug 2013 13:59:42 -0400|
You could write a wrapper shell script around rdiff-backup like this to start it:#!/bin/bashif [ -n pidof rdiff-backup ] ; thenkill -CONT $(pidof rdiff-backup)elserdiff-backupfiand then at 6 AM run a cron job with a script like this:#!/bin/bashif [ -n pidof rdiff-backup ] ; thenkill -STOP $(pidof rdiff-backup)fiThe first script sees if rdiff-backup is running, and if it is, it uses kill to unpause it (if if is already unpaused, this has no effect/error), otherwise it just fires up rdiff-backup. The second script just sees if rdiff-backup is running, and if so, pauses it.John WesorickIT Systems Engineer | Riders Discount866.931.6644 x852 | www.RidersDiscount.comOn Thu, Aug 15, 2013 at 1:17 PM, Greg Troxel <address@hidden> wrote:Eric Gendron <address@hidden> writes:Limit the area being backed up.
> So how to limit backup working time ?
rdiff-backup can't do this.
> Or how to interrupt a working backup that will continue next night?
rsync the entire remote system to shadow tree, incrementally when you
can, and run rdiff-backup locally
go learn about bup (not obviously ok to use right now, but I find it
rdiff-backup-users mailing list at address@hidden
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
|[Prev in Thread]||Current Thread||[Next in Thread]|