Amanda-Users

Re: Interpreting Logs & GNUTAR

2005-06-27 16:32:53
Subject: Re: Interpreting Logs & GNUTAR
From: Joshua Baker-LePain <jlb17 AT duke DOT edu>
To: Graeme Humphries <graeme.humphries AT vcom DOT com>
Date: Mon, 27 Jun 2005 16:16:20 -0400 (EDT)
On Mon, 27 Jun 2005 at 1:37pm, Graeme Humphries wrote

> I'm just getting my first Amanda setup working, and I've got a couple of
> questions. First, is there documentation that tells how to interpret log
> entries like the following?
> 
> SUCCESS dumper filename /files/share1 20050627 0 [sec 326.117 kb 550813
> kps 1689.0 orig-kb 1843300]
> SUCCESS taper fileserver /files/share1 20050627 0 [sec 34.484 kb 550814
> kps 15972.6 {wr: writers 17214 rdwait 0.383 wrwait 29.156 filemark
> 2.233}]
> 
> That directory *should* contain 1.8 GB of files to backup, so I'm unsure

And that's how much amanda backed up -- "orig-kb 1843300".  It took 
326.117 seconds, the compressed size of the backup was 550813 kb, and the 
dump rate was 1689 kb/s.

> what I'm missing. However, I have a suspicion, and it ties into my next
> question: how do you control dump levels when using GNUTAR?

You don't -- amanda does.

> I want to have individual directories in my disklist (ie, not individual
> partitions, but subdirectories of those partitions), and dump just
> chokes on this. I've switched to using GNUTAR, but I'm unsure how to
> control when a full backup is done and when an incremental-style dump
> level is done, or how it really works out when using GNUTAR.

Amanda manipulates tar to work just like dump.  And with both, amanda 
schedules level 0s or level 1s (and, if necessary, level 2s, level 3s, 
etc) according to dumpcycle and runspercycle.

-- 
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University

<Prev in Thread] Current Thread [Next in Thread>