best method to debug problems with amdump runs?

I'm wondering if there are any additional debugging features that could be used to delve more into why the nightly amdump runs cannot do their thing and instead report network errors. amcheck has just run from cron a short while ago and reported no errors. Could there be something in the aman

Re: incremental with gnutar bogusly dumping old files

On Wed, Sep 26, 2007 at 06:57:11PM -0600, John Hein wrote: > The other night, a number of incremental dumps included a lot of files that > should not have been dumped. > > As a result, I got a number of 'dumps way too big' failure messages > causing a number of DLEs to not get dumped since the pla

Re: incremental with gnutar bogusly dumping old files

Just a guess -- is this a Linux machine that recently had hardware added/removed? If so, the device numbers may have changed for that partition, leading tar to think that all files have been changed. Gene Heskett chased down such a bug several months ago. Other than that, I can't see how this wo

incremental with gnutar bogusly dumping old files

The other night, a number of incremental dumps included a lot of files that should not have been dumped. As a result, I got a number of 'dumps way too big' failure messages causing a number of DLEs to not get dumped since the planner decided there was no room. For example, I have a old file, foo,

Re: amfetchdump inventory mode

On Wed, Sep 26, 2007 at 04:26:50PM -0400, Jean-Francois Malouin wrote: > > One of the most important feature of amanda was (it still is but read > on) the possibility of doing a bare-metal restore with just a few > utilities. I say was because in my case the ever increasing amount of > data, the s

Re: amfetchdump inventory mode

Jean-Francois Malouin wrote: * Ian Turner <[EMAIL PROTECTED]> [20070926 15:37]: On Wednesday 26 September 2007 14:57:58 Jean-Francois Malouin wrote: I'm trying to understand how 'amfetchdump -i' works (amanda-2.5.2p1): At the moment, not all tha

Re: amfetchdump inventory mode

* Ian Turner <[EMAIL PROTECTED]> [20070926 15:37]: > On Wednesday 26 September 2007 14:57:58 Jean-Francois Malouin wrote: > > I'm trying to understand how 'amfetchdump -i' works (amanda-2.5.2p1): > > At the moment, not all that well. :-( In theory, amfetc

amfetchdump inventory mode

Hi, I'm trying to understand how 'amfetchdump -i' works (amanda-2.5.2p1): gertrude:$ /opt/amanda/sbin/amfetchdump -i - left2 Doing inventory/search, dumps will not be uncompressed or assembled on-the-fly. Beginning tape-by-tape search. Scanning av24-2_left2_U00015L3 (slot 6) amfetchdump: Search

amcrypt vs. autoflush

Hello... RHEL5 x86_64 , amanda 2.5.2p1 I am using 'server_encrypt "/usr/sbin/amcrypt-ossl-asym" ' I can do backups. I can flush to tape. If I add 'autoflush yes' to amanda.conf backups fail. Is anyone else seeing this? from a taper...debug file: ( I think there should be more entries

Re: gtar still running after amdump was done

I am running amanda 2.5.2p1 with "-o tpchanger= -o tapedev=" options, my holding disk is 100GB. The server/client is on the same computer. After amdump finished, I found there are still two "gtar" running. I checked amanda log file, it says "... FAIL driver [host] [disk1] [date] 0 [no more hold

Re: gtar still running after amdump was done

On 2007-09-25 17:02, Jean-Francois Malouin wrote: * Yu Chen <[EMAIL PROTECTED]> [20070925 10:13]: Hi, I am running amanda 2.5.2p1 with "-o tpchanger= -o tapedev=" options, my holding disk is 100GB. The server/client is on the same computer. After amdump finished, I found there are still two "