Amanda-Users

Re: Always-full and incrementals

2003-11-05 10:52:06
Subject: Re: Always-full and incrementals
From: Joshua Baker-LePain <jlb17 AT duke DOT edu>
To: Stephen Carville <carville AT cpl DOT net>
Date: Wed, 5 Nov 2003 10:48:44 -0500 (EST)
On Wed, 5 Nov 2003 at 7:07am, Stephen Carville wrote

> I have the following dumptype defined:
> 
> define dumptype global {
>     comment "Global definitions"
>     index yes
> }
> 
> define dumptype always-full {
>     global
>     comment "Full dump of this filesystem always"
>     program "GNUTAR"
>     compress none
>     priority high
>     dumpcycle 0
> }
> 
> Then in the disklist I have entries like:
> 
> chena /db/nt-backups/bering {
>         always-full
>         exclude "Changer.cfg"
> }
> 
> However, lately I keep seeing entries like this in the emails:
> 
> chena:/db/nt-backups/bering      1 [dumps way too big, must skip incremental 
> dumps]
> 
> Now, if I am requesting always full, I should never see an incremental. 
> Right?  

Not exactly.  If amanda does the estimates for all your level 0s and it's 
> tapelength, then it will start demoting dumps so that every DLE at least 
gets an incremental.  If you *never* want it to do an incremental, even in 
this case, you can specify 'skip-incr' in the dumptype.

> Secondly what does the message mean?  The file sizes are no larger than 
> usual.  The particuar one above is only about 5.3G.  Also, the amuont of data 
> written to tape is consistent with the backup being done sucessfully.

It means that the sum of all the level 0s is greater than tapelength.  
Look in the amdump.N file for all the gory details.

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


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