Hi There!
> ---
> amrestore: 7: restoring gateway.hdb1.20010919.0
> File size limit exceeded
> --
The file is too large for a pre-2.4 series kernel. Try unpacking it
under a 2.4 series kernel...
DSL
If you actually READ what Amanda said, it's not complaining about the
length of your disklist (1). It's getting a "badly formatted response";
I'm not sure why. Try checking the debug files on that machine in
/tmp/amanda.
DSL
(1)
How does one interpret this:
mpe-3. /sistemas/folha/folha
Chandra!
> server --with-user=(username) --with-gorup=(groupname). Then installation
> went through the rigourmole but couldn't find flex but gave up when it
> couldn't find lex. Can someone shine me shine light as to why this crashed.
An actual posting of the error would help, but it probably
Hang on a moment here. What we should be thinking is that "someone
thinks there should be a cross reference to this question in the
FAQ...". We all categorise things differently to each other so what
might seem like a sensible place for a question to you, may not be
sensible to the next person...
Oh?
> If you use tar (as opposed to dump) as the low-level utility, you can
> use a single amanda config, with a line in the disklist for each 10G
> subdirectory.
I didn't know one could do that. How?
DSL
--
ACCUSATION:
"David Newall, you have not read your Microsoft Manual"
REPLY:
"No I ha
Tyrone!
> I've created an user called amanda and a group called backup on the client
> and server machines. The amanda user is in the disk group as a secondary
> group on the client machine.
>
> What am I doing wrong? If you know of any source online where I can find the
> answer? Thanks in adv
> (*) Dump may work fine for you a thousand times. But it _will_ fail under
> the right circumstances. And there is nothing you can do about it.
Let's generalise:
[any program and anything] may work for you a thousand times. Bit it
_will_ fail under the right circumstances. And there is nothi
Todd!
> Marty says his samba setup works, but because of the fallback from wins to
> broadcast the lookup takes longer than amanda is willing to wait. Amanda
> times out and as far as amanda is concerned, smbclient failed. I'm not
> even sure what the implications of this are or how to make it
Marty!
I suggest you put your asbestos, flame resistant suit on...
> Again: THIS IS NOT AMANDA'S FAULT! IT IS SMBCLIENT'S FAULT!
You obviously cannot understand what I am saying, or you have not
followed this thread. If you cannot understand English I will have this
translated into any other
The error I see is:
"Host is down or invalid password"
Essentially my guess is that Amanda via smbclient attempts to use a
local wins server to resolve the Netbios name which didn't work because
I didn't have a wins server configured. Hence, rather than wait for the
broadcast to function (it ca
Ummm!
> > >added interface ip=128.84.247.9 bcast=128.84.247.255 nmask=255.255.255.0
> > >added interface ip=128.84.247.9 bcast=128.84.247.255 nmask=255.255.255.0
> > >added interface ip=128.84.247.9 bcast=128.84.247.255 nmask=255.255.255.0
> > >added interface ip=128.84.247.9 bcast=128.84.247.2
Steve!
> Can I just remove the holding disk directories that were created? I don't
> particularly want to flush these to tape, but I also don't want to break
> anything.
I wouldn't "just remove" them if I were you, especially if the dumps
were incremental. If you remove them it's possible you'l
Verdon!
> i was wondering if it is possible to extract data from the holding disk
> with amrecover ?
"amrecover" will speak to whatever tape or holding disk happens to have
the file or files you request. So the answer is, yes.
> if it isn't is suppose i had to use amrestore?
"amrestore" can t
Hi There!
> Sorry for this easy question . I don't have tape drive , can I use
> amanda to backup my system.
John Jackson has developed a function that lets you pretend that a disk
drive is a tape device. This is in one of the latest beta releases. If
you don't want to do that it is possib
Oops!
> However the syntax David Lloyd gave was not quite right. It should be:
>
> host.your.domain disk-to-back-up dump-type
Damned Samba backups in disklists and god knows what...
:-(
--
And though you turn from me
To glance behind
The Phantom of the Opera is there...
In
I've just produced this for an HP-Pure Store DLT1 drive. It looks about
right (the drives claim 40Gb). This was created with mt -f /dev/nst1
datcompression off and with the tapetype that comes with amanda-2.4.2p1.
define tapetype HP-DLT1E {
comment "just produced by tapetype program"
len
Andrew!
> Amanda Tape Server Host Check
> -
> /holdingtank: 8182314 KB disk space available, that's plenty.
> NOTE: skipping tape-writable test.
> Tape nwc0 label ok.
> Server check took 17.913 seconds.
> "disklist", line 15: disk dumptype expected
> "disklist", line
Hmmm!
Amanda is running:
sendsize.debug:sendsize: spawning "/usr/bin/smbclient" in pipeline
sendsize.debug:sendsize: argument list: "smbclient"
"\\THESHARE\thedirectory" "the_password" "-d" "0" "-U" "backup" "-E"
"-c" "archive 1;recurse;du"
And it's working. Notably the command it says its run
Hi There!
I have the 2.4.2 sources and pulled down the latest patch for 2.4.2.
> Does it fail when you use amcheck? What's in /tmp/amanda/selfcheck*debug
> on the Samba machine?
No.
> I assume the Samba machine is running Amanda 2.4.2+? That's where it
> counts, not on the tape server.
Hm
Hmmm!
I have amanda-2.4.2p1 (I recently patched it), and despite the
documentation saying /etc/amandapass should look like:
[/etc]% cat amandapass
//NAME/SHARE user%password
It only works if I use
[/etc]% cat amandapass
//NAME/SHARE password
I receive "host down or invalid password" errors o
Hmmm!
I have compiled Samba 2.4.2 with:
./configure --with-libsmbclient (and the other options are the same as
the ones that worked before)
Added:
[adlcds1 ]# cat /etc/amandapass
//WEBAPP/Web asifiwouldtellapubliclist
Added:
[adlcds1 ]# cat disklist
adlcds1 //WEBAPP/Web comp-tar
BUT
amche
H
> i 'm a Amanda Newbie using amanda-2.4.2, executing:
> su amanda amlabel -f amanda.conf DailySet1-000
> getting the error message:
> amlabel: amlabel: cannot execute binary file
>
> I don't know what i did wrong...
It might be worth BECOMING the amanda user and doing it
Oops!
> To disable it completely, I think you'd need to hack the source.
Obvously you don't need to but I wouldn't if I were you :-)
DSL
--
CWA - Chin Waggers Association
"Let's sit around and complain about something.
Our topic for today is: ADSL...h...that `L'
stands for Linux doesn'
Hmmm..
To disable it completely, I think you'd need to hack the source.
DSL
Charlie!
> Amanda Backup Client Hosts Check
>
> ERROR: office: [addr 192.168.0.83: hostname lookup failed]
> Client check: 1 host checked in 0.109 seconds, 1 problem found
>
> (brought to you by Amanda 2.4.2)
>
> But 'office' is really pingable in fact,
What d
Hi There!
> root@fileserver:/usr/local/sbin > ./amrecover Daily
> AMRECOVER Version 2.4.2-19991216-beta1. Contacting server on fileserver ...
> 220 fileserver AMANDA index server (2.4.2-19991216-beta1) ready.
> 200 Access OK
> Setting restore date to today (2001-03-12)
> 200 Working date set to
amadmin MYCONFIG force [share name]
You could use a script to walk through you dump file thingo to do
this...
DL
--
Domine O venite O sacramentum eo deo
Domine O venite O sacramentum eo deo
Omnem crede diem tibi diluxisse supremum.
Sacramentum eo deo
Ramesh!
> "/usr/local/etc/amanda/confname/amanda.conf",line 0:default tapetype EXABYTE
> not defined
> amcheck: could not find config file
> "/usr/local/etc/amanda/confname/amanda.conf"
It can't find your configuration. Drop the -m switch - all that seems to
do is make amcheck go quiet. Dependi
The alternative is to do what my local LUG does would be to add:
* X-Mailing-List: <[EMAIL PROTECTED]> archive/latest/4749
(naturally amand-users wouldn't claim to be linuxsa :-P)
And filter on that...every now and then someone will send you something
directly and it will end up in the wrong b
U...
> For me the ideal would be a test-mode where I could rerun repeatedly
> with the same tape, remove the switch and then it would be production,
> though I realize this may not be feasable with the amanda design
> philosophy. Still there must be a standard way to test. How do I
> create
Ummm...
> The DNS is set up correctly. I have set up the primary DNS. It is working
> fine a lot of time.
Is it working fine ALL the time or does it fail sometimes?
DL
--
You have a deformed comb,
so go suck eggs...
Adolfo!
> for generating the right tapetype def. My dude is if with the "-e"
> parameter. Have I put 4g or 8g?
What is a "dude"? That is a stupid question but I have no idea what it
means in the context you have said...
DL
--
You have a deformed comb,
so go suck eggs...
Yikes!
> You can actually relabel the tape just after you have amrmtaped it. For
> AMANDA, after "amrmtape" the tape is "new", even if for you it is "old"
> ;-)
I refuse to immediately reuse a tape after it's been amrmtaped because
one of my other fellow system administrators amrmtaped a real t
John et al:
> >/usr/local/amanda/sbin/amrecover -s amandaserver.mydomain.com
>
> Are you certain the default configuration built into amrecover is the
> config you wanted to use? Put a different way, try this:
I gave up using the "default" configuration because it would always
"default" to so
Hi There!
> I looked up the websites, and saw there are some requirements, which are:
>
> tar1.12, samba1.9.18p10, perl5.004, readline2.2.1, awk3.0.3, gnuplot3.5
>
> Do you really have to have installed before using amanda?
If you plan to use tar get the very latest version. You don't need to
Hi!
> I've never had to post a question until now because I have always
> been able to find the answer by searching past emails - here's to a
> great program and it's great users! So this is my maiden voyage. I
> just upgraded to 2.4.2 and everything works fine, except that amflush
> doesn't del
Bernhard!
> And verify DNS reverse lookup
Off the top of my head that gives a different error...
:-)
--
GOD SAVE AMERICA!
- because President Bush, the Second Will Not!
Roshan!
> ERROR: stat: [hostnames do not match: amanda1 amanda1.popken.de]
> Client check: 1 host checked in 0.264 seconds, 1 problem found
amanda1 is not the same as amanda1.popken.de. They don't match...
specify:
amanda1.popken.de in the disk list file followed by the other normal
stuff...
Hmm...
> couple of choices to fix this: You could just let it ride, knowing that that
> disk isn't getting backed up, and sometime in the next few tapes, AMANDA
> might have enough space (because other disks backups get bumped to higher
> incremental levels) to do the level 0 backup; OR, you cou
Justin!
> The first one started to occur after rebuilding my Tape Backup Server after
> a Hard Disk Crash. I changed it from a SCSI disk to a IDE disk. Now when
> ever it goes to dump any of the file systems on that system (sol), it gives
> this in the AMDUMP report:
> solhda1 lev 0
Phil et al:
> one of two ways... either run a cron job to execute your Perforce checkpoint
> program on a cron job x mins before the cron job for amanda happens knowing
> that the perforce program takes x mins to complete (and of course some buffering
> wouldn't hurt) and then have the cron job
Chris!
> Why does if= work and if= does not? Is this
> because I have an ext2 filesystem on the disk and copied the file with
> cp?
If it's a file on an ext2 system, just use tar directly:
tar -xzvf the_file
OR
tar --extract --gzip --verbose --file=the_file
DL
--
The new century begins at
Hmm!
> Of course, a DNS server would "simplify" things. But besides the
> theoretical point of "Occam's razor" (what is simple?), we have all
> these security announcements for bind, that make the blood chill, even
> with the most nuclearly hardened packet filter...
Without being too laconic, y
Hmmm...
Someone could write a device driver that made IDE drives look like tape
drives :-P
DL
Denise!
> I forced a level 0 to run this afternoon - when it was done no AMANDA MAIL
> REPORT was generated.
>
> When I looked at the current info via amadmin I noticed that all of my
> partions were backed up to tape except sda10 which was 'forced to a level
> 0 dump on next run'.
Was it, or
Casile!
> *** A TAPE ERROR OCCURRED: [[writing file: Input/output error]].
> *** PERFORMED ALL DUMPS TO HOLDING DISK.
>
> THESE DUMPS WERE TO DISK. Flush them onto a new tape.
> Tonight's dumps should go onto 1 tape: a new tape.
>
> FAILURE AND STRANGE DUMP SUMMARY:
> davinci01 sda1 lev 0
Sven!
> Which tape would amanda use if she could choose (changer) between
> daily06 - daily10? Does that depend on the order of the tapelist (I
> think so)?
That and other things.
> What is a new tape? Is daily06 a new tape (take a look at my tapelist
> above)?
A tape that has never been used
Casile!
> FAILURE AND STRANGE DUMP SUMMARY:
> raffaello /etc lev 0 FAILED [missing result for /etc in raffaello
> response]
I assume that you are using:
* the latest dump (http://dump.sourceforget.net /)
* the latest GNU tar
>
> Amanda 2.4 REQ HANDLE 000-28360508 SEQ 975705290
> S
You could try running amrestore rather than amrecover on that tape...and
then using restore or tar to get it back...I've seen amrecover get
bamboozled at times before :-(
DL
Brian and Alexandre!
> > but once the process is finished, i get back the the amrecover>
> > prompt, and i cannot find the stuff i wanted to be restored.
>
> Note that stuff will be restored into a directory tree that mirrors
> the tree of the backed up filesystem. So, if you restore bar/baz t
You can kind of do it. Basically:
Set the reserve parameter very low:
reserve 0
And set the tape device to /dev/haha (unless you actually have a device
called "/dev/haha").
You'll need to clear the backups manually when you want to get rid of
them though...given that AMANDA names the direc
Tom!
> I remember for awhile, there were problems with some versions of tar and
> amanda. Is that still the case and if it is what versions are known to be
> compatible with 2.4.2 and what versions are not. I am using the binary
> tar-1.13.17-8 (i386.rpm)
We're using 1.13.17-3 and it
Tom!
> I've done about every alteration of the permissions of
> /usr/lib/amanda/runtar that I can think of and I still get the error
> below.
>
> Any direction would be appreciated!
My guess is that it's a setuid program; I find these particular styles
of programs difficult to get the permissi
Chris!
> My suspicion is that GNU tar, which I use in the version 1.12, somehow
> cannot compute incrementals right, for filesystems of vfat type that are
> mounted the way I described above...(?)
Eeck!
Even RedHat have a later version of GNU tar than 1.1.2 and (honestly)
they're not known to
Edwin!
> Whenever I force a full dump of one directory on host 'A' the level 1
> dumps for the same host will fail.
It could be because AMANDA believes you don't have enough tape space...
> I forced a level 0 dump of /home on Tuesday and now all the other dumps
> for Host A fail... e.g. /etc,/
Paul!
> Any idea why amanda seems to be disregarding my exclude.gtar file?
I found adding a "*" before a directory name totally stuffed things up.
I have things like:
./squid
Which gets rid of /home/squid and such...
DL
--
Don't you find it rather touching to behold
The OS that came in from
Someone I work with accidentally amrmtaped the wrong tape (number 10),
but immediately flushed what was in the holding disk to the correct tape
(number 15). Therefore I have the following situation:
* I have all of tape 10's data (but it may or may not have a header)
* I have the curinfo records
Hi There!
Excuse my odd subject but I can't quite decide what has caused my whole
AMANDA configuration to crash.
On the weekend I built, installed and ran the tapetype program on my
system. Unfortunately I had to change tape drives before I did this but
it was exactly the SAME model (Seagate ST
Joi!
> Amcheck tests and reports on all of these conditions. Didn't you put it
> into your nightly backup script as suggested in the install guide?
Yes. And amdump still dies with no error if one of them doesn't work.
Personally, I would be inclined to set the logic to:
* can't write to /tmp
Joi et al:
> (I'm not positive about the read-write, but it definately needs read.)
It appears that AMANDA must write to:
* its config directories
* /etc/dumpdates (if you're using dump)
* /etc/amandates
* /usr/adm/amanda or wherever you've set the log directories to
* /tmp
If it can't write t
Daniel!
> Does the AMANDA conf directory need to be writable?
No, provided you set tapelist, disklist etc to some other, writable
directory.
> read-write if it really needs it. Amcheck reports conf directory not
> writable. I'm thinking of commenting the conf directory check out of
> amcheck.
Ummm, what happens when you get a REAL error?
DL
The seek errors you're seeing generally occur because some other process
is atempting to use the blocks that AMANDA (rather dump) is attempting
to back up. I've noticed that if I get enough of them it just trashes my
backup and I have to do it again :-)
DL
--
Do you believe in life after love?
John!
> What does amcheck have to say?
Everything is OK (except I don't have any spare tapes for it to do a
tape write test, but I've fixed that problem at last).
> What's in /tmp/amanda/sendsize*debug on adlcds1.nci.com.au?
I'm not certain, but I'll have a look asap :-)
DL
--
Do you believ
Hmm!
I thought AMANDA only backed up whole "disks" or "partitions"...i.e:
[lloy0076] % df
/dev/hda /usr
/dev/hdb /tmp
And I would only be able to backup ALL hda or ALL hdb, but not just
/usr/bin without getting into GNUTAR exclusions and such...maybe I'm
wrong...
DL
I forgot to say that I'm running:
* RedHat Linux 6.2
- vanialla except for important updates
* Latest Stable Release of dump for Linux
- I got an RPM from sourceforge...
dsl
--
Do you believe in life after love?
I can feel something inside me, say
I really don't think you're strong enoug
I have a small problem (again). The tools I'm using are:
* amanda 2.4.2
* dump 0.45b19 [the latest stable from the sourceforge site]
Yet I'm getting estimate failures. I have NO idea what is causing
them.../raid should be relatively empty, but adlgw should all work.
Things I have been doing inc
Hi!
I've done:
[amanda %] amadmin CONFIG force host.our.host disk
And received the confirmation message that it worked (forgotten the
exact message but the curinfo entry definitely changed according to
freeveracity) but the amanda mail report reports it as a level 5
dump...what's up here?
DSL
Hi Again!
> so, basically, tunnelling? but, would that override the requirement for
> .amandahosts?
No. I think .amandahosts. would still need to exist.
> from reading the docs on setting up, I get the impression
> that to even ackup the server itself, you have to have a .amandahosts file
> s
Hmm!
I'm almost certain you could forward AMANDA's default ports through SSH:
i.e.
ssh -C -L 100080:amandahost:100080 amandahost
Or some such thing...
DL
--
Non navis acta hieme portum posse
Capiet nisi dominum
Patrem filiumque
Et spiritum sanctum
George!
> I'm still using 2.4.1p1. Can anyone give me good reason(s) to upgrade to
> 2.4.2? What do you gain by going to the new version, if anything?
>From what I understand the code for 2.4.2 is stable. It does have some
more sane error messages, although to be honest I've not found any of
AM
I'm already using 2.4.2 in a production environment. That's out enough
for me...
DL
--
Words are easy; words are cheap
Much cheaper than our priceless land
But promises can disappear
Just like promises in the sand...
72 matches
Mail list logo
