Hi,
I recently upgraded a system from RHL8 to RHL9 and am seeing the
following errors from Amanda's mailed backup report. I'm not sure if
it's Amanda or some of the underlying tools like dump(1) involved
here:
FAILURE AND STRANGE DUMP SUMMARY:
localhost feff9f0 lev 0 ERROR [not in disklis
Hi.
How does Amanda decide which tape to use next -- such as when mentioning
it in mailed backup reports?
"The next tape Amanda expects to use is .."
I ask because I have labelled a dozen tapes and, after the first dump is
complete, Amanda says "The next tape Amanda expects to use is Daily12
On Friday, amdump wrote my dump images to a tape successfully, but a
subsequent amverify showed that the tape is defective. Now, my dumps have
been removed from the holding disk, but I don't think the images on the
tape are usable.
Is there any way to re-do this backup onto a good tape or am
Has anyone successfully used the Tivano CD-RW taper replacement with
Amanda? After installing it, I get fatal errors from amdump about
"Connection reset by peer". If anyone has it working, could you please
contact me so that we can compare setups? Thanks,
Ben
> "David" == David Lloyd <[EMAIL PROTECTED]> writes:
David> If that doesn't work, try dig 83.0.168.192.in-addr.arpa
dig -x 192.168.0.83 is less of a mouthful. :-)
Ben
> "Alain" == Alain Muls <[EMAIL PROTECTED]> writes:
Alain> 2. how to do tests to check whether the configuration is
Alain> working?
Once you've configured Amanda, you run `amcheck ' to test the
configuration. This is documented in the `amcheck' manual page.
To *really* test the configu
> "Casey" == Casey Scott <[EMAIL PROTECTED]> writes:
Casey> Sorry, I should I have clearer in my description. Yes, it is very
Casey> possible, in fact probable that a full Level 0 was performed before
Casey> killing amanda. So I am correct in thinking that all should be Level 0?
Casey
> "Casey" == Casey Scott <[EMAIL PROTECTED]> writes:
Casey> Does doing amlabel -f reset the tape? I only have one tape right now,
Casey> and I have completed the procedure for flush out the database. I would
Casey> like the tape to be reset also
You can relabel the tape if you want. J
> "Casey" == Casey Scott <[EMAIL PROTECTED]> writes:
Casey> Hi all. I am new to Amanda, so please forgive the newbie question.
Casey> How do I blank a tape? amlabel -f ? When I attempted my first real
Casey> backup, it finished sucessfully but was a mix of Level 0 and 1.
> "John" == John Jolet <[EMAIL PROTECTED]> writes:
John> i have an intel-based server running solaris x86 8. inetd
John> causes it to listen on the amanda port, until you do an
John> amcheck or amdump or something on the server. then it stops
John> listening on that port. this is wh
> "Olivier" == Olivier Collet <[EMAIL PROTECTED]> writes:
Olivier> I have a doubt. I launched the backup yesterday at 18:00 and today it is
Olivier> 10:35 and it is still not done! I have put 'only' three servers in this
Olivier> backup as a test. Is it normal it is so slow ? How can I
> "Jonathan" == Jonathan Dill <[EMAIL PROTECTED]> writes:
Jonathan> In case you haven't heard, don't open that Snow White attachment! I'll
Jonathan> send more details shortly so you know this isn't a hoax...
I would have thought that by now, users would have been sufficiently
slapped ar
For anyone interested--and for the purposes of archiving for the next
poor b*stard--I solved my problem with the Dell PowerVault 100T
producing excessive soft errors with DDS4 media (but working fine with
DDS, DSS2 and DDS3). It turns out to be a bug in the drive's firmware
which is present in re
When configuring Amanda to restrict its port ranges for UDP and TCP
"back connections", can a range of `x,x' be used? (ie only one
possible value?). In the case of the TCP sockets, it seems that there
are three of them used (when indexing) and that these may need to be
distinct.
Thanks, B.
> "Gerhard" == Gerhard den Hollander <[EMAIL PROTECTED]> writes:
Gerhard> Dat tapedrives are aparently notorious for getting real bad real soon if
Gerhard> they cannot write in streaming mode . That is, if you are sending data to
Gerhard> the tape at a lower speed than the tapedrive can
Ben> Apologies for the semi-off-topic posting, but this no doubt reaches
Ben> many people with experience in tape drives. My Dell PowerVault 100T
Ben> (an Archive Pyton) has developed a strange problem where it reports
Ben> excessive soft errors for perfectly good, brand new DDS4 tapes (h
Apologies for the semi-off-topic posting, but this no doubt reaches
many people with experience in tape drives. My Dell PowerVault 100T
(an Archive Pyton) has developed a strange problem where it reports
excessive soft errors for perfectly good, brand new DDS4 tapes (having
now tried five in a ro
> "John" == John R Jackson <[EMAIL PROTECTED]> writes:
John> You must have some kind of hostname lookup problem, which is unrelated
John> to Amanda. Amanda tried to look up "master" and "localhost" and got
John> an error. Start checking your DNS configuration, /etc/resolv.conf,
John
Is there any easy way to force a level 0 backup of every disk in the
disklist?
Ben
> "John" == John R Jackson <[EMAIL PROTECTED]> writes:
John> In effect, yes (surprised you, didn't I? :-). It takes the average rate
Yes. :-)
John> You can see those rates with "amadmin info "
As I expected, I am averaging around 2KB/sec.
Ben
> "John" == John R Jackson <[EMAIL PROTECTED]> writes:
John> Planner generates the list of what to do based on size, requests for
John> special service (forced full dumps, etc) and so on. That's a text "file"
John> with one line per disk piped into driver.
Does the planner consider th
I have a couple of machines that are slow and poorly connected to my
tape server. In every instance, I happen to *know* that if these
machines were to appear first in the backup schedule, the backup would
finish more quickly.
Is there a way I can push them to the front?
Ben
> "John" == John R Jackson <[EMAIL PROTECTED]> writes:
>> AMRECOVER Version 2.4.2. Contacting server on scooby ...
>> amrecover: Unexpected server end of file
John> Did you give amrecover a valid config name on the command
John> line?
As it happens, I didn't. ;-( I simply r
Hi. When running `amrecover', I am getting the following error message:
AMRECOVER Version 2.4.2. Contacting server on scooby ...
220 scooby AMANDA index server (2.4.2) ready.
200 Access OK
Setting restore date to today (2001-02-17)
200 Working date set to 2001-02-17.
200 Working date
> "Sergio" == Sergio Pereira <[EMAIL PROTECTED]> writes:
Sergio> Hi folks, I'm trying to use AMANDA 2.4.2p1 but some
Sergio> problems are happening. So, first of all I need to know
Sergio> how can I call amandad, amindexd and amidxtaped on xinetd
Here's my files, which work for
jrj wrote:
Are you writing a new tapeio driver off of the amanda-242-tapeio CVS
branch? That would seem to me to be the cleanest way of implementing
something like this. In fact, another Amanda user contacted me
I've implemented my first pass as a cat-like filter that reads plaintext
Hi.
I'm about to try and wedge a program into the AMANDA pipeline that will
encrypt a dump image as it's being written to tape. Due to a couple of
complications with the algorithm I'm using, the size of the file in the
holding disk may be increased by up to 10 bytes when it's written to tape.
Wi
jrj wrote:
Is this 2.4.2? If so, I think you're not the only one who's mentioned
this. Sigh.
Yes, it is. Interestingly, I think this is the first partition of mine to
receive a level 3 dump.
Ben
>FAILURE AND STRANGE DUMP SUMMARY:
> mars sda7 lev 3 FAILED [data timeout]
It means dumper on your server stopped getting data for 30 minutes (or
whatever you set dtimeout to in amanda.conf).
That's interesting, considering `mars' is the tape server.
Ben
Can anyone help me diagnose what this error message precisely means?
FAILURE AND STRANGE DUMP SUMMARY:
mars sda7 lev 3 FAILED [data timeout]
Thanks, B.
I'm sure they would. However, I'd strongly recommend you start with
the main development branch (the main trunk, w/o any -r option), as it
has a new security model that is supposed to make this kind of thing
easier (more modular).
Okay.
Another concern of mine is that, for security,
>Is it possible that the error message could be improved?
Sure. Do you have a suggestion?
For starters, it should state that the error is coming from the client, not
from amcheck on the tape server. Something like:
"Client-side error: unable to perform reverse lookup on ".
Ben
I see that it's possible to encrypt client/server traffic with Kerberos 4.
Might it be possible to implement a simpler, less onerous security scheme
such as the private key CAST-128 algorithm?
I'd be prepared to have a shot at implementing it, if my patches have some
chance of being accepted. :-)
I don't have a tape changer defined (I found that when I used chg-manual, I
had to be present to run amcheck!). What will happen if I overflow a tape
without a changer defined? Will the backup fail?
Thanks, Ben
jrj wrote:
The only things I can think of to try at this point are a complete
rebuild of Amanda (blow away all traces of the build area you used
before), or upgrading to the latest gcc and building that for the
specific host, or making sure you have all the latest Solaris patches.
Yo
It says that when Amanda tried to do a reverse lookup (IP
203.24.38.228 back to a host name), it failed.
Ahh. Problem sorted, thanks. Name service had died at that machine's site.
Is it possible that the error message could be improved?
Being able to ping the host is irrelevant. I as
I just got a note from amcheck about a problem with one of my client
workstations:
Amanda Backup Client Hosts Check
ERROR: metro: [addr 203.24.38.228: hostname lookup failed]
Client check: 5 hosts checked in 1.692 seconds, 1 problem found
This is nonsense -- I ca
jrj wrote:
>When amstatus reports on estimates, are these supposed to be the estimates
>for the volume of data dumped at the specified dump level? ...
Yes. They are the estimates for the level Amanda picked to be done.
>Every day when
>Amanda runs, I see the same huge estimates
I back up a partition on a remote machine, connected by a 28.8k modem.
After only two days, Amanda has decided to do a level 0 backup of this
partition, which seems strange, if not wrong.
How can I discourage her from doing level 0s until the end of the dumpcycle?
Almost nothing is as bad as doin
When amstatus reports on estimates, are these supposed to be the estimates
for the volume of data dumped at the specified dump level? Every day when
Amanda runs, I see the same huge estimates for disks that, once backed up,
only had a few hundred KB of incrementals to do.
It's a bit confusing!
> I believe this is quite portable:
>
>dd bs=1 skip=257 count=5 if=/dev/tape of=/some/tmp/file
>if test `cat /some/tmp/file` = ustar ; then
> : This is a tar file.
>fi
But wait... You just threw away the first 257 bytes from stdin. Now
what are you going
I'll ask again, how do you do that in a shell script? And remember
that it has to run on every flavor of Unix in the world, not just
Linux or Solaris, so no cheating and using other than the most generic
commands and options :-).
I believe this is quite portable:
dd bs=1 ski
The basic problem is, how do you know (programatically, in a shell
script) that it's a tar image? All we have is the name of the dump
program, which might be "tar" or "gtar" or "gnutar" or
"gtar-1.12+amanda-patches". And this will get even more complicated
when the DUMPER-API is im
jrj wrote:
>(** Cannot do /usr/bin/gtar dumps)
This says that GNU tar is installed in /usr/bin/gtar on the client,
but since amverify runs on the server, it is apparantly not in that
same location, so it could not run it.
Version 2.4.2 tries to handle this better by looking f
martinea wrote:
It means the estimate (127811k) was wrong and the filesystem is larger
than the estimate. It must be dumping something, look for process
activity on your client and server.
I discovered the problem yesterday afternoon. Thanks to Mitch and including
Jean-Louis' ideas, I
It means the estimate (127811k) was wrong and the filesystem is larger
than the estimate. It must be dumping something, look for process
activity on your client and server.
There are five concurrent dump processes running for /dev/sda5:
404 ?S 0:00 dump 0usf 1048576 - /de
amstatus says that one of my partitions has been dumped to 110%. Then it
just sits there, never writing the dump to tape (there are no tapers
running).
scooby:sda5 0 127811k dumping 141056k (110.36%)
What's up with this? I'm running CVS Amanda on the tape server now.
Thanks,
cmarble wrote:
> Is this 2.4.2? If so, there's a known bug that we think is fixed in the
> latest CVS sources. If you can't or don't want to get them, there will
> be a 2.4.2p1 shortly, or ask me offline and I'll send you the patch.
Will I only have to update my 2.4.2 installation
Is this 2.4.2? If so, there's a known bug that we think is fixed in
the latest CVS sources. If you can't or don't want to get them, there
will be a 2.4.2p1 shortly, or ask me offline and I'll send you the
patch.
Yes, it was 2.4.2. One clue I omitted from my bug report is that the d
I've been running an `amdump' for about 16 hours now -- the following dump
(a level 0, as it happens) keeps happening over and over again. When I
reach 100%, it starts again!
dublin:sda4 0 1878319k dumping 1679872k (89.43%)
(8:08:27)
This file system is too large
Hi.
You wrote in the Amanda FAQ:
``This can be wasteful, specially if you have a small amount of data to back
up, but expensive large-capacity tapes. One possible approach is to run
amdump with tapes only, say once a week, to perform full backups, and run it
without tape on the other days, so th
> I want to use this template for labels. I just tried printing the template
> (through Ghostscript) and get an empty PCL output file. Is there something
> weird with this PostScript file that I should know about?
You're supposed to add it to amanda.conf's lbl-templ, so that Amanda
Is there a way for Amanda to eject the tape at the end of a run so that I
can simply remove it each day (and to indicate that the tape run has
actually completed)?
Or should I just run `mt offline' myself?
Ben
I want to use this template for labels. I just tried printing the template
(through Ghostscript) and get an empty PCL output file. Is there something
weird with this PostScript file that I should know about?
Ben
3 dumpers idle : no-diskspace
A bit of simple arithmetic shows me that there is no room in the holding
disk. :-) Sorry,
Ben
I'm doing a test run with about 8 entries in my disklist and Amanda is only
running one dumper. When I run `amstatus' I see:
3 dumpers idle : no-diskspace
taper idle
network free kps: 1984
holding space : 806496k ( 76.91%)
What does `no-diskspace' mean here? I seem to have free networ
I am in the process of debugging my Amanda setup and wish to reuse the same
tape over and over. Short of using `mt erase' to completely erase the tape,
is there a way I can prevent Amanda from aborting because it thinks I'm
overwriting a tape from the backup set?
Thanks,
Ben
>xinetd is running /usr/local/libexec/amandad, which I just re-installed to
>be certain. It's from a build tree whose config.status reads:
>
># ../amanda-2.4.2/configure --with-fqdn --with-user=amanda --with-group=disk
That was not the question. The question was, what user is th
The docs/INSTALL file says to use GNU tar 1.12 -- is there any reason why a
later version, such as 1.13, could not be used (with the provided patches)?
Ben
oliva wrote:
> Amanda Backup Client Hosts Check
>
> ERROR: running as user "amanda" instead of "operator"
Looks like it is the client that is complaining. Maybe xinetd is
still running an older version of amandad, that wants to be started as
Hi.
I configured Amanda with --with-user=amanda and am running all of the am*
programs under the amanda username. When running amcheck, I get:
Amanda Backup Client Hosts Check
ERROR: running as user "amanda" instead of "operator"
What gives here? Of cour
> Anyone got any suggestions?, I am running Amanda v2.4.1
First, this should probably have gone to amanda-users, and not
amanda-hackers, but that nit aside, my guess is the upgrade "upgraded"
your /etc/inetd.conf file and you will need to put back the entries
for amandad, etc.
Red
I am trying to back up a single partition having just installed Amanda. I
thought I'd try with this in my `disklist':
scooby sda8 always-full
I get the following error, but can't work out what I'm doing wrong. Any
tips? In general, how can I diagnose client-side problems?
Thanks, B.
Aman
Hi,
This is what my /etc/inetd.conf looks like:
amandadgram udp wait amanda /usr/local/libexec amandad
This is incorrect. The second last argument is a full path to your server
program, not just the directory. It should be /usr/local/libexec/amandad.
Ben
Hi,
I'm new to Amanda, but am configuring it for a spanking new Dell PowerVault
tape drive -- which has a Archive Python DDS4 unit in it. From the mail
archives, I got this tapetype:
define tapetype PV-100T-DDS4 {
comment "Dell PowerVault 100T"
length 16534 mbytes
file
65 matches
Mail list logo
