> The slow client is a Toshiba Magna 3000 with a single 18-GB SCSI disk. I am
> backing up another partition on the same disk on the same host at the same ti
>me with no problems. I do not see any disk or network errors on either the cl
>ient or the tape backup
> server.
The next thing I'd try
>Ok, I am ready to try debugging. ... I am not
>sure how to debug the server side ...
Take an amrecover*debug file from a failed run. Look for the lines
that start with ">". Those are commands amrecover sent to amindexd.
Run gdb as the Amanda user on the server and start amindexd with the
"-
>When I run amcheck I get 'selfcheck request timed out' while trying to
>connect to localhost ...
First, don't use "localhost". It will bite you eventually. Use the
fully qualified domain name of the host. Any modern network code will
notice they are the same thing and you won't lose any perfo
>I am having a strange problem here, I'm backing up one of my servers
>and in the middle of the dump (actually near 35%) the client crashes.
It's almost impossible for Amanda to have done this. Amanda, and
everything it runs for you (e.g. GNU tar), are strictly user level
programs. They cann
>FAIL dumper cobalt01.somewhere.nl /home 0 [data timeout]
>...
>Could it be because of MySQL (b)locking read-access to the tar process?
As Olivier said, it's unlikely to be a locking problem. Unix does not,
in general, apply mandatory locks. They are advisory, meaning a process
(such as a backu
>I'm having a problem backing up files on a NT-machine ...
As Olivier said, all those errors are from Samba, not Amanda. You need
to ask your question on one of their mailing lists.
>Jens Rohde
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
>Still, AFAIR, standard Amanda install puts things into
>/usr/local/etc/amanda, /usr/local/libexec and /usr/local/var/amanda at
>least...
Amanda uses the GNU autoconfigure tools, which in turn create all the
Makefiles and install rules. If you don't like where things are put,
complain to the GNU
> Dump back-up a complete disk partition, so it simply goes disk block
>by dick block and does not bother about the filse system logic set
>above the disk blocks.
That's not quite right. Dump knows as much about the file system
structure as the kernel does. For instance, it backs up one file at
> Its actually not. 192.168.X.X is not routed through the internet
> so it will be very hard to "jump" on it, especially if you mount it
But on the public interface of your fire wall is routed to
internet. And more service you add, more yu are prone to a bug in one
service. And if you miss config
Hello,
I don't know about you, but it get me a bit nervous to know that
passwords are available in clear text in /etc/amandapass (I mean
password for Samba). While it means little for Win9x, I have a couple
of NT servers and I don't fancy having those allmighty passwords so
readable.
I did a sho
>I'd like client hosts to do things like shut down database servers before
>backup, and then restart them after backup.
This will be handled much better when the DUMPER-API is available.
For now, the traditional hack is to use --with-gnutar and point that at
a script on the client that does the p
I'm using Amanda 2.4.2.p2 on RedHat 7.1 & 6.2, and it is great! Thanks to
everyone that contributed to it.
I'd like client hosts to do things like shut down database servers before
backup, and then restart them after backup.
Is there a facility to do this in Amanda that I've missed, or has anyo
s security check passed
> 6
amrestore_nargs=6
> -h
> -p
> 0n
> malt.nctimes.com
> ^/opt$
> 20010622
Ready to execv amrestore with:
path = /usr/local/sbin/amrestore
argv[0] = "amrestore"
argv[1] = "-h"
argv[2] = "-p"
argv[3] = "0n"
>... I hacked the script a bit to send mail *or* send to stdout (by
>means of a -m switch, the same way amcheck does).
That's probably a good idea.
Could you post the change again but use a context (-c) or unified
(-u) diff? Plain diff cannot be applied with "patch".
Any chance I can get you t
>Extracting files using tape drive 0n on host malt.
That ("0n") can't be the right device name. It needs to be the whole
path, e.g. "/dev/rmt/0n". Try setting it with the "-d" amrecover option.
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
On Fri, Jun 22, 2001 at 11:02:09PM +0700, Olivier Nicole wrote:
> Jobst,
>
> >Well I was more after:
> >
> > /home/amanda/configs #or whatever -> the backup configs
> > /home/amanda/logs
> > /home/amanda/gnutar-lists
>
> Whatever, instead of making an amanda subdirectory here and there
>I'm using the 2.4.2p2tapeio branch. This should behave like the normal
>2.4.2p2 version, right?
Yes.
I just looked at the code and it appears a change went in a while back
(like, 1999 :-), that flipped the order of port request attempts. It
used to be:
* try a reserved port.
* try the us
Jobst,
>Well I was more after:
>
> /home/amanda/configs #or whatever -> the backup configs
> /home/amanda/logs
> /home/amanda/gnutar-lists
Whatever, instead of making an amanda subdirectory here and there,
make ONE amanda directory, and as many sub-dirs as necessary.
Beside, under Uni
Just getting things setup here, thanks to JJ for all the help in email.
Having a bit of trouble with amcheck, getting this error:
"amanda.conf" line 0: default tape type EXABYTE not defined.
amcheck: could not read amanda config file
We didnt add any "EXABYTE" stuff in there at all.
the perms
>The two files are both using the special danish character 'ΓΈ' (oe) in
>the filename. Same error occur on an other NT-machine.
>Any surgestions?
Don't use any strange character in the filename :)
You could try to see in /tmp/amanda/senddbackup.* and find the
smbclient command that was used, see
>Could it be because of MySQL (b)locking read-access to the tar process?
>since MySQL operates under the /home directory? I sure am going to try.. (I
>installed it in about the same period..)
I do back-up MySQL database without problem. If the database is
updated during the back-up, it will issue
Hi John!
> >extracting files using tapedrive 0 on host fileserver
> Note the "tapedrive 0". That can't possibly the path to your tape drive.
> You probably need to put "-d /dev/whatever" on the amrecover command line.
For security: My NoRewinding device ist /dev/nst0.
Shall i take this device
Ok, I am ready to try debugging. I have compiled the code with the -g
option. I have tried gdb, which I am new to unix debugging, and I am not
sure how to debug the server side - ie. the call to amindexd from amrecover
via the send_command routine (I have a breakpoint in there, but I am not
su
Hi !
I am having a strange problem here, I'm backing up one of my servers
and in the middle of the dump (actually near 35%) the client crashes.
The fact is that it happened to me twice on this machine. I don't think
it's a corruption problem since the other time it happened it wasn't on
this
Hi
I'm having a problem backing up files on a NT-machine, using smbmount. A
cut from the log:
--- CUT ---
/-- afs1.eos //lemon/IntraToolsFiles lev 0 STRANGE
sendbackup: start [afs1.eos://lemon/IntraToolsFiles level 0]
sendbackup: info BACKUP=/usr/bin/smbclient
sendbackup: info RECOVER_CMD=/us
> I found that all the files required by amanda are "all over the place".
> Wouldnt it be a good idea to make amanda default to place everything in
> /home/amanda or at least $HOME? This way you would have ALL files at
> one position only .
Blame the person that compiled the package!
On Fri, Jun 22, 2001 at 03:02:40PM +0700, Olivier Nicole ([EMAIL PROTECTED]) wrote:
> > >and I do not want to install amanda client on it (if possible).
> >I have another reason, as the OS on that firewall is oldish I want to
> >upgrade it: wipe it and install fresh. I dont want to go to install
On Fri, Jun 22, 2001 at 03:04:40PM +0700, Olivier Nicole ([EMAIL PROTECTED]) wrote:
> > I found that all the files required by amanda are "all over the place".
> > Wouldnt it be a good idea to make amanda default to place everything in
> > /home/amanda or at least $HOME? This way you would have A
Great, thanks John, you had a point with the change in the config file.
It indeed tried to use dump instead of GNU tar..
And indeed, the amcheck returns to be having no problems anymore.
Though, the backup itself fails still.. the next report was in the log file
- -
>and I do not want to install amanda client on it (if possible).
>I have another reason, as the OS on that firewall is oldish I want to
>upgrade it: wipe it and install fresh. I dont want to go to install
Wow, a machine being a firewall and activated as a NFS server, this is
a bad idea, securit
> I found that all the files required by amanda are "all over the place".
> Wouldnt it be a good idea to make amanda default to place everything in
> /home/amanda or at least $HOME? This way you would have ALL files at
> one position only .
I second this motion :)
/usr/local/amanda/etc/dump
On Fri, Jun 22, 2001 at 12:22:01AM -0600, Kevin C Jones ([EMAIL PROTECTED])
wrote:
> thank you .. this worked... now I am getting another error when I try to
> label the tape.
there you go and I am only using it for two days
> How would I test to see if amanda is working?
> Label gives the err
"John R. Jackson" wrote:
>
> >... I've done that, but amrecover wants a portnumber < 1024... You can
> >off course hack the sources ;-)
>
> As far as I know, only the 2.5 (development) code branch has this problem
> with amrecover. Have you seen it with 2.4.2p2?
>
I'm using the 2.4.2p2tapeio b
I noticed that the amverify script sends both output by mail and via
stdout. I hacked the script a bit to send mail *or* send to stdout (by
means of a -m switch, the same way amcheck does).
Here's the patch.
Regards,
Arjan
25a26,34
> # First determine if we should run in mail mode: nothing is
Kevin C Jones wrote:
>
> I have installed amanda onto a Redhat 6.2 box.
> Everything went into okay, I edited the amanda.conf and made a dumptype and
> disklist.
OK.
> When I run the amcheck Daily comment... I get the following error:
>
> /usr/local/sbin/amcheck Daily
> Amanda Tape Server Host
all,
I found that all the files required by amanda are "all over the place".
Yet if I see other programs, eg listar, all files are based in one directory,
the home directory of the "user", that inlcudes in case of listar all
mailing list data and configuration directories.
Wouldnt it be a goo
All,
I am having a little problem here backing up a nfs volume.
This machine attached on the network (192.168.1.0) and its basically
a firewall. It has "absolutly nothing" on it (barest minimum)
and I do not want to install amanda client on it (if possible).
I have another reason, as the OS on th
37 matches
Mail list logo
