Amanda 3.3.4
Hi,
Seems like I'm having trouble getting amanda to use my holding disk.
Here's my setup in amanda.conf:
define holdingdisk holdingdisk1 {
directory "/mnt/amanda-holdingdisk1/"
use 4500Gb
chunksize 100Gb
}
define dumptype gui-base {
global
program "GNUTAR"
I don't believe amanda attempts to write to the holding disk.
Who owns it?
On Thu, Feb 27, 2014 at 03:09:20PM -0500, Michael Stauffer wrote:
> Amanda 3.3.4
>
> Hi,
>
> Seems like I'm having trouble getting amanda to use my holding disk.
>
> Here's my setup in amanda.conf:
>
> define holdingd
* Michael Stauffer [20140227 15:10]:
> Amanda 3.3.4
>
> Hi,
>
> Seems like I'm having trouble getting amanda to use my holding disk.
>
> Here's my setup in amanda.conf:
>
> define holdingdisk holdingdisk1 {
> directory "/mnt/amanda-holdingdisk1/"
> use 4500Gb
> chunksize 100Gb
> }
Ah,
Michael,
You define the holdingdisk but you don't tell amanda to use it.
Add:
holdingdisk "holdingdisk1"
after the define
Jean-Louis
On 02/27/2014 03:09 PM, Michael Stauffer wrote:
Amanda 3.3.4
Hi,
Seems like I'm having trouble getting amanda to use my holding disk.
Here's my setup in am
On Thu, Feb 27, 2014 at 03:09:20PM -0500, Michael Stauffer wrote:
> Amanda 3.3.4
>
> Hi,
>
> Seems like I'm having trouble getting amanda to use my holding disk.
>
> Here's my setup in amanda.conf:
>
> define holdingdisk holdingdisk1 {
> directory "/mnt/amanda-holdingdisk1/"
> use 4500Gb
>
My config merely has
holdingdisk hd1 { yada yada yada
}
Does it work because I didn't DEFINE it but merely declared it to be?
Just wondering. It works fine…. I've left the param in the dump type out,
so I guess I'm getting the "auto" for yes, do use it.
Deb
On Feb 27, 2014, at
Great, thanks - that's the trick. I figured it was something like this but
FWIW, this isn't in the amanda.conf docs.
-M
On Thu, Feb 27, 2014 at 3:21 PM, Jean-Louis Martineau
wrote:
> Michael,
>
> You define the holdingdisk but you don't tell amanda to use it.
>
> Add:
> holdingdisk "holdingdi
Yes, it's 4.5TB.
I's not clear to me from the docs whether a level 0 dump gets written fully
to holding disk before it gets streamed to tape, or if streaming starts
once one or more chunks have been written to the holding disk - anyone
know? I'd prefer the latter for performance reasons. If the fo
I believe the whole dump has to be done before it starts to write to tape.
This prevents incomplete dumps from wasting space on the tape.
I try to have numerous smaller DLEs, so that it takes several DLEs to fill a
tape. Thus, when any one of them is finished, it can start going
to tape. If
I see, I think then that's why there's a separate disk cache option
(tapetype:part-cache-type)?
So if have a very large DLE and I use disk for cache, it will spool chunks
to disk and starting streaming to tape before the whole DLE is written to
disk? I want to avoid memory cache since I'd end up wi
On Thu, Feb 27, 2014 at 04:44:13PM -0500, Michael Stauffer wrote:
> Yes, it's 4.5TB.
>
> I's not clear to me from the docs whether a level 0 dump gets written fully
> to holding disk before it gets streamed to tape, or if streaming starts
> once one or more chunks have been written to the holding
On 02/27/2014 05:54 PM, Michael Stauffer wrote:
I see, I think then that's why there's a separate disk cache option
(tapetype:part-cache-type)?
So if have a very large DLE and I use disk for cache, it will spool
chunks to disk and starting streaming to tape before the whole DLE is
written to di
On Thu, Feb 27, 2014 at 10:20:29PM +, Debra S Baddorf wrote:
> I believe the whole dump has to be done before it starts to write to tape.
> This prevents incomplete dumps from wasting space on the tape.
>
> I try to have numerous smaller DLEs, so that it takes several DLEs to fill a
> tape
13 matches
Mail list logo
