Yay!!! I'm reading and writing!!!
Many thanks to (in no particular order): Seth Mos, Robert Wideman, Matt
Domsch and Ashley from the amanda lists...
I got it working by using ide-scsi, and the following lilo.conf entry:
append=/dev/ht0=ide-scsi
and...
Then put this in /etc/rc.d/rc.local:
and phil cooper! sorry!
Chris Herrmann
Far Edge Technology
p. 02 99553640
f. 02 99547994
m. 0403 393309
http://www.faredge.com.au
Before running amcleanup I checked the content of my
holding disk. It contained a subfolder with the date
of the normal run, but the folder was empty.
There's not enough information yet to know what's going on with your
setup. You need to get through a complete amdump without it aborting
Hello All,
After adding ALL: ALL to my /etc/hosts.deny file, amrecover stopped working.
Before I go on, let me explain how I use amrecover; I never use it from the
client, only from the server. I recover files and folders to a web directory
on the amanda server and the clients pick them up
OK, it turned out to be the fully qualified (vs not) name in
.amandahosts.
I changed to just use the short name (which is what was used in the
amanda error message and amcheck doesn't give any errors now.
I found this in the faq-o-matic.
gene
On Mon, 2002-02-04 at 10:18, gene wrote:
On
Amanda Backup Client Hosts Check
ERROR: db-test.ems.sat: [GNUTAR program not available]
GNU tar exists on the client machine, I can log in as amanda, and gnu tar is
in amanda's path. I can also execute gnu tar as the amanda user. Owners for
tar are:
John,
No and Yes. /usr/local/sbin and /usr/local/libexec are on bali:/usr/local
which is of course local to bali but remote to all (other) amanda clients.
Also amanda server laksha (with clients laksha and andaman) mounts
/usr/local from bali.
The critical programs (the ones that are owned by
On Mon, 4 Feb 2002 at 10:55am, Davidson, Brian wrote
Amanda Backup Client Hosts Check
ERROR: db-test.ems.sat: [GNUTAR program not available]
GNU tar exists on the client machine, I can log in as amanda, and gnu tar is
in amanda's path. I can also execute
Send mail to
listname[EMAIL PROTECTED]
and when you want to unsubscribe, use the following line in the body:
unsubscribe your-email-address
/amanda
insgesamt 12
drwx--3 operator disk 4096 Feb 4 11:00 .
drwxrwxrwx9 root users4096 Jan 31 23:36 ..
drwx--2 operator disk 4096 Feb 4 11:00 20020204
[root@milestone amanda]# ls -la /big/amanda/2*
insgesamt 8
drwx--2 operator disk 4096
Hi everyone
I've used amanda a while now using xfsdump on mostly SGI Irix machines.
Recently I added a disklist entry that would use GNUtar though. But I
get the following error and I'm not sure what to make of it. It seems
tar is unable to accurately estimate the dump size. Here's all my
On Mon, 4 Feb 2002 at 12:13pm, Jan Boshoff wrote
get the following error and I'm not sure what to make of it. It seems
tar is unable to accurately estimate the dump size. Here's all my
outputs:
What's in /tmp/amanda/sendsize*debug on the client?
Oh yeah, and finally:
Hi fellows, finnally I've got amanda running I have made some
tests and I could see that amanda is what I was looking for, Now I
want to make amanda use a tape per day but I want it to make full
backups of my data each day I run it , How can I do this ??
Thanks in advance fo ryour answers
On Mon, 4 Feb 2002, Brian Cuttler wrote:
Unless, IRIX, unlike Solaris, is stripping the suid bit across the
NFS network mount. I mean, this works fine on the Solaris config
but is a problem on IRIX.
IRIX, like unix only different.
Come on, be fair. IRIX, like _ANY_ unix will strip the suid
Is there a way to determine what planner determines as the compressed
backup size of tthe various filesystems in your disklist while doing the
initial estimate.
I know when the completion report is sent you get the average
compression rate. I was just wondering if that is compiled initially
Thanks for the help Josh
I've upgraded to 1.13.19.
Also, here's the output of /tmp/amanda/sendsize*debug:
asking killpgrp to terminate
calculating for amname '/users', dirname '/users'
sendsize: getting size via gnutar for /users level 0
sendsize: running /usr/freeware/libexec/runtar --create
On Monday 04 February 2002 12:25, Alvaro Rosales R. wrote:
Hi fellows, finnally I've got amanda running I have made some
tests and I could see that amanda is what I was looking for, Now I
want to make amanda use a tape per day but I want it to make full
backups of my data each day I run it
Ok,
The answer to this is probably in front of my face. I am running
Amanda-2.4.2p2 on Solaris 8. I back up WinNT and Win2k clients at this
point, but would like to add in some RedHat clients. I set up the client on
a RedHat 7.2 box, but it failed on me. How can I find out why it failed?
On Mon, 4 Feb 2002 at 9:49am, Brandon Moro wrote
The answer to this is probably in front of my face. I am running
Amanda-2.4.2p2 on Solaris 8. I back up WinNT and Win2k clients at this
point, but would like to add in some RedHat clients. I set up the client on
a RedHat 7.2 box, but it
On Mon, 4 Feb 2002 at 12:37pm, Don Potter wrote
Is there a way to determine what planner determines as the compressed
backup size of tthe various filesystems in your disklist while doing the
initial estimate.
I know when the completion report is sent you get the average
compression
On Mon, 4 Feb 2002 at 12:42pm, Jan Boshoff wrote
Also, here's the output of /tmp/amanda/sendsize*debug:
asking killpgrp to terminate
calculating for amname '/users', dirname '/users'
sendsize: getting size via gnutar for /users level 0
sendsize: running /usr/freeware/libexec/runtar
Well, last nights test, using not HW compression and software compression
only was interesting. amverify failed miserably again on all the tape files,
an example of the output.
GDZN07 (agree-10._usr_local.20020204.1):
amrestore: WARNING: not at start of tape, file numbers will be offset
Brandon,
Sorry - lack of sub-text in email. I wasn't really meaning to
rag on IRIX, I've spent my whole tenure here working on it.
I was contrasting it with Solaris because Solaris is doing
what I want it to do and IRIX isn't. The truth is that one
of the great joys of working on unix is that
I've used amanda for several years and never had and issue compiling it
under anything. However, I am having problems compiling it on a Sun
E4500. I looked through the old list archives and there isn't a mention
of this problem. Compilation hangs on uparse.c, without an error or
warning of
Beautiful. I was hoping it was something simple. Now to re-read the
crontab manpage.
Thanks again.
On Fri, Feb 01, 2002 at 09:58:01AM -0500, Joshua Baker-LePain wrote:
On Fri, 1 Feb 2002 at 1:33am, Ashley wrote
I'm trying two configurations:
Archive to run once a week. Dumps full
I neglected to say what version of gcc I'm running:
% gcc --version
2.95.3
Robert Haskins wrote:
I've used amanda for several years and never had and issue compiling it
under anything. However, I am having problems compiling it on a Sun
E4500. I looked through the old list archives and
I've modified the /etc/exports file to export my bali:/usr/local
for root (though allowing root only from specific clients).
I've made no changes to /etc/fstab since we already didn't have
the nosuid option on the mount for the partition.
I've confirmed that I can create files on /usr/local
Hello,
I have a few question about tape changers LTO.
I know that amanda can not split a dump across multiple tapes, so if a
dump was too large to fit on the tape, will amanda write the dump to the
next available tape in the changer?
Does amanda support more than one tape device, and if so can
On Mon, 4 Feb 2002, Brian Cuttler wrote:
Should I expect this error when running amcheck on the amanda server
which also have /usr/local as a local XFS partition ?
I use NFS automounted amanda clients here with no problems. I have the
partition with the amanda software installed exported like
It would appear that there I am not getting a `selfcheck*debug.'
Here is what I have:
cd /tmp/amanda
ls -ltr
-rw---1 amanda disk 2081 Feb 1 16:47
amandad.20020201164738.debug
-rw---1 amanda disk 1624 Feb 1 16:49
sendsize.20020201164910.debug
-rw---
Using AMANDA version 2.4.2p2 on OSF/Tru64 v5.1
On the client side, amanda is sending an inappropriate parameter to
the /sbin/dump
=
sendsize: running /sbin/dump 0Esf 1048576 - /net/home1
running
Hi Everyone
I am trying to setup the amanda client on a TRU64 in particular OSF1
V4.0. (Note the amanda client is amanda-2.4.2p2)
This means that I need to apply the advfs.diff patch. To do this I
believed that I need ed to go into the client-src directory then type
patch getfsent.h
So, I upgraded my linux kernel to 2.4.17. I'm running a redhat system,
originally 7.1. I have the mt-st package version .5beta release 10.
Occasionally when I attempt to run an amcheck, my system merely stops. No
kernel panic, not segfaulting, it simply stops. Does anyone know of this
every machine I've tried to run 2.4.17 upto 2.4.18-pre4 crashed. those
kernels seem to be shit. although there are people who have had success.
I'm running 2.4.18-pre7-ac1 now which seems to have fixed the problem.
stick with 2.4.16 till 2.4.18 is released.
On Mon, Feb 04, 2002 at 08:42:13PM
On Mon, Feb 04, 2002 at 08:42:13PM -0500, Chris Dahn wrote:
So, I upgraded my linux kernel to 2.4.17. I'm running a redhat system,
originally 7.1. I have the mt-st package version .5beta release 10.
Occasionally when I attempt to run an amcheck, my system merely stops. No
kernel panic,
Chris Dahn wrote:
So, I upgraded my linux kernel to 2.4.17. I'm running a redhat system,
originally 7.1. I have the mt-st package version .5beta release 10.
Occasionally when I attempt to run an amcheck, my system merely stops. No
kernel panic, not segfaulting, it simply stops. Does
On Tue, 5 Feb 2002 at 5:51pm, Glen Eustace wrote
It would seem that we have some kind of conflict with hardware and software
compression. If both are on, the backups can not be restored. I have managed
to turn off software compression and that seems to cure the problem but would
prefer
Glen Eustace wrote:
It would seem that we have some kind of conflict with hardware and software
compression. If both are on, the backups can not be restored. I have managed
to turn off software compression and that seems to cure the problem but would
prefer to do software and not hardware.
I had a similar problem that meant amverify was not working. For some
reason tar was not available. I had to delete configure.cache, make a
symlink /usr/bin/gtar - /bin/tar, chown amanda:disk /usr/bin/gtar and then
./comfigure bla.bla. -with-gnutar=/usr/bin/gtar
versions: amanda 2.4.p2,
Hi,
I have been compiling that latest stable CVS branch of Amanda (co amanda)
plus the krb5 module in the amanda-krb-2 CVS tree, for an transition to a
krb5 aware Amanda from a Krb4 install. Below is the result from a Tru64
v5.0 system (this src tree has already successfully compiled on BSDI).
Please, I want to unsubscribe me from this list.
Tell me how.
42 matches
Mail list logo
