All,
Amanda has been awarded Best of Open Source Software Award in the Storage
category:
http://weblog.infoworld.com/tcdaily/archives/2008/08/best_of_open_so_6.html
Congratulations to Amanda developers and users.
Cheers!
Chander
On Tue, Aug 5, 2008 at 3:04 PM, Vectorz Sigma [EMAIL PROTECTED] wrote:
I have an Ultrium LTO-4, and cannot get it to work with Amanda.
You had pasted some other diagnostic output that I didn't recognize to
#amanda. Can you give some more details? Also, please have a look in
your kernel logs to
Hi List!
I've setup my amanda backup server and everything seems to be fine -
running for some weeks without any problem. (Using amanda 2.5.p1 with a
HP tape library - 8 tapes). Well, because of a mistake - I've done - one
tape was missing an so, amanda wrote all dumps to the holding disk.
(like
My tapedev entry that works is tapedev /dev/nst0 not tapedev tape:/dev/nst0
I have used the follow tape specific entries in my amanda.conf:
tapedev /dev/nst0 # Linux @ tuck, important: norewinding
tapetype LTO4 # what kind of tape it is (see tapetypes below)
labelstr ^FULLBACK-[0-9][0-9]*$ #
Doyle, thanks for the tip but I got errors when trying it without the
tape: in the string. I forgot to mention that I'm using 2.6.0p1
This is the error:
# amlabel WeeklySet1 Weekly-01
Reading label...
/dev/nst0 uses deprecated device naming convention;
using tape:/dev/nst0 instead.
Can't open
Marc -- Yes, I have tried to access it directly with tar, also mt commands
to rewind, etc. Also note that initially I setup Bacula on this system and
that worked so I know the drive is legit on that device name. I decided not
to use Bacula because the maintenance of the MySQL db got really out
On Wed, Aug 6, 2008 at 11:00 AM, Vectorz Sigma [EMAIL PROTECTED] wrote:
Doyle, thanks for the tip but I got errors when trying it without the
tape: in the string. I forgot to mention that I'm using 2.6.0p1
The tape: thing is not the issue here -- the code that writes the
deprecation warning
I would also verify that nst0 is assigned to your LTO 4 drive
What brand of Ultrium LTO 4 do you use. Mine is a Tandberg Data or Exabyte. I
use the ltoTool to check and see if the device is being recognized. If your
Ultrium LTO 4 is not an Tandberg, I am sure the manufacturer has a tool to
Hi, I'm not often running amflush but I would still expect a log file
to be generated in your log directory with more info. How many backups
on holding disk were you expecting this to have been flushing?
Paul
-In response to your message-
--received from Andre Brandt--
Hi List!
I've
The mystery deepens.
Can you run 'amlabel' under strace or truss or your local equivalent?
I'd like to know what syscall is returning EBADFD (Bad file
descriptor). Also, please remind me what version of Amanda you're
running.
You can send the strace output to me privately for analysis if you'd
TIA for your help thus far. Following your advice, here is a diag tool I
ran on my HP Ultrium LTO-4 that indicates all is working well on it and
verifies it is /dev/nst0. I have checked my logs and the last error I've
seen was a few days ago, nothing produced by the diags done recently.
Main
Matthew Marlowe [EMAIL PROTECTED] wrote:
Are you using RHEL or Fedora? The bug is reported for fedora 8 but
we just noticed a similar issue on a RHEL5.2 box (perhaps this is
one of the feature updates carried over from fedora during the 5.2
upgrade).
I'm on RHEL 4.x, latest updates, that's
I downgraded to Amanda 2.5.2p1 and it gave me a better clue when running
amlabel. Basically it said /dev/nst0 = permission denied. I've been
running the amlabel command as amandabackup but didn't realize you need to
give permissions to the /dev/nst0 device (which was 750 perms and owned by
On Wed, Aug 6, 2008 at 7:32 PM, Vectorz Sigma [EMAIL PROTECTED] wrote:
I downgraded to Amanda 2.5.2p1 and it gave me a better clue when running
amlabel. Basically it said /dev/nst0 = permission denied. I've been
running the amlabel command as amandabackup but didn't realize you need to
give
14 matches
Mail list logo
