/mnt/amanda-vtape ext4
noauto,owner,nofail 0 2
Any hints? Thanks in advance.
Moritz
--
aldebaran Programmierung & IT-Lösungen GmbH
Softwareentwicklung / Individualsoftware
mail:i...@aldebaran.de https://www.aldebaran.de
Tel: +49-511-270 416-0 Fax
Thanks Jean-Louis,
I followed your suggestion and of course it works.
Maybe when somebody touches that code it would be an idea to add a
possibility to unset parameters, for example like
application none
or
application -
or
no application
or
application withdraw ;)
Moritz
Am
:0511-270 416-33
Adresse: Weidendamm 19Ort: D-30167 Hannover
Geschäftsführung: Ursula (Usch) Wildt - Moritz Both
Handelsregister: Amtsgericht Hannover HRB 56 991
...@aldebaran.dehttp://www.aldebaran.de
Tel: 0511-270 416-0 Fax:0511-270 416-33
Adresse: Weidendamm 19Ort: D-30167 Hannover
Geschäftsführung: Ursula (Usch) Wildt - Moritz Both
Handelsregister: Amtsgericht Hannover HRB 56 991
You should probably double check your hardware. I once had a similar
error where every ~2,000,000,000th double word on the tape was
corrupted. It turned out to be a bad mainboard (asus a7v133 pci
problem). Run amverify regulary for a while, gzip will report these
kind of errors (crc error).
Hello everyone who considers using the Onstream ADR50 drive with
amanda, I won't let you wait any longer since Onstream support do not
get back to me this time.
The ADR50 drive, which is supposed to be a full linux compatible SCSI
tape drive (it should work with the standard st scsi tape
Henning,
have you ever been able to actually *restore* files from amanda tapes
using this device? Which is the firmware verison it has?
See also my email on the list from half an hour ago.
Greetings,
Moritz
Sarah,
I was waiting for the right moment to post this on the list for a
while now... It is a perl cgi which allows to view what the amanda
server is doing and to start dumps and verifys and to label tapes. It
can use different configurations and by default prints the amverify
output or, if
The reality check point of the poster who started this thread is very
valuable for the amanda community. It is true: amanda *is*
complicated. Given that it does not cost anything, there is no point
in complaining of course and that is not what I intend to do. However
in my opinion the awareness
Bill Carlson [EMAIL PROTECTED] wrote:
[...]
I think amanda falls under the qmail/smtpd category. If you have trouble
installing it, maybe you should rethink whether you are qualified to
implement the backup procedure.
Well... I think if you don't have trouble installing amanda for the
I have got an email from OnStream support today. They say that they
are *not* planning to release a new firmware for the ADR50 or the
ADR30 at the moment. Thus, no support for amanda.
They claim that their new generation drives, the ADR2 series, do not
have this problem.
Moritz
You should really search the mailing list archives for OnStream and
ADR. At the moment, the ADR50 has a firmware bug that prevents it
from working with amanda at all.
Greetings,
Moritz
Hi,
I have an Onstream ADR50, and I'm just learning how to get amanda
configured on RH72. One of the
Hello everyone who considers using the Onstream ADR50 drive with
amanda, I won't let you wait any longer since Onstream support do not
get back to me this time.
The ADR50 drive, which is supposed to be a full linux compatible SCSI
tape drive (it should work with the standard st scsi tape
You should probably double check your hardware. I once had a similar
error where every ~2,000,000,000th double word on the tape was
corrupted. It turned out to be a bad mainboard (asus a7v133 pci
problem). Run amverify regulary for a while, gzip will report these
kind of errors (crc error).
Hi after 2 years of struggling with this crap and getting no where, can
anyone help me figure out what is causing these errors.
it seems to be random doesn't matter which tape or drive I use they all
do it. even changing machine and scsi controllers doesn't fix the
problem.
is it
I think you must add a dot before each exclude list entry and you must
use shell wildcards:
./proc/*
./devices/*
Those are relative to the partition roots, not necessarily to the
filesystem root.
Moritz
Du schriebst am Dienstag, 4. Dezember 2001:
I have an exclude list that looks like:
16 matches
Mail list logo
