Hi,
On a system running FreeBSD-4.3 Release, I have retrieved the latest amanda
src from cvs. Ran autoconf on configure.in then configure and it fails.
Unfortunately I known nothing about autoconf, so any enlightment of my
ignorance is welcomed ;-)
* John R. Jackson [EMAIL PROTECTED] (Mon, Jul 30, 2001 at 05:04:47PM -0500)
Does anyone know if that puppy is supported by amanda ?
If it's SCSI, Amanda can do it (or it should be able to so we'll make it).
It is,
the thing is that it's a taperobot/tapechanger, and I remember reading
Hi,
I'm using amanda with the same configuration for 10 days without having
big issue.
but after the other administrator touchs the disklist by suppressing one
record and do change other stuff on the host that
that have the tape server...
all my dumps fails with the same error message
/--
Does netusage actually do anything with regard to the amount of
bandwidth amanda uses? I have mine set way down at 50 Kbps, and I'm seeing
it pull up to 6 Mbps at a time, regardless of what I set it to.
Does amanda actually shape its bandwidth usage, or is 'netusage' just for
estimates?
Dan
Hi,
I am using amanda2.4.2p1 version on a linux machine.. when I tried to
recover one users home directory it's giving one error.. Can someone help
out ...to figure out the pblm..?
The index server is also a Linux machine.. I have checked all the config
parameters in /etc/inetd.conf and
the thing is that it's a taperobot/tapechanger, and I remember reading
discussions that getting that to work is not always a trivial issue.
That's going to be true no matter what. Any time software comes in
contact with reality (hardware), bad things happen :-).
What kind of tapedrives do you
Hi,
I might be wrong here,
but isn't /dev/sa0 the rewind device ?
You are of course absolutely right. I guess I need a new pair of
glasses. The fact that this was the problem all the time makes
me want to smash my head against my monitor :-%
Thanks, however.
Try /dev/nsa0 (or whatever is
[EMAIL PROTECTED] wrote:
Hello there,
I figure my last mail was less than informative - usually not my
style and I apologize.
[snip]
$ amlabel Hundert6 Hundert601
rewinding, reading label, not an amanda tape
rewinding, writing label Hundert601, done.
... however, each and
Check tape device as well as the labelstr values. Here are mine:
tapedev /dev/nrsa0 # the no-rewind tape device to be used
tapetype DLT1 # what kind of tape it is
labelstr ^Taeglich-[0-9][0-9]*$ # label constraint regexp: all tapes
must match
HTH
-Christoph Sold
[EMAIL
Philippe,
Even then, the 2.5 version
of chg-scsi has been merged back into the 242-branch and chg-scsi builds
on FreeBSD 4.3 with only minor pain.
yes that's the one (chg-scsi) that I am looking after. I have been reading
the archive and was following a detailed procedure found
unsubscribe
* [EMAIL PROTECTED] [EMAIL PROTECTED] (Tue, Jul 31, 2001 at 03:09:24PM +0200)
Hello there,
I figure my last mail was less than informative - usually not my
style and I apologize.
ERROR: /dev/sa0: not
an amanda tape.
(expecting a new tape)
I might be wrong here,
but isn't /dev/sa0
I'm running amanda v2.4.2p2 on Solaris 8 server with a Sun STORedge
attached to it.
I could get the backups up and running succesfully, but I'm having a
problem when doing a restore. I can run amrestore and get the dump file
I want, but I didn't find out how to uncompress that file. If I do a
I guess I should have a
list of all my labels and a barcode code for each label, but I don't
know how to generate that or if I have to do it manually.
First, zap that file to zero length (cp /dev/null ...). Then, I
**think**
you should be able to do amtape config update (as the Amanda
Ben,
Thanks for you quick and detailed answer.
1. Are you sure you really want to build the 2.5 sources? Unless you are
just trying to get chg-scsi working on FreeBSD, it's probably a bad idea.
(Kind of like running FreeBSD-current! :).
I do run FreeBSD-current, thought on a 2nd
[EMAIL PROTECTED] writes:
Hello there,
I figure my last mail was less than informative - usually not my
style and I apologize.
Anyway, one problem seems to persist and I'm clueless as to what
may cause it.
So, my amanda server is a FreeBSD 4.3 STABLE machine with a
Tandberg MLR1.
I was using chg-zd-mtx, but seems to work now.
Thanks!
On Saturday, July 28, 2001, at 03:15 , Thomas Hepper wrote:
Hi,
On Fri, Jul 27, 2001 at 02:15:26PM -0500, Ignacio Tripodi wrote:
Hi!
I'm running amanda v2.4.2p2 on Solaris 8 server, attached to a Sun
STORedge L9 that supports
Hi, we're trying to start our first amanda bkup session
without any success
Facts:
amcheck and amverify succeded:
--
Tape DailySet1-01 label ok
NOTE: info dir /var/lib/amanda/DailySet1/curinfo: does not exist
NOTE: it will be created on the next run
Server check
Hello there,
I figure my last mail was less than informative - usually not my
style and I apologize.
Anyway, one problem seems to persist and I'm clueless as to what
may cause it.
So, my amanda server is a FreeBSD 4.3 STABLE machine with a
Tandberg MLR1.
amanda is version 2.4.1p1, installed
Right, I saw that. ...
What??? You read the man page??? :-)
But netusage is not in that section, it's under the
global CONFIG FILE PARAMETERS section. ...
But it refers you to the interface section.
Netusage was the original limit in Amanda. Then someone wanted finer
grained control and
On Tue, 31 Jul 2001, John R. Jackson wrote:
Does netusage actually do anything with regard to the amount of
bandwidth amanda uses? ...
No. From the amanda(8) man page (INTERFACE SECTION):
Right, I saw that. But netusage is not in that section, it's under the
global CONFIG FILE PARAMETERS
We are using a Ampex DST for our backups. It performs best when using an
8k block size. Currently amanda uses at 32k block size which ends up being
about a factor of 10 slower than using an 8k block size. How do I configure
amanda to use an 8k block size?
--
Robert Minsk
Hi,
On Tue, Jul 31, 2001 at 11:13:15AM +0200, thomas graichen wrote:
[...]
use inside of amanda ... any help would be appreciated
First which version of amanda ?. Lets assume 2.4.2p2 from cvs, if
not please get the cvs version.
Next try the following (From the 2.5.0 docs, i must update the
I have noticed that amanda does not do it estimates in parallel.
Is this something I can configure?
--
Robert MinskCentropolis Effects, LLC.
[EMAIL PROTECTED]10950 Washington Blvd., Studio B
Culver City, Ca.
If I do a
'file DUMPFILENAME', it shows it as a USTAR Tar file', and if I do a
'tar tvf DUMPFILENAME' I can view all the contents correctly.
Then you're all set. Use GNU tar to extract whatever you want.
You're right! In amanda.conf was set to use gnutar instead of dump, the
problem is
We are using a Ampex DST for our backups. It performs best when using an
8k block size. Currently amanda uses at 32k block size which ends up being
about a factor of 10 slower than using an 8k block size. How do I configure
amanda to use an 8k block size?
You don't.
I'll be applying a change
With the variable block size device the drive makes no assumptions about the
data coming down the pipe and does not buffer. This means every write request
goes stright to the tape.
Ah, I see. None of the device I'm familiar with do that (that I know of).
Would anything break if I set the
FAILURE AND STRANGE DUMP SUMMARY:
localhost /etc RESULTS MISSING
What version of Amanda?
First, don't use localhost in your disklist. It will bite you
eventually. Use the fully qualified host name.
Next, look at /tmp/amanda/sendsize*debug. That's likely where the
problem will show up.
John R. Jackson wrote:
Is the 8K value a hardware blocking factor? Can you set the device to
variable blocking?
On the SGI the non variable block size device is fixed at 8K. I can actually
change the tape drive block size to anything I want but the SGI limits you
to 8K.
With the
John R. Jackson wrote:
With the variable block size device the drive makes no assumptions about the
data coming down the pipe and does not buffer. This means every write request
goes stright to the tape.
Ah, I see. None of the device I'm familiar with do that (that I know of).
I just
I have noticed that amanda does not do it estimates in parallel.
Is this something I can configure?
All clients are processed in parallel, i.e. estimate requests are sent
to all the clients at the same time. To increase the number of requests
processed in parallel on a given client, raise
... If I
could increase the buffer size to 1199840 then I could achive about 15
megabytes a second. As it is now I am wasting space and time writing 32K
blocks.
1199840 is a strange number (as in, not a power of 2). Could you live
with a blocksize of 1199104 (1171 KBytes)? That would waste
John R. Jackson wrote:
... If I
could increase the buffer size to 1199840 then I could achive about 15
megabytes a second. As it is now I am wasting space and time writing 32K
blocks.
1199840 is a strange number (as in, not a power of 2). Could you live
with a blocksize of 1199104
33 matches
Mail list logo
