Compression time and amplot margin

Hi, I have a couple of questions. In amanda mail report, I cannot find the time it takes to compress the data. I am trying to see where amanda is spending more of its time (dump across the network, compression, taper). When I am using amplot for PostScript, top and right caption are mostly out

Re: Amtapetype wrongly reporting compression?

a variant like this: > > > > /usr/sbin/mtx load 1 0; > > /usr/bin/mt -f /dev/st0 compression 0; > > /usr/bin/mt -f /dev/st0 setblk 524288; > > /usr/bin/dd if=/dev/zero of=/dev/st0 bs=512k count=1; > > su amandabackup -c &quo

Re: Amtapetype wrongly reporting compression?

sure LEON is supported for theses drives. Jean-Louis On 13/01/18 04:48 PM, Luc Lalonde wrote: Hello Jean-Louis, I re-ran ‘amtapetype’ with a much larger blocksize (512k). Here’s the result: Checking for FSF_AFTER_FILEMARK requirement Applying heuristic check for compression. Wrote random

Re: Amtapetype wrongly reporting compression?

Luc, You should keep the driver in variable block size: eg . /usr/bin/mt -f /dev/st0 setblk 0 Jean-Louis On 12/01/18 03:20 PM, Luc Lalonde wrote: Hello Gene, Would a variant like this: /usr/sbin/mtx load 1 0; /usr/bin/mt -f /dev/st0 compression 0; /usr/bin/mt -f /dev

Re: Amtapetype wrongly reporting compression?

On Friday 12 January 2018 15:20:51 Luc Lalonde wrote: > Hello Gene, > > Would a variant like this: > >     /usr/sbin/mtx load 1 0; >     /usr/bin/mt -f /dev/st0 compression 0; >     /usr/bin/mt -f /dev/st0 setblk 524288; >     /usr/bin/dd if=/dev/zero o

Re: Amtapetype wrongly reporting compression?

On Fri, Jan 12, 2018 at 03:20:51PM -0500, Luc Lalonde wrote: > Hello Gene, > > Would a variant like this: > >     /usr/sbin/mtx load 1 0; >     /usr/bin/mt -f /dev/st0 compression 0; >     /usr/bin/mt -f /dev/st0 setblk 524288; >     /usr/bin/dd if=/dev/

Re: Amtapetype wrongly reporting compression?

Hello Gene, Would a variant like this:     /usr/sbin/mtx load 1 0;     /usr/bin/mt -f /dev/st0 compression 0;     /usr/bin/mt -f /dev/st0 setblk 524288;     /usr/bin/dd if=/dev/zero of=/dev/st0 bs=512k count=1;     su amandabackup -c "/usr/sbin/amlabel -f Monthly

Re: Amtapetype wrongly reporting compression?

hly 35 hours: > > define tapetype LTO7 { > comment "Created by amtapetype; compression enabled" > length 5874932832 kbytes > filemark 1813 kbytes > speed 118310 kps > blocksize 32 kbytes > } > > Why is it saying that it can write roughly

Re: Amtapetype wrongly reporting compression?

Hi, I have been using a 2048k blocksize on LTO5 and LTO6 for a few years now with good results. This is the tapetype that amtapetype generated with a non-compression LTO6 tape device (without the part-* options, they are of my own design) using this blocksize: define tapetype lto6-tapetype

Re: Amtapetype wrongly reporting compression?

0 long-timeout=14400 mode1 blocksize=32768 compression=1 mode2 blocksize=32768 compression=0 mode3 disabled=1 mode4 disabled=1 Sorry, about that! On 2018-01-11 02:43 PM, Luc Lalonde wrote: Hello Folks, I'm wondering if there's a bug with 'Amtapetype' (version 3.5.1). We're migrating from LTO5 to LT

Re: Amtapetype wrongly reporting compression?

gt; manufacturer="IBM" model = "ULTRIUM-HH7" { > > scsi2logical=1 > > can-bsr=1 > > auto-lock=1 > > two-fms=0 > > drive-buffering=1 > > buffer-writes > > read-ahead=1 > > async-writes=1 > > can-partitions=1 > > fast-mt

Re: Amtapetype wrongly reporting compression?

uto-lock=1 two-fms=0 drive-buffering=1 buffer-writes read-ahead=1 async-writes=1 can-partitions=1 fast-mteom=0 sysv=1 timeout=180 long-timeout=14400 mode1 blocksize=32768 compression=1 mode2 blocksize=32768 compression=0 mode3 disabled=1 mode4 disabled=1 Sorry, about that! On 2018-01-11 02:43 P

Re: Amtapetype wrongly reporting compression?

4400 mode1 blocksize=32768 compression=1 mode2 blocksize=32768 compression=0 mode3 disabled=1 mode4 disabled=1 Sorry, about that! On 2018-01-11 02:43 PM, Luc Lalonde wrote: Hello Folks, I'm wondering if there's a bug with 'Amtapetype' (version 3.5.1). We're migrating from LTO5 to LTO7 and I'm get

Amtapetype wrongly reporting compression?

Hello Folks, I'm wondering if there's a bug with 'Amtapetype' (version 3.5.1). We're migrating from LTO5 to LTO7 and I'm getting strange results when I run 'amtapetype'. Here's what I get after roughly 35 hours: define tapetype LTO7 { comment "Created by amtapetype; compression en

software vs hardware compression with large backups to LTO7

now had a bit of time running with LTO7, Amanda 3.4.5, and letting the tape drive do hardware compression. It happens that I (and some others on the list) couldn't figure out how to turn off compression on the LTO7, but I was already motivated to try running with hardware compression. I'm now

Re: new LTO7 library difficulties with amtapetype vs compression

e-header > > AMANDA: TAPESTART DATE 20170801124200 TAPE > amtapetype-1158747886 ^L > > $ sudo mt -f /dev/nst1 rewind > > $ sudo mt -f /dev/nst1 compression 0 > > $ sudo mt -f /dev/nst1 defcompression 0 > > $ sudo dd if=tape-header bs=512k count=1

Re: new LTO7 library difficulties with amtapetype vs compression

20170801124200 TAPE amtapetype-1158747886 ^L $ sudo mt -f /dev/nst1 rewind $ sudo mt -f /dev/nst1 compression 0 $ sudo mt -f /dev/nst1 defcompression 0 $ sudo dd if=tape-header bs=512k count=1 of=/dev/nst1 1+0 records in 1+0 records out 524288 bytes (524 kB

Re: new LTO7 library difficulties with amtapetype vs compression

y 2014 showing almost this exact sequence of commands when > > setting up my LTO6 library. > > Quite a high percentage of the modern tape drives, will, after a rewind, if asked for a read, will reread the tape header, see that compression is enabled, and will very helpfully (not!) re-ena

Re: new LTO7 library difficulties with amtapetype vs compression

to drive both of those close to their spec speeds. In both cases I was able to turn off compression and get a tapetype definition that showed close to spec speeds. I haven't got the LTO7 in production yet and have just been playing with it with amlabel and amtapetype to see what it does

Re: new LTO7 library difficulties with amtapetype vs compression

I had the same issue. Seems to work fine with compression on, just the estimates are off. Greg On Thu, Aug 3, 2017 at 3:59 PM, Will Aoki <wa...@umnh.utah.edu> wrote: > On Mon, Jul 31, 2017 at 04:37:37PM -0400, Chris Hoogendyk wrote: > > Here is my latest attempt, working with a

Re: new LTO7 library difficulties with amtapetype vs compression

6 library. > > Bottom line is that tapeinfo tells me compression is off, it's a new tape, > then > amtapetype tells me compression is on. I wasn't able to get compression turned off on the LTO-7 drive in my Quantum SuperLoader 3. I ended up deciding to leave compression on, as it didn'

new LTO7 library difficulties with amtapetype vs compression

So, I have this new NEOs T48 with two LTO7 drives. I thought it would go pretty smoothly getting it set up, as I have three NEOs T24 LTO6 libraries running with Amanda, each on a separate server. But, I'm finding it virtually impossible to get amtapetype happy with the compression

Re: Server compression vs: client compression

Sorry for being a bit late in replying to this. As you indicate, distributed processing ought to be more efficient, depending on the capabilities and loads of respective servers. I typically use client side compression, because all the servers I'm backing up have sufficient resources to do

Server compression vs: client compression

So, I understand the subject of software vs: hardware compression now (thanks for that very enlightening description of why it's good to let Amanda handle the compression, Chris) but now I'm wondering about the question of server vs: client compression. I would tend to think

Re: Software vs: Hardware compression

I could. But, I already have on the order of 150 DLEs spread across several servers for each Amanda server. Amanda's inherent multi-threading allows for multiple dumpers per server being backed up, restricted by spindle number. So, typically, when Amanda fires off, I might have 6 or 8 dump

Re: Software vs: Hardware compression

On Friday 28 October 2016 14:27:22 Charles Curley wrote: > On Fri, 28 Oct 2016 15:44:09 -0400 > > Chris Hoogendyk wrote: > > If it were "only" the Amanda server, I could go all out with pigz. > > However, it is also the department server and runs mail, web, samba, > >

Re: Software vs: Hardware compression

On Fri, 28 Oct 2016 15:44:09 -0400 Chris Hoogendyk wrote: > If it were "only" the Amanda server, I could go all out with pigz. > However, it is also the department server and runs mail, web, samba, > printing, etc. If I were to top out all the cores with pigz, I would >

Re: Software vs: Hardware compression

. On 10/28/16 3:37 PM, J Chapman Flack wrote: On 10/28/2016 02:37 PM, Chris Hoogendyk wrote: all of the data is being compressed, and the compression is significant, but it has become the bottleneck. Top shows multiple of Amanda's gz processes at the top of the list all day. In

Re: Software vs: Hardware compression

On 10/28/2016 02:37 PM, Chris Hoogendyk wrote: > all of the data is being compressed, and the compression is significant, > but it has become the bottleneck. Top shows multiple of Amanda's gz > processes at the top of the list all day. In your setup, are there enough DLEs to compress th

Re: Software vs: Hardware compression

On 10/28/2016 02:37 PM, Chris Hoogendyk wrote: > It also knows what a particular DLE can be compressed to based > on the history. If the tape drive is doing the compression, then it is a > black box. Amanda doesn't know what the DLE got compressed to, and it > doesn't know how

Re: Software vs: Hardware compression

That is somewhat of a complicated question. The simplest statement is that if Amanda manages the compression, and you have told it the capacity of the tape, then it knows what can fit on the tape. It also knows what a particular DLE can be compressed to based on the history. If the tape drive

Software vs: Hardware compression

Why does Amanda recommend the use of software compression vs: the built in hardware compression of the tape drive itself? Is that in fact still the current recommendation? -Sandro

querying device-side compression setting

Hi, I'm setting up amanda 3.3.4 with a Quantum Scalar i500 tape library. Regrading compression options, I'll go with the recommendation in the documentation to let Amanda do the compression client-side. How can I determine if hardware compression is enabled on my tape library? I can't find

Re: querying device-side compression setting

On 01/09/2014 01:44 PM, Michael Stauffer wrote: Hi, I'm setting up amanda 3.3.4 with a Quantum Scalar i500 tape library. Regrading compression options, I'll go with the recommendation in the documentation to let Amanda do the compression client-side. How can I determine if hardware

Tape Compression: Is it on or off

amanda 3.3.3 OmniOS 151006 Hi, This question has probably been answered elsewhere so maybe someone can redirect me to the short answer. I am still not sure if I'm using compression or not. My apologies in advance for the long post. I have an IBM-3580-LTO5 configured through the 'st' driver

ZFS Compression Oddities with Amanda

I'm attempting to commit 7 TB of text to tape. It's presently stored in a natively gzip-9 compressed zvol, weighing in at 1.7 TB. My holding area is 5 TB, and is set to a native gzip-5 compression. The functional difference between gzip-5 and gzip-9 is not very much: Level 9 compression has a 4

Re: ZFS Compression Oddities with Amanda

Guy, Are you also using amanda software compression? Using compression on the holding disk is probably just a waste of CPU as the data is compressed once and decompressed once, but if it the only way it can fit in the holding disk. If you use amanda software compression, then the data

Re: ZFS Compression Oddities with Amanda

I'd thought for both ZFS and the newer (LTO) tape drives that HW-compression was determined on a block by block basic (if enabled) so that expansion of data would not occur. Granted, this does nothing to help with on CPU usage, but I'd thought it did save, rather, preserve, storage volume

Delayed Compression?

Can amanda delay server-side compression? I'd like compression to occur on the server, but only after all the backups have occured. IE: 1) backup 2) compress 3) tape . is this possible, or does it have to happen inline during the backup process?

Fwd: Linux kernel compression with lrzip

. -- Forwarded Message -- Subject: Linux kernel compression with lrzip Date: Sunday, November 07, 2010 From: Con Kolivas ker...@kolivas.org To: linux-ker...@vger.kernel.org Hi all Let's do this backwards. Data first. tarball of every 3 point linux kernel from 2.6.0 to 2.6.36 9748285440 linux

HW Compression

in a none compression mode. # mt -f /dev/rmt/0n status HP Ultrium LTO 3 tape drive: sense key(0x0)= No Additional Sense residual= 0 retries= 0 file no= 2 block no= 0 The drive is sitting in a SL48 Tape library and the host is Solaris Sparc runnint Solaris 10. Sorry this is more of an os

Re: HW Compression

. I want to use the driver in a none compression mode. # mt -f /dev/rmt/0n status HP Ultrium LTO 3 tape drive: sense key(0x0)= No Additional Sense residual= 0 retries= 0 file no= 2 block no= 0 The drive is sitting in a SL48 Tape library and the host is Solaris Sparc runnint

Re: Weird compression results for DLE using 'compress NONE' (nocomp-root)

Tom Robinson wrote: DUMPER STATS TAPER STATS HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s --

Re: Weird compression results for DLE using 'compress NONE' (nocomp-root)

Jean-Louis Martineau wrote: Tom Robinson wrote: DUMPER STATS TAPER STATS HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s

Re: Weird compression results for DLE using 'compress NONE' (nocomp-root)

Tom Robinson wrote: Client: amanda: 2.4.4p3 It is an old release, sendbackup: time 2193.228: 93: normal(|): DUMP: Volume 1 4063380 blocks (3968.14MB) The block size is 1KB. It is improved in newer release. I can do nothing for the release you are using, if you have program with

SCSI DDS tape compression

Hi, I am using amanda with DDS tapes without h/w compression and during boot the compression is disabled using mt. I noticed however a different behaviour between the mt in the cpio 2.6 package (in opensuse 10.2) and the version 2.9 which is in opensuse 11.1. The command is mt -f [dev

Weird compression results for DLE using 'compress NONE' (nocomp-root)

Hi I've got several disks that are showing weird compression results in the amanda report. Here's one of them: DUMPER STATS TAPER STATS HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS

Re: Weird compression results for DLE using 'compress NONE' (nocomp-root)

John Hein wrote: John Hein wrote at 21:38 -0700 on Jan 21, 2009: Tom Robinson wrote at 12:30 +1100 on Jan 22, 2009: I've got several disks that are showing weird compression results in the amanda report. Here's one of them

Re: Weird compression results for DLE using 'compress NONE' (nocomp-root)

Tom Robinson wrote at 12:30 +1100 on Jan 22, 2009: I've got several disks that are showing weird compression results in the amanda report. Here's one of them: DUMPER STATS TAPER STATS HOSTNAME DISK

Re: Weird compression results for DLE using 'compress NONE' (nocomp-root)

John Hein wrote at 21:38 -0700 on Jan 21, 2009: Tom Robinson wrote at 12:30 +1100 on Jan 22, 2009: I've got several disks that are showing weird compression results in the amanda report. Here's one of them: DUMPER STATS

Compression ratios reported

Greetings; From the ChangeLog for amanda 2.6.0-p2 2008-08-22 Jean-Louis Martineau [EMAIL PROTECTED] * server-src/reporter.c: Fix computation of compression ratio. Thank you. -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please

software compression

I have decided to start useing software compression to see if I can get a little better tape utilization. I have set up the .conf file to use server best. I ran amdump with a test DLE with one file. The backup system log that was email said every thing went fine. The problem is that I do

Re: software compression

McGraw, Robert P wrote: I have decided to start useing software compression to see if I can get a little better tape utilization. I have set up the .conf file to use server best. I ran amdump with a test DLE with one file. The backup system log that was email said every thing went fine

Re: Can't seem to disable software compression.

On 2008-04-30 13:45, Edi Šuc wrote: Hi. It seems that I can't disable software compression in amanda. I tried everything that could in my opinion have an impact on compression. But no luck. The problem is that i have a relatively slow machine and it takes forever to complete the backup. If I

Re: Can't seem to disable software compression.

compress none turns off compression of the data, but amanda will still compress the indexes. You can check your tape contents to verify that the data there is uncompressed. -Mitch On Wed, 30 Apr 2008, [UTF-8] Edi ??uc wrote: Hi. It seems that I can't disable software compression

Encryption, compression

to encryption and compression play against one another. Some data compresses very well, some doesn't, If you are encrypting, doesn't that tend to cause the data to be less compressable ? We are looking an encryption on the tape for one of our amanda servers, just want to sort of know what to expect

Re: Encryption, compression

and haven't seen... how to encryption and compression play against one another. Some data compresses very well, some doesn't, If you are encrypting, doesn't that tend to cause the data to be less compressable ? We are looking an encryption on the tape for one of our amanda servers, just want

RE: Encryption, compression

In my (admittedly limited) experience with encryption and compression, the rule of thumb has always been to compress first (removing exploitable redundancy and pattern repetitions) and then encrypt. It also has the advantage that you are encrypting less volume and reducing the exploitable

RE: Encryption, compression

Good crypto will produce relatively random output data. Compressing prior to encrypting if storing encrypted is typically a must. --On October 30, 2007 6:06:09 PM -0500 [EMAIL PROTECTED] wrote: In my (admittedly limited) experience with encryption and compression, the rule of thumb has

backup disk and compression

Hi - is it possible to run amanda such that it backups up to disk instead of a tape? And compresses the output on the disk? -- Ken

Re: backup disk and compression

On 9/25/07, Simpson, Kenneth [EMAIL PROTECTED] wrote: Hi - is it possible to run amanda such that it backups up to disk instead of a tape? Sure -- we call it 'vtapes'. See http://wiki.zmanda.com/index.php/How_To:Set_Up_Virtual_Tapes and the wiki in general for more information. Dustin --

Re: Hardware Compression

Hi Paul, here are the two different typedefs, one for the 160Mb/s and one for the 320Mb/s SCSI-controller. In both cases HWC was enabled. This is the output, I used the very same tape for both runs: (I did a full run, not only the compression check, -c ): define tapetype LTO3_160

Re: Hardware Compression

On 2007-08-14 04:18, Ralf Auer wrote: Hello everybody, if you don't mind, I have two questions concerning hardware compression. I have two HP Ultrium 960 drives. Up to now I used them with hardware compression disabled and compressed my data on the clients. Now I enabled hardware

Re: Hardware Compression

Auer wrote: Hello everybody, if you don't mind, I have two questions concerning hardware compression. I have two HP Ultrium 960 drives. Up to now I used them with hardware compression disabled and compressed my data on the clients. Now I enabled hardware compression and ran amtapetype

Hardware Compression

Hello everybody, if you don't mind, I have two questions concerning hardware compression. I have two HP Ultrium 960 drives. Up to now I used them with hardware compression disabled and compressed my data on the clients. Now I enabled hardware compression and ran amtapetype. 1

Re: Hardware Compression

On Tue, Aug 14, 2007 at 04:18:51AM +0200, Ralf Auer wrote: Hello everybody, if you don't mind, I have two questions concerning hardware compression. I have two HP Ultrium 960 drives. Up to now I used them with hardware compression disabled and compressed my data on the clients

Re: Hardware Compression

Hi Jon, LTO is unusual. When hwc is enabled each input block is compared with and without compression. The smaller of the two is recorded. As amtapetype feeds random data, data that is not compressible, the original input block is taped. Thus you see the same results with or without hwc

software compression vs hardware compression

Hi all, I just wanted to share my experience. I'm usually using hardware compression on my backup server (because all data to be backuped ,1.2TB, are local) to save it some CPU. As a result my backup were going quite fast (about 4 hours) but the load balancing was far from my expectation

Amanda compression questions

drive. My tapetype is defined as followed define tapetype LTO2-HWC { comment LTO-2-Hardware Compression on. blocksize 1024 kbytes length 30 mbytes #200G filemark 0 kbytes speed 27315 kps #27 Mb/s } length 30 mbytes was calculated by 1.5

Re: Amanda compression questions

LTO2 tape drive. My tapetype is defined as followed define tapetype LTO2-HWC { comment LTO-2-Hardware Compression on. blocksize 1024 kbytes length 30 mbytes #200G filemark 0 kbytes speed 27315 kps #27 Mb/s } “length 30 mbytes” was calculated by 1.5 times the actual size

Re: Amanda compression questions

Chris, If I understand your question correctly... Q1) I have asked Sun and the makers of the LTO2 drive and it seems there is no way to turn hardware compression on or off on this unit, it is always on. From my reading in the Amanda forum it seems that the LTO2 drive will sense

amanda 2.4.4, compression issue

Good morning amanda users, I'm running amanda 2.4.4 on solaris 9, just built it on solaris 8. Finding that my TAR dumptypes seem to be running compression though I believe I've configured it not to. The (ufs)DUMP DLEs properly perform compression none. Not only that, but the default, I believe

Re: amanda 2.4.4, compression issue

On Tue, May 22, 2007 at 11:21:50AM -0400, Brian Cuttler wrote: Good morning amanda users, I'm running amanda 2.4.4 on solaris 9, just built it on solaris 8. Finding that my TAR dumptypes seem to be running compression though I believe I've configured it not to. The (ufs)DUMP DLEs

Re: amanda 2.4.4, compression issue

. Finding that my TAR dumptypes seem to be running compression though I believe I've configured it not to. The (ufs)DUMP DLEs properly perform compression none. Not only that, but the default, I believe is client fast and we seem be be compressing best. I'm undoubtedly

Re: amanda 2.4.4, compression issue

index are always compressed on the server with --best. Why do you think your data is compressed? Jean-Louis Brian Cuttler wrote: Good morning amanda users, I'm running amanda 2.4.4 on solaris 9, just built it on solaris 8. Finding that my TAR dumptypes seem to be running compression though I

Re: amanda 2.4.4, compression issue

Brian Cuttler wrote: When I tried a restore yesterday I found that the files I brought back had a long numeric number preceeding the original path. I will try a restore again when the current amdump run completes to see if this is still the case. Is this normal, or perhaps an artifact of not

RE: activate HW compression

This is my first post here - I thought people should never use tape hw compression because each vendor implements their own compression protocols. Say you need to restore files from a different tape host and if your not using the exact same hw vendor then you might have an *issue* or two

Re: activate HW compression

On Wed, May 02, 2007 at 08:25:13AM -0400, Donofrio, Lewis wrote: This is my first post here - I thought people should never use tape hw compression because each vendor implements their own compression protocols. Say you need to restore files from a different tape host and if your not using

Re: activate HW compression

I haven't encountered that. I thought that the compression algorithms were standardized for particular tape formats. Typically, the originator of a tape format is the primary manufacturer and other vendors repackage mechanisms with their own labeling and other components. So, e.g., a Sun or Dell

Re: activate HW compression

Hi, How can I enable Hw compression ? do I have to do it for each tape ? What if A reboot the server ? Yes you have to activate it for each tape, and on the safe side, I would activate it before each amanda run, so make it part of the cron that runs amanda dumps. Olivier

activate HW compression

Hello, I'm using HP ultrium 3 tape drive on RedHat Enterprise Linux 5 How can I enable Hw compression ? do I have to do it for each tape ? What if A reboot the server ? tx!

Re: activate HW compression

On Mon, Apr 30, 2007 at 02:31:21PM -0400, FM wrote: Hello, I'm using HP ultrium 3 tape drive on RedHat Enterprise Linux 5 How can I enable Hw compression ? do I have to do it for each tape ? What if A reboot the server ? Look into mt for interactive changes and stinit for creating

Re: Compression again

sizes are like the real ones on the disk. The problems start with the dumper. The dumper doesn't compare his result with the real sizes but with the real sizes divided by two because of the default compression set to 0.50. A compression to 50% isn't possible on all the disks and that why

Re: Compression again

of the estimates everything seems to be ok and all sizes are like the real ones on the disk. The problems start with the dumper. The dumper doesn't compare his result with the real sizes but with the real sizes divided by two because of the default compression set to 0.50. A compression to 50

Re: Compression again

sizes but with the real sizes divided by two because of the default compression set to 0.50. A compression to 50% isn't possible on all the disks and that why the data seems to grow. My question is now, is this a bug of version 2.4.5? At the moment I don't get packages for openSUSE 10.1 from SuSE

Re: Compression again

the calculation of the estimates everything seems to be ok and all sizes are like the real ones on the disk. The problems start with the dumper. The dumper doesn't compare his result with the real sizes but with the real sizes divided by two because of the default compression set to 0.50. A compression

Re: Compression again

sizes are like the real ones on the disk. The problems start with the dumper. The dumper doesn't compare his result with the real sizes but with the real sizes divided by two because of the default compression set to 0.50. A compression to 50% isn't possible on all the disks and that why

Compression again

4452664 kB /profiles 8996864 kB /data 2437400 kB /org376376 kB /lit 1316660 kB /projects 17768808 kB So first I don't understand why ORIG-kB is half of the size. I use software compression (compress server best). Hardware compression ist turned off (amtapetype -c proofs

Re: Compression again

20394240 fm 6 [OK] The original data has the following sizes: /home 4452664 kB /profiles 8996864 kB /data 2437400 kB /org376376 kB /lit 1316660 kB /projects 17768808 kB So first I don't understand why ORIG-kB is half of the size. I use software compression (compress server

Re: Compression

switched the hardware compression off and tried to use the software compression. Now I have the problem that amanda tells me every time You may be getting bit by something I ran into several years ago now. If the tape is written with the hardware compression on, then the drive

Re: Compression

On Wed, Apr 04, 2007 at 07:36:03PM -0400, Jon LaBadie wrote: - edit the curinfo files and add a set of fake historical comp-rates If editing makes you nervous you can also use 'amadmin export' / 'amadmin import'. Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda,

Re: Compression

from the beginning every 3 months. Didn't you say the problem occured when you switched from HW to SW compression? I've not heard anyone else encountering problems, so your's may have been an edge case. But presumably you will not change from HW to SW compression every 3 months. You got me

Re: Compression

On Tuesday 03 April 2007, Sebastian Henrich wrote: Hello, I'm using amanda 2.4.5 to backup my server. The tape is a HP DAT 72. This drives stores 36 GB of uncompressed data. I switched the hardware compression off and tried to use the software compression. Now I have the problem

Re: Compression

On Wed, Apr 04, 2007 at 11:01:20AM +0200, Sebastian Henrich wrote: On Tuesday 03 April 2007, Sebastian Henrich wrote: Hello, I'm using amanda 2.4.5 to backup my server. The tape is a HP DAT 72. This drives stores 36 GB of uncompressed data. I switched the hardware compression off

Re: Compression

On Wed, 4 Apr 2007 at 11:39am, Jon LaBadie wrote On Wed, Apr 04, 2007 at 11:01:20AM +0200, Sebastian Henrich wrote: How can I put the ratio in the dumptype spec? Can't. The history of last 3 dumps at full and incremental levels is recorded in the curinfo file for the DLE after a dump. I

Re: Compression

On Wed, Apr 04, 2007 at 02:09:52PM -0400, Joshua Baker-LePain wrote: On Wed, 4 Apr 2007 at 11:39am, Jon LaBadie wrote On Wed, Apr 04, 2007 at 11:01:20AM +0200, Sebastian Henrich wrote: How can I put the ratio in the dumptype spec? Can't. The history of last 3 dumps at full and

Re: Compression

At 17:39 04.04.2007, Jon LaBadie wrote: ... I diabled the hardware compression before I used the tapes for the first time like it's described in the docs. mt shows me that hardware compression is off after inserting a tape. So I think that it's really disabled. The switch may not occur

Re: Compression

On Wed, Apr 04, 2007 at 09:49:15PM +0200, Sebastian Henrich wrote: At 17:39 04.04.2007, Jon LaBadie wrote: ... I diabled the hardware compression before I used the tapes for the first time like it's described in the docs. mt shows me that hardware compression is off after inserting

Re: Compression

At 22:22 04.04.2007, Jon LaBadie wrote: On Wed, Apr 04, 2007 at 09:49:15PM +0200, Sebastian Henrich wrote: At 17:39 04.04.2007, Jon LaBadie wrote: ... I diabled the hardware compression before I used the tapes for the first time like it's described in the docs. mt shows me that hardware

Re: Compression

months. Didn't you say the problem occured when you switched from HW to SW compression? I've not heard anyone else encountering problems, so your's may have been an edge case. But presumably you will not change from HW to SW compression every 3 months. I recall 4 alternatives to deleting

  1   2   3   4   5   6   >