RE: dumpcycle 0 not using holding space

2002-07-25 Thread Bort, Paul

> weeks on 2 tapes. I need 2 tapes because I know at least one of the
> partitions will not fit on the tape. I intend to run amflush 

AMANDA can't split a partition across tapes, so if you're saying what I
think you're saying, and one of your partitions is bigger than one of your
tapes, you have a bigger problem than holding disk use. You'll need to split
the partition into several tar-able chunks. 




Re: dumpcycle 0 not using holding space

2002-07-25 Thread Deb Baddorf

At 02:35 PM 7/25/2002 -0400, Cory Visi wrote:
>I am running an Amanda configuration intended to do a full backup every 2
>weeks on 2 tapes. I need 2 tapes because I know at least one of the
>partitions will not fit on the tape. I intend to run amflush to get the
>last partition on the second tape. My problem is that with the current
>configuration, Amanda never leaves anything in the holding space! I have
>plenty of room, but there is never anything left there.

Look at the comments about holding disk, in the config file.
By default,  all the space is reserved for incremental backups,
and no fulls are stored on the holding disk  (once the first
tape is full,  I mean).

Here's the section:

# If amanda cannot find a tape on which to store backups, it will run
# as many backups as it can to the holding disks.  In order to save
# space for unattended backups, by default, amanda will only perform
# incremental backups in this case, i.e., it will reserve 100% of the
# holding disk space for the so-called degraded mode backups.
# However, if you specify a different value for the `reserve'
# parameter, amanda will not degrade backups if they will fit in the
# non-reserved portion of the holding disk.

reserve 30 # percent   ##  (this is MY value)
# This means save at least 30% of the holding disk space for degraded
# mode backups.

---
Deb Baddorf [EMAIL PROTECTED]  840-2289
"You can't help getting older, but you don't have to get old."
- George Burns  <






dumpcycle 0 not using holding space

2002-07-25 Thread Cory Visi

I am running an Amanda configuration intended to do a full backup every 2
weeks on 2 tapes. I need 2 tapes because I know at least one of the
partitions will not fit on the tape. I intend to run amflush to get the
last partition on the second tape. My problem is that with the current
configuration, Amanda never leaves anything in the holding space! I have
plenty of room, but there is never anything left there. The backup report
clearly states:

*** A TAPE ERROR OCCURRED: [[writing file: No space left on device]].
Some dumps may have been left in the holding disk. Run amflush to flush
them to tape.

But there is nothing in the holding disk! Can anyone help me out?

I have the following configuration for an archival backup setup:

amanda.conf:
dumpcycle 0
runspercycle 2
tapecycle 2 tapes

define dumptype comp-root-full {
comment "Root partitions with compression"
compress client fast
priority low
record no
index yes
}

define dumptype comp-user-full {
global
comment "Non-root partitions on reasonably fast machines"
compress client fast
priority medium
record no
index yes
}


disklist:
server02.ctsda1  comp-root-full   1
server02.ctsda2  comp-user-full   1
server02.ctsdb1  comp-user-full   2

Thank you,
Cory Visi