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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
See this idea on ideas.ibm.com
Please see mentioned PMR. Calculation of front end capacity for TSM for Virtual Environments is wrong, in my opinion. The results differ wildly depending on if the customer uses thin or thick disks and if there happen to be snapshots, for example. And the measured value does not reflect if the customer excludes some disks from backup at all, for example. The reason is that the calculator just calls a vSphere API to retrieve the "Space Used" value for each VM. This is only a very vague result and does not reflect the actual amount of data protected.
To be consistent with how the capacity is calculated for B/A data, the calculator should determine the "active blocks" from the TSM server for each VM. As far as I could see, this needs changes for TSM VE so that blocks stored in TSM are marked as active and (when replaced) as inactive similarly like done for B/A clients. Currently this does not seem to be the case.
Idea priority | High |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
IBM has evaluated the request, and has determined that it can not be implemented at this time or does not align with the current multi-year strategy.
Please take a look at this document, ftp://public.dhe.ibm.com/storage/tivoli-storage-management/front_end_capacity_measurement_tools/ISPSuite_FE_LicenseGuide_816_en.pdf to read the changes that have been made since this RFE was opened.
If needed, you can run the script manually with DEBUG enabled to see exactly how and what is counted: ftp://public.dhe.ibm.com/storage/tivoli-storage-management/front_end_capacity_measurement_tools/
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - Storage
Product - Tivoli Storage Manager (TSM) Family
For recording keeping, the previous attributes were:
Brand - Tivoli
Product family - Storage
Product - Tivoli Storage Manager (TSM) Family