On Fri, Oct 27, 2017 at 07:55:31AM -0400, Jean-Louis Martineau
(jmartin...@carbonite.com) wrote:
> Jobst,
>
> Every good bug report should include the version of the software you are
> using.
> Which amanda version are you using? On amanda server an client?
>
> Also tell us more information,
Jobst,
Every good bug report should include the version of the software you are
using.
Which amanda version are you using? On amanda server an client?
Also tell us more information, you just tell us 'no backup size line"'
on nothing more.
Which program or application are you using to do the
On Thu, Oct 26, 2017 at 01:16:35PM +0200, Michael M?skens (m...@muessi.nl)
wrote:
> hi,
> >
> > But I also do not know how to check this: GNU tar state file
> > /var/lib/amanda/gnutar-lists/XYZSOMETHING.new is corrupted.
>
> did you solve that problem by now? I???m not sure, but deleting the
hi,
> Now I get the following error: "no backup size line", in the log it looks
> like this
>
> FAIL dumper 192.168.0.1 /boot 20171024230002 1 [no backup size line]
>sendbackup: start [192.168.0.1:/boot level 1]
>sendbackup: info BACKUP=/bin/tar
>sendbackup: info
Hi
I never had problems with amanada, been using it for more than 15 years (i
think)
Had to delete one machine that had only two purposes: behind DMZ firewall and
amanda host.
Due to changes of my setup I did not need the firewall anymore so I moved the
amanda tape host to another existing
On Fri, Oct 20, 2017 at 08:45:11AM -0600, Steven Backus
(bac...@whimsy.med.utah.edu) wrote:
> Did you put auth "local" in your dumptype? Here's mine:
>
> define dumptype comp-integ-root-tar {
> global
> program "GNUTAR"
> comment "root partitions with compression"
> compress
Did you put auth "local" in your dumptype? Here's mine:
define dumptype comp-integ-root-tar {
global
program "GNUTAR"
comment "root partitions with compression"
compress client fast
priority low
auth "local"
}
Steve
--
Steven J. BackusComputer
Hi
This used to work for years, never had any trouble.
Due to a Internet configuration change (from SHDSL -> Fiber) I had to change
the backup server as the previous backup server was not required anymore.
I know about .amandahosts, hosts.allow, amanda.conf, xinet.d, the different
daemons
Still looks like a general NFS time out, see anything in the system
logs on any of these machines (or the SmartStor?)? Also, are you
trying dump or tar to back these up? Dump might have issues over the
NFS Mount...
You might also think about an alternate approach: mount all of these
RO
Long ago, I wrote:
I have a Promise SmartStor, a network drive. It's NFS mounted on
a Red Hat server. Sometimes it gets backed up, other times I get:
whimsy.med.utah.edu/sstore/9gb lev 0 FAILED [dumper returned FAILED]
whimsy.med.utah.edu/sstore/9gb lev 0 FAILED
I have a Promise SmartStor, a network drive. It's NFS mounted on
a Red Hat server. Sometimes it gets backed up, other times I get:
whimsy.med.utah.edu/sstore/9gb lev 0 FAILED [dumper returned FAILED]
whimsy.med.utah.edu/sstore/9gb lev 0 FAILED [data timeout]
Hi,
I have a Promise SmartStor, a network drive. It's NFS mounted on
a Red Hat server. Sometimes it gets backed up, other times I get:
whimsy.med.utah.edu/sstore/9gb lev 0 FAILED [dumper returned FAILED]
whimsy.med.utah.edu/sstore/9gb lev 0 FAILED [data timeout]
Paul Bijnens wrote:
On 2006-04-21 14:22, John Clement wrote:
Paul Bijnens wrote:
On 2006-04-21 13:28, John Clement wrote:
I've just inherited an amanda setup that has apparently never
worked properly. The specific problem I'm trying to sort at the
moment is summed up below.
Amanda Backup
I've just inherited an amanda setup that has apparently never worked
properly. The specific problem I'm trying to sort at the moment is
summed up below.
Amanda Backup Client Hosts Check
ERROR: NAK finn.internal.domain.com: access as amanda not allowed from
On 2006-04-21 13:28, John Clement wrote:
I've just inherited an amanda setup that has apparently never worked
properly. The specific problem I'm trying to sort at the moment is
summed up below.
Amanda Backup Client Hosts Check
ERROR: NAK
Paul Bijnens wrote:
On 2006-04-21 13:28, John Clement wrote:
I've just inherited an amanda setup that has apparently never worked
properly. The specific problem I'm trying to sort at the moment is
summed up below.
Amanda Backup Client Hosts Check
ERROR: NAK
On Fri, Apr 21, 2006 at 12:28:05PM +0100, John Clement wrote:
I've just inherited an amanda setup that has apparently never worked
properly. The specific problem I'm trying to sort at the moment is
summed up below.
Amanda Backup Client Hosts Check
ERROR:
On 2006-04-21 14:22, John Clement wrote:
Paul Bijnens wrote:
On 2006-04-21 13:28, John Clement wrote:
I've just inherited an amanda setup that has apparently never worked
properly. The specific problem I'm trying to sort at the moment is
summed up below.
Amanda Backup Client Hosts Check
of //machine_name/c$
and if so what is the syntax?
Thx,
gil
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Paul Bijnens
Sent: Tuesday, December 14, 2004 5:23 PM
To: Gil Naveh
Cc: [EMAIL PROTECTED]
Subject: Re: a problem backing up a window machine
Gil Naveh wrote
Gil Naveh wrote:
Thanks much Paul,
Your English is quit good and eventually I successfully run the amcheck on
the window box :)
Yet, I was not able to back up a shared folder on a window box.
Is it possible to backup a shared folder instead of a full drive like:
//machine_name/shared_folder
Thanks for the help.
However, when I am following through the example you gave me.
ACA I updated the /etc/amandapass and I have created a domain account with
admin privileges.
Yet, when I run the command
smbclient /etc/amandapass //machine_name/c$ user%passwd mydomain
I get the following error
Gil Naveh wrote:
Thanks for the help.
However, when I am following through the example you gave me.
ACA I updated the /etc/amandapass and I have created a domain account with
admin privileges.
Yet, when I run the command
smbclient /etc/amandapass //machine_name/c$ user%passwd mydomain
I get the
Title: Problem backing up just a few machines
Hello all,
We currently have about 10 HP-UX 11 and 11i machines in our Amanda setup.
Our server is HP-UX 11i with Amanda version 2.4.4 installed on all clients
and server.
I have two systems (HP-UX 11) that give me issue about once a week
Henson, George Mr JMLFDC wrote:
logfun02 / lev 0 FAILED [Request to logfun02 timed out.]
Then the next day I had two hosts with the same error. In trying to fix the
issue I found if I removed the curinfo directories for these two hosts, the
backups would run the next time amdump was called. It
Title: RE: Problem backing up just a few machines
Henson, George Mr JMLFDC wrote:
logfun02 / lev 0 FAILED [Request to logfun02 timed out.]
Then the next day I had two hosts with the same error. In
trying to fix the issue I found if I removed the curinfo directories
Henson, George Mr JMLFDC wrote:
Increase etimeout. (probably)
Currently etimeout is 300. Should this be increased
Could be, but to find out how much, the sendsize.XXX.debug log helps a
lot. But see below.
planner: time 30.790: error result for host logfun02 disk /: Request to
logfun02 timed
Title: RE: Problem backing up just a few machines
planner: time 30.790: error result for host logfun02 disk
/: Request to logfun02 timed out.
snip
If I am reading the above messages correctly the timeout is
happening well within the etimeout window. And the 30 second time
On Fri, 15 Feb 2002, Jean-Francois Malouin wrote:
Authentication access to the snap server maybe?
Just my 2EU.
I think I have it. The account I created doesn't have universal read
permissions, although it does have all permissions on the root of the
master share. The errors are when it
On Mon, 29 Apr 2002 at 9:11pm, Luke Miller wrote
I am having some problems backing up a large partition (raid).
I have a raid as a single partition with 56 GB of space. My tape drive
is a DLT 20 GB drive with a tape library with 7 slots using mtx for the changer.
I am running amanda version
I am having some problems backing up a large partition (raid).
I have a raid as a single partition with 56 GB of space. My tape drive
is a DLT 20 GB drive with a tape library with 7 slots using mtx for the changer.
I am running amanda version 2.4.2p2. I have set runtapes to 2 in amanda.conf
Hi all,
I'm in the process of setting up an Amanda backup server to back up a
collection of new servers. The Linux and Solaris servers aren't posing
any problems so far. But I also have to back up a SNAP 4100 appliance. In
my old pre-amanda backup scheme, I was backing it up as an NFS volume,
* Dave Edick ([EMAIL PROTECTED]) [20020215 14:28] thus spake:
Hi all,
I'm in the process of setting up an Amanda backup server to back up a
collection of new servers. The Linux and Solaris servers aren't posing
any problems so far. But I also have to back up a SNAP 4100 appliance. In
my
On Fri, 15 Feb 2002, Dave Edick wrote:
I'm in the process of setting up an Amanda backup server to back up a
collection of new servers. The Linux and Solaris servers aren't posing
any problems so far. But I also have to back up a SNAP 4100 appliance. In
my old pre-amanda backup scheme, I was
On Fri, 15 Feb 2002, Jean-Francois Malouin wrote:
Authentication access to the snap server maybe?
Just my 2EU.
I think I have it. The account I created doesn't have universal read
permissions, although it does have all permissions on the root of the
master share. The errors are when it
160 Mb, not that much huh, and it gives me the answer in just 1.5 second or
so..
And I'm not quite sure that the duration of 1.5 second is okay... Is the
command used to make an
inventory of the data to backup?
GNU tar is very clever about noticing it is writing to /dev/null and
essentially does
simulate and test...
Thanks again for additional help.
- Original Message -
From: John R. Jackson [EMAIL PROTECTED]
To: Robert Hoekstra [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Saturday, June 23, 2001 4:09 AM
Subject: Re: Problem backing up
FAIL dumper cobalt01.somewhere.nl /home 0
Okay, I did the following command on the cobalt01 machine:
---
/usr/local/libexec/runtar --create --directory /home --listed-incremental
/tmp/ff --sparse --one-file-system --ignore-failed-read --totals --file -
./dev/null
---
It gave me this result:
---
/usr/local/libexec/runtar:
Since a few weeks I have serious problems backing up a remote system (Cobalt
server) with my Sun Solaris 2.6 machine.
I backup different machines and different directories on each machine.
all machines (including the cobalt) backup well, except for two directory
branches on the Cobalt (the other
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
- report
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 a
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 backup
Since a few weeks I have serious problems backing
up a remote system (Cobalt server) with my Sun Solaris 2.6 machine.I backup
different machines and different directories on each machine.all machines
(including the cobalt) backup well, except for two directory branches on the
Cobalt (the
cobalt01.s /home lev 0 FAILED [data timeout]
...
sendbackup: info BACKUP=/bin/gtar
This tells me two things. First, that at this time you were using GNU
tar to do the backup, and second that the Amanda server side waited half
an hour and didn't get any data from the client (which triggered the
Please let me know if this solves your problem so I can get it into the
source tree.
Amanda rocks! (No problem after applying your patch)
Thanks you very much for your quick help - what's the number of your
paypal account? ;-)
Regards,
Bernie
I was able to reproduce the problem. It was what I thought it was, but
the original patch was the wrong solution (sort of -- it gets complicated
with the multiple OS's we have to support). The following patch forks
a separate amandad process just to write the packet to the service child
and
Hi,
This sounds like a classic case of running out of file descriptors --
either on a per-process basis, or on a system-wide basis (more likely
per-process, as you seem to be able to reproduce it at will with the
same number of disklist entries on that host).
probably not on a system-wide
Hi,
Please give the following patch a try and let me know if it solves the
problem.
the problem persists: selfcheck checked the last 100 lines of the
disklist.
Yes, the patched amandad has been started:
amandad: debug 1 pid 26880 ruid 37 euid 37 start time Sat May 12
12:06:57 2001
amandad:
the problem persists: selfcheck checked the last 100 lines of the
disklist.
Well, nuts. I was pretty sure that patch was involved.
In the first letter you said:
After adding one or more lines to the disklist file, only the last 100
lines get checked, then an amandad and a selfcheck
Hi,
So the next step is to make sure amandad and sendsize were compiled
with -g, get them hung and attach a debugger to them, then get a stack
traceback (where) so we can see where they are stopped.
I compiled the whole suite (without amandad.diff, but with make
CFLAGS=-g) and copied
I compiled the whole suite (without amandad.diff, but with make
CFLAGS=-g) and copied client-src/.libs/{amandad,selfcheck} to
/usr/libexec/amanda/.
I forgot to mention that advfs.diff is applied.
This sounds like a classic case of running out of file descriptors --
either on a per-process basis, or on a system-wide basis (more likely
per-process, as you seem to be able to reproduce it at will with the
same number of disklist entries on that host).
It seems to me that Amanda should
Up to and including 171 disklist entries of type root-tar, everything is
ok. ...
If I add some more disklist entries of the same type, amcheck hangs for
a minute (ctimeout 60) and then reports selfcheck request timed out.
Host down?
Wow. If it's what I think it is, that bug has been around
52 matches
Mail list logo
