Michigan IBM Storage Protect User Group

Michigan IBM Storage Protect User Group

Our user group focuses on the IBM Storage family of software defined storage solutions.

 View Only

Cloud Cache sizing guidance

By Doug Grayer posted 11/11/16 10:23 AM

  

There were some questions about how to size the cache for object storage.  Austen found some sizing info to share

http://www.ibm.com/support/knowledgecenter/SSGSG7_7.1.7/srv.install/c_dedup_cont_config_install-linux.html

Did you allocate enough disk space in the cloud-container storage pool? To prevent backup failures, ensure that the local directory has enough space. Use the following list as a guide for optimal disk space:
    •    For serial-attached SCSI (SAS) and spinning disk, calculate the amount of new data that is expected after daily data reduction (compression and data deduplication). Allocate up to 100 percent of that amount, in terabytes, for disk space.
    •    Provide 3 TB for flash-based storage systems with fast network connections to on-premises, high-performance cloud systems.
    •    Provide 5 TB for solid-state drive (SSD) systems with fast network connections to high-performance cloud systems.
Did you select the appropriate type of local storage? Ensure that data transfers from local storage to cloud finish before the next backup cycle starts.
Tip: Data is removed from local storage soon after it moves to the cloud.
Use the following guidelines:
    •    Use flash or SSD for large systems that have high-performing cloud systems. Ensure that you have a dedicated 10 GB wide area network (WAN) link with a high-speed connection to the object storage. For example, use flash or SSD if you have a dedicated 10 GB WAN link plus a high-speed connection to either a Cleversafe® location or to an Amazon Simple Storage Service (Amazon S3) data center.
    •    Use larger capacity 15000 rpm SAS disks for these scenarios:
    ◦    Medium-sized systems
    ◦    Slower cloud connections, for example, 1 GB
    ◦    When you use Cleversafe as your service provider across several regions
    •    For SAS or spinning disk, calculate the amount of new data that is expected after daily data reduction (compression and data deduplication). Allocate up to 100 percent of that amount for disk space, in terabytes.

 

0 comments
1 view

Permalink