For what its worth, this creates problems with inter-operability between
CentOS and Debian; we rebuilt the CentOS rpm for amanda client so it used
the backup user instead of amanda, as our amanda server was on Debian. We
tried hard but never found a way to configure this.
It would be nice to be
Optional systemd configuration files for amanda; please don't make it
compulsory.
On Thu, Aug 27, 2015 at 5:07 AM, Jean-Louis Martineau martin...@zmanda.com
wrote:
systemd (which you probably already run) replace xinetd.
Most services are already started by systemd.
We just need systemd
Hi there
I'm preparing some documentation on our backup/restore process.
Some time ago I linked to amanda documentation on how to extract from tapes
without using any amanda tools or indexes.
This link was:
http://www.amanda.org/docs/using.html#restoring_without_amanda
and is now broken.
Gene Heskett wrote:
On Tuesday 09 March 2010, Dustin J. Mitchell wrote:
On Wed, Mar 3, 2010 at 1:58 PM, Steve Wray steve.w...@cwa.co.nz wrote:
Right, so the LATEST most up-to-date version of Debian uses a 3 year old
version of amanda. Fantastic, thanks Debian for keeping things so
'stable
Hi there
I've been looking at the state of Amanda in a few distros.
Ubuntu and Centos so far seem to have pretty old versions of Amanda.
Can anyone suggest a distro that tracks Amanda upstream reasonably well? Ie
doesn't include bug-ridden versions in their stable releases...
Not that I'm
the upstream to this
extent is simply unforgivable. I'm revising my opinion of Debian.
Steve Wray wrote:
Dustin J. Mitchell wrote:
On Thu, Jan 21, 2010 at 5:05 PM, Jean-Louis Martineau
martin...@zmanda.com wrote:
xinetd is still configured to accept a tcp connection, but amandad
expect a
udp
Dustin J. Mitchell wrote:
On Thu, Jan 21, 2010 at 5:05 PM, Jean-Louis Martineau
martin...@zmanda.com wrote:
xinetd is still configured to accept a tcp connection, but amandad expect a
udp packet, so amandad do nothing and the server fail while waiting for an
ACK.
Right - it was the failure I
Garbee bd...@gag.com
Architecture: i386
Source: amanda
Version: 1:2.5.2p1-5
Steve Wray wrote:
Steve Wray wrote:
Jean-Louis Martineau wrote:
Run 'amadmin CONFIG disklist' and check the auth is set as expected
for all dles.
I've done this, with the amanda.conf having bsdudp and with it having
Steve Wray wrote:
Jean-Louis Martineau wrote:
Run 'amadmin CONFIG disklist' and check the auth is set as expected
for all dles.
I've done this, with the amanda.conf having bsdudp and with it having
bsdtcp for that entry.
In both cases all auth entries for all other DLE's are 'BSD
Steve Wray wrote:
Dustin J. Mitchell wrote:
I suspect an estimate or data timeout. Have you tried increasing
dtimeout and etimeout?
etimeout 2000
dtimeout 2000
I'd be surprised. These seem like fairly substantial values. 2000
seconds is roughly half an hour. I'll increase them by another
Jean-Louis Martineau wrote:
Steve Wray wrote:
On the client, in the sendbackup.20100106012630.debug log I see:
sendbackup-gnutar: time 0.056: /usr/lib/amanda/runtar: pid 3348
sendbackup: time 0.057: started backup
sendbackup: time 90.352: index tee cannot write [Broken pipe]
sendbackup: time
Jean-Louis Martineau wrote:
Steve Wray wrote:
On the client, in the sendbackup.20100106012630.debug log I see:
sendbackup-gnutar: time 0.056: /usr/lib/amanda/runtar: pid 3348
sendbackup: time 0.057: started backup
sendbackup: time 90.352: index tee cannot write [Broken pipe]
sendbackup: time
Jean-Louis Martineau wrote:
Steve Wray wrote:
Dustin J. Mitchell wrote:
On Wed, Jan 6, 2010 at 4:01 PM, Steve Wray steve.w...@cwa.co.nz wrote:
Am I to understand that there could be a problem in having 'too
many' DLE's
for bsd or bsdudp to cope with?
I never thought of there being a limit
Dustin J. Mitchell wrote:
On Wed, Jan 6, 2010 at 3:42 PM, Steve Wray steve.w...@cwa.co.nz wrote:
Ah hang on, am I right in understanding that you can't have just one dle
using bsdtcp auth? That they would all have to have it? (ie the inetd
configuration)
Well, all DLEs on a given host have
Dustin J. Mitchell wrote:
On Wed, Jan 6, 2010 at 4:01 PM, Steve Wray steve.w...@cwa.co.nz wrote:
Am I to understand that there could be a problem in having 'too many' DLE's
for bsd or bsdudp to cope with?
I never thought of there being a limit to the number of DLE's before... Our
disklist file
Jean-Louis Martineau wrote:
Steve Wray wrote:
Jean-Louis Martineau wrote:
Steve Wray wrote:
On the client, in the sendbackup.20100106012630.debug log I see:
sendbackup-gnutar: time 0.056: /usr/lib/amanda/runtar: pid 3348
sendbackup: time 0.057: started backup
sendbackup: time 90.352: index
that one DLE is reported as having either bsdtcp or
bsdudp, in both cases matching what is in the amanda.conf
So I'd say that was all as expected.
Jean-Louis
Steve Wray wrote:
Jean-Louis Martineau wrote:
Steve Wray wrote:
Jean-Louis Martineau wrote:
Steve Wray wrote:
On the client
/.amandahosts on the client
Client check: 2 hosts checked in 5.097 seconds, 1 problem found
(brought to you by Amanda 2.5.2p1)
Steve Wray wrote:
Jean-Louis Martineau wrote:
Run 'amadmin CONFIG disklist' and check the auth is set as expected
for all dles.
I've done this, with the amanda.conf
brnn8r wrote:
Hi All,
This is my first post on this forum and I'm a bit of a Amanda newb.
At my company we have a Weekly backup regime and after each weekly
backup the tape is sent offsite for storage and the next Weekly tape is
brought in.
I've just come back from holiday and Amanda
Hi there
I have a server, at a remote location, which has recently started to
intermittently fail backups.
The amanda client is running Debian Lenny, the amanda server is running
Debian Etch.
On the amanda server, dpkg -s amanda-server shows Version: 1:2.5.2p1-5
On the amanda client, dpkg
Dustin J. Mitchell wrote:
I suspect an estimate or data timeout. Have you tried increasing
dtimeout and etimeout?
etimeout 2000
dtimeout 2000
I'd be surprised. These seem like fairly substantial values. 2000 seconds
is roughly half an hour. I'll increase them by another 1000 seconds
Steve Wray wrote:
Hi there,
I am still trying to get to the bottom of this.
I think I got to the bottom of this.
You know how Debian never fixes bugs in the stable release unless its a
security related bug?
And how the amanda in Debian Etch was released to stable with the gtar bug?
So
Hi there,
I am still trying to get to the bottom of this.
I have some servers running Debian Etch. They have been fine with amanda
for a very long time now.
I just ran an apt-get upgrade to apply some security patches and suddenly
I'm getting the old file changed as we read it and error
Dustin J. Mitchell wrote:
On Tue, Jun 16, 2009 at 9:11 AM, Charlie Reitsmareit...@denison.edu wrote:
So, perhaps, the ISP is mistaking the backup traffic as a broadcast storm.
It would appear as a sudden spike of traffic leaving the server. If so, a
conversation with the ISP should clear up the
Hi there,
We have a server hosted with our ISP and we have recently started to run
amanda backups from this server to our main backup server.
The ISP has contacted us about broadcast storms emanating from this server.
These storms coincide with backup runs.
I wasn't aware that amanda used
Hi there,
over the last month or so I've been seeing increasing amounts of disk list
entries showing this in the amanda report:
FAILED [/bin/tar returned 1]
I've gone to the hosts involved and checked their logs and really thats
about as informative as it gets.
I've checked the tar
Paul Bijnens wrote:
On 2008-03-06 21:38, Steve Wray wrote:
Stefan G. Weichinger wrote:
Patrick M. Hausen schrieb:
So if you want to backup/copy an entire VM with the guarantee of
consistent hard disk state, you need to shut it down. Copying
a multi gigabyte virtal disk file is bound to take
Stefan G. Weichinger wrote:
Patrick M. Hausen schrieb:
So if you want to backup/copy an entire VM with the guarantee of
consistent hard disk state, you need to shut it down. Copying
a multi gigabyte virtal disk file is bound to take quite some time.
So you need to power down your virtual
Hi there,
We have just acquired an LTO3 Ultrium drive but we still have a tape
robot with AIT tape drive.
I am wondering if there is a way to use the AIT drive together with the
LTO drive in some useful fashion.
I doubt that RAIT would work as the capacity of the tapes is so
different, but I'm
Dominik Schips wrote:
Hello,
Am Dienstag, den 31.10.2006, 08:12 +1300 schrieb Steve Wray:
Hi there,
My amanda backup scripts do an amverifyrun after every run.
One of our backup sets is on a tape changer.
Sorry for the questinon, but I also have a tape changer.
How do you do
Gene Heskett wrote:
On Tuesday 31 October 2006 14:12, Steve Wray wrote:
Dominik Schips wrote:
Hello,
Am Dienstag, den 31.10.2006, 08:12 +1300 schrieb Steve Wray:
Hi there,
My amanda backup scripts do an amverifyrun after every run.
One of our backup sets is on a tape changer.
Sorry
Hi there,
My amanda backup scripts do an amverifyrun after every run.
One of our backup sets is on a tape changer.
Recently, amverifyrun appears to have been getting 'stuck', verifying
the same tape over and over again regardless of which tape was actually
used in the last backup run.
Most
Paul Yeatman wrote:
-In response to your message-
--received from Jean-Louis Martineau--
I have been seeing the same thing for about two weeks.
[snip]
This is all with Debian Etch.
Now I'm experiencing similar problems again as explained in this thread
but with Fedora 5 boxes.
I
Jon LaBadie wrote:
On Tue, Oct 17, 2006 at 11:44:53AM -0400, Steven Settlemyre wrote:
I have 24 tapes and a 8 tape changer. For some reason, it is going
13-16-15-14-17. How can I fix this? can i just force it to take 14
after 13 by only having 14 in there when it's expecting 16? My tapecycle
Geert Uytterhoeven wrote:
On Tue, 30 Aug 2005, Graeme Humphries wrote:
Guy Dallaire wrote:
Yes, thanks. I know about hard links. But how would it impact the size
or performance of my backups ?
Well, if a file is hard linked multiple times, it'll be backed up multiple
times. Therefor, a
Hi there,
I know that on a Linux firewall through which amanda traffic is routed
or natted, one needs to load the appropriate modules
(ip_conntrack_amanda, ip_nat_amanda).
I am wondering what we will need to do to ensure that amanda traffic can
pass/nat through an openbsd firewall with no
Hi there,
we'd like it if amanda would use /var/tmp/amanda instead of /tmp/amanda
Ideally, we'd do this without rebuilding the debian package.
I've noticed this in the examples/config.site and I'm wondering if I set
this to /var/tmp/amanda in my amanda.conf will this change all of
amanda's use
Gaby vanhegan wrote:
Hello again!
Whilst setting up a full dump configuration to do monthly full dumps to
tape, I'm torn between either:
strategy noinc
or
dumpcycle 0
To do a full dump. What's the difference here? Does it matter which
one I use?
Heres my reading of what I've
Peter Kunst wrote:
Hi Steve,
Steve Wray wrote:
Gaby vanhegan wrote:
Hello again!
Whilst setting up a full dump configuration to do monthly full dumps
to tape, I'm torn between either:
strategy noinc
or
dumpcycle 0
To do a full dump. What's the difference here? Does it matter which
one
Hi there,
we just had an inexplicable hiccup in our (recently configured) backup
cycle.
Night before last, the backup for this host went perfectly.
Last night, it didn't come back with its estimates.
So far as I can tell, there were no changes to the amanda config on this
host in between these.
I was wondering if there was any way to predict, say a few days in
advance, which tapes amanda would want to use?
Thanks!
David Newman wrote:
On Sun, 13 Feb 2005, Gene Heskett wrote:
On Sunday 13 February 2005 12:02, David Newman wrote:
Greetings. For backups to a server with one DLT-IV drive, I would
like to change the tape once per week. During the week, I would
like to do one full backup on day 1, and incremental
Hi there,
I've been reading this thread;
http://www.mail-archive.com/amanda-users@amanda.org/msg27491.html
which is interesting because we've been experiencing a very similar
problem since upgrading 2.6.8 to 2.6.9 on a small cluster here.
The amanda connection tracking is all built into the
Its interesting that they don't configure it to use gnu tar...
and so far as I can tell, none of the config that they give
would use gnutar to backup Solaris boxes.
On Fri, 14 Nov 2003 16:02, Galen Johnson wrote:
Jon LaBadie wrote:
Recently posted to the Big Admin
section of Sun's website is
the above, that it all went so swimmingly
well after merely changing $PATH...
On Thu, 13 Nov 2003 06:24, Paul Bijnens wrote:
Steve Wray wrote:
Finally I seem to have figured it out;
If $PATH has another version of tar which would be found
before the gnu tar, even though one explicitly
Hi all!
I've been having trouble getting amanda to support gnu tar
on Solaris boxes.
What I discovered was that even though I explicitly set the
path to gnu tar at configure time;
./configure other options --with-gnutar=/usr/local/bin/tar
and even though amanda appeared to configure for gnu
46 matches
Mail list logo
