Veritas-bu

Re: [Veritas-bu] oracle policy with compression turned on

2008-03-12 11:04:59
Subject: Re: [Veritas-bu] oracle policy with compression turned on
From: "Parker, Matthew" <matthewp AT amazon DOT com>
To: Paul Keating <pkeating AT bank-banque-canada DOT ca>, "Jared.Seaton AT mylanlabs DOT com" <Jared.Seaton AT mylanlabs DOT com>, mark wragge <mark_t_wragge AT yahoo DOT ie>
Date: Wed, 12 Mar 2008 07:23:02 -0700
If you use RMAN for your Oracle backups, it is already stripping off the unused blocks above the HWM, so your compression shoud only be relative to the compressibility of the used/previously used blocks. If you are using other tools than RMAN to back up the files, then yes you can get fantastic rates of compresion as the blocks above the HWM are zero filled blocks.
 


From: veritas-bu-bounces AT mailman.eng.auburn DOT edu [mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Paul Keating
Sent: Wednesday, March 12, 2008 6:55 AM
To: Jared.Seaton AT mylanlabs DOT com; mark wragge
Cc: veritas-bu AT mailman.eng.auburn DOT edu; veritas-bu-bounces AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] oracle policy with compression turned on

depends...
DBs tend to be padded with a ton of dead space.
Any tape drive, VTL, or de-duping Disk target will compress most databases quite well.
The problem is, you're still pulling that data off the host.
If the client has the CPU cycles available, it can compress the data itself and minimize the data you're sending over the network, or in the case of SAN media servers, over the FC infrastructure.
 
if there's any dead space in the file when it hits the target, you'll still get some compression there as well.
 
Paul
 
 
--
-----Original Message-----
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu [mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Jared.Seaton AT mylanlabs DOT com
Sent: March 12, 2008 8:51 AM
To: mark wragge
Cc: veritas-bu AT mailman.eng.auburn DOT edu; veritas-bu-bounces AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] oracle policy with compression turned on


We get unbelievable compression on our EMC CDL on tapes that are used for DB backups.  I would recommend turning on compression only at the CDL/EDL level.

An example:

(A 100 GB max virtual tape, with compression enabled on the CDL)

From NetBackup Media:
Media ID                                                                 images                kilobytes
AXB009        HCART        00_003_TLD        AIX        30        <snip>        <snip>        5                2150450784        0        Full                 0

From CDL Report:
Name,VID,Barcode,Current:Allocation:(MB),Location,Maximum:Capacity:(MB),Used:Size:(MB),Data:Written:(MB),Compression:Ratio,
VirtualTape-01075,1075,AXB009,100352,In Slot: 11,100352,100177,2100050,20:1,


That is 20:1, and I've actually seen it higher on different backups.





Jared M. Seaton
Recovery Administrator
Mylan Inc.
304-554-5926
304-685-1389 (Cell)



"mark wragge" <mark_t_wragge AT yahoo DOT ie>
Sent by: veritas-bu-bounces AT mailman.eng.auburn DOT edu

03/12/2008 06:34 AM

To
veritas-bu AT mailman.eng.auburn DOT edu
cc
Subject
[Veritas-bu] oracle policy with compression turned on





How does the compression option on an Oracle policy function? Is it the same as turning on compression on a standard filesystem backup OR is this a compression feature specific to oracle database backups?
 
I am considering turning on compression on a Virtual Tape Librayr and on the oracle policy. Should i just turn it on on the VTL (EMC EDL).
 
Thanks.

 Send instant messages to your online friends http://uk.messenger.yahoo.com _______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

==============================================================================
CONFIDENTIALITY NOTICE:  This e-mail message and all attachments transmitted with it may contain legally privileged, proprietary and/or confidential information intended solely for the use of the addressee.  If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution, duplication or other use of this message and/or its attachments is strictly prohibited.  If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message and its attachments.  Thank you.
==============================================================================

====================================================================================

La version française suit le texte anglais.

------------------------------------------------------------------------------------

This email may contain privileged and/or confidential information, and the Bank of
Canada does not waive any related rights. Any distribution, use, or copying of this
email or the information it contains by other than the intended recipient is
unauthorized. If you received this email in error please delete it immediately from
your system and notify the sender promptly by email that you have done so. 

------------------------------------------------------------------------------------

Le présent courriel peut contenir de l'information privilégiée ou confidentielle.
La Banque du Canada ne renonce pas aux droits qui s'y rapportent. Toute diffusion,
utilisation ou copie de ce courriel ou des renseignements qu'il contient par une
personne autre que le ou les destinataires désignés est interdite. Si vous recevez
ce courriel par erreur, veuillez le supprimer immédiatement et envoyer sans délai à
l'expéditeur un message électronique pour l'aviser que vous avez éliminé de votre
ordinateur toute copie du courriel reçu.
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
<Prev in Thread] Current Thread [Next in Thread>