• Please help support our sponsors by considering their products and services.
    Our sponsors enable us to serve you with this high-speed Internet connection and fast webservers you are currently using at ADSM.ORG.
    They support this free flow of information and knowledge exchange service at no cost to you.

    Please welcome our latest sponsor Tectrade . We can show our appreciation by learning more about Tectrade Solutions
  • Community Tip: Please Give Thanks to Those Sharing Their Knowledge.

    If you receive helpful answer on this forum, please show thanks to the poster by clicking "LIKE" link for the answer that you found helpful.

  • Community Tip: Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING)

    Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.

Directory Container pool capacity planning

rowl

ADSM.ORG Senior Member
#1
I can't seem to find any information how to plan out the underlying disk capacity for use in a directory container storage pool. For example, say we have 500TB source data and testing shows we can achieve 80% reduction with dedup and compression.

First pass it would appear we need 100TB to store this data, and we don't want to run this more than 80% full so take that to 125TB. Then there is expired data in containers, new containers and this will generate additional overhead that we need to account for. I have always been told for tape or disk volumes one should use a ~2x multiplier to account for worst case where every volume is 60% full (before reclaim).

Is there any good rule of thumb for this sort of capaicty planning?

Thanks,
-Rowl
 

SElias

ADSM.ORG Member
#2
Hi Rowl,
I found this pdf, if you fancy reading :D
https://www.google.com/url?sa=t&rct...s%20v3.1.pdf&usg=AOvVaw0GxJxb-G3XW074_nOVeT6g

Snippet:
IBM Spectrum Protect container storage pool data reduction ratios typically range from 2:1 (50% reduction) to 15:1 (93% reduction). The ratio of 15:1 corresponds to an overall data reduction when factoring in the data reduction benefits of progressive incremental backups. Data reduction depends on both the type of data and type of backups performed. Lower data reduction ratios are associated with backups of unique data (for example, such as progressive incremental data). Higher data reduction ratios are associated with backups that are repeated, such as repeated full backups of databases or virtual machine images. Mixtures of unique and repeated data results in ratios within that range. If you aren't sure of what type of data you have and how well it reduces, for planning purposes, use a 4:1 data reduction for progressive incremental workloads, or an 8:1 data reduction for daily full workloads.

Regards,
SElias
 

Advertise at ADSM.ORG

If you are reading this, so are your potential customer. Advertise at ADSM.ORG right now.

UpCloud high performance VPS at $5/month

Get started with $25 in credits on Cloud Servers. You must use link below to receive the credit. Use the promo to get upto 5 month of FREE Linux VPS.

The Spectrum Protect TLA (Three-Letter Acronym): ISP or something else?

  • Every product needs a TLA, Let's call it ISP (IBM Spectrum Protect).

    Votes: 14 17.3%
  • Keep using TSM for Spectrum Protect.

    Votes: 51 63.0%
  • Let's be formal and just say Spectrum Protect

    Votes: 9 11.1%
  • Other (please comement)

    Votes: 7 8.6%

Forum statistics

Threads
31,381
Messages
133,669
Members
21,495
Latest member
patbel
Top