Recommended Storage Design when using NetApp E-Series regarding using Dynamic Disk Pools

Last post 06-23-2020, 7:29 PM by Wwong. 3 replies.
Sort Posts: Previous Next
  • Recommended Storage Design when using NetApp E-Series regarding using Dynamic Disk Pools
    Posted: 06-22-2020, 12:10 PM

    Folks,

    We are about to purchase a NetApp E-Series (5760) for use with two separate grids. One grid will have 4 Mediaagents and the other will have 2. NetApp is suggesting we leverage Dynamic Disk Pools (DDP) and then carve out LUNS from the pool. Looking for some guidance on how to design the storage layout.

    1. I'm thinking we should have one DDP per grid. Something like 4 LUNS per MA
    2. Or one DDP and carve out the LUNS accordingly
    What I don't want to happen is to have an Aux copy job or Synthetic Full which are read intensive become a 'noisy' neighbor and consume the disk IOPs while operations on other grid suffers. Would like to keep them logically separated. Is that a valid concern or would it be fine to have one large DDP?
    Many thanks!
  • Re: Recommended Storage Design when using NetApp E-Series regarding using Dynamic Disk Pools
    Posted: 06-22-2020, 11:42 PM

    Hi oalexis

    The recommendation from NetApp to use Dynamic Disk Pools is a good suggestion assuming it is limited to a single grid.

    This will ensure all the LUNs will have distributed IOPs across the Dynamic Disk Pool. 

    The one DDP per Grid will work better, as this would be easier to manage and isolate IOPs related issue (if it does occur) in the future. 

    Regards

    Winston 

  • Re: Recommended Storage Design when using NetApp E-Series regarding using Dynamic Disk Pools
    Posted: 06-23-2020, 10:31 AM

    OK thank you!! That's what we were moving towards

  • Re: Recommended Storage Design when using NetApp E-Series regarding using Dynamic Disk Pools
    Posted: 06-23-2020, 7:29 PM

    No problem, glad that helped

    Winston

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 © 2020 Commvault | All Rights Reserved. | Legal | Privacy Policy