Re: Tolerating network errors

[Colin Percival <cperciva@tarsnap.com>]

Hi Luke (& list),

Sorry about that -- you probably ran into the 12 minute outage I posted
about earlier this morning.  The good news is that if you were running
with the default configuration options, you should have a checkpoint of
your archive.

The 'Callbacks uninitialized' is a bug in tarsnap 1.0.35 which is triggered
when tarsnap is unable to communicate with the server; it will be fixed in
the next release but if you try again now you shouldn't see that any more.

Please run `tarsnap --recover`, which will attempt to recover a checkpoint
from the archive which was interrupted (this is also done automatically if
you create or delete another archive), then run `tarsnap --list-archives`
again; you should now see an "archivename.part" archive in the listings.

You won't be able to *resume* an archive (once created, an archive cannot
be modified except by deleting it) but you can create a new archive and it
will be deduplicated against any data you have previously stored.  So just
create a new archive with a new name.

Colin Percival

On 04/06/14 06:28, Luke Plant wrote:
> While doing my first real backup, which included 40Gb of data, I
> eventually saw this error:
> 
> tarsnap: Connection lost, waiting 30 seconds before reconnecting
> tarsnap: Connection lost, waiting 60 seconds before reconnecting
> tarsnap: Connection lost, waiting 90 seconds before reconnecting
> tarsnap: Connection lost, waiting 90 seconds before reconnecting
> tarsnap: Too many network failures
> tarsnap: Error storing chunk
> 39304ac482fc548c57492120287fd20831557dfd32049b4f37c38a8834b63374
> tarsnap: Error in chunk storage layer
> tarsnap: Error writing archive
> 
> I'm trying to work out how to resume the backup, if that's possible. I'm
> doing this to backup a computer over a broadband connection, so internet
> connection is not always reliable, and it is always slow, and I need to
> be able to tolerate more network errors.
> 
> Further, when I try to "--list-archives" to see if that gives any more
> details, I just get this error message:
> 
> $ tarsnap --list-archives
> tarsnap: Callbacks uninitialized
> tarsnap: Callbacks uninitialized
> tarsnap: Error listing archives
> 
> Any guidance would be appreciated - even if it is "tarsnap is not
> appropriate for your use case".
> 
> Thanks,
> 
> Luke
> 


-- 
Colin Percival
Security Officer Emeritus, FreeBSD | The power to serve
Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid