Paul Yeatman wrote:
-In response to your message-
--received from Jean-Louis Martineau--
Paul,
I haven't followed the thread and I don't have old mail.
You should not need bsdudp.
Your disklist should specify : auth bsdtcp
Are you sure you have a correct plist for bsdtcp?
Are you sure
You are doing a dump to tape and the taper failed.
The dumper close the socket to the client, and the client detect the
socket is close.
The first error is the taper. sendbackup error is the result of the
taper error.
Jean-Louis
Stefan G. Weichinger wrote:
Some infos from the
It's not a .amandahosts problem.
Check the xinetd configuration for the amindexd service.
Check system log for xinetd error.
Jean-Louis
Johan Booysen wrote:
Hope someone can help me out here.
I'm testing Amanda 2.5.0 on RHEL5, to upgrade from our older version.
Everything went well and I
It must abort the dump, and restart it.
Jean-Louis
Stefan G. Weichinger wrote:
Jean-Louis Martineau schrieb:
You are doing a dump to tape and the taper failed.
The dumper close the socket to the client, and the client detect the
socket is close.
The first error is the taper. sendbackup
Stefan G. Weichinger wrote:
Jean-Louis Martineau schrieb:
It must abort the dump, and restart it.
And what's the solution for my problem?
Did it retried the dump on the next tape?
Can you explain the problem, because i don't understand it, except you
hit the end of a tape.
Post the amdump
Everything look good.
But it doesn't explain why amanda rejected those tape, the email report
will tell you why.
I'm not sure if the error is already written to the log file, but you
can check them: (amdump or amdump.1) or (log or log.TIMESTAMP.*).
btw, why are you installing an old amanda
Johan Booysen wrote:
Well, there wasn't any email report because it was waiting for the job
to finish...
I eventually manually killed the job, but the email report only says:
*** THE DUMPS DID NOT FINISH PROPERLY!
These dumps were to tape daily-3.
The next 2 tapes Amanda expects to use are: a
A bug in amstatus should not prevent your backup to run correctly.
Changing amdump.1 can't help to start a backup run (amdump).
Your backup should run correctly even if amstatus crash.
Can you send me a copy of the bogus amdump.1 file? I would like to look
at it.
Which locale are you using?
it give any sort of indication that it's time to insert the second
tape?
Just a little confused over that issue.
Thanks very much.
-Original Message-
From: Jean-Louis Martineau [mailto:[EMAIL PROTECTED]
Sent: 30 May 2008 12:56
To: Johan Booysen
Cc: Amanda user's group
Subject: Re: Amanda
Johan Booysen wrote:
Ok, on Thurday night at 21:00 I kicked off a backup job that should span
over 2 tapes. I wasn't in the office on Friday, but this morning the
first tape was ejected, and amstatus tells me the following:
server:/whatever/clients 0127494663k writing to tape (9:43:32)
I
back with:
/dev/nst0: Device or resource busy
So, alas, I don't think it's doing anything.
Any other suggestions at all?
Thanks.
-Original Message-
From: Jean-Louis Martineau [mailto:[EMAIL PROTECTED]
Sent: 09 June 2008 13:25
To: Johan Booysen
Cc: Amanda user's group
Subject: Re: Amanda
What's is the runtapes setting?
It's hard to read files when many characters are converted to HTML, it's
a lot better if you attach a file, they will not be converted.
Jean-Louis
nbarss wrote:
Can you send
your whole amflush log, as well as the taper debug log?
Sure. Here is
Douglas,
Many bugs are already fixed in the 2.5.1 tree, but we didn't made a release.
You can try the latest 2.5.1 snapshot from
http://www.zmanda.com/community-builds.php
It is only bug fixes since the 2.5.1p3 release.
I don't remember if this bug was fixed.
Jean-Louis
Douglas K. Rand
Can you post the dumper.*.debug file?
Jean-Louis
Luc Romain wrote:
I recently installed FedoraCore 9 and I am having trouble getting
amdump to run. I am using amanda (amanda-2.5.2p1-10.fc9.i386). Amcheck
runs clean but amdump fails. Here is the error I get when I run
'amstatus DailySet1'
Luc Romain wrote:
dumper: time 319.981: stream_client: Could not bind to port in range 0-0.
0-0 ? that's strange, do you have set reserved-udp-port in amanda.conf?
amadmin config config | grep -i reserved
What was the value of --with-udpportrange setting when amanda was
configured?
Sorry, it's not an error with an udp port, what's the setting of
unreserved-tcp-port
amgetconf config unreserved-tcp-port
Jean-Louis
Jean-Louis Martineau wrote:
Luc Romain wrote:
dumper: time 319.981: stream_client: Could not bind to port in range
0-0.
0-0 ? that's strange, do you have set
Martineau wrote:
Sorry, it's not an error with an udp port, what's the setting of
unreserved-tcp-port
amgetconf config unreserved-tcp-port
Jean-Louis
Jean-Louis Martineau wrote:
Luc Romain wrote:
dumper: time 319.981: stream_client: Could not bind to port in
range 0-0.
0-0 ? that's strange
Do you have a firewall on the server? That would explain why amanda
doesn't receive the packet even if the server receive it.
Can you post the amandad.*.debug from the client and the dumper.*.debug
from the server.
Jean-Louis
Wallace, Michael wrote:
Hello,
I have Amanda 2.5.1 running on a
Craig Dewick wrote:
ERROR: ziri: [could not access /dev/hda6 (/dev/hda6): Permission denied]
ERROR: ziri: [could not access /dev/hda2 (/dev/hda2): Permission denied]
ERROR: ziri: [could not access /dev/hda1 (/dev/hda1): Permission denied]
which is rather strange as I've already made sure, as
Amanda use 14 digits for holding disk directory name since many
releases, it is not related to usetimestamps.
Jean-Louis
Paul Yeatman wrote:
Hi,
Are 14 digit directory names on the holding disk only when using time
stamps or in any case with amanda 2.6.0p1?
I tried using time stamps for
xinetd must be configured to run amandad as root.
Jean-Louis
Chad Kotil wrote:
I am trying to setup krb5 auth on amanda 2.6.0p1. I built the server
and client --with-krb5-security, added a new principal to my KDC
([EMAIL PROTECTED] REALM), and wrote a keytab file and placed it
on the server.
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?
Jean-Louis
Jukka Salmi wrote:
Jukka Salmi -- amanda-users (2008-06-25 12:37:15 +0200):
Hello,
since I upgraded an Amanda installation from
Jukka Salmi wrote:
What about using record locking on a file in the logdir (maybe on the
logfile itself)? I.e. making sure that all involved processes always
acquire an exclusive lock, then write the log and afterwards release
the lock?
Amanda already lock the 'log' file.
But why it is not
): running as user root
instead of amandabackup
In the kerberos wiki it says amandad will relinquish root permissions
after reading the keytab. It doesnt seem to be doing that.
Also, What keytab on the client needs to be read as root?
--Chad
On Jun 25, 2008, at 5:29 PM, Jean-Louis Martineau wrote
It search the .amandahosts file in the home directory of the user.
Jean-Louis
Weiwei Luo wrote:
Hi all,
When I use amcheck, the following error message is returned.
***
Amanda
John Heim wrote:
# Do faster estimates
estimate calcsize
It must be in a dumptype.
Jean-Louis
[EMAIL PROTECTED] wrote:
sendsize[7952]: time 0.003: /dev/sda2: Bad magic number in super-block while
opening filesystem^M
sendsize[7952]: time 0.003: DUMP: The ENTIRE dump is aborted.
sendsize[7952]: time 0.004: .
sendsize[7952]: time 0.004: estimate time for / level 0: 0.002
Mister Olli wrote:
Hi...
when I try to do an 'amcheck' on my daily backup jobs I have one system,
that does not pass the selftest.
it's configured identically to some other machines that work like a
charm.
the debug output of 'amandad' on the client side looks like this:
-auth=bsd: debug 1
...
are there any hints on what to check, or how to trace/ debug this
failure in more detail?
greetz
olli
Am Mittwoch, den 16.07.2008, 07:20 -0400 schrieb Jean-Louis Martineau:
Mister Olli wrote:
Hi...
when I try to do an 'amcheck' on my daily backup jobs I have one system,
that does not pass
Which release of amanda?
Are you sure you are running the newly compiled amcheck? Use the full
patch when running it and show me the file is recent with 'ls -l'.
Post the configure output, did it find the ssh binary?
Post the output of make, did it compiled the ssh-security.c file?
Jean-Louis
As Jon said, it's a problem with new tape marked as no-reuse, only the
report is bad, amanda will works as expected.
The attached patch fix 'amadmin CONF tape' and amreport.
I don't know if the patch apply to 2.5.1p3.
Jean-Louis
Olivier Nicole wrote:
Hello,
I am setting up a new Amanda
--one-file-system doesn't works for NFS mountpoint.
You must exclude the ./rabbit.honeypot.net directory.
Jean-Louis
Kirk Strauser wrote:
I'm using Amanda 2.5.1p3 and GNU tar 1.20 on a FreeBSD 7 system. I
noticed something was askew when Amanda made an 11GB backup of a 6GB
filesystem:
#
man tar
-C, --directory DIR
change to directory DIR
It change the directory to '/data/nihpd/nihpd3/users' and then backup '.'
It is the expected behaviour.
The DLE should not be a symlink if you don't want to follow it.
Jean-Louis
Jean-Francois Malouin wrote:
A funny
Do 'amadmin config find' list the dump you want to restore?
What error do you get from amrecover? no longer accessible is not
helpful to find the problem.
Which amanda release are you using?
You can try to use amrestore on the server.
Jean-Louis
Dan Brown wrote:
Hi,
I've got a backup set
amrecover require a level 0 to still exist to works.
You have no level 0 dump of the disk (according to amadmin), it is very
dangerous, it is impossible for amanda to restore the complete disk.
I'm surprised amrecover show you the level 2 dump that are on holding
disk, it should not.
Hans Sandsdalen wrote:
Hi
I use amanda 2.4.4p3 and have a problem with a space ( ) in a
directory name in a disklist. How do I specify a directory name with a
space in it?
You can't, newer version can do it easily.
Easiest solution is to create a simlink:
cd /disk1/vmuser
ln -s Virtual\
Prashant Ramhit wrote:
Hi All,
Thanks for your help.
Attached is the amdump.1
Do you think its because it is not using the tape FULLBACK-01.
How can I make it to reuse fullback-01 again.
Do the following two command:
amrmtape fullbackfullback-01
amlabel -f fullback fullback-01
Your
Increase the estimate timeout setting (etimeout) in amanda.conf.
Jean-Louis
aminukapon wrote:
Hello all,
I have 2 directories that I'm trying to backup ...both directories are live and
constantly running (P.s:- running a website off them).. I have tried to backup
them up but amanda keeps
Like the message says: You can't use DUMP to backup a subdirectory, DUMP
work only on partition.
You must use GNUTAR to backup a directory.
Jean-Louis
Neil Marjoram wrote:
Hello all,
I'm a little confused, I've been running the same config for years,
last change a couple of years ago, and
to recover it
On day 12, it will be on the level 0 backup of /home/bar.
Jean-Louis
Aaron J. Grier wrote:
On Thu, Oct 02, 2008 at 10:15:52AM -0400, Jean-Louis Martineau wrote:
sendbackup: info end
| DUMP: You can't update the dumpdates file when dumping a subdirectory
| DUMP: The ENTIRE dump
man amanda.conf:
diskfile string
Default: disklist. The file name for the disklist file
holding client hosts, disks and other client dumping
information.
You can use: amdump -odiskfile=disklista
Why do you want to do use different disklist file? You could have one
Prashant Ramhit wrote:
Changer problem: mtx command (mtx) doesn't exist
changer problem: mtx command (mtx) doesn't exist (expecting a
new tape)
mtx was not in your when you configured amanda, add it to your PATh and
reconfigure amanda.
Check the configure output to know if it find it.
Are you sure /dev/rmt/1cn is the device for the tape drive?
What's the output of:
mt -f /dev/rmt/1cn status
mt -f /dev/rmt/1cn rewind
Jean-Louis
Krahn, Anderson wrote:
Trying to label my tapes and I get the following errors:
]#/opt/amanda/amanda-2.6.0p2/server-src/amtape Full update
Prashant Ramhit wrote:
Hi Paddy,
Thanks for you email.
I am using GNUTAR.
Index is set to yes in amanda.conf and all other clients are being
indexed.
What's the output of: amadmin config disklist
Did it list 'index YES' for the DLE?
Do you get index under your indexdir (amgetconf config
rakesh wrote:
Hi
amandad.*.debug is not generating any new logs
Then check your xinetd config and system log.
Jean-Louis
Thomas Vogt wrote:
Hello
I use amanda-server-2.5.1p3 and amanda-client-2.5.1p3 with FreeBSD 6.3.
Today I tried to restore a file from a directory with spaces in the
name. I started amrecover, set host and disk and tried to access my
directory called Data Check.
When i type ls in amrecover
rakesh wrote:
Hi
I have tried to apply the recommended changes and after doing so i started to get the error, i have
copied syslog along with .amandahosts contents and xinetd config details for
amanda
[EMAIL PROTECTED]:/backup/amanda_hold/DailySet1# amrecover
AMRECOVER Version 2.5.1p1.
rakesh wrote:
Hi
Thanks a lot your recomendations worked, atlast amrecover has started but i
haven't recovered any files till now.I would like to share some entries of the
same , what am i missing in here ?
[EMAIL PROTECTED]:/backup/amanda_hold/DailySet1# amrecover
AMRECOVER Version
Jean-Francois Malouin wrote:
Running amanda-2.6.0p2 an attempting to restore a run:
# id
uid=0(root) gid=0(root) groups=0(root)
# amfetchdump -p -d tape:/dev/nst0 conf1 gustav | tar -xpGf -
amfetchdump: running as user root instead of amanda
ugh?
jf
amfetchdump must be able to access the
Jean-Francois Malouin wrote:
Is this a new feature? I've done restore as root in the past I'm sure
and never seen this before. Have been living blind all this time? :)
So I guess I was lucky enough to do the amfetchdump in a dir owned by
amanda and then it could recreate the dir structure and
Jean-Francois Malouin wrote:
* Jean-Louis Martineau [EMAIL PROTECTED] [20081104 13:46]:
Jean-Francois Malouin wrote:
Is this a new feature? I've done restore as root in the past I'm sure
and never seen this before. Have been living blind all this time? :)
So I guess I was lucky enough
Ian Turner wrote:
I don't know if 2.5.1 is old enough to qualify for this issue, but it used to
be the case that the entire set of disklists for a client had to fit in a
single packet. What that meant is that if you had more than a few dozen disks
on one client (depending on disklist options),
What are the other configure option?
Is it amrecover that use /usr/local or is it amindexd and amidxtaped?
check you xinetd config to be sure you run the amandad in /local/...
Jean-Louis
Steven Backus wrote:
I'm doing a trial installation of amanda and don't want to mess
up my regular
Hi Jean-François,
Can you try the attached patch?
Jean-Louis
Jean-Francois Malouin wrote:
Hello,
I've finally got to install amanda-2.6.0p2 on a system going soon into
production and while getting used to the new features and I noticed a
few things that have changed since 2.5.x :
- I use
Try this newest patch.
Some fix will works only if the dump is done with the patched version.
Jean-Louis
Jean-Francois Malouin wrote:
* Jean-Louis Martineau [EMAIL PROTECTED] [2008 20:12]:
Hi Jean-François,
Can you try the attached patch?
Tried it but something is still
What's in your changer config file?
What's the output of : mtx -f /dev/sg? status
What's in the debug file?
Jean-Louis
Nicholas Brockner wrote:
Hi All,
I have been banging my head against this all day:
I have a superloader3 16 slot LTO3 unit I am trying to set up. For
some reason, the glue
Nicholas Brockner wrote:
Hi Jean-Louis,
Please see inline.
Jean-Louis Martineau wrote:
What's in your changer config file?
-sh-3.2$ more changer.conf
changerdev=/dev/sg3
havereader=1
offline_before_unload=1
OFFLINE_BEFORE_UNLOAD=1
poll_drive_ready=10
Max_drive_wait=99
unloadpause=20
driveslot
Try to put tape in the library, chg-zd-mtx automatically skip empty slot.
Jean-Louis
Nicholas Brockner wrote:
Jean-Louis Martineau wrote:
Nicholas Brockner wrote:
Hi Jean-Louis,
Please see inline.
Jean-Louis Martineau wrote:
What's in your changer config file?
-sh-3.2$ more changer.conf
What are you extracting? If the DLE have hard link you must extract the
complete DLE. gtar save the DLE only for the first file, this file must
be extracted.
You tried to extract './sysconfig/networking/profiles/default/hosts' but
you didn't extracted './hosts'.
Which release of amrecover are
and improvement.
* amgetconf '--client' option to retrieve config from
amanda-client.conf on a client.
* Amanda configuration file changes
o new application-tool section
o new script-tool section
o new device section
o new changer section
Jean-Louis
Seth Rothenberg wrote:
I'm looking for a clue for troubleshooting a new
amandaclient install. My main problem is
that this hasn't been worked on in about 5 years...
I have a dozen clients, including two ubuntu GNU/Linux,
and we are trying to add one more.
This one happens to be
Is it each samba dle that take take a long time or because they are done
sequentially?
If each dle take a long time, check for 'dumporder' setting. you might
want to set it to TTT.
If they are done sequentially, you should increase maxdumps, and be sure
the DLEs are not on the
Check firewall
Check xinetd configuration
Check system log for error to start amandad
Check amandad.*.debug files.
Check selfcheck.*.debug files.
Jean-Louis
Gene Heskett wrote:
Greetings;
Its borken:
[EMAIL PROTECTED] amanda-2.6.2alpha-20081209]# su amanda -c amcheck Daily
Amanda Tape Server
Steve, you are just crying that autoflush is not working, you post
nothing that show it.
As a bug reporter, you should show us that you have a bug.
Always prove what you say?
Prove autoflush is set: what is the output of: amgetconf conf autoflush
Prove you have something in the holding disk
What is the error you get in the report?
What is the number of 'reuse' tape in the tapelist?
Is it greater than your tapecycle?
Jean-Louis
Jean-Francois Malouin wrote:
Hi,
An amanda run last night ended up in the holddisk due to the fact
that chg-zd-mtx didn't hunt for the requested tape even
Zembower, Kevin wrote:
Is your 'holding delete' the same as this version's 'delete'? I'm nervous about something
that just says, Delete from database.
NO, it's not the same.
You should move the holding files on another directory
force a full dump of the disk: amadmin $conf force $host
mandaillou wrote:
NOTES:
taper: tape DailySet-05 kb 1783648 fm 2 writing file: No space left on
device
The tape got full after 1783648 was written, you need bigger tape.
amtapetype for amanda.conf configuration.
Below is the extract from amanda.conf related to the tapetype definition.
define tapetype HP-C1537A{
length 3868 mbytes
filemark 225 kbytes
speed 491 kps
}
Jean-Louis Martineau wrote:
mandaillou wrote:
Quote:
NOTES:
taper
Christiaan de Vries wrote:
Hello all,
(After quite some time spent on initial configuration issues...)
It seems the dump works successfully, but when I try an amrecover from
the client, I get the following error:
=
r...@chris-desktop:~# amrecover -s 10.100.100.150
Christiaan de Vries wrote:
Hello Jean-Louis,
File Permissions:
==
bac...@dub-amanda1:~$ ls -al /usr/lib/amanda/amidxtaped
-rwxr-xr-x 1 root root 16248 2007-11-09 01:08 /usr/lib/amanda/amidxtaped
Xinetd.d conf:
r...@dub-amanda1:/etc/xinetd.d# cat /etc/xinetd.d/amidxtape
Tom Robinson wrote:
DUMPER
STATS TAPER STATS HOSTNAME
DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s
MMM:SS KB/s
--
Tom Robinson wrote:
Client:
amanda: 2.4.4p3
It is an old release,
sendbackup: time 2193.228: 93: normal(|): DUMP: Volume 1 4063380 blocks
(3968.14MB)
The block size is 1KB.
It is improved in newer release.
I can do nothing for the release you are using, if you have program with
What do you get if you run:
/usr/bin/smbclient '//not.a.host.name/notashare' -U nosuchuser -N -Tx
/dev/null
Maybe your DNS is slow to return that 'not.a.host.name' is not a valid
hostname
Check your DNS configuration.
Jean-Louis
Gene Heskett wrote:
On Sunday 25 January 2009, Dustin J.
The DETAIL section of the report list the output of tar, you should see
why it failed (exit with code 2).
Jean-Louis
Prashant Ramhit wrote:
Hi All.
Does any one knows what this error code means
FAILURE AND STRANGE DUMP SUMMARY:
backupserver /mnt/fileserver1/bb-share/project/ lev 0 FAILED
...@amanda.org] On Behalf Of Jean-Louis Martineau
Sent: Thursday, January 29, 2009 06:01
To: Prashant Ramhit
Cc: amanda-users
Subject: Re: Error on backup
The DETAIL section of the report list the output of tar, you should see
why it failed (exit with code 2).
Jean-Louis
Prashant Ramhit wrote
man amzfs-snapshot
You must give to the 'amanda' user the right to execute some zfs command.
Use 'zfs allow' or set the 'PFEXEC' and 'PFEXEC-PATH' properties.
Brian Cuttler wrote:
Yes! leaving the /opt/sfw/lib out of the path entirely seems to have
done the trick, we linked against the correct
Hi Stefan,
Try the attached patch.
Jean-Louis
Stefan G. Weichinger wrote:
Greets,
as I start to explore the wonders of opensolaris I have a testbox
running OpenSolaris 2008.11. I installed the amanda-packages from zmanda
and set up amanda 2.6.1 to give zfs-snapshots a try.
Things work fine
This bug is already fixed.
Fix will be in 2.6.1p1.
Jean-Louis
Brian Cuttler wrote:
Successful run of the new version yesterday, performing a new
run this morning with autoflush (production capacity tape drive
is on the current production system).
Ran amstatus and noted an error, thought I'd
Yoshihiro Ishikawa wrote:
[r...@centos32 recover-src]# diff -uNr extract_list.c.o extract_list.c
--- extract_list.c.o2008-12-13 02:59:47.0 +0900
+++ extract_list.c 2009-02-06 12:40:52.0 +0900
@@ -1755,6 +1755,10 @@
if (file.program != NULL) {
if
./configure --help
--with-amlibexecdir[[[=PATH]]]
Where amanda own programs are installed,
default:
$libexecdir/amanda
--without-amlibexecdir Amanda own
stan wrote:
On Thu, Feb 19, 2009 at 10:23:59AM -0500, Jean-Louis Martineau wrote:
./configure --help
--with-amlibexecdir[[[=PATH]]]
Where amanda own programs are installed,
default
Read previous post and './configure --help' output.
Add --without-amlibexecdir
Jean-Louis
stan wrote:
On Thu, Feb 19, 2009 at 11:18:37AM -0500, Dustin J. Mitchell wrote:
On Thu, Feb 19, 2009 at 10:48 AM, stan st...@panix.com wrote:
But, if one is already puting amanda in it's own
Check the client amandad.*.debug and sendsize.*.debug files.
Jean-Louis
ay4you wrote:
Hi
i am getting an error with amanda backup i am using amanda 2.6.0 on the server and 2.5.1 on the client. the error is
FAILURE DUMP SUMMARY:
LON-TI-OFF-01 /home/company lev 0 FAILED [missing result
Stan,
It's known bug, remove the line 1042.
Jean-Louis
stan wrote:
When I ran amstatus to check on last nights run, I got a serries of the
follwing error messages:
:Use of uninitialized value in addition (+) at /opt/amanda/sbin/amstatus
line 1042.
Looking at that line of the script makes me
stan wrote:
On Thu, Feb 26, 2009 at 07:31:44AM -0500, Jean-Louis Martineau wrote:
Stan,
It's known bug, remove the line 1042.
So, that element of the structure does not need to get aded to the
acumulation
It's done a few line below.
Jean-Louis
Why you can't open the file?
Jean-Louis
ay4you wrote:
Hi
Can anyone tell me how to use amrestore i have done
amrestore tapefile host
now i have a big file which i cant open
how do i extract the files there
+--
|This was
I have numerous clients still running amanda 2.4.x clients and talking to my
2.6.1 server. I would think that maintaining backward compatibility within
the amanda server is a more fruitful path than trying to build the latest
version on all sorts of older platforms. Is there reason to believe
BUILT_MACH is set from the output of ./config/config.guess
What is the ouput?
Jean-Louis
Peter Kunst wrote:
Hi there,
just noticed in another Solaris10/sparc machine's amandad debug file:
1237478934.669711: amandad:
BUILT_MACH=x86_64-unknown-linux-gnu BUILT_REV=1609
This amandad
Hi,
Server use tcp port between 10084 and 10100 to connect to client
trel.wadsworth.org on port 56446.
It looks good.
Do you have firewall on server or client? Disable them while you test
amanda.
Can you post server and client debug files?
Jean-Louis
Brian Cuttler wrote:
I am running
(revision 1649)
@@ -1,3 +1,7 @@
+2009-02-06 Jean-Louis Martineau martin...@zmanda.com
+ * server-src/dumper.c: options is already unquoted.
+ * common-src/util.c: argument should not be quoted when added to argv.
+
2009-02-06 Dustin J. Mitchell dus...@zmanda.com
* installcheck
The 4 DLEs are already flushed.
There is a bug in 2.6.1 that don't erase them from holding disk, this
bug is already fixed in SVN.
You can securely remove the files from holding disk.
Jean-Louis
Steven Backus wrote:
Jean-Louis Martineau martin...@zmanda.com wrote:
You get this message
The email report should give you the complete output of tar, check the
DETAIL section of the report.
Jean-Louis
Steve Wray wrote:
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]
Post the output of: amadmin config disklist grifserv /griffyp/hiu
and the client amandad.*.debug, sendbackup.*.debug and zfs*.*.debug
Jean-Louis
Brian Cuttler wrote:
Ok, scratched my head a little and thought about was what different
between testing in-preproduction and now, we changed the
-Louis
Glenn Gillis wrote:
Brian Cuttler wrote, On 3/24/2009 7:42 AM:
Jean-Louis,
On Tue, Mar 24, 2009 at 10:37:22AM -0400, Jean-Louis Martineau wrote:
Hi,
Server use tcp port between 10084 and 10100 to connect to client
trel.wadsworth.org on port 56446.
It looks good.
Do you have firewall
dump larger than available tape space, 40258881 KB, full dump delayed
Do you know amanda have not done a full DUMP in the more than 327 days?
I hope you have keep all the needed tapes otherwise you can't recover
the complete dle.
You should enabled splitting (I don't remember if it is possible
Amanda use a new tape at every run. If you configure a big enough
holding disk, amanda can be configured to write to a tape only it is has
enough data in holding disk to fill the tape.
You must at least do one full backup, you are configure to do only level
1 backup, but they are relative to
amrecover from 2.5.2p1 and 2.4.4p3 use different protocol to communicate
with the server.
What's the xinetd configuration for the amindexd and amidxtaped network
services on the server?
Jean-Louis
Jukka Salmi wrote:
Hello,
I'm having a problem with amrecover(8) on Linux systems. The
Change it to:
amandaidx stream tcp nowait backup /usr/sbin/tcpd /usr/lib/amanda/amindexd
amidxtape stream tcp nowait backup /usr/sbin/tcpd /usr/lib/amanda/amidxtaped
Other arguments should only be used for amandad.
Jean-Louis
Jukka Salmi wrote:
Jean-Louis Martineau -- amanda-users (2009-04-03
It's important to do the dump direct to tape at the end if you have a
small holding disk, Amanda was designed for this case.
But hard disk are now cheap, what you propose is a good idea.
Patch is welcome.
Jean-Louis
Stefan G. Weichinger wrote:
Dustin J. Mitchell schrieb:
However, the
pre and post scripts are 2.6.1 features, it's not available in 2.5.1.
Jean-Louis
Topper wrote:
Hello community,
I'm just first time starter with Amanda.
Due to machine limitation (kernel and software) we can't use the last vers 2.6.1
So we installed 2.5.1 works like a charm but now first
601 - 700 of 1694 matches
Mail list logo
