What has to be taken into account when performing capacity planning for HPE Nimble storage using deduplication?

What has to be taken into account when performing capacity planning for HPE Nimble storage using deduplication?
A. Deduplication is performed on a per volume basis.
B. Deduplication is performed on a per application category basis.
C. Deduplication is performed on a per array basis.
D. Deduplication is performed on a per pool and block size basis.

Download Printable PDF. VALID exam to help you PASS.

0 thoughts on “What has to be taken into account when performing capacity planning for HPE Nimble storage using deduplication?

  1. Per volume basis.

    From HPE ASE Storage solutions V4:

    As indicated in Figure 2-36, Nimble uses a number of data reduction techniques and the most important are:

    • Compression

    – Offers highest compression rate (2.5 to three times) typical, as measured by customers
    – Works together with SQL Server compression
    – Runs inline
    – Enabled per volume

    • Deduplication

    – Dedupe is excellent at detecting full or partial copies of databases and saving the space those copies would otherwise use (for example, Always On availability groups).
    – Deduplication on SQL backups is typically 4 to 7 times as tested. Must be uncompressed from SQL (meaning Nimble must handle both compressions and deduplication).
    – Runs inline

Leave a Reply

Your email address will not be published. Required fields are marked *


The reCAPTCHA verification period has expired. Please reload the page.