Glenn Case - Informix Software wrote:
>
> OK I have checked through the archives and found some
> details but I thought I would ask to see If anyone else
> has this working.
>
> I am Going to be starting to use amanda to back up
> a set of Network appliances. (I have amanda backing
> up most of
Denise Ives wrote:
>
> My Amanda level 1 back-ups are failing consistanly on one of my drives.
> However there is small amounts of activity going on during the time
> amanda dump. Sometimes I have mtrg running in the background
> backing up files and folders - do you think that is the cause of th
>I can't seem to figure this one out. I've got my Linux host running
>Amanda-2.4.2 and all the Linux clients working allright but not my
>Ultra10's running Solaris 2.7.
>...
>Is there a Solaris patch I should know about?
I don't think so. I have several Solaris 2.7 machines, both Sparc and
Ultr
Hey folks,
I can't seem to figure this one out. I've got my Linux host running
Amanda-2.4.2 and all the Linux clients working allright but not my
Ultra10's running Solaris 2.7.
Here's a listing of runtar:
-rwsr-x--- 1 root backup 216808 Jan 20 21:19 runtar
And here's the error I get in /
>FAILURE AND STRANGE DUMP SUMMARY:
> mail /home/httpd/html/users lev 0 FAILED
>[mail: [access as operator not allowed from
>...
>3) amcheck happy
Huh? Are you saying amdump reports the above error but amcheck is happy?
Did you run amcheck as the Amanda user (operator?)?
>4) in /usr/local
I thought that the programs were supposed to be user root, group disk or
operator, and that **some** of the programs were setuid root: (courtesy
John)
FYI, here's the proper list of setuid programs:
-rwsr-x--- 1 root backup244716 Dec 1 14:19 libexec/calcsize
-rwsr-x--- 1 root
On Mon, 22 Jan 2001, Efrem Edwards wrote:
> FAILURE AND STRANGE DUMP SUMMARY:
> mail /home/httpd/html/users lev 0 FAILED
> [mail: [access as operator not allowed from
> [EMAIL PROTECTED]]
>
> Can someone help me with this.
To start with, have you followed the suggestions in docs/FAQ ?
FAILURE AND STRANGE DUMP SUMMARY:
mail /home/httpd/html/users lev 0 FAILED
[mail: [access as operator not allowed from
[EMAIL PROTECTED]]
Can someone help me with this. I've done the
following:
1) changed my inetd.conf to
amandadgram udp wait operator
/usr/local/amanda/libexec/ama
OK I have checked through the archives and found some
details but I thought I would ask to see If anyone else
has this working.
I am Going to be starting to use amanda to back up
a set of Network appliances. (I have amanda backing
up most of the rest of the site )
Unfortunately One of the
On Tue, 23 Jan 2001, Ben Elliston wrote:
>> I believe this is quite portable:
>>
>> dd bs=1 skip=257 count=5 if=/dev/tape of=/some/tmp/file
>> if test `cat /some/tmp/file` = ustar ; then
>>: This is a tar file.
>> fi
>
>But wait... You just threw away the fir
On Mon, 22 Jan 2001, John R. Jackson wrote:
> >I'm not having any luck on my PC shares. ...
>
> What does one of the disklist entries look like?
>
> If you comment out everything else but one PC entry in disklist and
> run "amcheck", does /tmp/amanda/selfcheck*debug or amandad*debug on the
>
>Is there a way to get more "debug" information out of amcheck?
Not really.
>I'm not having any luck on my PC shares. ...
What does one of the disklist entries look like?
If you comment out everything else but one PC entry in disklist and
run "amcheck", does /tmp/amanda/selfcheck*debug or ama
> but when I ran make it stops with:
>...
>make: don't know how to make amoverview. Stop
>*** Error code 1
>
> Hmmm... Any suggestions?
This was discussed about a month ago with the following nice summary
from David Wolfskill ([EMAIL PROTECTED]):
Sounds sounds suspiciously like the symptoms I
> I believe this is quite portable:
>
>dd bs=1 skip=257 count=5 if=/dev/tape of=/some/tmp/file
>if test `cat /some/tmp/file` = ustar ; then
> : This is a tar file.
>fi
But wait... You just threw away the first 257 bytes from stdin. Now
what are you going
My Amanda level 1 back-ups are failing consistanly on one of my drives.
However there is small amounts of activity going on during the time
amanda dump. Sometimes I have mtrg running in the background
backing up files and folders - do you think that is the cause of these
errors here?
Or is the
On Tue, 23 Jan 2001, Ben Elliston wrote:
> I believe this is quite portable:
>
> dd bs=1 skip=257 count=5 if=/dev/tape of=/some/tmp/file
> if test `cat /some/tmp/file` = ustar ; then
> : This is a tar file.
> fi
But wait... You just threw away the first 257 bytes fro
>The error message I get is the following:
>
>amcheck-server: could not get changer info: badly formed result from
>changer: "/usr/amanda/libexec/chg-zd-mtx: /usr/adm/amanda/changer-
>status-clean: No such file or directory"
>
>Im trying to find where in chg-zd-mtx is it looking for the changer-
I'll ask again, how do you do that in a shell script? And remember
that it has to run on every flavor of Unix in the world, not just
Linux or Solaris, so no cheating and using other than the most generic
commands and options :-).
I believe this is quite portable:
dd bs=1 ski
>I using amanda to backup several servers, but now some of my disks
>started signaling the following error. Those are vx filesystems of
>an HP 10.20 ...
>| vxdump: SIGSEGV: ABORTING!
This is either an HP or Veritas (is that who does VX?) problem.
You'll probably need to talk to your vendor a
>By looking at byte 257 of the file?
I'll ask again, how do you do that in a shell script? And remember that
it has to run on every flavor of Unix in the world, not just Linux or
Solaris, so no cheating and using other than the most generic commands
and options :-).
Also keep in mind that wheth
>... If I bring all my amandas up to v2.4.2, this should go away, right?
Just upgrading the server would take care of amverify, assuming GNU tar
is named "gtar" on both server and clients.
>Bill
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
The basic problem is, how do you know (programatically, in a shell
script) that it's a tar image? All we have is the name of the dump
program, which might be "tar" or "gtar" or "gnutar" or
"gtar-1.12+amanda-patches". And this will get even more complicated
when the DUMPER-API is im
>Why does it try to match the name at all? If you know the file on tape is a
>tar file, why not just run the designated tar command on the tape server?
The basic problem is, how do you know (programatically, in a shell script)
that it's a tar image? All we have is the name of the dump program,
* Josh Huston <[EMAIL PROTECTED]> (Mon, Jan 22, 2001 at 10:54:10AM -0600)
> You can get the mirrors offline and then fsck the master disk and then
> attach the mirror again to re-sync it. Hopefully, it should fix the
> problem.
Yeah, you can do that.
But you can get the same kind of errors if yo
Is there a way to get more "debug" information out of amcheck?
I'm not having any luck on my PC shares. I can talk to them just fine
through smbclient on the new amanda server, just seems that amanda itself
can't.
-Gerry
"John R. Jackson" wrote:
> >However, the AMANDA VERIFY REPORT says it skipped the verificiation on
> >this server because;
> >
> >(** Cannot do /usr/bin/gtar dumps)
>
> This says that GNU tar is installed in /usr/bin/gtar on the client,
> but since amverify runs on the server, it is apparantl
jrj wrote:
>(** Cannot do /usr/bin/gtar dumps)
This says that GNU tar is installed in /usr/bin/gtar on the client,
but since amverify runs on the server, it is apparantly not in that
same location, so it could not run it.
Version 2.4.2 tries to handle this better by looking f
>However, the AMANDA VERIFY REPORT says it skipped the verificiation on
>this server because;
>
>(** Cannot do /usr/bin/gtar dumps)
This says that GNU tar is installed in /usr/bin/gtar on the client,
but since amverify runs on the server, it is apparantly not in that same
location, so it coul
>I recently added a new disk mirror to one of our SUN servers but I can't
>get amanda to back it up. ...
Do I understand you correctly that you're detaching the mirror and
then trying to back that up? What makes you think the data is any more
consistent than the "live" copy?
Mirrors live at a
> Are there any clues in the /tmp/amanda directory on the server ?
Nope. not a thing. When I run 'amcheck eagle' it doesn't write anything in
the /tmp/amanda directory.
I do see stuff in there from last night's successful backup of the two
unix boxes though. That's the goofy part. The backups
> Are you able to communicate with the PC using the smbclient program ?
> i.e. Can you interact with it by typing from the amanda server
> smbclient file://mypcname/mysharename share-password
Yep.
./smbclient file://ww2/d -U samba
It then prompts me for the password, and I can list the fil
You can get the mirrors offline and then fsck the master disk and then
attach the mirror again to re-sync it. Hopefully, it should fix the
problem.
Josh
-Original Message-
From: Steven Law
To: [EMAIL PROTECTED]
Sent: 1/22/01 4:08 AM
Subject: Block errors with Mirror disk
Hi
I recentl
And while tinkering, I deinstalled and re-installed the ports version... I
always get this error when it tries to check the PC slices:
Amanda Backup Client Hosts Check
WARNING: amanda: selfcheck request timed out. Host down?
Client check: 3 hosts checked in 30.43
I'm still trying to get my new replacement amanda server to backup peecee
shares with smbclient. It's backup up other Unix machines just fine.
It was suggested to compile from the source code directly, instead of
using the ports collection method.
Download 2.4.2
ran ./configure with my opti
I am setting up a SAMBA client server to be backed by amanda, which is
running on RH7. The first night I ran the backup, it seems to have gone
well. The AMANDA MAIL REPORT says it backed up 1.9 GB on the /home/samba
directory on the client machine in 143:02 minutes.
However, the AMANDA VERIFY REP
Hello All. I have solved the problem with xinetd where killpgrp can't be
run because of group permissions. The key is to use xinetd's "groups" option.
See my xinetd configuration file for amanda below:
service amanda
{
protocol= udp
socket_type = dg
Hi
I recently added a new disk mirror to one of our SUN servers but I can't
get amanda to back it up. The other disk mirrors backup fine and the
metatool program doesn't report any problems with this mirror. The errors
I get in sendsize.debug are as follows .
DUMP: Writing 32 Kilobyte rec
* Christoph Scheeder <[EMAIL PROTECTED]> (Mon, Jan 22, 2001 at 10:31:14AM
+0100)
>> It looks like amanda tries to squeeze exactly 1 0 dump for each filesystem
>> in a dumpcycle.
>>
>> This is bad
>> (just imagine a diskcrash just as the disk is being 0dumped to the tape
>> that had the last 0du
On Jan 22, 2001, Gerhard den Hollander <[EMAIL PROTECTED]> wrote:
> It looks like amanda tries to squeeze exactly 1 0 dump for each filesystem
> in a dumpcycle.
Yep. dumpcycle specifies how often you want full backups. tapecycle
specifies how many tapes you have. If you want more than one ful
Hi,
Gerhard den Hollander schrieb:
>
> It looks like amanda tries to squeeze exactly 1 0 dump for each filesystem
> in a dumpcycle.
>
> This is bad
> (just imagine a diskcrash just as the disk is being 0dumped to the tape
> that had the last 0dump on it).
No, that is the intended way amanda w
It looks like amanda tries to squeeze exactly 1 0 dump for each filesystem
in a dumpcycle.
This is bad
(just imagine a diskcrash just as the disk is being 0dumped to the tape
that had the last 0dump on it).
Is there any way to get amanda to do 2 0dumps per filesystem in each
dumpcycle (apart for
41 matches
Mail list logo
