Amanda-Users

Re: Can someone explain to me what no-hold in amstatus means ?

2005-09-14 13:52:10
Subject: Re: Can someone explain to me what no-hold in amstatus means ?
From: Guy Dallaire <clepeterd AT gmail DOT com>
To: amanda-users AT amanda DOT org
Date: Wed, 14 Sep 2005 12:50:20 -0400
2005/9/14, Jon LaBadie <jon AT jgcomp DOT com>:
> 
> Just the dump space.  Backup the config dir and other associated dirs.
> Some would actually reflect the previous run as they are not complete
> until the end of the dump.
> 
> > If I lose the index data, it means I will no longer be able to use
> > amrecover right ?
> 
> Correct, though amrestore or manual recovery will still work.
> 

I've just realized that maybe my understanding of the holding disk
concept was not adequate. It looks like IDEALLY, the holding disk(s)
devices should be used/dedicated specifically for that purpose only.

In my case, the holding disk was used as the holding disk, as well as
a place for amanda db, logs and indexes. The disk was probably VERY
HEAVILY STAMPED ON so that might explain the no-hold problem.

What I did, is that I moved the idx, log and db directories to
/usr/local/var/amanda (as explained in the sample config file section
that I probably failed to read correctly or skipped over) and left
ONLY the holding disk directory on the physical disk. This should
speed up things considerably.

Again, thanks again for your time

P.S.: I'll leave the holding disk device OUT of the disklists as I
don't think it need to be backed up if it only contains the amanda
dumps. Right ?