if some of your DLEs contain lots of data that
is random
(compressed iso images, mp3 files, images, zip
archives, ...)
they will expand when taped
So the advantage of using SW compression instead of
HW compression is that we can selectively choose on which DLEs compression
should be enabled
On 2006-07-04 16:11, Chuck Amadi Systems Administrator wrote:
Hi List
I am a bit concerned as for a few days I have had to run amflush after
amdump has complained as per error below:
This particular server siis on the other side of the fw fence thus not
in my LAN I had increased the timeouts
On 2006-07-05 09:18, Nicola Mauri wrote:
if some of your DLEs contain lots of data that is random
(compressed iso images, mp3 files, images, zip archives, ...)
they will expand when taped
So the advantage of using SW compression instead of HW compression is
that we can selectively
Thanks to everyone for your replies.
Ok, so what I really wanted to do was to use software compression, and not
hardware compression.
Cyrille's suggestion sounds like what I need, but again I'm not sure whether
using this command will mean that compression is turned off permanently.
I'll look
On Wed, Jul 05, 2006 at 02:42:14AM -0700, Joe Donner (sent by Nabble.com) wrote:
Thanks to everyone for your replies.
Ok, so what I really wanted to do was to use software compression, and not
hardware compression.
Cyrille's suggestion sounds like what I need, but again I'm not sure
Lengyel, Florian wrote:
I'm running amanda version 2.4.4 under Cent OS.
So far it has been used to back up Linux machines;
now I've acquired four windows 2003 machines that I'd like
to back up with Samba. Does someone on the list have
experience with this?
Thanks,
Florian Lengyel
Hello,
We are currently using amanda 2.4.5p1 to backup a mix of Unix + Linux hosts. Now, we need to backup HUGE (100 Gb) subversion repositories that reside on a Windows XP box. From what I have read, the SMB client seems flaky.
I only have ONE big directory to backup from windows. My amanda tape server
Guy wrote:
What are our other alternatives ?
What we tend to do is create a share (via Samba) on a Linux server, and
do our backups from the Windows servers to there. This sidesteps a lot
of these kinds of issue for us, but you may not have a Linux server with
enough free disk space.
Graeme
On Wed, 5 Jul 2006 at 3:51pm, Guy wrote
We are currently using amanda 2.4.5p1 to backup a mix of Unix + Linux hosts.
Now, we need to backup HUGE (100 Gb) subversion repositories that reside on
a Windows XP box.
From what I have read, the SMB client seems flaky.
Not so bad, really. It
2006/7/5, Joshua Baker-LePain [EMAIL PROTECTED]:
If it were me, I'd look at using subversion's various internal backupscripts (e.g. 'svnadmin dump', 'hotbackup') and putting the resultingimages on a network drive served out via samba on a *nix box.Then
backup the svn backup images on the *nix
Hi all, I'm posting here for the benefit of the next person who runs
into this problem:
If amandad is running through inetd on a Linux system with the ipv6
kernel module loaded, it will try to talk to 0.0.0.0 instead of
whoever's on the other side of port 10080. The fix is to either
remove the
Obvious choice (probably not suitable, but no harm in suggesting it):
Is there space available (or can be made available) on the tape server?
If so, the second backup is local to the Amanda tape server.
Another possibility: Are there network connections available to put up
a local, isolated
On Wed, Jul 05, 2006 at 03:51:05PM -0400, Guy wrote:
We are currently using amanda 2.4.5p1 to backup a mix of Unix + Linux hosts.
Now, we need to backup HUGE (100 Gb) subversion repositories that reside on
a Windows XP box.
From what I have read, the SMB client seems flaky.
I only have
Guy wrote:
Once from the subversion server to the samba server
And again from the samba server to the tape server.
I wanted to avoid that.
One thing you can do to reduce this is to use rsync to copy the data
from the subversion server to the samba server. Chances are that lots of
that
Hi everyone,
I really want to start taking advantage of the tape-spanning features of
amanda 2.5, so I've begun the upgrading process... I've come a across a
problem that I am having difficulty resolving though. Here's what I've
done so far.
1) Upgrade version of amanda on server to version 2.5
Hi Cameron,
Cameron Matheson wrote:
Hi everyone,
I really want to start taking advantage of the tape-spanning features of
amanda 2.5, so I've begun the upgrading process... I've come a across a
problem that I am having difficulty resolving though. Here's what I've
done so far.
1) Upgrade
Peter Kunst wrote:
Hi Cameron,
Cameron Matheson wrote:
Hi everyone,
I really want to start taking advantage of the tape-spanning features of
amanda 2.5, so I've begun the upgrading process... I've come a across a
problem that I am having difficulty resolving though. Here's what I've
done so
Hi Peter,
On Thu, Jul 06, 2006 at 12:36:43AM +0200, Peter Kunst wrote:
try using a larger number (in seconds) for etimeout in your amanda.conf
try estimate server within the dumptype used for that DLE (which is
something new since, let me guess, can't remember, 2.5.x ?)
Thanks, I had never
Cameron Matheson schreef:
Hi everyone,
I really want to start taking advantage of the tape-spanning features of
amanda 2.5, so I've begun the upgrading process... I've come a across a
problem that I am having difficulty resolving though. Here's what I've
done so far.
1) Upgrade version of
Graeme Humphries schreef:
Guy wrote:
Once from the subversion server to the samba server
And again from the samba server to the tape server.
I wanted to avoid that.
One thing you can do to reduce this is to use rsync to copy the data
from the subversion server to the samba server. Chances
20 matches
Mail list logo
