amcheck must always be run by the amandabackup user.
Your xinetd config looks good.
Are you sure you are running amandad for 2.6.0p2 on the client? The
first line of the debug files should confirm it.
Jean-Louis
Daniel Novotny wrote:
hello,
one of our users has a problem while configuring
Post dumper.*.debug files?
Jean-Louis
Brian Cuttler wrote:
Dustin,
Jean-Louis,
On Thu, Apr 09, 2009 at 04:37:24PM -0400, Dustin J. Mitchell wrote:
On Thu, Apr 9, 2009 at 4:21 PM, Brian Cuttler br...@wadsworth.org wrote:
? everest /images3 lev 0 ?FAILED [dumper1 died]
Check
Brian,
Can you try this patch?
I need this path to connect to a 2.4.2p1 client, I was not able to
compile 2.4.1
Jean-Louis
Brian Cuttler wrote:
I'm trying to migrate an amanda client, SGI/IRIX with amanda 2.4.1p1
from server Solaris 9 with amanda 2.4.4 to a server Solaris 10 with
amanda
What is /usr/libexec/amanda/application/abas-stop?
file /usr/libexec/amanda/application/abas-stop
head -1 /usr/libexec/amanda/application/abas-stop
ldd /usr/libexec/amanda/application/abas-stop
Jean-Louis
Topper wrote:
FAILED Script 'abas-stop' command 'PRE-HOST-ESTIMATE': sendsize: error
Gene,
Where do you the gtar state files? Do you remove them on reboot?
Jean-Louis
in distribution tarballs.
* Many bugs fixed
o S3 device driver
o rait device driver
o amstatus
o configure
o application-api
o compilation on some platform
o others small bug
Jean-Louis Martineau
Gene,
Knowing which release failed is useful, but it is more useful if we can
find why it failed, can you post all debug files generated by a failed
run? From both amanda client and server.
From the client: amandad.*.debug, sendsize.*.debug, amgtar.*.debug,
sendbackup.*.*debug.
From the
I committed a fix, thank for finding the bug.
CHECK-DEVICE is correct, properties are sent send to the 'support'
application command because they are not needed, the script just log the
default value.
Jean-Louis
Dustin J. Mitchell wrote:
OK, after some logfile exchange off-list, I think
You are using the bsdtcp auth mechanism, you must configure the client
for it.
/etc/services: add
amanda 10080/tcp
SCOPENAME=VALUE
name=amanda
endpoint_type=dytream
proto=tcp
isrpc=FALSE
wait=FALSE
exec=/libexec/amanda/amandad
Add '-auth=bsdtcp in argument to amandad.
Jean-Louis
Abilio Carvalho wrote:
I'm getting this message when trying to run amcheck. I've run
amservice as is specified in the wiki page about this error, and I'm
getting the same error, so it's a client issue. Can someone help me
debug this?
All,
Amanda has won Linux Journal's Linux Choice Award for 2009:
http://www.linuxjournal.com/article/10451
Jean-Louis
It is easier to restore a splitted dump with amfetchdump. It will write
a 250Go file.
There is no way to automatically rebuild index from tape.
Jean-Louis
Franck GANACHAUD wrote:
Hello,
Server and client are 2.5.1p1 on debian etch
I've been trying to use amrestore but the backup is around
to manually get what's on various tapes?
Btw, I changed the chunksize to 1Gb in amanda.conf as Dustin suggested.
Jean-Louis Martineau a écrit :
It is easier to restore a splitted dump with amfetchdump. It will
write a 250Go file.
There is no way to automatically rebuild index from tape.
Jean
You can try to set the locale before executing amrecover.
A 'cd *niveau*' should change directory.
Jean-Louis
Franck GANACHAUD wrote:
Hi,
Server is debian etch using amanda 2.5.1p1
I have the following directory structure
/export/users/fganacha/Directory with space
- Directory_level_2
-
Small disk are often promoted to try to get a balanced schedule.
If it is a problem, you can set the 'maxpromoteday' for this disk.
Jean-Louis
Brandon Metcalf wrote:
I recently changed my config from
dumpcycle 4 weeks
runspercycle 20
tapecycle 25 tapes
to
dumpcycle 2 weeks
Jeffrey D Anderson wrote:
Perhaps the solution is not in changing the planner behavior, but in taper
options. It would be acceptible to me if amanda wrote most of the holding
disk files to tape, but elected to save some for the next night if it meant
better allocation of media.
Look at
Abilio Carvalho wrote:
the log directory on the client only has the following:
r...@backupclient:/tmp/amanda/amandad# cat amandad.20090519111556.debug
1242724556.328466: amandad: pid 18933 ruid 0 euid 0 version 2.6.1:
start at Tue May 19 11:15:56 2009
ruid 0 euid 0
That's root user
Do you
Brandon Metcalf wrote:
m First, am I correct in thinking the '.' are required? If so, how can
m Amanda be told to exclude, for example, /dumps on sda1 but still
m backup /dumps on sda2 other than defining different dumps types with
m their own exclude list?
m
m You can't.
Seems
The '.' is required, all excludes are relative to the dle you back up.
Brandon Metcalf wrote:
I have defined an exclude list in a dumptype using
exclude list /etc/amanda/DailySet1/exclude-list
with entries like
$ cat /etc/amanda/DailySet1/exclude-list
./dumps
Brandon Metcalf wrote:
m == martin...@zmanda.com writes:
m Brandon Metcalf wrote:
m m First, am I correct in thinking the '.' are required? If so, how
can
m m Amanda be told to exclude, for example, /dumps on sda1 but still
m m backup /dumps on sda2 other than defining different
I try to keep them compatible, but I don't test with release before 2.4.5.
index_server is used only by amrecover.
Can you post the amandad.*.debug file from the client?
Jean-Louis
Mitch Collinsworth wrote:
Hi,
Is there any gross imcompatability that would prevent a 2.6.1p1 client
from
amanda client 2.6.1p1 is compatible with server 2.4.3b4 and up. But it
is not with 2.4.3b3 and previous.
Try the attached patch.
Jean-Louis
Mitch Collinsworth wrote:
Hi,
Is there any gross imcompatability that would prevent a 2.6.1p1 client
from being backed up by a 2.4.3b3 server?
I've
In the inet log, syslog, /var/log/message
In the amandad.*.debug files, selfcheck.*.debug, sendsize.*.debug,
sendbackup.*.debug, ...
ps -ef
Jean-louis
McGraw, Robert P wrote:
I do not know where to start looking for the problem. Any suggestions.
Mitch Collinsworth wrote:
Yes, this patch solved the problem. Thank you! Can we anticipate
it being integrated into future versions?
I committed the patch to SVN, it will be in the next release.
Jean-Louis
Check the holding disk directory.
amflush doesn't flush an image if the dle is removed from the dumplist file.
You can remove the datestamp directories if you don't want to keep the
backup.
You must do the folowing f you want to keep theses backup and move them
to tape:
- Re-add the dle to
Yes, recovery works if the dle is not in the disklist.
Jean-Louis
Jon LaBadie wrote:
On Thu, Jun 04, 2009 at 08:42:57AM -0700, Jean-Louis Martineau wrote:
Check the holding disk directory.
amflush doesn't flush an image if the dle is removed from the dumplist file.
You can remove
Onotsky, Steve x55328 wrote:
Hi all,
I’ve compiled a 2.6.1p1 client on Solaris 9 earlier this year, and for
dumps it works great, but if I use amrecover to connect to my backup
server (tapehost and index host are the same box), I get the following
message from amrecover:
NAK: user
Use a different strategy for week and friday.
eg . strategy nofull# on the week, could be 'incronly'
strategy standard # on friday
Editing the disklist or amanda.conf is not an easy solution, but you can
do the following:
If all DLE inherit from a 'my_strategy' dumptype, you could
Same things as a real changer, you must tell it to use slot1.
$amtape conf slot 1
$amrestore -p file:/nas1/amanda/vtapes/DailySet1/slots blah
or
$ rm /nas1/amanda/vtapes/DailySet1/slots/data
$ ln -s slot1 /nas1/amanda/vtapes/DailySet1/slots/data
$ amrestore -p
Onotsky, Steve x55328 wrote:
Hmm... I added the requisite lines to .amandahosts on the server, and
now I get amindexd: invalid service, add 'amindexd' as argument to
amandad.
I added the parameters to the appropriate line in the client's
inetd.conf but no joy.
Add it to the amanda server.
Onotsky, Steve x55328 wrote:
-Original Message-
From: Jean-Louis Martineau [mailto:martin...@zmanda.com]
Sent: June 10, 2009 14:41
To: Onotsky, Steve x55328
Cc: amanda-users@amanda.org
Subject: Re: amrecover looking for .amandahosts in wrong directory
Hmm... I added the requisite
man amanda.conf
maxdumps int
Default: 1. The maximum number of backups from a single host that
Amanda will attempt to run in parallel. See also the inparallel
option.
Note that this parameter may also be set in a specific dumptype
(see
Steve,
Amanda doesn't use broadcast.
Jean-Louis
Steve Wray wrote:
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.
Just enter 'S' (skip) when it ask for the level 0 tape.
Jean-Louis
Brandon Metcalf wrote:
I've been looking through the docs, but can't find anything on this.
Is there a way with amrecover to restore only the data in the latest
level 1 backup? For example, let's say I've extracted all of
Yogesh Hasabnis wrote:
gzip: stdout: Connection timed out
This is weird, do your system automaticaly close connection after some time?
After how many it happens? is it always the same?
Jean-Louis
Post the complete amdump.? file
Yogesh Hasabnis wrote:
--- On *Thu, 6/18/09, Jean-Louis Martineau /martin...@zmanda.com/*
wrote:
No it doesn't. The backup system with amanda was working fine all
these days. The problem has cropped up since last 4 days. All of
the last 4 daily
You can try to increase the 'etimeout'.
Jean-Louis
ay4you wrote:
Hi
i am getting a weird error from my amdump it has been working fine up until last night and i got an error
These dumps were to tape DailySet11-014.
The next tape Amanda expects to use is: DailySet11-016.
FAILURE DUMP
Jean-Francois Malouin wrote:
Just upgraded a server from 2.6.0p2 to 2.6.1p1 and now amcheck outputs:
Server check took 0.004 seconds
amcheck-clients: amanda/tcp unknown protocol
This message is misleading when configured with '--with-testing'.
amanda use the 'amanda-av48-2/tcp' service,
What's your xinetd config? Did it execute amandad? Check system log.
If amanda get executed, post its debug file.
localhost resolve to an IPv6 address, can you use a name that resolve
only to an IPv4 address.
Jean-Louis
aminukapon wrote:
Hello all,
I ran across a problem when I tried to
We made no change in 2.6.1 for --with-testing, but we didn't test it
either...
What's the value of AMANDA_SERVICE_NAME is config/config.h in the build
directory? That's the service name it is using.
Jean-Louis
Jean-Francois Malouin wrote:
* Jean-Louis Martineau martin...@zmanda.com [20090708
Edit chg-lib.sh and set MTX to the full path:
MTX=/opt/csw/sbin/mtx
Jean-Louis
Andreas Kuntzagk wrote:
Jean-Louis Martineau wrote:
Andreas Kuntzagk wrote:
Hi,
I'm trying to do a (test) recovery using our SL24 changer.
I set amrecover_changer and use setdevice but still get an error
message
Andreas Kuntzagk wrote:
Hi,
I'm trying to do a (test) recovery using our SL24 changer.
I set amrecover_changer and use setdevice but still get an error
message when trying to extract files.
Could the reason be that I did the dumps before setting
amrecover_changer ?
no.
Look for message in
Do you have a dump on holding disk?
Jean-Louis
Brian Cuttler wrote:
I have an older version of amanda 2.4.4 on a Solaris 10/sparc server.
It is both client and server.
Oddly, planner seems to be trying to backup clep:/xerox DLE, which
was removed from the disklist 2 years ago... I guess its
Brian,
Can you run a debugger on the live amandad process and print a
backtrace? or with truss? I want to know where it is hung
Jean-Louis
at 10:45:30AM -0400, Jean-Louis Martineau wrote:
Brian,
Can you run a debugger on the live amandad process and print a
backtrace? or with truss? I want to know where it is hung
Jean-Louis
---
Brian R Cuttler brian.cutt...@wadsworth.org
Computer Systems Support
Can you apply the attached patch to lyra?
And run the following command on the amand server:
$ amdump curie lyra / -otapedev=/no/such/device -otpchanger=
Post the complete sendbackup.*.debug file
Jean-Louis
Brian Cuttler wrote:
Continuation of previous initiated thread.
Server, Solaris
amadmin CONF force '*'
Brandon Metcalf wrote:
d == dus...@zmanda.com writes:
d On Thu, Jul 16, 2009 at 2:28 PM, Brandon
d Metcalfbran...@geronimoalloys.com wrote:
d I had to rebuild the disk array where our vtapes were stored. After I
d recreate the vtapes is there anything in
Brandon Metcalf wrote:
I've changed all of my Amanda hosts to use bsdtcp instead of bsd
authentication, but one isn't cooperating. The client works using
service amanda
{
socket_type = dgram
protocol= udp
wait= yes
user= backup
group
Do the clients are set for the bsdtcp auth?
Jean-Louis
Brandon Metcalf wrote:
m == martin...@zmanda.com writes:
m Brandon Metcalf wrote:
m I've changed all of my Amanda hosts to use bsdtcp instead of bsd
m authentication, but one isn't cooperating. The client works using
m
m
The tapetype definition and the complete amdump.X are needed to
understand what amanda do wrong.
Maybe the estimate are bigger than the actual backup size, or ...
You can try to set 'maxdumpsize' to a value bigger than 1600GB.
Jean-Louis
Mark Fisher wrote:
Hi everyone,
We have been running
You should look at the REQ packet in the amandad.*.debug file to find
what is bogus in it.
I don't understand why you want to increase rep_tries?
Jean-Louis
Bryan wrote:
Looking for some guidance on a perplexing problem, plus a summary
update on my earlier note (below):
Answers to my earlier
Bryan wrote:
Jean-Louis,
Thank you for replying.
OK ... but I'm beginning to think there are network issues.
Last night this machine failed during the auth phase. First
time that's happened. 'amcheck -c' later succeeded.
Would the amandad.*.debug REQ packet received be an entry
like this?
Darin, Gunnar,
I committed a fix for this bug a few minutes ago.
Chris was right, this bug could only be seen with an UDP auth (bsd or
bsdudp).
Jean-Louis
Darin Perusich wrote:
I should have posted a follow-up to an earlier post of mine which is
similar it this if not the same. Chris Ritson
The syntax is: amlabel daily daily-21 slot 21
Which amlabel are you executing? Specify the full path of the installed
binary.
Jean-Louis
crom84 wrote:
Hi all :)
I am trying to use amlabel to label some more slots that I have created for my
daily backup configuration.
Here is the command
Dustin J. Mitchell wrote:
Hmm, well one problem is that that's a snapshot of the the 2.6.1
branch, which is pretty stable at this point. The other problem,
which Jean-Louis might be able to address, is that it's now almost
20090812, so we should probably have a new build installed by now.
gzip: stdout: Resource temporarily unavailable
I have no idea what's that error mean.
Can you try the latest 2.6.1p1 snapshot from
http://www.zmanda.com/community-builds.php
Jean-Louis
stan wrote:
WE deployed 3 OpenBSD machines yesterday to replace older OpenBSD machines
that had been
Check system log
Post complete amandad.*.debug and sendbackup.*.debug.
You can try to disable client compression.
Jean-Louis
stan wrote:
On Fri, Aug 14, 2009 at 09:50:22AM -0400, Jean-Louis Martineau wrote:
gzip: stdout: Resource temporarily unavailable
I have no idea what's that error
And what is the error?
It's probably not a gzip: ...
Jean-Louis
stan wrote:
On Fri, Aug 14, 2009 at 03:26:10PM -0400, Jean-Louis Martineau wrote:
Check system log
Post complete amandad.*.debug and sendbackup.*.debug.
You can try to disable client compression.
It still fails
man amanda.conf
compress [client|server] string
Default: client fast.
Set it to none if you don't want compression.
ig. compress none
Jean-Louis
stan wrote:
On Fri, Aug 14, 2009 at 03:26:10PM -0400, Jean-Louis Martineau wrote:
Check system log
Post complete amandad
This bug is already fixed.
stan wrote:
I am working on some issues that result in having failed partial dumps.
Historically, these are written to the tape, and then deleted, which allows
for the dumpdisk directory for that run to be automatically cleaned up.
On my 2.6.1 server, these
stan wrote:
Any thoughts as to why I have twice as many debug files as I expect?
When a dump fail, amanda try it a second time.
' auth, it is a lot more firewall
friendly.
Jean-Louis
stan wrote:
On Tue, Aug 18, 2009 at 08:06:46AM -0400, Jean-Louis Martineau wrote:
stan wrote:
Any thoughts as to why I have twice as many debug files as I expect?
When a dump fail, amanda try it a second time.
Got
stan wrote:
I know I have asked this before, but I can't recall getting a definative
answer. Is port usage different between 2.5.x and 2.6 clients, when
talkimng to a 2.6 server?
No, the same port are used if configured with the same port range.
Do yousee something in the firewall log?
Patch looks good.
All code that copy/rename listed incremental files should be done only
if it is used.
If you disable --listed-incremental, you will get FULL backup at every
run, is it what you want?
The amgtar_support function must output MAX-LEVEL 0 in this case.
Jean-Louis
Christopher
John Hein wrote:
On a 2.6.1b1 client ...
Hmm, beta software ...
It's not fixed in 2.6.1 neither in 2.6.1p1.
You must use the latest 2.6.1p1 snapshot from
http://www.zmanda.com/community-builds.php
Jean-Louis
This bug can't be fixed until we understand it.
Ask on a OpenBSD list how a write to a blocking pipe can return EAGAIN.
Or the pipe semantics changed and they don't default to blocking.
You can also try the attached, it check the pipe are opened in blocking
mode.
Jean-Louis
stan wrote:
On
Chris Hoogendyk wrote:
driver: FATAL Did not get DATE line from planner
The planner crashed, what's in the amdump.1 log file?
Chris Hoogendyk wrote:
planner: create debug directory /tmp/amanda: File exists
It's a race, both planner and driver tried to create the directory at
the same time.
Next run should be fine.
Jean-Louis
Chris Hoogendyk wrote:
Jean-Louis Martineau wrote:
Chris Hoogendyk wrote:
planner: create debug directory /tmp/amanda: File exists
It's a race, both planner and driver tried to create the directory at
the same time.
Next run should be fine.
Thank you, Jean-Louis. Nice to know exactly
Brian,
I think you can't change ufsdump default.
The untested attached patch might do what you want.
Jean-Louis
Brian Cuttler wrote:
What is the recommended solution to this problem ?
sendbackup: time 473.920: 93: normal(|): DUMP: Warning - block 2801050268
is beyond the end of
man disklist, look for spindle, set them to different value or '-1' if
you want parallel estimate and dump.
Jean-Louis
stan wrote:
In doing some testing, it appears that Amanda 2.6.1 no longer does
estimates for multiple DLE's on a client in parallel.
Is this true? If so, can I configure
Is it the snapshot that doesn't have the subdir or is it because gtar
see them to be on different filesystem?
It the problem is because they have different device number, then you
can set the ONE-FILE-SYSTEM property of the application amgtar to
NO. And you must use the amgtar application.
What program do you use to do the backup? dump or tar?
Jean-Louis
khalil_noura wrote:
Hi all,
I am trying to do a bare metal restore. After I partionsed the disk and
restored the client to holding. I rebooted to rescue mode created a
/mnt/sysimage directory mounted /dev/sda1 to
2.5.0p2 working, but could never get 2.5.1p3
working, even with
the same config. No idea why.
I started looking at the source code last night in the 0825
snapshot. I'll
discontinue that search if there's a patch.
This is interesting. I sent Jean-Louis Martineau an email
: Broken pipe
1251693126.825377: sendbackup: 90: normal(|): DUMP: The ENTIRE
dump is aborted.
1251693126.833573: sendbackup: critical (fatal): error [dump (22791)
/sbin/dump returned 3]
Thanks,
Michael
On Mon, Aug 31, 2009 at 12:49 PM, Jean-Louis Martineau
martin...@zmanda.com
, and a quick, about-to-go-to-bed readthrough of the
pipe write path shows that it shouldn't; is Amanda doing fcntls to
the fd? If so, check those to be absolutely sure that they're not
doing something hinkey.
Thanks,
Michael
On Mon, Aug 31, 2009 at 2:41 PM, Jean-Louis Martineau
martin
We need to find a minimal patch that fix the problem.
Cat you try the attached patch?
Jean-Louis
Michael Burk wrote:
I applied the patches to the 0827 version again (had to do the
sendbackup-dump.c patch by hand since the patch was for another
version). I ran a full backup again, and all 3
Michael Burk wrote:
So it seems reliable that those 3 lines fix the problem somehow.
Anything else you want to try before I ask for help on the OpenBSD list?
I have nothing else to try.
The order of system call is a follow:
In amandad process:
pipe(pipefd)
dup2(pipefd[1],b)
fork
in the
Msiipola,
Try with 'taperflush 100'
Jean-Louis
Msiipola wrote:
I' trying to utilize tapes better by using a holdingdisk and by setting i
amanda.conf:
flush-threshold-dumped 100
flush-threshold-scheduled 100
taperflush 0
But looks like amanda does not take any notice about these settings.
Jean-Francois Malouin wrote:
* Dustin J. Mitchell dus...@zmanda.com [20090908 13:08]:
On Tue, Sep 8, 2009 at 12:03 PM, Jean-Francois
Malouinma...@bic.mni.mcgill.ca wrote:
Hmmm, more than a week now and no replies.
So I'll attempt to fix it myself: just to be on the safe side,
any
Brian Cuttler wrote:
Using amanda 2.6.1 on Solaris 10 (server x86, client Sparc)
I currently have entries in the disklist like these, currently
there are 55+ entries.
finsen /export/home/agaupelzfs-snapshot
finsen /export/home/along zfs-snapshot
finsen /export/home/amanda
Hi Matt,
On all fridays, before amdump, run: amadmin CONF force *
In the dumptype, set maxpromoteday to 0.
Jean-Louis
Matt Ingram wrote:
Hi All,
We're having issues with our Level 0 backups taking an extremely long
time.. (200-300GB taking 12-24 hours.. is that normal?)
One temporary
Robert,
You can't, but 'amadmin CONF due' tell you which DLE are due for a full
dump tonight.
Jean-Louis
McGraw, Robert P wrote:
Is there a command that will tell me what backup level will run tonight on the
different DLE?
Robert
McGraw, Robert P wrote:
I have a filesystem called /export/comm. In this filesystem I have
./ftppub/site/mirrors which has a lot files and take a long time to backup at
level 0.
Since this mirror directory can be rebuilt from the master site I have decided
to not backup the mirrors with
There is no automatic way to do that.
You can force one of the dle to do a full toning, in 2 days, you force
another dle to do a full on that day, and 2 days later you force the
last dle to do a full.
After that, amanda will probably not try to do the 3 full the on same day.
eg.
october 8:
-Louis Martineau wrote:
Brian Cuttler wrote:
Using amanda 2.6.1 on Solaris 10 (server x86, client Sparc)
I currently have entries in the disklist like these, currently
there are 55+ entries.
finsen /export/home/agaupelzfs-snapshot
finsen /export/home/along zfs-snapshot
finsen
Brian,
What is the path of the snapshot, post the
Amzfs_snapshot.20091019*.debug files.
Jean-Louis
Brian Cuttler wrote:
Jean-Louis,
I reconfigured one of my globs to use dumptype zfs-snapshot
rather than user-tar. Backups ran well but I believe that we
did a single snapshot of /export/home
-cf /tmp/amzfs-snapshots.tar
Amzfs_snapshot.20091019*
On Tue, Oct 20, 2009 at 11:21:55AM -0400, Jean-Louis Martineau wrote:
Brian,
What is the path of the snapshot, post the
Amzfs_snapshot.20091019*.debug files.
Jean-Louis
Brian Cuttler wrote:
Jean-Louis,
I reconfigured one of my
, 2009 at 11:50:34AM -0400, Jean-Louis Martineau wrote:
It create one snapshot for each DLE.
Yes, however I'm afraid that if it creates a single disklist
for a glob, for instance /export/home/a*, creates snapshot /export/home
which I think would be acceptable.
But 'attempts' to create
Use the amgtar application and set the TAR-BLOCKSIZE to a bigger value
(half the STREAM_BUFSIZE.
Why do you believe it is bottleneck?
Jean-Louis
Alan Griffiths wrote:
Thanks for the pointer.
I've re-compiled with
define STREAM_BUFSIZE (NETWORK_BLOCK_BYTES * 16)
And I can see that
You talk about one dle or multiple dle?
Are you using compression or encryption? on client or server?
Are you using holding disk? or dumping directly to tape?
Post the amdump.n file for when it use NFS and when it doesn't use it.
Jean-Louis
Alan Griffiths wrote:
amgtar with blocksize set to
Brian,
Post the amandad.*.debug file form finsen.
Jean-Louis
Brian Cuttler wrote:
Amanda users,
Dustin,
Jean-Louis,
We have updated amanda to Amanda-2.6.1p1-20091023 and applied
a patch for zfs-snapshot names within disklist globs.
We have run 2 nights with this config where client!=server
Brian Cuttler wrote:
Jean-Louis,
On Thu, Oct 29, 2009 at 10:50:43AM -0400, Jean-Louis Martineau wrote:
With this patch, you will get the error reported by sendsize.
So the error will be more explicite - or will the additional info
help amanda development ?
The error will be more
:
On Thu, Oct 29, 2009 at 10:05:25AM -0400, Jean-Louis Martineau wrote:
Brian,
Post the amandad.*.debug file form finsen.
attaching.
Jean-Louis
Brian Cuttler wrote:
Amanda users,
Dustin,
Jean-Louis,
We have updated amanda to Amanda-2.6.1p1-20091023 and applied
a patch for zfs
Alan,
Most people report faster throughput without nfs, your result is weird.
Your sample is small (1.5GB), is it possible it was cached by the nfs
client?
Do amanda and NFS use the same network route?
Do the NFS server have enough memory and cpu to run the amanda client
software?
Check the
Hi Brian,
The attached should fix the Too many open files problem.
Can you try it and tell me the result.
Jean-Louis
Brian Cuttler wrote:
In order to work around the glob issue I removed the globs
from my disklist and replace them with entries for each
user directory.
We at least doubled the
Do amdump is running? The output of 'amadmin due' is not reliable if it is.
'amadmin due' only looks at latest full, the holsing file have '.tmp'
suffix, this dump is not successful.
Jean-Louis
Brian Cuttler wrote:
This is a very minor issue, but caught my attention.
Clearly have have
What is your tapecycle?
How many vtapes do you have?
What is the output of amcheck?
Jean-Louis
Mike R wrote:
Good day all. I'm a fairly new amanda user, I used the 15 minute
backup guide for my setup. During the first week my backups seemed to
have gone off without a hitch as indicated by the
What's the complete output of: amcheck -s daily
Mike R wrote:
Jean-Louis Martineau wrote:
What is your tapecycle?
How many vtapes do you have?
What is the output of amcheck?
Jean-Louis
Mike R wrote:
Good day all. I'm a fairly new amanda user, I used the 15 minute
backup guide for my setup
What are in those slots?
use 'amlabel' to label them.
Jean-Louis
slot 10: not an amanda tape (Read 0 bytes)
slot 11: not an amanda tape (Read 0 bytes)
slot 12: not an amanda tape (Read 0 bytes)
slot 13: not an amanda tape (Read 0 bytes)
slot 14: not an amanda tape (Read 0 bytes)
slot 15: not an
701 - 800 of 1694 matches
Mail list logo
