[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: resuming backups

To: Michael Stevens <mstevens@etla.org>
Subject: Re: resuming backups
From: Johan Brinch <zerrez@gmail.com>
Date: Wed, 7 Jul 2010 16:54:10 +0100
Cc: tarsnap-users@tarsnap.com
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=oNyV1LWj8WD+qFPYlXv2SsGzQfYSl1DTjSV4TxmKbgT7XlBIefjTiBsBDN9I38OMRX shOLT7Gb9U6ptU8IM9dcEdJ0SCy6i+4V6uQmogMBrj087SaDxb1y4va6ciorLy0xElzX GfoB4iCcJRbrsrarec20nugBCwonAu+LJsWbo=
In-reply-to: <20100707124549.GA20917@eris.etla.org>
Mailing-list: contact tarsnap-users-help@tarsnap.com; run by ezmlm
References: <20100707124549.GA20917@eris.etla.org>

On Wed, Jul 7, 2010 at 13:45, Michael Stevens <mstevens@etla.org> wrote:
> Is there a sensible way to resume an incomplete backup?

--checkpoint-bytes bytespercheckpoint
             (c mode only) Create a checkpoint after every
bytespercheckpoint bytes of uploaded data.  The value
             bytespercheckpoint must be at least 1000000, and a higher
value is recommended since creating a check‐
             point in an archive can take a few seconds and several
hundred kB of bandwidth.


--
Johan Brinch

References:
- resuming backups
  - From: Michael Stevens <mstevens@etla.org>

Prev by Date: resuming backups
Next by Date: Re: resuming backups
Previous by thread: resuming backups
Next by thread: Re: resuming backups
Index(es):
- Date
- Thread