Todd Kover wrote:
It looks like someone wiped out a bunch of the faq-o-matic data at
sourceforge. I'm seeing if I can recover it but it mean reverting the
faq-o-matic back to an old backup version... :-(
You are not going to tell us that the amanda team doesn't
have a recent backup? :-)
[EMAIL PROTECTED] wrote:
Thanks for your quick answer. Ok it sounds clear to me that all points to
the advantages of having software compression. I will then disable hardware
compression.
If there is one flipped bit (read error), everything compressed with gzip
after that position is lost.
Jerry wrote:
Is it just me, or do people not generally change that
option and just live with it going into /usr/local???
I use the followin gconfigure options (and more):
./configure --prefix=/opt/amanda\
--sysconfdir=/etc/opt/amanda
Gene Heskett wrote:
I take it you unpacked, made, and installed amanda as root.
Generally speaking, thats a no-no.
Yes I did. But that's only for a quick test... It should not be relevant
who builds the code (only for security considerations). (Or am I wrong)?
If a segfault occoures the
Thanks for all the help. The problem goes away as soon as I
used the following device (in changer.conf).
changerdev /dev/scsi/changer/c1t5d1
This device is created by sgen and not by st. I'll write a summary
with what I did as soon as I got amanda completely up and running.
Sven
I have a very strange problem. chg-scsi (2.4.2p2) does work if it is
called as root. When I call it as user amanda it dumpes core.
By comparing two truss files I found that there is a problem with
the permissions of the device file:
open64(/dev/rmt/1mn, O_RDWR|O_NDELAY) = 4
ioctl(4,
I have a HP SureStore DDS-3 24x6 tape changer. This changer
worked as expected with AMANDA under Linux but I have huge
problems getting it to work with chg-scsi. I can navigate the changer
with chio and talk to the tape with mt.
Is there someone using chg-scsi with a HP tape changer under a
Robert SHEN wrote:
title: daily AMANDA MAIL REPORT FOR BogusMonth 0, 0
..
THE DUMPS DID NOT FINISH PROPERLY!
FAILURE AND STRANGE DUMP SUMMARY:
/dev/sda2 RESULTS MISSING
That happens if your backup server crashes while doing a backup.
Sven
Olivier Nicole wrote:
tapetype: could not rewind /dev/nst0: Input/output error
Did you run tapetype as root?
Yes. And mt -f /dev/nst0 rewind works prefect.
Sven
Alexandre Oliva wrote:
/-- localhost /dev/md190 lev 1 FAILED [data write: Broken pipe]
What does that mean? Is my tape broken?
It probably means you ran out of tape space during a direct-to-tape
backup.
I don't think that was the problem because I have a DDS-3 tape and amanda
used only:
NOTES:
taper: tape daily26 kb 0 fm 0 writing filemark: Input/output error
Sory for replaying to my own message. I found something in syslog:
kernel: st0: Error with sense data: Info fld=0x1, Current st
09:00: sense key Medium Error
kernel: Additional sense indicates Write error
I think
Alexandre Oliva wrote:
I think that means the tape is broken...?
Quite possibly. Try running tapetype on it and see how far it goes.
tapetype did not complain but it found 44235 mbytes on a DDS3 (without hw
compression). And I got a
tapetype: could not rewind /dev/nst0: Input/output error
I got the following error:
--
These dumps were to tape daily26.
*** A TAPE ERROR OCCURRED: [[writing file: Bad file descriptor]].
Some dumps may have been left in the holding disk.
Run amflush to flush them to tape.
The next tape Amanda expects to use is: daily27.
[snip]
FAILED AND
http://amanda.sourceforge.net/fom-serve/cache/30.html
The best approach is to create a separate configuration for your
archive
backups. It should use a separate set of tapes, and have all
dumptypes
configured with `record no', so it doesn't interfere with regular
backups.
But that would
Is there a way to compile amanda in the following way:
Configuration: /etc/opt/amanda-2.4.2
instead of: /etc/opt/amanda-2.4.2/amanda
which is produced by --sysconfdir=/etc/opt/amanda-2.4.2
Var:/var/opt/amanda-2.4.2
instead of: /var/opt/amanda-2.4.2/amanda
15 matches
Mail list logo
