ng
funny things also when you type uppercase, you'll be run out of options
already.
;)
Cheers, Jukka
[1] https://wiki.zmanda.com/index.php/GSWA/Build_a_Basic_Configuration
[2] https://wiki.zmanda.com/index.php/Getting_Started_with_Amanda
> > On Apr 25, 2020, at 5:55 AM, Jukka Salmi
Hello
I just installed Amanda 3.5.1 on a Debian 10.3 (buster) system and am
following the [1]"GSWA/Build a Basic Configuration" example.
$ amgetconf MyConfig tapecycle
4
$ amgetconf MyConfig dumpcycle
3
Running amdump a few times seemed to be successful, but the I noticed
that while the
Jukka Salmi -- amanda-users (2013-05-13 22:37:12 +0200):
Hello
I'm currently updating Amanda on some NetBSD/amd64 5.2_STABLE systems from
2.5.2p1 to 3.3.1; Amanda has been built from pkgsrc. So far the Amanda server
and one Amanda client have been updated. The first thing I tried after
Hello
Jukka Salmi -- amanda-users (2013-05-14 08:22:16 +0200):
Jukka Salmi -- amanda-users (2013-05-13 22:37:12 +0200):
Hello
I'm currently updating Amanda on some NetBSD/amd64 5.2_STABLE systems from
2.5.2p1 to 3.3.1; Amanda has been built from pkgsrc. So far the Amanda
server
Hello
Sorry, I only noticed your email after I sent my previous one...
Jean-Louis Martineau -- amanda-users (2013-05-14 10:39:15 -0400):
On 05/14/2013 02:22 AM, Jukka Salmi wrote:
critical (fatal): Can't locate object method new via package
Amanda::Xfer::Dest::Taper::Splitter (perhaps you
Jean-Louis Martineau -- amanda-users (2013-05-14 12:21:28 -0400):
On 05/14/2013 12:01 PM, Jukka Salmi wrote:
$ grep AMANDA_COMPONENTS
/usr/pkg/lib/perl5/vendor_perl/5.16.0/Amanda/Constants.pm
$AMANDA_COMPONENTS = ndmp;
That's the problem, it should be like:
$AMANDA_COMPONENTS = server
Jean-Louis Martineau -- amanda-users (2013-05-14 12:21:28 -0400):
On 05/14/2013 12:01 PM, Jukka Salmi wrote:
$ grep AMANDA_COMPONENTS
/usr/pkg/lib/perl5/vendor_perl/5.16.0/Amanda/Constants.pm
$AMANDA_COMPONENTS = ndmp;
That's the problem, it should be like:
$AMANDA_COMPONENTS = server
Hello
I'm currently updating Amanda on some NetBSD/amd64 5.2_STABLE systems from
2.5.2p1 to 3.3.1; Amanda has been built from pkgsrc. So far the Amanda server
and one Amanda client have been updated. The first thing I tried after
the update was to check the latest backup (created by the old
amidxtaped
Regards, Jukka
Jean-Louis
Jukka Salmi wrote:
Hello,
I'm having a problem with amrecover(8) on Linux systems. The backup
server runs Amanda 2.5.2p1 on Debian lenny, the backup client runs
Amanda 2.4.4p3 on Debian sarge. Running amrecover(8) on the server
works fine
, works fine now, thanks a lot!
Hmm, I wonder why the Debian package adds those arguments to the
amandaidx and amidxtape services... Seems to be a bug, doesn't it?
Regards, Jukka
Jean-Louis
Jukka Salmi wrote:
Jean-Louis Martineau -- amanda-users (2009-04-03 11:49:53 -0400):
amrecover from
Hello,
every now and then I see this error on an otherwise perfectly working
Amanda system (server 2.4.4p3, client 2.5.1p1):
FAILURE AND STRANGE DUMP SUMMARY:
host.staso / lev 0 FAILED [data timeout]
The client's sendbackup log for such a failed run:
sendbackup: debug 1 pid 14726 ruid 34
Hello,
while reading amanda.conf(5) I noticed the following comment about the
`include' dumptype option:
All include expressions are expanded by Amanda, concatenated in one
file and passed to GNU-tar as a --files-from argument. They must
start with ./ and contain no other /.
I've been
Paul Bijnens -- amanda-users (2008-10-13 14:18:51 +0200):
On 2008-10-13 13:55, Jukka Salmi wrote:
Hello,
while reading amanda.conf(5) I noticed the following comment about the
`include' dumptype option:
All include expressions are expanded by Amanda, concatenated in one
file and passed
Jukka Salmi -- amanda-users (2008-09-10 14:40:29 +0200):
[...]
Hmm, EINTR. I'll try to reproduce this with another version of NetBSD
(trying with 4.0_STABLE ATM) before debugging any further...
It seems that I hit a known problem:
http://mail-index.netbsd.org/pkgsrc-users/2008/06/14/msg007388
Dustin J. Mitchell -- amanda-users (2008-09-09 09:58:15 -0400):
On Tue, Sep 9, 2008 at 8:50 AM, Jukka Salmi [EMAIL PROTECTED] wrote:
c:10080 - s:846 udp Amanda 2.5 REP HANDLE ... CONNECT DATA 56639 MESG
56638 INDEX 56637 ...
s:846 - c:10080 udp Amanda 2.4 ACK HANDLE ...
s:50029 - c
Jukka Salmi -- amanda-users (2008-09-05 14:51:31 +0200):
Hello,
I'm trying to add a NetBSD system running Amanda 2.5.2p1 as a backup
client to an existing backup server running Amanda 2.4.4p3 on Linux.
Running amcheck(8) shows no problems, and both the `noop' and `sendsize'
stages during
Hello,
I'm trying to add a NetBSD system running Amanda 2.5.2p1 as a backup
client to an existing backup server running Amanda 2.4.4p3 on Linux.
Running amcheck(8) shows no problems, and both the `noop' and `sendsize'
stages during an amdump(8) run seem to be fine. But then, during the
Dustin J. Mitchell -- amanda-users (2008-06-28 13:53:43 -0400):
Actually, it's not quite wrong. Gnulib is a little weird. What the
rest of that macro does is to *check* for alloca.h, and if it's not
found in the system, create a local copy of the file. I think that
the compiler wasn't
Dustin J. Mitchell -- amanda-users (2008-06-29 14:22:16 -0400):
I would remove the #ifdef HAVE_ALLOCA_H from amanda.h and just
unconditionally include alloca.h.
Hmm, the problem was that there is no alloca.h on my systems, so this
won't work ;-)
The attached patch fixes the problem for me, but
Dustin J. Mitchell -- amanda-users (2008-06-27 13:56:06 -0400):
On Thu, Jun 26, 2008 at 11:34 AM, Jukka Salmi [EMAIL PROTECTED] wrote:
This is on NetBSD/i386 where at least fcntl, flock and lockf are
available; config.log reveals that the record locking function tests
failed because
Jukka Salmi -- amanda-users (2008-06-25 12:37:15 +0200):
Hello,
since I upgraded an Amanda installation from 2.4.4p4 to 2.5.2p1, backup
reports always contain lines like these:
FAILURE AND STRANGE DUMP SUMMARY:
amreport: ERROR unexpected log line: 20080625 2 [sec 45.227 kb 41655 kps
Dustin J. Mitchell -- amanda-users (2008-06-26 10:11:54 -0400):
[...]
Unfortunately, that file is basically the intermingled freeform stderr
of just about every process spawned by amdump/amflush, so there's no
single interface through which we can funnel all notifications. The
long-term plan
Jean-Louis Martineau -- amanda-users (2008-06-26 10:12:11 -0400):
Amanda lock the file while writing to it.
What is the output of: amadmin vv version | grep LOCKING
Which filesystem is used, is it NFS mounted?
Hmm, amadmin reveals that
LOCKING=**NONE**
on my system, which probably
Hello,
since I upgraded an Amanda installation from 2.4.4p4 to 2.5.2p1, backup
reports always contain lines like these:
FAILURE AND STRANGE DUMP SUMMARY:
amreport: ERROR unexpected log line: 20080625 2 [sec 45.227 kb 41655 kps
921.7]
amreport: ERROR unexpected log line: 20080625 0 [sec
Hello,
to backup some client systems I use an Amanda config containing
dumpcycle 0 days
tapecycle 4 tapes
which I run manually from time to time. The config uses the file driver
(in case this matters).
Because on some clients lots of files were moved during the last amdump
run,
Joshua Baker-LePain -- amanda-users (2006-06-17 06:53:42 -0400):
On Sat, 17 Jun 2006 at 10:33am, Jukka Salmi wrote
to backup some client systems I use an Amanda config containing
dumpcycle 0 days
tapecycle 4 tapes
which I run manually from time to time. The config uses
Hi,
on a Amanda 2.4.4p4 system which ran fine for some months I noticed today
amverify was still running after about 5 hours; normally it only takes some
minutes to complete. I killed the process, and then received the so far
missing verify report (which was about 3MB...). For some reasons a
Jukka Salmi -- amanda-users (2005-06-03 13:14:09 +0200):
Hi,
on a Amanda 2.4.4p4 system which ran fine for some months I noticed today
amverify was still running after about 5 hours; normally it only takes some
minutes to complete. I killed the process, and then received the so far
missing
Hi,
Jean-Louis Martineau -- amanda-users (2005-06-03 10:10:19 -0400):
Could you try the attached patch.
thanks. After applying it amverify doesn't loop endlessly anymore:
[ ... successful checks ... ]
Checked host1._opt.20050603.1
** Error detected (host1._opt.20050603.1)
amrestore: WARNING:
Lengyel, Florian -- owner-amanda-users (2005-06-03 11:18:05 -0400):
This business about tar reminds me of a not-terribly well documented problem
with tar: under some operatinjg systems, tar has a 2 gigabyte limit on the
size of
the tar archive! The tar that came with red hat 7.3 had this
Eric Siegerman -- amanda-users (2004-11-04 14:02:13 -0500):
On Wed, Nov 03, 2004 at 10:53:59PM +0100, Jukka Salmi wrote:
Hmm, when setting dumpcycle to zero, to what value should runspercycle
be set if amdump runs once a day? Zero (same as dumpcycle) or one?
Both settings are equivalent
Hi,
Erik Anderson -- amanda-users (2004-11-03 14:44:55 -0600):
[...]
full backup every night.
[...]
dumpcycle 1 day
According to the amanda man page you should set dumpcycle to zero to
get full dumps each run.
Hmm, when setting dumpcycle to zero, to what value should runspercycle
be set if
Toralf Lund -- amanda-users (2004-10-18 16:07:48 +0200):
Jukka Salmi wrote:
Hi,
I'm using the chg-disk tape changer. When restoring files using
amrecover, after adding some files and issuing the extract command,
amrecover tells me what tapes are needed, and asks me to Load tape
label now
Hello,
Paul Bijnens -- amanda-users (2004-10-18 22:14:10 +0200):
Before the chg-disk tape changer was written, I used the chg-multi
changer with the file-driver. It's a little more complicated
to configure, but the advantage is that it finds and load automatically
the vtapes.
To what extent
Hi,
I'm using the chg-disk tape changer. When restoring files using
amrecover, after adding some files and issuing the extract command,
amrecover tells me what tapes are needed, and asks me to Load tape
label now. I load the needed tape using amtape, and tell amrecover
to continue. After a while
Hello,
using Amanda 2.4.4p2, I'd like to do daily full backups, no matter
what happens. I.e.: There are about 20 tapes, and humans (as opposed
to Amanda) are responsible for the correct tape beeing loaded before
each amdump run. If one forgets to change tapes the next run should
overwrite the
Paul Bijnens -- amanda-users (2004-06-23 13:14:45 +0200):
Jukka Salmi wrote:
To achieve this I set dumpcycle and runspercycle to 0, and tapecycle
and runtapes to 1.
This seems to work so far, except for the planner being discontent:
NOTES:
planner: tapecycle (1) = runspercycle (1
Paul Bijnens -- amanda-users (2004-06-23 14:53:04 +0200):
In that case, yes, just ignore the note.
OK, I'll try that... But hmm, why does one get warned if
tapecycle = runspercycle? How could that be a problem?
Oops. I was wrong. The note is there indeed.
(why didn't I see that this
38 matches
Mail list logo
