Hi,
amanda 2.5.1 doesn't support old syntax/obsoletes options.
Use holdingdisk and logdir instead.
Jean-Louis
Chan, Victor wrote:
To all,
I’ve changed up to Amanda 2.5.1. For some reason, these three
parameters that used to work in Amanda.conf didn’t work anymore.
diskdir “var/tmp:
Gene Heskett wrote:
On Tuesday 19 September 2006 08:10, Jean-Louis Martineau wrote:
Hi,
I found the problem that lead to the timeout waiting for ACK error.
If you have this problem, try the latest 2.5.1 snapshot from
http://www.iro.umontreal.ca/~martinea/amanda
Jean-Louis
Ok, I
Steve,
Anything about ssh in your system log?
Could you ssh from the server to the client without amanda?
Did it create /tmp/amanda/amanda/amandad.*.debug files?
Jean-Louis
Steve Newcomb wrote:
We've been using Amanda continuously since 1999. Amanda has minimized
our backup effort and
Bruce,
I committed the suggested fix to the 2.5.1 tree.
Thanks
Jean-Louis
Bruce Thompson wrote:
Hi Paddy,
I've located what appears to be the source of the _keytable errors.
in common-src/util.h there appears:
- BEGIN -
typedef struct {/* token table entry */
char
Jean-Francois,
Could you send the amrecover.timestamp.debug and
amindexd.timestamp.debug files?
Jean-Louis
Jean-Francois Malouin wrote:
Hello,
amanda-2.5.1 on irix-6.5.x using bsdtcp auth
amrecover don't want to play ball:
yorick 130# /opt/amanda/amanda10/sbin/amrecover
AMRECOVER Version
Hi,
Irix doesn't have the same return value for vsnprintf as linux have.
Could you try this patch.
Jean-Louis
Jean-Francois Malouin wrote:
* Jean-Louis Martineau [EMAIL PROTECTED] [20060921 13:04]:
Jean-Francois,
Could you send the amrecover.timestamp.debug and
amindexd.timestamp.debug
Jean-Francois,
Could you try this patch?
Jean-Louis
Jean-Francois Malouin wrote:
Hello,
I've been testing 2.5.1 for a few days now and I have 2 nitpicks:
With 2.4.5 'amtoc -a' produces outputfile with names
label_of_tape.toc as per the man page. This doesn't seem to be the
case anymore with
Fabio,
You installed amanda-2.5.1-20060922.tar.gz on the client?
Could you send me the sendbackup.timestamp.debug file?
Jean-Louis
Fabio Corazza wrote:
Jean-Louis Martineau wrote:
Fabio,
It's a known bug, it is already fixed.
Get the latest 2.5.1 snapshot from
http://www.iro.umontreal.ca
David Trusty wrote:
Hi,
I checked the logs. There is no error message, and I have no cron
running either.
I can duplicate the problem every time.
Is it always at the same place (part 51)?
Could you provide the LABEL= line from the amidxtaped.*.debug file?
What is the output of `amadmin
The Amanda core team is pleased to announce the release of Amanda
2.5.1p1. This is a bug fix only release, it fix all known bug in 2.5.1.
Source tar ball can be downloaded from
http://sourceforge.net/projects/amanda
or http://www.amanda.org
If you find bugs or have feature requests, please
Hi,
The timeout waiting for ACK is a known problem in 2.5.1
It is fix in amanda 2.5.1p1.
Jean-Louis
JB Segal wrote:
Kevin Till wrote:
Nick Brockner wrote:
Hi All,
I am new to amanda, and I have just set up a backup scheme and am
trying
to test (using 2.5.1). When I have only one of
amverify try to match the name of the program with tar/gtar/gnutar.
Your /usr/local/bin/gtar should work but not /usr/local/bin/mygtar,
you must add mygtar to the list.
But this features was added after 2.4.2p2
Jean-Louis
Olivier Nicole wrote:
Hi,
This may be because I am using a prehistoric
Your bug is also with:
chmod -R 6770 /home/amanda/libexec/* /home/amanda/sbin/*
Setting all binary to suid and sgid is a bad idea, especially since you
set their owner to root.
With the owner set to amanda, it's not a good idea either.
You should only set suid and sgid on required binary
Steve Newcomb wrote:
Jean-Louis Martineau [EMAIL PROTECTED] writes:
Your bug is also with:
chmod -R 6770 /home/amanda/libexec/* /home/amanda/sbin/*
Setting all binary to suid and sgid is a bad idea, especially since
you set their owner to root.
From my script
Jean-Francois,
Could you try these two patch?
Jean-Louis
Jean-Francois Malouin wrote:
Irix-6.5.x amanda-2.5.1p1.
o- amcleanup exits with an error:
# su amanda -c amcleanup config
amcleanup: no unprocessed logfile to clean up.
amcleanupdisk: Usage: amcleanupdisk confdir
amcleanup:
I have been seeing the same thing for about two weeks.
I'm running Fedora Core 5, and the same version of Amanda. Last night
my computer crashed, so I ran fsck on everything. There were numerous
errors on my / file system, where /var/lib/amanda resides. If those
were real errors I would think
Mike,
The patch is not required with amanda 2.5.1
Could you send me the amandad.timestamp.debug file and the
sendsize.timestamp.debug file
Jean-Louis
Mike Coyne wrote:
I am currently working with amanda2.5.1-p1 on a HPUX 11.11 machine. I
seem to be getting my packets truncated to about
amanda generate a lot of debug and log files, have you looked at them?
What's in amdump.1 and planner.timestamp.debug?
Jean-Louis
Giuseppe Sacco wrote:
Hi list,
I am (still) configuring amanda for the first time. I am at the point
where everything should be configured, but, when running
H,
The -o flags are not sent to all subprocess. the taper process never get
your tapedev overwrite.
I will try to make a patch available for that soon.
Are you using a changer? It might need fix too.
Jean-Louis
Lee, Raymond wrote:
Thanks, Sven. That's exactly what I'd like to do.
Lee,
Could you start from
http://www.iro.umontreal.ca/~martinea/amanda/amanda-2.5.1p1-20061020.tar.gz
and apply the attached patch.
The patch will send the -o options to taper/dumper and chunker process.
changer will not get the options.
run: amdump DailySet1 -o tapedev=/dev/null -o
Hi Tanniel,
You are the second person to report this problem with the debian package.
Could you try
http://www.iro.umontreal.ca/~martinea/amanda/amanda-2.5.1p2-chg-scsi.tar.gz
Compile it, you don't need to install it.
cd to your config directory.
run '/path/to/new/chg-scsi -info'
send me the
Hi Ian,
Remove the trailling '/' from your include/exclude.
Jean-Louis
Ian R. Justman wrote:
Hi, all.
To summarize, I'm trying to back up a hashed spool of mailboxes on our
mailserver at work. The top directory of that spool has five hundred
directories numbered 0-499 and I want to back
Frank,
In 2.5.1, we removed all old options/syntax from the configurations files.
For the problem of holdingdisk 'use' set to 0, it's a bad check that was
added to amcheck, amdump will work as expected with the use set to '0'
Jean-Louis
Frank Smith wrote:
Since I play further on the edge
Frank Smith wrote:
Thanks to Jean-Louis for the reply on my amcheck issues.
I got some really strange results from my first amdump run last
night after my upgrade.
I updated my home Amanda server and clients (Debian etch
packages) from 2.5.0p2-2.1 to 2.5.1p1-2, and tar from 1.15.91-2 to
Hi,
A s/__/_/ should be enough, you will need to also do it in the gnutar-lists.
A will release a patch that do the rename automatically.
Jean-Louis
Jean-Francois Malouin wrote:
Hello,
Upgrading from 2.4.5 to 2.5.1p1 and 2.5.1p2 I've noticed that if a DLE
has a diskname with an underscore
Could you post amandad.timestamp.debug file from yorick?
Jean-Francois Malouin wrote:
On a server running irix-6.5 and amanda 2.5.1p2
planner debug shows:
security_getdriver(name=bsdtcp) returns 4075aa8
security_handleinit(handle=1001d4a8, driver=4075aa8 (BSDTCP))
sendbackup and runtar debug file.
It's not the first time I notice that when a DLE fails to make it
to tape successfully processes are left running...
* Jean-Louis Martineau [EMAIL PROTECTED] [20061122 09:32]:
Could you post amandad.timestamp.debug file from yorick?
Jean-Francois Malouin wrote
Geert Uytterhoeven wrote:
Hi,
Since a few days one of my DLEs consistently fails with:
| /-- anakin /home/src lev 1 FAILED [no backup size line]
| sendbackup: start [anakin:/home/src level 1]
| sendbackup: info BACKUP=/bin/tar
| sendbackup: info RECOVER_CMD=/bin/gzip -dc |/bin/tar -f
Amanda expect tar to exit with a broken pipe.
I looks that we need to kill it.
Jean-Louis
Jean-Francois Malouin wrote:
* Jean-Louis Martineau [EMAIL PROTECTED] [20061123 17:20]:
Do amandad is running?
To be sure that I would hit the problem again I didn't load new tapes
so after
Steve,
Could you send me the amdump.1 log file?
What is at the beginning of the holdingdisk files? Could you send me one
of the header?
Jean-Louis
Steve Newcomb wrote:
As a temporary measure, I have re-installed 2.5.1 on my server
and it's working again, but I'd prefer to be running the
Jean-Francois,
Could you try the attached patch, it should kill the tar process.
If it still doesn't work, could you attach a debugger to the sendbackup
process to know where it is?
Jean-Louis
Jean-Francois Malouin wrote:
* Jean-Louis Martineau [EMAIL PROTECTED] [20061123 17:20]:
Do
Steve,
Could you try the attached patch for 2.5.1p2?
It remove the check for tapedev if tpchanger is defined.
All changer check tapedev if it require it.
Jean-Louis
Steve Newcomb wrote:
I'm using chg-multi. It works under 2.5.1. When I upgraded to
2.5.1p2, it stopped working, even with no
dumcycle is a number of days? you set it to 4 days.
The scheduler work in days, not in number of tapes or run.
Jean-Louis
René Kanters wrote:
Hi,
I am trying to set up my test system so that I get on 5 tapes 2 full
backups at any time and incremental ones in between them. I thought
that I
It's a new features of tar-1.16
Try the attached patch.
Jean-Louis
Tony Lill wrote:
I'm running amanda 2.5.1p1 on sparc/solaris with gnu tar v1.16, and tar
is exiting with error code 1, presumably because some files have changed
while they were being read.
I thought that amanda was supposed
mario wrote:
Hello List,
i am running Amanda version 2.4.5 on Ubuntu Breezy and i get this error:
These dumps were to tape TEST-2.
The next tape Amanda expects to use is: a new tape.
The next new tape already labelled is: TEST-3.
FAILURE AND STRANGE DUMP SUMMARY:
planner: ERROR
Thorsten,
Could you try the attached patch?
If it doesn't work, could you send me the config/config.h file?
Jean-Louis
Thorsten Bremer wrote:
Hi,
I'm using the pre-build package of Amanda from Debian 3.1 until now.
But I want to try to improve my DLT-Streamer by feeding him with a
bigger
You hit a known bug in 2.5.p1 with parsing the disklist file, it is
fixed in 2.5.1p2.
I didn't remember the detail, but try 2.5.1p2
Jean-Louis
Joel Coltoff wrote:
Hi,
I added a new DLE today
cluster1-node1.wmi.com /services /services {
system-files
} 1 local
Along with the
Now I remember,
The bug is with the use of strategy skip or ignore.
If you want to use them, you must upgrade your server to 2.5.1p2.
Jean-Louis
I moved the dumptype define for this DLE to the bottom of amanda.conf and
the problem was still there. When I added strategy skip to the dumptype
Frank Smith wrote:
Debian package 2.5.1p1-2.1
At home I leave the tape out of the drive most of the time and
only insert a tape and run amflush when the space used on the
holding disk approaches the capacity of my tape. This has been
working well until the latest upgrade (which overwrote the
Nicki,
Amanda 2.4.4p3 and 2.5.1p1 should be compatible.
These two versions might not have been tested, but I believe they are
compatible.
Could you send me the complete following debug files:
client: /tmp/amanda/client/config/sendbackup.timestamp.debug
client:
Nicki,
The next amanda version will understand tar returning 1.
You can already use the latest snapshot or CVS.
Jean-Louis
Nicki Messerschmidt, Linksystem Muenchen GmbH wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
another problem with my backup with debian testing as a client was
amanda remove most the environment variable for security reason.
mailx require the HOME environment variable to find the user .mailrc file
Could you try the attached patch.
Do someone know if the HOME environment variable can be used to break
suid program?
Jean-Louis
Thomas Steiger wrote:
chg-manual require user input.
You can't run it from cron.
Jean-Louis
Hans Almqvist wrote:
Hi all!
I am a bit puzzled of the behavior of amcheck.
System : OpenBSD 4.0.
Amanda : amanda-2.5.1p2
crontab:
#minute hourmdaymonth wdaycommand
5 2 * * 1,3,6
amverify/amverifyrun can't verify split dump.
Jean-Louis
Gordon J. Mills III wrote:
I have recently setup my config to be able to split dumps across tapes due
to an increase in size. I get the following message in the backup report:
taper: no split_diskbuffer specified: using fallback split
Since you are using the old amindexd/amidxtaped protocol, you must
configure them in your server xinetd the same way you did for your
amanda 2.4.5 server.
Deb Baddorf wrote:
What kind of configuration do I need, now that I've upgraded my
server to 2.5.1p2? Most of the clients are
Tell amrecover to connect to your tape server with the -s and -t options.
You don't need to install amidxtaped on the client
Deb Baddorf wrote:
My clients seem to fail at doing recovers unless I have the
amidxtaped process
installed (and in inetd.conf) on the client. Yet doing an
Jon LaBadie wrote:
There is an implied assumption in the chg-disk script that the virtual
tapes will be online at all times. This comes from the line:
LASTSLOT=`amgetconf$SUF tapecycle`
In tape changer scripts like chg-mtx the last slot and tapecycle are
not linked.
You might submit a
device priority use by mtx:
the -f argument
CHANGER environment variable
TAPE environment variable
/dev/changer
chg-zd-mtx set the TAPE environment variable, mtx use it unless you have
the CHANGER variable set.
maybe we should set CHANGER too.
I don't know why it doesn't use -f, but
Toomas Aas wrote:
Hence my question: Does Amanda now enforce the length parameter when
writing to a vtape? In such a way that if length is reached in the
middle of taping the DLE then taping is stopped and out of tape
announced?
Yes, we fixed that bug.
If you want old behavior, increase your
Lars Monsees wrote:
Hello,
I´m quite new to amanda so I have left something out don´t slap me =)
(I know from the documentation that it is possible to use ?* wildcards.)
We have a server with several customer domains located at our ISP who controls
the backup. Therefore, it is only possible
Which release of amanda? There was a bug in amrestore, it stopped on the
10th file.
You can fsf the the correct file before you execute amrestore.
Jean-Louis
Chris Cameron wrote:
This is what I'm seeing:
$ ./amadmin daily info devl2 '/dev/md/dsk/d8'
Current info for devl2 /dev/md/dsk/d8:
amanda is not localized, it doesn't understand the french date.
The attached patch fit it by using a not localized time
This patch works only run done with the patch.
Jean-Louis
Thomas Ginestet wrote:
Hi list,
When using amstatus this morning (february the first) and I've got the
folllowing
Mark,
Install latest amanda 2.5.1p2 snapshot from
http://www.zmanda.com/community-builds.php,
or wait for 2.5.1p3, it will be release next week.
Jean-Louis
Mark Hennessy wrote:
I'm using AMANDA 2.51p2 and gtar 1.16.
I want to make AMANDA ignore any error 1 response from gtar and react like
Jean-Francois,
Maybe it's an incompatibility with the sed command,
could you try the attached patch?
If it still doesn't work, could you send me the
chg-zd-mtx.timestamps.debug file.
Jean-Louis
Jean-Francois Malouin wrote:
Hello,
Just testing 2.5.1p2-20070202 and looking at the ChangeLog
Alan,
Could you send the amandad.timestamps.debug file?
You said all other client works, are they using the same amanda version?
Do they have one or more DLE?
Jean-Louis
Alan Pearson wrote:
Ok,
I've managed to get more info on this.
If I run amdump with the failing entry in the disklist on
The Amanda core team is pleased to announce the release of Amanda
2.5.1p3. This is a bug fix only release, it fix all known bug in 2.5.1.
Source tar ball can be downloaded from
http://sourceforge.net/projects/amanda
or http://www.amanda.org
If you find bugs or have feature requests, please
Try setting the DUMP/RESTORE variables before executing ./configure
Jean-Louis
Chris Hoogendyk wrote:
ok. just tried this. I have /usr/local/etc/amanda/tools/ with symlinks
for gtar and ufsdump in that directory. Before doing the ./configure,
I added that directory to the beginning of PATH
Yogesh Hasabnis wrote:
Hi,
The output of the amandad.timestamps.debug is as
given below. But an interesting and unfortunate thing
is that I downgraded from amanda-2.5.1p2 to
amanda-2.5.0p2 and it started working fine. So I am
giving up with amanda-2.5.1 at least for the time
being.
amandad:
Sascha wrote:
okay here is the complete way i did that
back-srv:/backup/restore# amrecover daily
AMRECOVER Version 2.5.1p1. Contacting server on localhost ...
220 back-srv AMANDA index server (2.5.1p1) ready.
Setting restore date to today (2007-02-13)
200 Working date set to 2007-02-13.
200
Cédric,
Amanda can't find the IP for the hostname 'pc-cedric'.
Check your name server configuration, /etc/hosts, ...
Jean-Louis
Cédric Lucantis wrote:
hi!
I'm actually trying to upgrade amanda to the latest svn version (from the cvs
2.51b2 version which was working fine) and by the same
Hi,
Run 'amstatus config', it will tell you why it don't start new dump in
parallel.
Jean-Louis
Dipl.Ing.Trompler Wilhelm wrote:
Dear reader,
I am using VERSION=Amanda-2.4.4p2 on a LINUX 2.6.5 with LTO-3 tapes. In
general the performance is great, but on every forced, complete backup, the
Jean-Francois,
Do you have an amanda.timestamp.debug file? Post it.
Could you show your inetd configuration?
Did 10088 the correct port number for your confX testing config?
Jean-Francois Malouin wrote:
Hi,
Just had my first hand at 2.5.1p3 and I got a error with amcheck similar
to the one I
Jean-Francois Malouin wrote:
amandad:COMPRESS_BEST_OPT=--best UNCOMPRESS_OPT=-dc
amandad: time 0.000: getpeername returned: Transport endpoint is not connected
This is strange, it's like the stdin of amandad is not connected to the
network socket.
Apply the attached patch and
PROTECTED]
---
Erdös 4
Jean-Louis Martineau wrote:
Chris,
The attached patch fix the problem.
The problem is the two 'S', one of them should be 'h'.
The patch is already in the CVS.
Jean-Louis
Chris Stenton wrote:
Not sure if this is to do with the FreeBSD port but upgrading
Yogesh,
The exact same config you are using for 2.5.0 should also work for 2.5.1
Jean-Louis
Yogesh Hasabnis wrote:
Hi,
I decided to use amanda-2.5.0 instead of 2.5.1 because
I was not able to resolve some configuration issues
related to 2.5.1. I would like to know which features
I would
Gene,
Sorry for this stupid typo, I committed the wrong patch.
Try today's snapshot.
Jean-Louis
Gene Heskett wrote:
Greetings;
I didn't get an email from amverify this morning, having installed
amanda-2.5.1p3-20070216 last evening.
From the email genes-amanda-helper sent me:
Verify
Gene,
You found a bug.
Old debug files are not removed, this bug exist since we created subdir
for debugging files, only the root is cleaned.
Jean-Louis
Gene Heskett wrote:
Greetings;
I just unpacked the 2.5.1p3-20070220 src tree and ran a grep
for 'amanda-dbg', finding it only in my
Gene,
Try the attached patch.
Jean-Louis
Gene Heskett wrote:
On Wednesday 21 February 2007, Jean-Louis Martineau wrote:
Gene,
You found a bug.
Old debug files are not removed, this bug exist since we created subdir
for debugging files, only the root is cleaned.
Jean-Louis
I'd
Debug files are kept 4 days by default (can be configured with
'--with-debug-days').
Only the files from the same program will get deleted.
eg. amcheck will only delete the amcheck.*.debug files
Jean-Louis
Gene Heskett wrote:
On Wednesday 21 February 2007, Jean-Louis Martineau wrote
Jeffrey,
If amrecover doesn't fsf to the correct file, you can disable the fsf by
setting
'amrecover_do_fsf off' in your amanda.conf file.
What is the 'file' reported by 'amadmin config find client.lbl.gov
hda1' ? is it 37 or 38?
Could you send me the amrecover.*.debug, amidxtaped.*.debug
Jeffrey,
It's a known bug, it was fix on 2007-09-19
You can try the attached patch or upgrade your server to 2.5.1p3.
Jean-Louis
jeffrey d anderson wrote:
I'm running amanda 2.5.0p2 on a RHEL3 server with numerous clients of various
flavors. I recently needed to perform a recover and found a
kamalesh krishna murthy wrote:
hi stefan this is my disklist entry
129.227.150.124 http://129.227.150.124
/home/kamalesh/kamalesh/amanda-2.5.0p2 user-tar-span
Report the output of 'amadminTEST 129.227.150.124
http://129.227.150.124 /home/kamalesh/kamalesh/amanda-2.5.0p2'.
That way, we
This is a known bug, which is fixed in latest snapshot from
http://www.zmanda.com/community-builds.php
You have an exactly 32k bytes files in your holding disk, you must
remove it.
Jean-Louis
Francesc Guasch wrote:
Hi. I migrated an old amanda server 2.4.5p1 to a new 2.5.1p1.
So I copied
This problem is fixed.
It will use single '_' it it exist, or double '__' if it exist.
If none exist, it will create with a single '_'.
Jean-louis
Jean-Francois Malouin wrote:
Hi,
I can't seem to find any info on that post I made a while ago
and if any provisions have been made to fix it in
Alan,
Try the attached patch, it add krb5principal and krb5keytab to the
amanda-client.conf file.
Jean-Louis
alan pearson wrote:
Ok, so now I'm fighting with amanda-client.conf
It seems it only allows options that are specified in the man page, so I cannot
specify the krb5principal or
If you can't kill sendsize, it's because it is hang in a system call.
It's often when it try to access a mount point.
Do you have a hanged mount point?
did df also hang?
Jean-Louis
Toralf Lund wrote:
We just started to get a serious problem with our amdump execution
(Amanda 2.5.0p2). As
Read the ReleaseNotes and docs/howto-auth.txt
You can disable the amindexd and amidxtaped services, they are not use
by newer amrecover.
You must add '-auth=bsd amdump amindexd amidxtaped' as argument to
amandad in your inetd.conf file.
Alternatively, you can use amrecover with ssh, read the
Gene Heskett wrote:
Greetings;
In my troubleshooting of the 2.6.21-rc* vs tar thinking the whole system
is new, where it works normally for any kernel up to 2.6.20.3. I find I'm
in need of an amestimate command, to have amdump survey the system and
report how much data (before compression
Gene Heskett wrote:
Ahh, I see, there are two 'planner's on the system, one is a gtk tool of
some sort, and one that is part of amanda is in /usr/local/libexec.
Running this as root gives a way too verbose output, can I strip it down
to just the final results?
No
What I need is the line
Steven,
It is a known bug, it is already fixed in the CVS tree.
Try the latest 2.5.1p3 snapshot from
http://www.zmanda.com/community-builds.php
You can also try to use wildcard: cd Directory?with?space
Jean-Louis
Steven Atkinson wrote:
Hi,
I am using amanda-2.5.1p3 with DLEs backed up
Douglas,
Could you try the attached patch? it might fix the coredump.
What do you have in the amanda.timestamps.debug files? It should show
an error message.
Jean-Louis
Douglas K. Rand wrote:
I'm running an Amanda client on a pair of FreeBSD 5.4 and after
upgrading from 2.4.5p1 to 2.5.1p3
Karsten,
Did you get an amidxtaped debug fileson the server? What did it contains?
Did amidxtaped configured correctly in xinetd?
Any xinetd log?
Jean-Louis
Karsten Fuhrmann wrote:
Hello List,
i have a serious situation here, i can not recover anything from my
backups anymore. I am using
You must configure amanda with '--with-bsdtcp-security' if you want to
use the bsdtcp auth mechanism.
Jean-Louis
Shehab wrote:
Hello,
I am facing some configuration issue with Amanda. When I am checking
the configuration it gives the following error:
sh-3.1$ amcheck daily
The 'Illegel seek' is not a problem.
The sendsize is working correctly, the problem is with sendbackup
Could you post the sendbackup and amandad debug files?
Jean-Louis
Chris Cameron wrote:
I have Amanda 2.5.1p3 running on Solaris 8 for the server, and the
client is the same version running
Jurgen,
There is no file: driver in 2.4.2, you must upgrade to a newer release.
Jean-Louis
Jurgen Pletinckx wrote:
Dear all,
In my continuing quest to master an inherited Amanda 2.4.2p install,
I tried playing around with the file driver, as detailed in
FL wrote:
What does the fllowing error mean?
Something really bad, could you post the amflush.1 log file?
What's in your holding disk? ls -alR /path/to/holding/disk
-- Forwarded message --
From: backup [EMAIL PROTECTED]
Date: Mar 30, 2007 12:09 AM
Subject: Daily Backup AMFLUSH
Could you post the amdump.1 log files and the
curinfo/b02.foo.com/_var_db_pkg/info file.
Charles Sprickman wrote:
Hello all,
I recently upgraded from 2.4.3 to 2.5.1p3 and things have mostly been
working correctly except for a few rough edges. To complicate
matters, we also upgraded from an
/var
ls -ald /var/db
ls -ald /var/db/amanda
du /var/db/amanda
Jean-Louis
Charles Sprickman wrote:
Hello all,
On Sat, 31 Mar 2007, Jean-Louis Martineau wrote:
Could you post the amdump.1 log files and the
curinfo/b02.foo.com/_var_db_pkg/info file.
Last night's run has gotten worse
[EMAIL PROTECTED] wrote:
Hi,
I have a lot of computers to backup running on different os centos, redhat, debian, gentoo, freebsd, on those computers the amanda-client is running with different users (amanda, backup, dump...)
How it's possible to backup all those computers with one
Sebastian,
amanda think your data are not compressible because you didn't use
software compression before.
It will adapt to the new config after a few run.
Temporary, you can lie to amanda and increase the length of your tapetype.
Jean-Louis
Sebastian Henrich wrote:
Hello,
I'm using
Look in the client sendsize.*.debug or sendbackup.*.debug file to find
the error reported by tar.
Which tar release? (tar --version)
If it's tar 1.16, you need amanda-2.5.1p3
Jean-louis
Glenn English wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm using v 2.5.1p with tar. The
Use 'settape' command to set the tape drive you want to use.
Charles Sprickman wrote:
Hi all,
I'm about to give up on 2.5, this is the latest error.
Since amanda has been acting so odd, I thought I'd try some recovery
to see what happens. My results leave me with little confidence that
The seek failed: Illegal seek are normal error.
The got partial result lines are expected.
You have no problem with the estimate phase, don't try to search for bug
there.
Jean-Louis
Charles Sprickman wrote:
Perhaps the root of the problems I'm having, perhaps not.
I keep saying I'm done
on the server and amandad.*.debug
and sendbackup.*.debug in the client.
Jean-louis
Charles Sprickman wrote:
On Tue, 10 Apr 2007, Jean-Louis Martineau wrote:
The seek failed: Illegal seek are normal error.
The got partial result lines are expected.
You have no problem with the estimate phase
Post the amdump.1 log file.
Jean-Louis
Sebastian Henrich wrote:
Hello again,
I still try find the cause of my problems with amanda. When the backup
finishes, I get the following dump summary:
DUMPER STATSTAPER STATS
HOSTNAME DISK
Hello,
The Amanda core team is pleased to announce the first beta release
of Amanda 2.5.2, the 2.5.2b1 release.
It can be dowloaded from http://www.amanda.org (not yet available) or
https://sourceforge.net/project/showfiles.php?group_id=120
Here's a list of the changes for release 2.5.2b1
is openSUSE 10.1.
server:~ # tar --version
tar (GNU tar) 1.15.1
server:~ # dump
dump 0.4b41 (using libext2fs 1.38 of 30-Jun-2005)
The last dendbackup.*.debug is attached.
Thanks
Sebastian
At 13:50 13.04.2007, Jean-Louis Martineau wrote:
The orig-kb is the size reported by the backup tool
:
Operation timed out
---
You must find why the client (h10) timeout:
- check client system log message
- client overloaded
- network problem
- ...
Jean-Louis
Charles Sprickman wrote:
On Wed, 11 Apr 2007, Jean-Louis Martineau wrote:
When
Sebastian Henrich wrote:
My OS is openSUSE 10.1.
server:~ # tar --version
tar (GNU tar) 1.15.1
server:~ # dump
dump 0.4b41 (using libext2fs 1.38 of 30-Jun-2005)
The last dendbackup.*.debug is attached.
Thanks
Sebastian
At 13:50 13.04.2007, Jean-Louis Martineau wrote:
The orig-kb
Yogesh,
Always look in the log and debug files if you have a problem.
What's in the amcheck.*.debug, amandad.*.debug and selfcheck.*.debug files?
Jean-Louis
Yogesh Hasabnis wrote:
Hi,
We use Amanda 2.5.0p2 in our backup setup. The setup
was working fine for last 2 months. I have started
301 - 400 of 1694 matches
Mail list logo
