Oracle Compression

Last post 12-03-2019, 8:36 AM by omer. 5 replies.
Sort Posts: Previous Next
  • Oracle Compression
    Posted: 11-29-2019, 7:50 AM
    Hello All,

    Can we get backup Oracle DB with Oracle Compression enable and Commvault Dedup + Compression enable?
    If we back it up, how does Commvault behave, anybody has any research on this?

    Best Regards.
  • Re: Oracle Compression
    Posted: 11-30-2019, 1:51 AM

    For non-databases Commvault compresses before hashing the block, for databases the compression occurs after the  block has been hashed.What problem are you trying to solve by introducing Oracle Compression as well? 

  • Re: Oracle Compression
    Posted: 11-30-2019, 8:40 PM

    Hi Omer 

    If Oracle Compression is enabled this can greatly impact the Deduplication Saving, as the block will always compress first from the Client level and then sent to Commvault for Deduplication and Compression. 

    I would recommend to only use Commvault Deduplication and Compression and not use Oracle Compression 

    Regards

    Winston

  • Re: Oracle Compression
    Posted: 12-02-2019, 3:41 AM

    Anthony.Hodges:

    For non-databases Commvault compresses before hashing the block, for databases the compression occurs after the  block has been hashed.What problem are you trying to solve by introducing Oracle Compression as well? 

     

    We're not actually trying to solve a problem. What we're trying to learn is: Can we reduce the amount of data written using Oracle Compression and Commvault Compression + DDB?

  • Re: Oracle Compression
    Posted: 12-02-2019, 9:12 AM
    • efg is not online. Last active: 12-06-2019, 8:50 AM efg
    • Top 10 Contributor
    • Joined on 02-02-2010
    • CommVault Tinton Falls NJ
    • Master
    • Points 1,687

    Hi Omer,

    It is not recommended to use both Oracle compression and Commvault compression.  This will only chew up CPU cycles and not gain any additional space savings.  Plus, enabling Oracle compression will also impact DDB in a negative way.  Where as Commvault compression is designed to work with Commvault DDB (See the responses from Anthony & Winston) which will yield the best possible space savings.

    So the recommended best practice for Oracle = CV Compression ON + CV DDB.  Also it is recommended to set BFS (In subclient settings) to between 4 & 8 which will yield in better deduplication & performance.  Also keep in mind that archive log backups automatically disable deduplication (since they are all unique) and achieve better results with only compression.

    Hope this helps...


    Ernst F. Graeler
    Senior Engineer III
    Development
  • Re: Oracle Compression
    Posted: 12-03-2019, 8:36 AM

    Hello efg,

     

    Thank you for the detailed explanation. I will keep in my that.

     

    Best Regards.

The content of the forums, threads and posts reflects the thoughts and opinions of each author, and does not represent the thoughts, opinions, plans or strategies of Commvault Systems, Inc. ("Commvault") and Commvault undertakes no obligation to update, correct or modify any statements made in this forum. Any and all third party links, statements, comments, or feedback posted to, or otherwise provided by this forum, thread or post are not affiliated with, nor endorsed by, Commvault.
Commvault, Commvault and logo, the “CV” logo, Commvault Systems, Solving Forward, SIM, Singular Information Management, Simpana, Commvault Galaxy, Unified Data Management, QiNetix, Quick Recovery, QR, CommNet, GridStor, Vault Tracker, InnerVault, QuickSnap, QSnap, Recovery Director, CommServe, CommCell, SnapProtect, ROMS, and CommValue, are trademarks or registered trademarks of Commvault Systems, Inc. All other third party brands, products, service names, trademarks, or registered service marks are the property of and used to identify the products or services of their respective owners. All specifications are subject to change without notice.
Close
Copyright © 2019 Commvault | All Rights Reserved. | Legal | Privacy Policy