FULL on TAPE DEVICE, INCR on FILE

[Samuel]

Hi everybody,

I was wondering wether it is possible to have two orgs :

- one "weekly" which would be making full backups on tape using
dumptype "full-always"
- the other one incremental dumping on file using the file-driver and
a "incr-always" dumptype like for instance :

(...)
org "daily"
dumpcycle 1 weeks
runspercycle 5
tapecycle 20 tapes
tpchanger "chg-disk"
changerfile "/etc/amanda/daily/changer"
tapedev "file:/amandatapes/daily
tapetype HD
(...)
define tapetype HD {
comment "Dump onto hard drive"
length 1024 mbytes
}
define dumptype always-incr {
comment "Incremental dump always"
strategy nofull # (or may be incronly)
options compress-best, index
priority medium
}

The idea beyond this is to incremental dump on a reliable disk
starting from the "weekly" full dump... That'd be great since i don't
wanna spend time changing tapes as we do not have a tape changer in
our small organisation. Besides, the /amandatapes directory would be
full backed-up.

I have actually tried with the incronly strategy, but it complains:

These dumps were to tape daily1.
The next tape Amanda expects to use is: a new tape.
The next new tape already labelled is: daily2.

FAILURE AND STRANGE DUMP SUMMARY:
manosque sdb3 lev 0 FAILED [dump larger than tape, -1 KB, but
cannot incremental dump new disk]
manosque sda3 lev 0 FAILED [dump larger than tape, -1 KB, but
cannot incremental dump new disk]
manosque sdb1 lev 0 FAILED [dump larger than tape, -1 KB, but
cannot incremental dump new disk]
planner: FATAL cannot fit anything on tape, bailing out

Could someone give me a hint ?

Cheers,

Sam

[Samuel]

Here is a working config (only relevant informations):

-------------------------------------------------------------
# FULLS ON TAPE
org "weekly" # your organization name for reports
mailto "operator" # space separated list of operators at your
site
dumpuser "backup" # the user to run dumps under
(...)
dumpcycle 0 # the number of days in the normal dump cycle
(temps maximum entre 2 fulls)
runspercycle 1 # the number of amdump runs in dumpcycle days
tapecycle 9 tapes # the number of tapes in rotation
(...)
define dumptype always-full {
comment "Full dump of this filesystem always"
options compress-best
index
priority high
dumpcycle 0
maxcycle 0
}

-----------------------------------------------------------
# INCR on DISK
org "daily" # your organization name for reports
mailto "operator" # space separated list of operators at your
site
dumpuser "backup" # the user to run dumps under
(...)
dumpcycle 1 weeks # the number of days in the normal dump cycle
(temps maximum entre 2 fulls)
runspercycle 5 # the number of amdump runs in dumpcycle days
tapecycle 20 tapes # the number of tapes in rotation
(...)
tpchanger "chg-disk" # the tape-changer glue script, see TAPE.CHANGERS
changerfile "/etc/amanda/daily/changer"
tapedev "file:/amandatapes/daily" # Linux @ tuck, important:
norewinding

(...)
define tapetype HD {
comment "Dump onto hard drive"

length 3072 mbytes
}
(...)

define dumptype always-incr {
comment "Incremental dump always"
strategy nofull

options compress-best, index
priority medium
}

------------------------------------------------

Check http://www.oops.co.at/AMANDA-docs/howto-filedriver.html for
setting up virtual tapes.

Cheers,

Samuel