Re: problem with manual tape changer
Hi, now i added this:
define taperscan oldest {
comment "bla"
plugin "oldest"
}
taperscan "oldest"
into my amanda.conf. Now i got an email to change the tape. But then i am
stuck, amanda does not notice the newly inserted tape, and also does not react
on the file /tmp/email_input i created with touch.
It just waits forever. What am i missing?
On 14.02.2013, at 16:53, Jean-Louis Martineau wrote:
> On 02/14/2013 10:00 AM, Karsten Fuhrmann wrote:
>> Hello,
>> i tried that but does not work. I dont get an email to change the tape,
>> instead amanda quits with:
>>
>> FAILURE DUMP SUMMARY:
>> datastore /tank/koh/user/./k-o lev 0 partial taper: No acceptable volumes
>> found
>>
>> i added the following in my amanda.conf:
>>
>> define interactivity email {
>> comment "interactivity email"
>> plugin "email"
>> property "mailto" "[email protected]"
>> property "resend_delay" "0"
>> property "check-file" "/tmp/email_input"
>> property "check-file-delay" "10"
>> }
>> interactivity "email"
>>
>>
> The default taperscan do not use the interactivity module, you must use the
> 'oldest' or 'lexical' taperscan.
> see: man amanda-taperscan
>
> Jean-Louis
>
Greetings,
Karsten Fuhrmann
System Administrator
Rothkirch Cartoon-Film GmbH
Hasenheide. 54
D-10967 Berlin
phone +49 30 698084-109
fax +49 30 698084-29
mobile +49 176 49118462
skype: parceval3000
AIM: [email protected]
Jabber: [email protected]
Re: problem with manual tape changer
On 02/14/2013 10:00 AM, Karsten Fuhrmann wrote:
Hello,
i tried that but does not work. I dont get an email to change the tape, instead
amanda quits with:
FAILURE DUMP SUMMARY:
datastore /tank/koh/user/./k-o lev 0 partial taper: No acceptable volumes
found
i added the following in my amanda.conf:
define interactivity email {
comment "interactivity email"
plugin "email"
property "mailto" "[email protected]"
property "resend_delay" "0"
property "check-file" "/tmp/email_input"
property "check-file-delay" "10"
}
interactivity "email"
The default taperscan do not use the interactivity module, you must use
the 'oldest' or 'lexical' taperscan.
see: man amanda-taperscan
Jean-Louis
Re: problem with manual tape changer
Hello,
i tried that but does not work. I dont get an email to change the tape, instead
amanda quits with:
FAILURE DUMP SUMMARY:
datastore /tank/koh/user/./k-o lev 0 partial taper: No acceptable volumes
found
i added the following in my amanda.conf:
define interactivity email {
comment "interactivity email"
plugin "email"
property "mailto" "[email protected]"
property "resend_delay" "0"
property "check-file" "/tmp/email_input"
property "check-file-delay" "10"
}
interactivity "email"
On 12.02.2013, at 16:19, Jean-Louis Martineau wrote:
> Karsten,
>
> You must set an interactivity (man amanda-interactivity):
>
> define interactivity email {
> comment "interactivity email"
> plugin "email"
> property "mailto" "root"
> property "resend_delay" "0"
> }
> interactivity email
>
>
> Jean-Louis
>
> On 02/12/2013 09:06 AM, Karsten Fuhrmann wrote:
>> Hello,
>> i have a problem with the manual tape changer configuration. I set
>>
>> runtapes 2
>> and
>> tpchanger "chg-single:tape:/dev/nsa0"
>>
>> But still after amanda fills up the first tape, amanda quits with a 'partial
>> taper: No acceptable volumes found' message.
>> What i want is amanda to send my an email that i should load the next tape
>> and then continue with the backup.
>>
>> I am using amanda 3.3.0 in a cronjob with an LTO4-Ultrium tape drive.
>>
>> Here my Amanda.conf:
>> mailto "administration" # space separated list of operators at
>> your site
>> dumpuser "amanda"# the user to run dumps under
>> displayunit "G" # Display filesizes in megabytes
>> tpchanger "chg-single:tape:/dev/nsa0"
>> inparallel 1 # maximum dumpers that will run in parallel (max 63)
>> maxdumps 1
>> flush-threshold-dumped 50# Start taping when 90% of tapesize Capacity
>> reside on HD
>> flush-threshold-scheduled 50
>> device-property "LEOM" "FALSE"
>> dumporder "T"# specify the priority order of each dumper
>> netusage 12 Kbps# maximum net bandwidth for Amanda, in KB per
>> sec
>> taperalgo first
>> dumpcycle 21 # the number of days in the normal dump cycle
>> runspercycle 15 # the number of amdump runs in dumpcycle days
>> tapecycle 21 tapes # the number of tapes in rotation
>> bumpsize 10 Gb # minimum savings (threshold) to bump level 1
>> -> 2
>> bumpdays 1 # minimum days at each level
>> bumpmult 2 # threshold = bumpsize * bumpmult^(level-1)
>> etimeout 6000# number of seconds per filesystem for
>> estimates.
>> dtimeout 1800# number of idle seconds before a dump is
>> aborted.
>> ctimeout 300 # maximum number of seconds that amcheck waits
>> runtapes 2 # number of tapes to be used in a single run of amdump
>> tapedev "tape:/dev/nsa0" # the no-rewind tape device to be used
>> maxdumpsize 3200 gb # Maximum number of bytes the planner will schedule
>> tapetype LTO4-ULTRIUM# what kind of tape it is (see tapetypes below)
>> labelstr "^cf-daily-lto[0-9][0-9]*$" # label constraint regex: all tapes
>> must match
>> reserve 10
>> autoflush yes
>> columnspec
>> "HostName=0:10,Disk=1:-1,Level=1:3,OrigKB=1:15,OutKB=1:15,DumpTime=1:8,TapeTime=1:8,DumpRate=1:8,TapeRate=1:8"
>> infofile "/var/amanda/cf-daily-lto/curinfo" # database DIRECTORY
>> logdir "/var/amanda/cf-daily-lto" # log directory
>> indexdir "/var/amanda/cf-daily-lto/index"# index directory
>>
>> holdingdisk hd1 {
>> comment "first holding disk"
>> directory "/mnt/amanda-holding" # where the holding disk is
>> use -5 Gb# how much space can we use on it
>> chunksize 50Gb # size of chunk if you want big dump to be
>> }
>>
>> define tapetype LTO4-ULTRIUM {
>> comment "LTO4"
>> length 1600 gbytes #was 1200gbytes
>> filemark 0 kbytes
>> part_size 50 gbytes
>> }
>>
>>
>>
>> define dumptype global {
>> comment "Global definitions"
>> index yes
>> }
>>
>> define dumptype root-tar {
>> global
>> program "GNUTAR"
>> index yes
>> comment "root partitions dumped with tar"
>> priority low
>> compress server best
>> }
>>
>> define dumptype high-tar-ssh {
>> auth "ssh"
>> ssh_keys "/usr/local/etc/amanda/cf-daily-lto/ssh-key"
>> root-tar
>> comment "partitions dumped with tar"
>> index yes
>> priority high
>> compress none
>> }
>>
>>
>> Greetings,
>> Karsten
>
Greetings,
Karsten
Re: problem with manual tape changer
Karsten,
You must set an interactivity (man amanda-interactivity):
define interactivity email {
comment "interactivity email"
plugin "email"
property "mailto" "root"
property "resend_delay" "0"
}
interactivity email
Jean-Louis
On 02/12/2013 09:06 AM, Karsten Fuhrmann wrote:
Hello,
i have a problem with the manual tape changer configuration. I set
runtapes 2
and
tpchanger "chg-single:tape:/dev/nsa0"
But still after amanda fills up the first tape, amanda quits with a 'partial
taper: No acceptable volumes found' message.
What i want is amanda to send my an email that i should load the next tape and
then continue with the backup.
I am using amanda 3.3.0 in a cronjob with an LTO4-Ultrium tape drive.
Here my Amanda.conf:
mailto "administration" # space separated list of operators at
your site
dumpuser "amanda" # the user to run dumps under
displayunit "G" # Display filesizes in megabytes
tpchanger "chg-single:tape:/dev/nsa0"
inparallel 1# maximum dumpers that will run in parallel (max 63)
maxdumps 1
flush-threshold-dumped 50 # Start taping when 90% of tapesize Capacity
reside on HD
flush-threshold-scheduled 50
device-property "LEOM" "FALSE"
dumporder "T" # specify the priority order of each dumper
netusage 12 Kbps # maximum net bandwidth for Amanda, in KB per sec
taperalgo first
dumpcycle 21# the number of days in the normal dump cycle
runspercycle 15 # the number of amdump runs in dumpcycle days
tapecycle 21 tapes # the number of tapes in rotation
bumpsize 10 Gb # minimum savings (threshold) to bump level 1 -> 2
bumpdays 1 # minimum days at each level
bumpmult 2 # threshold = bumpsize * bumpmult^(level-1)
etimeout 6000 # number of seconds per filesystem for estimates.
dtimeout 1800 # number of idle seconds before a dump is aborted.
ctimeout 300# maximum number of seconds that amcheck waits
runtapes 2 # number of tapes to be used in a single run of amdump
tapedev "tape:/dev/nsa0" # the no-rewind tape device to be used
maxdumpsize 3200 gb # Maximum number of bytes the planner will schedule
tapetype LTO4-ULTRIUM # what kind of tape it is (see tapetypes below)
labelstr "^cf-daily-lto[0-9][0-9]*$" # label constraint regex: all tapes must
match
reserve 10
autoflush yes
columnspec
"HostName=0:10,Disk=1:-1,Level=1:3,OrigKB=1:15,OutKB=1:15,DumpTime=1:8,TapeTime=1:8,DumpRate=1:8,TapeRate=1:8"
infofile "/var/amanda/cf-daily-lto/curinfo" # database DIRECTORY
logdir "/var/amanda/cf-daily-lto" # log directory
indexdir "/var/amanda/cf-daily-lto/index" # index directory
holdingdisk hd1 {
comment "first holding disk"
directory "/mnt/amanda-holding" # where the holding disk is
use -5 Gb # how much space can we use on it
chunksize 50Gb # size of chunk if you want big dump to be
}
define tapetype LTO4-ULTRIUM {
comment "LTO4"
length 1600 gbytes #was 1200gbytes
filemark 0 kbytes
part_size 50 gbytes
}
define dumptype global {
comment "Global definitions"
index yes
}
define dumptype root-tar {
global
program "GNUTAR"
index yes
comment "root partitions dumped with tar"
priority low
compress server best
}
define dumptype high-tar-ssh {
auth "ssh"
ssh_keys "/usr/local/etc/amanda/cf-daily-lto/ssh-key"
root-tar
comment "partitions dumped with tar"
index yes
priority high
compress none
}
Greetings,
Karsten
