ALso,  it sounds like amanda may indeed think you only have one tape drive ….
but amanda is being impatient and KEEPS ON asking you to change the tape.
I wonder if there is a setting for how often it should ask you?
I wonder if that’s a system setting, related to the tape drive, rather than 
amanda?
   (Who sent the emails,  amanda  or the system?)

Just throwing out things to think about.
Deb Baddorf


> On Nov 10, 2016, at 10:42 AM, Matthew Carter <[email protected]> 
> wrote:
> 
> Hi! So I'm pretty new to amandabackup and wanted to know if someone could 
> help me with something I'm seeing.
> 
> I have a small network, consisiting of ten clients and one server which is 
> the amanda backup server. I don't run anything but local backups of an NFS 
> shared space. The server has a HP LTO-5 tapedrive directly attached and I was 
> given 30 tapes in which to complete backups.
> 
> I'm the only admin on the network, so if I am out that day, no tapes get put 
> in the drive and when I arrive the next day, I see 100 emails from amanda 
> that makes me think amanda thinks I have a changer instead of a single tape 
> drive.
> 
> Here is my amanda.config:
> 
> org "DARSet"
> mailto "admin@localhost"
> dumpcycle 6week
> runspercycle 5
> tapechanger "chg-manual"
> tapedev "/dev/nst0"
> changerfile "/etc/amanda/DARSet/chg-manual.conf"
> changerdev "/dev/null"
> tapetype HP-LTO-5
> labelstr "^DARSet[0-9][0-9]*$"
> dtimeout 1800
> ctimeout 30
> etimeout 300
> 
> define dumptype global {
>    comment "Global Definitions"
>    auth "local"
> }
> define dumptype gui-base {
>    global
>    program "GNUTAR"
>    comment "gui base dumptype dumped with tar"
>    compress none
>    index yes
> }
> define tapetype HP-LTO-5 {
>    length 1480633696 kbytes
>    filemark 739 kbytes
>    speed 81970 kps
>    blocksize 32 kbytes
> }
> includefile "advanced.conf"
> includefile "/etc/amanda/template.d/dumptypes"
> includefile "/etc/amanda/template.d/tapetypes"
> 
> 
> How can I tell amanda that it is a single drive? Thanks for any help!
> 
> 
> Matt
> 


Reply via email to