Am 04.10.2010 01:11, schrieb Dustin J. Mitchell:
On Sun, Oct 3, 2010 at 5:37 PM, Stefan G. Weichinger s...@amanda.org wrote:
applies and seems to work. encrypted DLE dumped.
Great! I'll wait to hear back from Jean-Louis about the potential
memory leak, then, before committing.
Started the
Hi,
I'm using the the poor mans changer-manual on one system and amrecover is not
so happy with it. The setup works with andump.
Thanks Gunnar Gunnarsson
amanda.conf
tpchanger chg-manual # the tape-changer glue script
changerfile /etc/opt/amanda/hansa-arkive/changer
tapedev
On Sun, Oct 3, 2010 at 1:46 PM, Gunnarsson, Gunnar
gunnar.gunnars...@svk.se wrote:
Yes this is much better - log is attached.
Fixed up in
http://github.com/djmitche/amanda/commit/z12092.patch
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
Yes I hope so. What version should I go for ?
Thanks Gunnar Gunnarsson
Incidentally, I can't help but notice that you're backing up disks named
/var/amanda/amandatapes/ems/slotNN. Will amvault be able to help you out?
If so, could you find some time to test it before I set sail in a week and
Incidentally, I can't help but notice that you're backing up disks
named /var/amanda/amandatapes/ems/slotNN. Will amvault be able to
help you out? If so, could you find some time to test it before I set
sail in a week and a half?
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
On Mon, Oct 4, 2010 at 1:59 AM, Gunnarsson, Gunnar
gunnar.gunnars...@svk.se wrote:
Yes I hope so. What version should I go for ?
This - or rather a version improved by Jean-Louis' suggestion to print
the more precise flush successfully retried - will be in the next
3.2.0 beta, which we're
Add: amrecover-changer chg-manual
in amanda.conf
Jean-Louis
Gunnarsson, Gunnar wrote:
Hi,
I'm using the the poor mans changer-manual on one system and
amrecover is not so happy with it. The setup works with andump.
Thanks Gunnar Gunnarsson
amanda.conf
tpchanger chg-manual
On Mon, Oct 4, 2010 at 2:09 PM, Charles Curley
charlescur...@charlescurley.com wrote:
It might be nice if the installation process not only made the directory
but changed its ownership to the amanda user.
The only reason that Amanda references its home directory is for
.amandahosts, which is
On Mon, 4 Oct 2010 13:09:38 -0600
Charles Curley charlescur...@charlescurley.com wrote:
Currently, when you run 'make install', amanda may or may not make the
user directory for the amanda user. The default is /var/backups, which
already exists on debian systems.
It might be nice if the
On Mon, 4 Oct 2010 14:52:11 -0500
Dustin J. Mitchell dus...@zmanda.com wrote:
On Mon, Oct 4, 2010 at 2:09 PM, Charles Curley
charlescur...@charlescurley.com wrote:
It might be nice if the installation process not only made the
directory but changed its ownership to the amanda user.
The
On Mon, Oct 4, 2010 at 3:28 PM, Charles Curley
charlescur...@charlescurley.com wrote:
Understandable. Yes, useradd should set it up correctly. However, on
debian and Ubuntu, the default user directory, /var/backups, is already
created by the time you run make install, and so is the backup user.
I finally, after much wrestling, got a single computer installation of
the 3.2.0 beta1 release, amanda-3.2.0_beta1.tar.gz, compiled and
running on Ubuntu 10.10 (a pre-release, as it is due out in about a
week).
Initially I compiled with no arguments to ./configure. That produced a
problem where
On Mon, 4 Oct 2010 21:59:50 -0500
Dustin J. Mitchell dus...@zmanda.com wrote:
However, approximately every other use of the client results in no
service at the amanda port:
# netstat -a | grep amanda
#
This sounds like an xinetd bug, somehow. Are you using UDP or TCP?
Are the
On Mon, Oct 4, 2010 at 9:45 PM, Charles Curley
charlescur...@charlescurley.com wrote:
I'm no expert on configure, so that could be wrong. BTW, are the
options for configure documented anywhere?
Only in ./configure --help. It looks like you got things figured out, though.
That done, I was
On Mon, Oct 4, 2010 at 10:30 PM, Charles Curley
charlescur...@charlescurley.com wrote:
I plan to go back to tcp and auth=bsdtcp once I get this issue solved.
Of course it could be that making those changes will solve this issue.
I'd recommend that. I consider BSD and BSDUDP authentications to
just an update, I tried recovering with amrestore and it gives me the following
error
sh-3.1$ amrestore
/offsitebackup/amanda/vtapes/slots/slot19/00090.site._home_tk20_pullbackupinprogress_DATABASE.3
| tar xvjf -
Reading from
16 matches
Mail list logo
