What's the environment that you are running in from the command line? (You can
find this out by typing 'env' at the command line -- this will print out a long
list of the variables in the environment)
Ricky
-Original Message-
From: Renzetti Robert A [mailto:[EMAIL PROTECTED]]
Sent:
Hi! I'm about to start setting up a small backup network for about five
computers (not counting the backup server) -- four Solaris 2.6/7 boxes, and one
NT4 box. I may later add in some Win2K boxes.
I am planning on taking an older (ie, spare) i386 box and adding a 20gig holding
disk, and our
Hi! Perhaps I'm just not looking in the right place, but I can't seem to find
any sources on setting up the following backup with tar...
I understand how to backup entire folders in the root partition as a separate
group (that is, /usr, /var, /tmp, /etc, etc.). But suppose that I have the
Hi! I'm still having problems with ufsdump returning error code three, thus
causing the dumps to fail. There seems to be no consistancy to this -- the
disks get backed up correctly eventually, but it takes a number of tries. None
of the log files that I know about (/tmp/amanda/*) seem to
Ulrik Sandberg [mailto:[EMAIL PROTECTED]] wrote:
How about this:
... amverify standard /tmp/amanda/amverify.debug 21
It worked! Many thanks...
Ricky
Hi! I've been trying to apply the results from the previous discussion I
initiated to my backup system, but nothing I do seems to get any results (ie,
stopping getting duplicate data from amverify). The reason this is important is
that some of my bosses want to get copied on the amanda reports,
Ulrik Sandberg [mailto:[EMAIL PROTECTED]] wrote:
mt comp off; /usr/local/amanda/sbin/amdump standard
((mt status 21 /dev/null)
(/usr/local/amanda/sbin/amverify standard 21
/tmp/amanda/amverify.debug)); mt offline
How about this:
... amverify standard
Hi! I'm sure this is covered somewhere -- if someone can just tell me where
to look, that would be great.
I just added an amverify run to my backup. The problem is that I now get
the report twice: once from Amverify emailing it to me, and once from cron,
emailing the same text. Is there some
U... are you sure that it didn't send you the email? Try this: log on to
your backup server, then su to the amanda user (you may need to be root to do
this). Then type 'mail'. The report should be there.
If it is, then you need to set up a .forward file, or create an alias in
Joshua Baker-LePain [mailto:[EMAIL PROTECTED]] wrote:
Actually, the easiest way to control who gets the amreport at
the end of
the run is via the mailto parameter in amanda.conf. Of
course, you may
still want to set up a .forward for the amanda account to get
CRON errors,
but you
I wrote:
I'm now wondering if the problem has to do with
having more than one dumper dumping at the same time -- I
think that it might be that some of the partitions are
on the same disk, and perhaps there is a conflict with dump?
I will try using the spindle values in the disklist to
see
Axel Schaefer [mailto:[EMAIL PROTECTED]] wrote:
The .amandahosts (in var/lib/amanda) shows this:
amanda@ll11:~ less .amandahosts
localhost amanda
localhost root
One of the standard recommendations is to never use 'localhost' -- use the
FQDN...
This might not solve your problem, but it's
David Flood [mailto:[EMAIL PROTECTED]] wrote:
I've just upgraded from 2.4.2p2 to 2.4.3b3, at the same time
I've changed my
amanda user from root to bin. I notice when I get the report
at the end of a
level 0 backup. It has backed up nowhere near all the data
that exists.
For
No -- this is the group that the files/amanda user belong to. The idea is that
disk devices (and files such as /etc/dumpdates) are owned by root, but the group
disk (on my linux box), or operator (on my freebsd one), or sys (I think,
on the solaris machines) has read and write access. This
Greg Wardawy [mailto:[EMAIL PROTECTED]] wrote:
Amanda Backup Client Hosts Check
ERROR: localhost: [access as amanda not allowed from amanda@linver]
amandahostsauth failed
Client check: 1 host checked in 0.020 seconds, 1 problem found
Hmmm... I can't help
Chris Marble [mailto:[EMAIL PROTECTED]] wrote:
This started happening to me early this year. Just on 2
partitions out of 91. As best we could diagnose I was
exceeding a CPU time limit.
How did you diagnose this?
When I turned off compression on those 2 partitions the
backups went
Actually, and perhaps this should be noted somewhere else?, you can do the
following:
kill -USR1 your-xinetd-pid-here
which should cause it to intelligently reload (ie, don't cut off any already
existing connections)
HTH,
Ricky
-Original Message-
From: Joshua Baker-LePain
John R. Jackson [mailto:[EMAIL PROTECTED]] wrote:
While I'm sure JJ and other lurking ...
Lurking? You call my 5,000 replies to this list a day
lurking??? :-) :-)
don't you need at least 10,000 a day not to be a lurker... :-)
Ricky (who is, by any measure what-so-ever, a lurker)
John R. Jackson [mailto:[EMAIL PROTECTED]] wrote:
You're looking at the wrong end of the pipe. The messages imply the
server side shut things down, which broke the pipe and filtered back
to the clients as bad news (there was nowhere to shove their data).
So what else is in the Amanda mail
John R. Jackson [mailto:[EMAIL PROTECTED]] wrote:
Are there any particular log files that
I should look at to see what happened?
First, look for any core files in /tmp/amanda.
None found...
Then read through the
amdump.NN file that corresponds to this run. It's in the logdir
directory
Hi! I'm still having problems with ufsdump returning error code three, thus
causing the dumps to fail. There seems to be no consistancy to this -- the
disks get backed up correctly eventually, but it takes a number of tries. None
of the log files that I know about (/tmp/amanda/*) seem to
Hi! I'd like to, in addition to my current backup setup, have a series of
archival snapshots that I take every other month or so. This is an issue,
because I was just asked to retrieve a file from 1998, which was (hopefully)
backed up under a previous sysadmin, in some form or other, but which
Hi! I have a Seagate DDS-3 drive, attached to a FreeBSD 4.5-release computer.
When ever the system restarts, it by default turns on hardware compression. As
I wish to use software compression, this could present a problem. I tried
writing a shell script that would run at startup which
James Kelty [mailto:[EMAIL PROTECTED]] wrote:
Morse, Richard E. [mailto:[EMAIL PROTECTED]] wrote:
James Kelty [mailto:[EMAIL PROTECTED]] wrote:
[amanda@warbaby docs]$ id
uid=55(amanda) gid=6(disk) groups=6(disk),4(adm),55(backup)
[amanda@warbaby docs]$ ls -l /etc/dumpdates
-rw-rw-r--1
Who owns the amanda programs -- amcheck, amstatus, selfcheck, rundump,
dumper, etc...
Ricky
James Kelty [mailto:[EMAIL PROTECTED]] wrote:
I get the same error with the FQDN as I do with the IP.
-James
-Original Message-
From: Morse, Richard E. [mailto:[EMAIL PROTECTED]]
Sent
Hi! Thanks to Jon LaBadie and John R. Jackson for helping me get gtar exclusion
lists up and running -- it seems to have worked!
Ricky
-
Richard MorseSystem Administrator
MGH Biostatistics Center 50 Staniford St. Rm
Hi! How stable is the Win32 Amanda Client found on SourceForge? I have a few
NT/Win2K boxes that I would like to add to my backup, and I'm looking at the
different options available...
Thanks,
Ricky
-
Richard MorseSystem
Hi! Perhaps I'm just not looking in the right place, but I can't seem to find
any sources on setting up the following backup with tar...
I understand how to backup entire folders in the root partition as a separate
group (that is, /usr, /var, /tmp, /etc, etc.). But suppose that I have the
Hi! Does amanda automatically remove files in /tmp/amanda after a set time?
Thanks,
Ricky
-
Richard MorseSystem Administrator
MGH Biostatistics Center 50 Staniford St. Rm 560
[EMAIL PROTECTED]
-LePain [mailto:[EMAIL PROTECTED]]
Sent: Tuesday 26 March 2002 11:31 AM
To: Morse, Richard E.
Cc: '[EMAIL PROTECTED]'
Subject: Re: Question on how to configure tar backups..
On Tue, 26 Mar 2002 at 11:21am, Morse, Richard E. wrote
That is, I want to have the following disks:
/home/user1
/home
Thanks! I didn't see that, although I thought that I had read all
of the configure options...
Ricky
-Original Message-
From: John Koenig [mailto:[EMAIL PROTECTED]]
Sent: Tuesday 26 March 2002 5:31 PM
To: Morse, Richard E.
Subject: Re: Removing the debug files in /tmp/amanda?
see
Fernan Aguero [mailto:[EMAIL PROTECTED]] wrote:
[I've tried also building amanda --with-user=amanda and creating the
user to no avail]
The only thing that works is letting amanda have a login shell in
/etc/passwd, which I guess is the wrong thing to do (from a security
standpoint).
Hi! It's
Hi! I just started using amanda on Monday night. That night, something caused
my backup server to go off the network about halfway through the night, leaving
several disks unbacked up. On Tuesday night, however, this didn't happen. Yet
still, three disks didn't get backed up -- the dump
Hi! I've seen on FreeBSD a listing for gtar 1.13.25. However, I can't seem
to find the sub-revision number in the sources downloaded from ftp.gnu.org ,
and the most recent rpm from redhat is for 1.13.19-1. Are the sources on
ftp.gnu.org for 1.13.25? Or should I just upgrade the lone gnu/linux
Hi! Thanks for all the responses so far -- I finally got it to compile on
one of the Solaris 2.7 boxes (I found 'ar' -- I forgot that Solaris doesn't
have a root path which includes most of the tools by default). I then
tranferred it over to the other 2.7 machine, and it seems to be happy there
Is there some way to preprocess a file with gcc to determine why it is
hanging? Whenever the machine tries to compile recover-src/uparse.c, it
hangs. It has no problems with any of the other files (so far as I can
tell).
Thanks,
Ricky
-
Hi! I'm trying to build amanda on a Solaris 2.6 box (I don't know if there are
other things that would describe it better -- if you can think of anything,
please let me know...).
I ran configure with the following line (running as root):
# ./configure --with-user=amanda --with-group=root
Hi! I'm about to start working on installing Amanda for the first time.
I've been reading all the docs, as well as the chapter from Unix Backup and
Recovery on the web. They mention a program called amplot, which creates a
pictoral view of how the setup is working. In order to use this
Hi! I've got a DDS3 drive, and I need to buy tapes for it. I'm comparing
different brands, and frankly, I don't know enough to make a good decision.
I've narrowed it down to Sony, Maxell, HP, and Verbatim (the Fuji cassettes
are cheap, but that worries me...).
Does anyone have suggestions as
, and
it's a seagate STD6240 (ie, DDS-3)
Any suggestions?
Thanks,
Ricky
-Original Message-
From: Chris Dahn [mailto:[EMAIL PROTECTED]]
Sent: Wednesday 20 February 2002 10:10 AM
To: Morse, Richard E.
Cc: [EMAIL PROTECTED]
Subject: Re: Testing a tape drive?
On Wednesday 20 February 2002
Hi! I would like to start using Amanda to back up a small LAN I have,
consisting mainly of Solaris 2.6 machines (+ 1 NT box, although that can wait,
and 1 RedHat 7 box). The machine that I intend to use as a host is an older
SPARCstation 2, which has two tape drives attached -- a DDS3 drive and
41 matches
Mail list logo
