Amanda-Users

Re: two tape drives

2007-10-31 13:15:30
Subject: Re: two tape drives
From: Brian Cuttler <brian AT wadsworth DOT org>
To: "Krahn, Anderson" <AKrahn AT gs1us DOT org>
Date: Wed, 31 Oct 2007 13:08:00 -0400
Andy,

I had two config that ran concurrently on the same amanda
server, each having access to its own tape, also the tapes
where actually Storedge L9/LTO jukeboxes, so each config
owned a jukebox.

In order to avoid conflicts I was able to segregate my
clients into two groups, one having only local UFS mounted
partitions on the server, the other having partitions that
where non-local to the amanda server, so I was able to avoid
any conflicts on the known amanda TCP and UPD ports without
having to compile and run different amanda binaries for each
config. Also I avoided any chance of putting a single amanda
client in both configs, which would have caused conflict (since
the client will only respond to a single server at any one time
and there is no way to interlock/schedule a common client
between amanda servers).

For added clarity, each jukebox had its own tape pool with
config specific tape labels. I guess you could run a single
jukebox with two drives with unique tape labels, especially
if you restrict the slots per config, but I don't things that
would be necessary since each config would check labels before
writing (but it would save time finding the next tape during the run).

I ran that config for years with no problems.

Not sure if I'm addressing your exact question, if not or you
need follow-up please let me know.

                                                Brian

On Wed, Oct 31, 2007 at 11:02:08AM -0500, Krahn, Anderson wrote:
> Quick question will Amanda work correctly with two different
> configurations, each one using a tape drive running at the same time?
> 
> Ex.
> 
> Data Transfer Element 0:Empty
> 
> Data Transfer Element 1:Full (Storage Element 9 Loaded):VolumeTag =
> EGV010    these are my 2 drives.
> 
> However,
> 
> When I try to run 
> 
> /opt/amanda/server/sbin/amlabel -f FullDB EGV010 slot 9
> 
> Here is the error I get
> 
> "amlabel: could not load slot "9": Drive not ready after 120 seconds,
> rewind said "/dev/rmt/3cn:"Drive not ready after no seconds, rewind said
> "tape"Drive not ready after loaded seconds, rewind said "or"Drive not
> ready after drive seconds, rewind said "offline""
> 
>  
> 
> The tape EGV010 always goes to drive 0 instead of 1. 
> 
> mtx -f /dev/scsi/changer/c5t3d1 status
> 
>   Storage Changer /dev/scsi/changer/c5t3d1:2 Drives, 24 Slots ( 1
> Import/Export )
> 
> Data Transfer Element 0:Full (Storage Element 9 Loaded):VolumeTag =
> EGV010
> 
> Here are the conf files for FullDB
> 
> cat changer.conf
> 
> firstslot=1
> 
> lastslot=23
> 
> driveslot=1
> 
> cleanslot=-1
> 
> autoclean=0
> 
> autocleancount=99
> 
> havereader=1
> 
> offline_before_unload=0
> 
> initial_poll_delay=0
> 
> tapedev "/dev/rmt/3cn"  # the no-rewind tape device to be used
> ***Currently using hardware compression
> 
> changerdev "/dev/scsi/changer/c5t3d1"
> 
> amrecover_changer "/dev/scsi/changer/c5t3d1"
> 
> Thanks
> 
---
   Brian R Cuttler                 brian.cuttler AT wadsworth DOT org
   Computer Systems Support        (v) 518 486-1697
   Wadsworth Center                (f) 518 473-6384
   NYS Department of Health        Help Desk 518 473-0773



IMPORTANT NOTICE: This e-mail and any attachments may contain
confidential or sensitive information which is, or may be, legally
privileged or otherwise protected by law from further disclosure.  It
is intended only for the addressee.  If you received this in error or
from someone who was not authorized to send it to you, please do not
distribute, copy or use it or any attachments.  Please notify the
sender immediately by reply e-mail and delete this from your
system. Thank you for your cooperation.



<Prev in Thread] Current Thread [Next in Thread>