Radu Filip <[EMAIL PROTECTED]> writes:

> Hello, Johanness!
> 
> Thank you very much for your answer.
> 
> On 27 Feb 2001, Johannes Niess wrote:
> 
> > 1) Amanda sets options for gnutar to stop at partition boundaries.
> 
> >From the logs I see that it's not this one...
> 
> > 2) If your holding disk is on the same partition as /, Amanda tries to
> > backup the holding disk. Its a vicious circle.
> 
> holdingdisk hd1 {
>     comment "main holding disk"
>     directory "/tmp"
>     use -150 Mb
>     chunksize -1
>     }
> 
> [root@server2 DailySet1]# mount
> /dev/sda1 on / type ext2 (rw)
> none on /proc type proc (rw)
> /dev/sda6 on /tmp type ext2 (rw)
> /dev/sda5 on /var type ext2 (rw)
> none on /dev/pts type devpts (rw,gid=5,mode=620)
> 
> > I'd recomment to include your holding disk directory into the
> exclude > list. My setup uses the /tmp partition as holding disk,
> which is not > backed up.
> 
> Like I wrote into the holding disk? It is correct?

That's ok. I recommend to set chunksize to 1.9 GB, a positive value to
"use", and a fair percentage for reserve (to allow level 0's while in
degraded mode). But it depends on your situation.

>
> But if I write exludce list /tmp" in define dumptype root-tar I
> get the error: (/ disk offilne).
> 
> Now, then I tryed again I get another strange error. Aay ideea?

[...]

> FAILED AND STRANGE DUMP DETAILS:
> 
> /-- server2 / lev 0 STRANGE
> sendbackup: start [server2:/ level 0]
> sendbackup: info BACKUP=/bin/tar
> sendbackup: info RECOVER_CMD=/bin/tar -f... -
> sendbackup: info end
> ? gtar: ./dev/log: socket ignored
> | Total bytes written: 353484800 (337MB, 2.8MB/s)
> sendbackup: size 345200
> sendbackup: end
> \--------

The "socket ignored" looks ok to me. You can double check 337MB vs. df
/ .

> (brought to you by Amanda version 2.4.1p1)

The current version is 2.4.2(p1?)

Reply via email to