On Sat, Oct 9, 2010 at 4:02 PM, Gunnarsson, Gunnar
wrote:
> Sat Oct 9 22:23:08 2010: amgtar: Spawning "/usr/local/bin/tar
> /usr/local/bin/tar --create --verbose --file - --directory /
> --one-file-system --no-check-device --listed-incremental
> /var/opt/lib/amanda/gnutar-lists/hansabck_1.new
Snapshot is created but not used see below in 3.2.0beta3
Sat Oct 9 22:23:08 2010: amgtar: Spawning "/usr/local/bin/tar
/usr/local/bin/tar --create --verbose --file - --directory / --one-file-system
--no-check-device --listed-incremental
/var/opt/lib/amanda/gnutar-lists/hansabck_1.new --sparse
On Sat, Oct 9, 2010 at 12:22 PM, Gunnarsson, Gunnar
wrote:
> ok then I must overide the tapetype def with -o option in the amvault command.
I'm not sure about that. Your amvault run demonstrated that your
tapes can actually hold almost 6 times the data you've suggested in
your default tapetype.
ok then I must overide the tapetype def with -o option in the amvault command.
>No, it needs to be in the tapetype. It's weird, I know, but there are some
>difficult problems with combining those two sections.
Thanks Gunnar Gunnarsson
On Sat, Oct 9, 2010 at 8:21 AM, Gunnarsson, Gunnar
wrote:
>>OK. You should adjust the length in your tapetype definition, then - your
>>tape appears to be at least 550% longer than you have configured.
>
> Can I add the tape length to:
>
> define changer vault {
No, it needs to be in the tapety
>OK. You should adjust the length in your tapetype definition, then - your
>tape appears to be at least 550% longer than you have configured.
Can I add the tape length to:
define changer vault {
tpchanger "chg-manual"
tapedev "tape:/dev/rmt/0n"
changerfile "changer.conf"
}
> Not
