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
High end customers using TSM with SSD for DB directories and running 7x24 are very likely to run into the following situation:
because SSD space is very expensive, it is not always possible to permanently attach hundreds of GBs to each TSM instance only for running an online index reorg for the big tables like BACKUP_OBJECTS.
Sample: customer has 20 TSM instances with each 350GB space on SSD allocated for TSM DB directories, DB usage is in average 300GB. Online index reorg is aborting with unsufficient space, because at least 80-90GB of free space in the DB directories are needed for the index reorg.
Offline reorg is not an option, because of 7x24 availability for the TSM servers.
Solution could be having a temporary filesystem (on SSD or regular disk) which can be specified for online index reorg usage and only needs to be attached to the TSM instance for running the online index reorg.
E.G:
check if index reorg is needed for big tables like BACKUP_OBJECTS
attach temporary space to specific TSM instance
setopt allowreorgindex yes
... let online index reorg run to end over all tables
setopt allowreorgindex no
detach temporary space from TSM instance and attach it to the next instance.
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.
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
Thank you for submitting this request. This is a recognized requirement and a solution appears to be desirable. This request is not in a committed release plan for this year, but the theme is aligned with our multi-year strategy, and will be a candidate for a future release. IBM’s plans may change and no commitment is made that a solution will be provided.