Hi all,
I understand that it is better to turn the tape drive's hardware compression
off and let Amanda know the real size of the tape and gzip do the compression.
So... How do I turn it off, or for that matter, how do I know if it's on or off?
My tape is a DLT 80/160 and I use the following for
Shai Ayal wrote:
configures with it's uncompressed length. The backups seem
to be working as expected, but how to make sure there is no hardware
compression ?
Amtapetype has a test for that, with the -c option:
amtapetype -c -f /dev/yourtape
(Note: the tapecontents will be destroyed! Don't
On Mon, Feb 07, 2005 at 10:07:50AM +0200, Shai Ayal wrote:
Hi all,
I understand that it is better to turn the tape drive's hardware
compression off and let Amanda know the real size of the tape and gzip do
the compression.
better is very subjective here. There are valid reasons for
Hello,
We have a new tape drive but I am unsuccessfully running amlabel.
Some background:
I was successfully running amlabel on HARD-DISK.
I modified amanda.conf file to accommodate the new tape drive
specifications:
I added the new tape drive spec - which I got through running amtapetype.
On Monday 07 February 2005 10:56, Gil Naveh wrote:
Hello,
We have a new tape drive but I am unsuccessfully running amlabel.
Some background:
I was successfully running amlabel on HARD-DISK.
I modified amanda.conf file to accommodate the new tape drive
specifications:
I added the new tape drive
The Operating system is Solaris 9
and tape drive is under /dev/rmt/0n which is the defualt for Solaris.
Thx,
gil
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Gene Heskett
Sent: Monday, February 07, 2005 12:43 PM
To: amanda-users@amanda.org
Cc: Gil
On my amanda server (redhat 7.3) I'm running amanda-server-2.4.2p2-7 and on
the client I'm running amanda-client-2.4.4p1-0.3E (RedHat ES). I keep getting
selfcheck request timed out when I try to run amcheck on the server? Is
this caused by the different versions??
On Fri, Feb 04, 2005 at 07:21:59PM -0500, Gene Heskett wrote:
Aha, LVD! LVD is not compatible with the rest of the system unless
the rest of the system is also LVD. It is two, completely seperate
signalling methods that just happen to use the same cabling.
Yes and no. From the SCSI FAQ:
I am near positive I did not fry anything since everything is working correctly except a sustained write to the tape. If anything were damages, I would expect nothing to work at all. I have ordered the new scsi card and I will report back in to this thread when I find the results. I am also
On Mon, Feb 07, 2005 at 03:55:36PM -0500, Eric Siegerman wrote:
On Fri, Feb 04, 2005 at 07:21:59PM -0500, Gene Heskett wrote:
Aha, LVD! LVD is not compatible with the rest of the system unless
the rest of the system is also LVD. It is two, completely seperate
signalling methods that
The message indicates that the self-check portion of the amcheck command
timed out while communicating with either itself or the client. Make sure
that xinetd configuration files are set up correctly to respond to the
Amanda commands sent over the Amanda UDP port.
1. Check your /etc/services
Gene - thanks for trying to help,
Currently the only reason that I can think of is that Amanda has not read
correctly our tape drive so I am re-running
#amtapetype -f /dev/rmt/0n
By tomorrow I'll see what the results are and hopefully it should work...
Any thoughts why amlabel is not working are
Gil Naveh wrote:
Gene - thanks for trying to help,
Currently the only reason that I can think of is that Amanda has not read
correctly our tape drive so I am re-running
#amtapetype -f /dev/rmt/0n
Add an estimate value! And it takes about 5 hours only. Without
an estimate it takes a week or so.
On Monday 07 February 2005 14:40, Don Carlton wrote:
On my amanda server (redhat 7.3) I'm running amanda-server-2.4.2p2-7
and on the client I'm running amanda-client-2.4.4p1-0.3E (RedHat
ES). I keep getting selfcheck request timed out when I try to run
amcheck on the server? Is this caused by
On Monday 07 February 2005 18:31, Paul Bijnens wrote:
Gil Naveh wrote:
Gene - thanks for trying to help,
Currently the only reason that I can think of is that Amanda has
not read correctly our tape drive so I am re-running
#amtapetype -f /dev/rmt/0n
Add an estimate value! And it takes about
On Mon, Feb 07, 2005 at 10:06:09PM -0500, Gene Heskett wrote:
On Monday 07 February 2005 18:31, Paul Bijnens wrote:
Gil Naveh wrote:
Gene - thanks for trying to help,
Currently the only reason that I can think of is that Amanda has
not read correctly our tape drive so I am re-running
16 matches
Mail list logo
