Does anyone know the reason why you cannot snapshot
powered off machines?
I have learned that backups of VMware Windows-XP guests
under Linux are easy, and seem reliable, without starting or
restarting VMware or the VM. The method we use requires
that the Windows NTFS filesystem be set up
How do I get off this list?
Dustin J. Mitchell [EMAIL PROTECTED] writes:
On Jan 28, 2008 10:58 AM, Tony van der Hoff [EMAIL PROTECTED] wrote:
It seems like everyone here is equally baffled :(
In the interests of getting to the bottom of this, do you think you
could run an 'strace' the
How do I get off this list?
Tony van der Hoff [EMAIL PROTECTED] writes:
On 28 Jan at 14:35 Nick Brockner [EMAIL PROTECTED] wrote in message
[EMAIL PROTECTED]
Tony van der Hoff wrote:
Hi,
I've been using amanda for some years, but have just moved from Mandriva
to Debian Etch.
I
How do I get off this list?
Nick Brockner [EMAIL PROTECTED] writes:
Do a
#modprobe ide-scsi
And see if that loads the kernel module.
-Nick
Tony van der Hoff wrote:
Hi,
I've been using amanda for some years, but have just moved from Mandriva to
Debian Etch.
I have a Seagate
I regret my behavior and I most sincerely and abjectly apologize. My
head certainly should have been cooler. (Sometimes mere baldness
isn't quite enough.)
I wish nothing but the best for Amanda and her excellent crew, you
included, Dustin.
-- Steve
Steven R. Newcomb, Consultant
Coolheads
How do I get off this list?
I used to use Amanda, and I'm grateful for many (!) years of good
service from it, but I finally got tired of changing tapes and
worrying about them, and I didn't want to buy expensive new tape
equipment and even-more-expensive tapes just to keep using Amanda.
(Unlike
Mitch Collinsworth [EMAIL PROTECTED] writes:
On Tue, 7 Aug 2007, Dustin J. Mitchell wrote:
All in all, it sounds like a lot of work, unless this is a months-long
conference :)
I agree. Changing a working backup configuration in order to handle a
temporarily out-of-town condition is just
I've been using ssh-auth since the earliest days of 2.5. Yes, the
dumps themselves go through the ssh tunnel. I have not noticed any
appreciable increase in backup time, at least on our system, which has
over 400 DLEs. (I'm not sure why the number of DLEs would be
relevant, really.)
Ralf Auer
I had some headaches switching to SSH. The good news is that I
succeeded eventually and that it was well worth the trouble. When
amdump fails, it is remarkably unhelpful, and as far as can be told,
it's a timeout problem. But it's *not* a timeout problem.
If you really want to know what's
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 same
version everywhere.
Well, I lied. amcheck worked OK, but amflush 2.5.1 refuses to flush
the dumps made with 2.5.1p2 on the holding disk, saying:
[EMAIL
I'm using chg-multi. It works under 2.5.1. When I upgraded to
2.5.1p2, it stopped working, even with no changes to any configuration
file. With 2.5.1p2, the backups are made to the holding disk, but
nothing gets written to tape. There's a warning:
WARNING: No tapedev specified
It's true
If your situation permits, you could use an administrator-friendly,
rational operating system, such as Linux or Mach, that permits you to
backup a working system comprehensively, and, after a disk crash,
fire, or other mishap, to quickly restore a *working* system from a
*comprehensive* backup
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, with added comments:
chown -R amanda.disk
I'm using chg-multi with two identical Exabyte drives. The capacity
of each tape is slightly less than 5 Gb. I have a DLE that, at level
0, creates a dump of 22 Gb.
I haven't found any way to flush the dump from the holding disk onto
tape. I have specified for the dumptype:
Dear Kevin, et al.,
My bug in which Amanda created its dump-holding directory with
permissions that made it impossible for it to write on that directory
--- it's fixed. The fix was to change the ownership of one or more of
the files in /home/amanda. I'm not sure which file ownerships made
the
get this thing stabilized before going to Leipzig
for the Topic Maps -- Research Applications conference on
October 11-12 (www.tmra.de).)
Josef Wolf [EMAIL PROTECTED] writes:
On Wed, Sep 20, 2006 at 05:41:09PM -0400, Steve Newcomb wrote:
Fabio Corazza [EMAIL PROTECTED] writes:
Lee, Raymond
Dear Amanda maintainers...
As already noted, my ssh problems are all solved, BUT...
I still have no backups at all, since upgrading to 2.5.1. The server
creates the directory on the holdingdisk (that directory has a
timestamp as its name), and then Amanda complains that it can't write
anything
Amanda Backup Client Hosts Check
Host key verification failed.
WARNING: dimanche.coolheads.com: selfcheck request failed: EOF on read from
dimanche.coolheads.com
Client check: 1 host checked in 0.137 seconds, 1 problem found
does
Well, we're getting there, but 2.5.1 still doesn't quite work for me,
this time because of what looks like an Amanda permissions bug.
The only work-around I can see is to have Amanda be super-user.
Here's what happens...
Nothing gets written to the holdingdisk. Amdump complains that
it's not
Kevin Till [EMAIL PROTECTED] writes:
In the Amanda client .ssh/authorized_keys file, try to use ip address instead
of
fqdn name in the from field, e.g:
from=192.26.10.10,no-port-forwarding,no-X11-forwarding,no-agent-forwarding,command=/usr/lib/amanda/amandad
-auth=ssh amdump ssh-rsa
We've been using Amanda continuously since 1999. Amanda has minimized
our backup effort and headaches and it has saved us from serious data
losses on several occasions. Brava!
I was delighted to see that 2.5.1 now supports ssh, and if I could
just get it to work, it would be a godsend to us. I
In answer to my request for suggestions as to why Amanda 2.5.1 doesn't
seem to work with auth=ssh on our network, Jean-Louis Martineau
[EMAIL PROTECTED] writes:
Anything about ssh in your system log?
Nothing in /var/log/syslog of the client. However, in
/var/log/auth.log, the following is the
BLAHBLAHBLAHBLAHBLAHBLAHBLAHBLAHBLAHBLAHBLAHBLAH
[EMAIL PROTECTED]
Hope this helps.
Ray
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Steve Newcomb
Sent: Wednesday, September 20, 2006 12:23 PM
To: amanda-users@amanda.org
Subject: amanda over ssh
We've been using Amanda
Fabio Corazza [EMAIL PROTECTED] writes:
Lee, Raymond wrote:
Steve,
[cut]
I'm interested on this as well. Just a little question before starting
the new configuration by myself: is ssh used just for the
*authentication* or for the dumps as well?
I asked that in my first e-mail, and
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=384508
tar: -l option changed meaning, without any warning!
I've been on this list for only a few hours, and it has already solved
a baffling and annoying mystery for me. I have been using tar for at
least 20 years and I would never have
25 matches
Mail list logo
