On my 16GB holding disk I have a dump image of about 12.5GB made by
amanda2.4.1p1 (tar1.12 + amanda patches, chuncksize of 1GB, software
compression enabled) that is too big for my single tapes (DDS3 - 12GB). This
is a level 0 dump of a WinNT share, so before reducing share size, I was
looking
Hello Olivier
The only configuration problem was that I forgot to HUP inetd grin.
We has a power interruption this morning which brought down the whole
computer room (backup server and client in question too). When they
came back up amanda was able to connect and backup. Conclusion: Dogh!
Attached is a minor patch which changes the stats printed on tape labels
to reflect what is actually on the tape rather than what got dumped.
This makes all fields accurate during an amflush run, where Total Size
used to be reported as 0, as well as after an amdump run that hit EOT.
As such,
Hi,
I'm trying to set up amanda-2.4.2p2 on an Irix 6.5.11 system, using a
exabyte EXB-210 tape library exabyte mammoth (EXB-8900) drive and
the chg-scsi tpchanger.
As far as I know the EXB-210 library conforms to the SCSI-2 Medium Changer
command set, so I suppose the chg-scsi module can
Hello,
I recently upgraded our only Solaris 8 box from Solaris 8 Maintenance
Update 2 to MU4. In addition, I hardened some of the security on the box,
among other things enabling BSM auditing. Now, amandad will not run from
inetd, although I can launch it from the command line without a
From: Kevin M. Myer [EMAIL PROTECTED]
In my logs, I see:
May 28 16:00:00 newt inetd[105]: [ID 858011 daemon.warning]
/usr/local/libexec/amandad: Hangup
May 28 16:00:02 newt last message repeated 38 times
May 28 16:00:02 newt inetd[105]: [ID 667328 daemon.error] amanda/udp
server failing
On Tue, 29 May 2001, Scot W. Hetzel wrote:
From: Kevin M. Myer [EMAIL PROTECTED]
In my logs, I see:
May 28 16:00:00 newt inetd[105]: [ID 858011 daemon.warning]
/usr/local/libexec/amandad: Hangup
May 28 16:00:02 newt last message repeated 38 times
May 28 16:00:02 newt inetd[105]: [ID
Configure error: installation or config problem: C compiler can not
create executables.
Take a look at config.log. It should give you more information on why
the compiler didn't work.
Anthony Carter
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
P.S. Please turn
... The default blocking factor of 20
performs really poorly over network. Increasing the blocking factor
from 20 to 126 improves performance tenfold.
What do you mean by over [the] network? What were you talking to on
the other side? A tape drive? Or writing into a file?
Amanda doesn't
Can I use the same amanda.conf file I was using before?
Yes, except for the tpchanger lines.
Do I need to comment out the changer related lines,
or can I leave those alone?
You'll have to do something with them. One possibility (probably the
simplest) would be to comment
Should 'dev' be just a number (0) ...
If by dev you mean tapedev in amanda.conf, then yes, that's my
understanding, it should just be 0.
Ollie
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
On 29 May 2001 16:58:20 -0400, Anthony Carter wrote:
I am getting the following error messages on a SCO Unix client. I hope
someone can point me in the right direction. I finally got the server
running
Checking whether make set ${MAKE} ./configure:Make: not found no
I'm trying to run amanda on a Sun E250, with Exabyte Mamamoth 2 220
Library.
What version of Amanda (looks like 2.4.2p2 or later)? What version
of chg-scsi?
amtape: could not get changer info: error could not read result from
/soft/backup/amanada//libexec/chg-scsi (got signal 11)
signal 11 is
However, when I try to label a tape, the chg-scsi module dies with
signal 11 (SIGSEGV)
I just replied to someone else whose chg-scsi was segfaulting, and the
same suggestions probably apply to you:
It's my understanding chg-scsi is not being maintained in the 2.4.2
branch, but that you
On my 16GB holding disk I have a dump image of about 12.5GB made by
amanda2.4.1p1 (tar1.12 + amanda patches, chuncksize of 1GB, software
compression enabled) that is too big for my single tapes (DDS3 - 12GB). ...
I was
looking for a way to save on (multiple?) tapes this dump image with amanda
or
Ready to execv amrestore with:
path = /usr/local/sbin/amrestore
argv[0] = amrestore
argv[1] = -h
argv[2] = -p
argv[3] = /dev/nsa0
argv[4] = mail.netsys.hn
argv[5] = ^da0s1f$
argv[6] = 20010524
amrestore: error reading file header: Invalid argument
Is /dev/nsa0 the same device you're using in
The server is running redhat 6.2, and the tape drive is a Dell powervault
120, but so far, i havn't found anything useful. Guess I will keep
looking.. and contact Dell if all else fails.
-Aaron
On 28 May 2001, Alexandre Oliva wrote:
On May 28, 2001, Aaron Levitt [EMAIL PROTECTED] wrote:
Attached is a minor patch which changes the stats printed on tape labels
to reflect what is actually on the tape rather than what got dumped.
Thanks! I tried it on a couple of my configs and it seems to do the right
thing. The patch has been applied to all the current source branches.
About
Hi, Amanda Users,
I am new to Amanda software. I have two concerns to clarify before I explore
futher.
1) Does Amanda support incremental backup? It should be obvisou but I didn't
see it on the feature list on Amanda home page. Is it easy to schedule full
backup and incremental backups?
2) If
19 matches
Mail list logo
