Have you verified that your kernel has loaded the appropriate module for
the hardware, so that the system can interact with the device?
Try here for linux documentation: http://tldp.org
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of LaValley,
Thank you to everyone that assisted me with this problem. In the end,
removing the 'nosuid' from /etc/auto.net allowed autofs to mount the NFS
shares correctly.
As a result, I'm able to successfully backup the additional linux
clients.
-Rob
Humm I missed this in the first read, did you do an ldconfig
after the install of the libs? And what do you mean by
building new libs?
Theres more to amanda than just the libs...
I built the entire amanda package... My apologies for the
misunderstanding. I did an ldconfig, and will
PROTECTED] On Behalf Of Eric Siegerman
Sent: Monday, February 21, 2005 2:54 PM
To: Amanda Mailing List
Subject: Re: Runtar error
On Fri, Feb 18, 2005 at 09:10:30AM -0600, Dege, Robert C. wrote:
runtar: error [must be setuid root]
On Fri, Feb 18, 2005 at 10:49:46AM -0600, Dege, Robert C. wrote
Last night, I had two systems fail on new amanda libs that I built. Upon
investigation, I found
this in the runtar debug logs in /tmp/amanda:
# more /tmp/amanda/runtar.20050217191004.debug
runtar: debug 1 pid 11435 ruid 7510 euid 7510: start at Thu Feb 17 19:10:04 2005
I think it is complaining about runtar not being suid root
like it's supposed to be. After you build amanda as the
appropriate user, you need to do the 'make install' as root
to get the proper permissiona and suid bits set appropriately.
Frank
Frank,
I think so to, but when I did, ls
I'm adding a new linux client to my current amanda backup system. I
built installed the binaries, added the system to the disklist, and
ran an amcheck -c. For some odd reason, I get a runtar permissions
error, and I can't figure out why. I compared the build to other
functioning systems, but
Good call. I changed the xinetd.d/amanda file:
group = diskto group = amanda
That resolved the problem. Now what disturbs me is why the other linux
box was able to work with that incorrect xinetd.d/amanda file. Time to
do some more investigating :)
-Rob
Amanda not in the amanda
I'm trying to get amandad running on a client. When I run 'amcheck -c', I get
the following error message from syslog:
Dec 22 16:21:34 alpha09 inetd[426248]: someone wants amanda fd 24 rad_id -1
Dec 22 16:21:34 alpha09 inetd[426268]: 426268 execl
/usr/local/dist/libexec/amandad rad_id -1
Dec
John,
what problems were you experiencing with the template? I've been having issues
as well, and am wondering if your fixes to the template will resolve the
problems I've been experiencing.
-Rob
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent:
-0600, Dege, Robert C. wrote:
John,
what problems were you experiencing with the template?
I've been having issues as well, and am wondering if your
fixes to the template will resolve the problems I've been
experiencing.
Not my solution, but Eric Siegerman's with some initial
Hey all,
I have (2) issues with printing reports that I'm hoping someone can assist me with.
1) Can I print old reports from previous backups (for cataloging purposes)? I think I
can do that using amreport, but I want to verify this. If not, what do I have to do?
2) amanda will no longer
Please put in some line breaks. Each of your paragraphs
shows up as one
line to me.
I totally blame Outlook for that! Actually, I blame my company for forcing me off of
pine ;)
2) amanda will no longer print out reports after a
successful backup.
The program used to, but we had
Steve,
try checking out the logs in /tmp/amanda (if that's where your logs are set to for the
client).
You can check rundump or sendsize. It should show you the absolute path of the dump
program and possibly any parameters used when performing the dump command.
-Rob
-Original
A few things I would check:
*) Since you area already part of a domain, your amandapass does not require the third
field that specifies the workgroup.
*) Your disklist specifies nocomp-user-gnutar as the backup method. What is listed in
there?
*) check out the errors logs in /tmp/amanda.
The '-m' parameter will only send you an email if there are errors during the amcheck.
If you want to receive an email on any amcheck output, try using '-a' instead.
# amcheck -a DailySet1
-Rob
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Wednesday,
, June 03, 2004 4:59 AM
To: Dege, Robert C.
Cc: [EMAIL PROTECTED]
Subject: Re: Multiple NICs
Dege, Robert C. said the following:
Our amanda server has 2 NICs in it, each with separate IPs. We're
running 2.4.22 kernel, RedHat 9, Amanda 2.4.4p1.
We'd like to back up a particular machine
It's been over a month, and I'm still having problems with my AIT-2 tape drive (seems
like I'm having a lot of amanda problems in general as of late).
As a recap... I could successfully run amdump have amanda write dumps to tape. But
when I tried to restore data from Amanda via am recover,
gnutar jumped from 1.13.25 to 1.13.9? in one leap.
Some reported problems with these very recent versions.
I don't recall the nature of the problems, check the archives.
But a build of 1.13.25 would seem a reasonable approach to
see if that is the problem.
I was originally having this
Hello,
Our amanda server has 2 NICs in it, each with separate IPs. We're running 2.4.22
kernel, RedHat 9, Amanda 2.4.4p1.
We'd like to back up a particular machine over the second NIC exclusively; is there a
way to do that? We want our 1 NIC to be dedicated for NFS, and the other NIC to be
-Original Message-
From: Gene Heskett [mailto:[EMAIL PROTECTED]
Sent: Friday, May 28, 2004 5:07 PM
To: [EMAIL PROTECTED]
Subject: Re: MapBarCode error
On Friday 28 May 2004 15:31, Dege, Robert C. wrote:
Hello all,
when I try to run amcheck, I keep getting a MapBarCode error
Hi,
I'm trying to build amanda client binaries for TRU64 4.0F. I am able to run configure
fine (minus /sbin/dump issues). When I run make, it errors out with the following
message:
cc -g -o .libs/amqde amqde.o ./.libs/libamclient.so ../common-src/.libs/libamanda.so
-lm -ltermcap -rpath
I figured out the problem. snprintf vsnprintf are absent in libc for TRU64 4.0F.
However, they can be found in the libdb.so library. So, I was able to fix my problem
by adding LD=-ldb to the configure line.
-Rob
-Original Message-
From: Dege, Robert C.
Sent: Friday, May 28
Hello all,
when I try to run amcheck, I keep getting a MapBarCode error, which causes amcheck to
exit tape scanning prematurely. Here's a snippet of output:
bash$ amcheck simnet
Amanda Tape Server Host Check
-
Holding disk /mnt/raid/holding: 3250292 KB disk space
Every so often, I'll run the following command to quickly see which amanda tape is
currently in my tape drive:
# dd if=/dev/nst0 bs=32k
Most of the time, I'll get the header information, but every so often I have to run
the command twice for the system to successfully read the tape. i.e.:
First, thanks to all for your suggestions. I've gotten slighty farther with fixing
this problem with my AIT-2 Tape Drive. After a few changes, I am able to restore a
lot more files before amrestore crashes.
Here's what I did:
1) Power off tape changer system
2) Change dip switches on the
Hi,
I'm currently having problems restoring files from my amanda backup system. I am able
to narrow the problem down to my AIT-2 tape drive. If I restore files from amanda
backups that are still on the holding disk, I have a successful restore. If I restore
files from any of the AIT-2
On my SDX-500 AIT-2 drives, I have 1-7 off and 8 on. The
documentation
says switches 1-4 6 are reserved and should be off, 5 is termination
power, 7 is HW compression (0-off,1-on), and 8 is SW
compression control
(0 lets host enable/disable compression, 1 disables host control). I
what platform/OS is your tapehost?
AMD System, running RedHat 9.0. I'm using a stock 2.4.22 kernel.
did you also modify your SCSI tape driver config file
(/kernel/drv/st.conf
on Solaris) so the driver can know about particular capabilities of
the tapedrive?
I didn't modify any kernel
Are you recovering on the client or the server?
Are you recovering from more than one DLE?
Perhaps the data was compressed on a box using a compression program
not available on the box doing the recover.
Frank
The system is both the client the server. I checked the config file in the
-
From: Jay Fenlason [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 07, 2004 5:20 PM
To: Dege, Robert C.
Subject: Re: AIT-2
On Wed, Apr 07, 2004 at 01:23:53PM -0700, Dege, Robert C. wrote:
Can you take one of your backup tapes and access the files on it
reliably with dd
I know that I can specify the tape device via CLI, or with settape in amrecover. I
was curious why it's default value isn't set to /dev/st0, when:
1) it is listed in the man page as such
2) was compiled with that value when I passed the --with-tape-device=/dev/st0
parameter to ./configure
System Stats:
Linux - 2.4.22
OS - RedHat 9.0
Amanda - 2.4.4p1
Question:
According to the man page for amrecover, the settape default is set to /dev/st0 (my
only tape device).
However, when I run amrecover extract, amrestore program fails. When I view the
debug info, I see that amrecover
I noticed something odd today while maintaining my amanda server, and I seek
some advise.
My amanda server is slow (350MHz CPU), so most of the dump are configured so
that the clients compress the data. The global dumptype is setup with
compress client best.
For slower systems, I override the
Seems to be the strange-questions-day ;) ...
Why not use two dumptypes?
For example:
define dumptype important {
dumpcycle 2
priority high
}
define dumptype unimportant {
dumpcycle 5
priority low
}
I'm already using 2 different dumpcycles. My global
Is there a way to have multiple disklists per config? I plan is to
alternate the amdump cycles with the different disklists. I'm running into
a tape space issue, and am trying to split my disklist into 2 disklists; one
with lower priority backups one with higher priority backups. The one
with
Thanks for the info... I'll check it out.
-Rob
-Original Message-
From: Stefan G. Weichinger [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 22, 2004 11:14 AM
To: Amanda List
Subject: Re: multiple disklists
Hi, Dege, Robert C.,
on Donnerstag, 22. Jänner 2004 at 17:06 you
Hi,
I've appeared to run into a restore problem. I've been backing up several
directories on a nightly basis using amanda for the past several months.
Today, I had to restore a fairly large directory. About 1/3 through the
restore, and error message appeared:
tar: Skipping to next header
tar:
Thanks for the info Paul (and Jay).
Paul, a few additional questions directed towards your response.
In my experience the compress best uses 4 times as much CPU for only
5% better compression, so it's not worth it, unless you have spare CPU
cycles to burn. Maybe it's better to increase the
System:
RedHat 7.1, kernel 2.4.19
amanda 2.4.2p2, samba 2.2.6
I've been backing up several Windows machines for a while now (months).
Recently, I've been getting cramped with tape space, so I added
compress-client-best to my samba-pc dump type.
However, while watching amanda perform the dump,
I'm running amanda-2.4.2p2-7 (a default RedHat 7.3 rpm).
When doing an amverify after an amdump, I receive the following messages
was wondering why:
Skipped bast._devel_digital.20030903.1 (** Cannot do /bin/gtar dumps)
Skipped bast._devel_dev__grp__db.20030903.4 (** Cannot do /bin/gtar dumps)
To: '[EMAIL PROTECTED]'
Subject: Re: amverify errors
On Wed, Sep 24, 2003 at 06:34:20AM -0700, Dege, Robert C. wrote:
I'm running amanda-2.4.2p2-7 (a default RedHat 7.3 rpm).
When doing an amverify after an amdump, I receive the following messages
was wondering why:
Skipped bast._devel_digital
Thank you for the suggestions. I'll checkout the bumpsize, bumpmult, and
bumpdays report my findings.
-Rob
-Original Message-
From: Jon LaBadie [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 02, 2003 12:47 PM
To: [EMAIL PROTECTED]
Subject: Re: Dumps Levels 1?
On Tue, Sep 02,
My config:
Redhat 9.0
Amanda version 2.4.4p1
I'm slightly concerned with my backups. I'm backingup a central NFS server
for my UNIX network. Using disklist, I broke the NFS share into 21 separate
sections. I did this so that I could benefit from higher dump levels on
sections that are used
, Aug 07, 2003 at 05:59:11AM -0700, Dege, Robert C. wrote:
I just installed amanda-2.4.4p1, and am getting this error message:
amreport: ERROR no printer command defined
Backups are still being done however. Any ideas why I'm gettign this?
Do you have lbl-template defined?
If so
locking issue with the indexing DB.
-Rob
-Original Message-
From: Frank Smith [mailto:[EMAIL PROTECTED]
Sent: Monday, August 11, 2003 11:11 AM
To: Dege, Robert C.; Amanda List (E-mail)
Subject: Re: amrecover
Amanda always expect the no-rewind device (/dev/nst0) so that the tape
remains
I have a few dquestions regarding the new config optinos in amanda.conf for
2.4.4p1:
dumpuser - how does the format work? default shows sssS, and a commented
BTBTBTBTBTBT. Is there a set length for the string? is there a
significance in string length?, etc.
autoflush - I don't completely
Okay, I've got a problem here. I running amanda-2.4.4p1 on a linux Redhat
9.0, with a tape changer connected directly to the machine. I'm trying to
restore a few directories, and am having problems getting the amrecover to
work.
After I set host, disk, date, and extraction list, I start the
on my system??
(btw, thanks for the indepth info :)
-Rob
-Original Message-
From: Jon LaBadie [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 07, 2003 9:58 AM
To: '[EMAIL PROTECTED]'
Subject: Re: Amanda Printing error
On Thu, Aug 07, 2003 at 06:38:41AM -0700, Dege, Robert C. wrote:
Yes
I just installed amanda-2.4.4p1, and am getting this error message:
amreport: ERROR no printer command defined
Backups are still being done however. Any ideas why I'm gettign this?
-Rob
I'm trying to configure amanda so that it will printout daily reports when
amdump runs.
I have the following in my amanda.conf:
printer ls
define tapetype AIT-2 {
comment SDX-500C with 50GB cartridge.
length 54538 mbytes
filemark 1541 kbytes
speed 2920 kps
lbl-templ
I have a Quantum PowerStor L200 Disk Changer with a Quantum DLT8000 tape
drive builtin. It is connected to an alpha running TRU64 5.1A.
Now that I have my specs out of the way, lemme explain my problem. This is
my first time setting up an amanda server, so I made sure to read the docs
to the
52 matches
Mail list logo
