IBM System Storage Ideas Portal
This portal is to open public enhancement requests against IBM System Storage products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
IBM agrees the requested enhancement has value, and will consider this request when prioritizing enhancements for future releases.
Larry, please ignore my previous comment.
The cache capacity tube shows only the various types of data IN CACHE. With 'active data' the total amount of valid data is meant in a cluster INCLUDING what's resident on BACKEND TAPE. And 'active data' is tpyically composed of the private virtual volumes plus scratched virtual volumes that are still not released due to expire/hold.
'Active data' is useful in each sizing, be it 60 or 60T where a client cannot provide VEHSTATS for whatever reason (not implemented, public tender, not opportune because of sales stage (price info only) or tight timeline etc.). For a tapeless it gives a direct value how large the cache needs to be at minimum. For a tape attached sizing to determine the number of cartridges it is useful als well. Today - wherever the client cannot provide VEHSTATS - there are two inaccurate ways to determine the required backend cartridge capacity: a) take the amount of data managed by the tape management system e.g. RMM; this is fuzzy because of the compression achieved. Having 'active data' would help to quality check the RMM value. b) take the numer of existing tapes (e.g. JB) and calculate the required number of e.g. JDs.; this is fuzzy as the average utilization of the pyhsical tapes is also difficult to determine.
I think implementation wouldn't be too difficult as the value is already present in the cluster. It just would need to be added to an interface. E.g. the CACHE response output could be extended by one additional line with TOTAL ACTIVE DATA or by an additional column showing the 'active data' per CP. Same for the GUI cache capacity tube.
What kind of additional information is required? Rgds, Thorsten
Thorsten, the Cluster Summary in the GUI shows both the used capacity and the total capacity of the cluster's disk repository. Please describe why that does not satisfy this request, e.g. what different data is needed, for what purpose, and how often it would be accessed. Thanks.