Michael Loftis [EMAIL PROTECTED] writes:
--On March 2, 2007 10:31:33 AM + Anthony Worrall
[EMAIL PROTECTED] wrote:
This is not strictly an amanda question but I thought I would see if any
one has any views on SDLT-4 compared to LTO-3.
We are currently looking at replacing our tape
2007/2/27, Guy Dallaire [EMAIL PROTECTED]:
We're happily running amanda 2.4.5 right now. I'm wondering if we should
move toward 2.5.1. I don't see the advantages for us. Are major bug fixes
still issued for 2.4.5 ?
If we move to 2.5.1, will we be able to recover the backups we made with
2.4.5.
LTO-3 also has atleast one advantage for (capable) libraries, each
cartridge has a contactless (read... RFID like) memory that can
report the tapes last known condition, as well as user data. in
theory atleast an LTO drive or library has only to read this tag to
decide whether-or-not
2007/2/27, Guy Dallaire [EMAIL PROTECTED]:
We're happily running amanda 2.4.5 right now. I'm wondering if we
should move toward 2.5.1. I don't see the advantages for us. Are
major bug fixes still issued for 2.4.5 ?
If we move to 2.5.1, will we be able to recover the backups we made
with
Are we really the only ones wanting to use amanda with kerberos 5 on
Solaris?
Feels a bit lonely...
Hi!
Anyone out there using amanda on Solaris with Kerberos 5?
We've been trying to get Amanda working with Kerberos 5 on Solaris
(10)
with limited success.
We've tried builds with
FL schrieb:
After watching the trouble recur, I see that the device associated with
the changer SCSI device ID moved: it was /dev/sg2, today it is /dev/sg1.
No changes were made to the Exabyte LTO-2 tape library or to the SCSI
card (or anything else). So there is something I'm failing to
All,
I'm just digging around a little more but I figured I'd put this out anyway.
I'm just curious if anyone has tried anything like this ... I'd like to
maintain longer retention period backups to tape and still have the advantage
of using the file-driver and a virtual library of tapes.
Based
On Tue, Mar 06, 2007 at 04:09:42PM -0500, FL wrote:
On 2/22/07, Stefan G. Weichinger [EMAIL PROTECTED] wrote:
After watching the trouble recur, I see that the device associated with the
changer SCSI device ID moved: it was /dev/sg2, today it is /dev/sg1. No
changes were made to the Exabyte
Thanks for getting back to me so quickly!
Here's the relevant data:
OS is debian linux
[EMAIL PROTECTED]:~$ uname -a
Linux Wilf 2.6.17 #4 SMP PREEMPT Wed May 10 13:53:45 CEST 2006 i686
GNU/Linux
Amanda version:
amadmin Daily version
build: VERSION=Amanda-2.5.1p1
BUILT_DATE=Wed Nov 29
FL schrieb:
Thanks for getting back to me so quickly!
Why should I sleep at midnight? ;-)
And in my startup script, I have:
modprobe sg
chown root.tape /dev/sg0
chown root.tape /dev/sg1 # moved from sg2 to sg1!!!
chown root.tape /dev/sg2
chown root.tape /dev/sg3
if [ ! -h
On 3/6/07, Stefan G. Weichinger [EMAIL PROTECTED] wrote:
FL schrieb:
Thanks for getting back to me so quickly!
Why should I sleep at midnight? ;-)
You too?
And in my startup script, I have:
modprobe sg
chown root.tape /dev/sg0
chown root.tape /dev/sg1 # moved from sg2 to sg1!!!
Unfortunately, my system doesn't have sg_scan (perhaps I could install
this).
There is another script you can use for rescanning devices on a SCSI interface
that works quite well. The output looks quite similar to that the sg_scan
script does. You can find it here:
FL schrieb:
On 3/6/07, *Stefan G. Weichinger* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
FL schrieb:
Thanks for getting back to me so quickly!
Why should I sleep at midnight? ;-)
You too?
:)
This is what I settled on as a first guess
# my customized rule
13 matches
Mail list logo
