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
Develop the storage migration mechanism (both the MIGRATE STG command and automatically initiated equivalents) to either move data at a more granular level than node ownership, or develop it to support multiple processes per whatever level of granularity you support, currently the node level. � Currently a single node can fill up the initial destination for a domain�s copygroup, such as a storage pool of DISK devices, faster than a single MIGRATE STG command can empty it if the output device for MIGRATE STG isn�t particularly fast. Allowing MIGRATE STG to use more than one process for a storage pool doesn�t matter if TSM won�t use more than a single process for a node�s data, even if the data comes from several file systems. Allowing MIGRATE STG to use more than one process per a node would give MIGRATE STG a better chance of staying ahead of an unusually large backup stream from a single client, preventing the eventual overrun of the storage pool in question. The one process per node model may have fit well a decade ago when storage I/O speeds were much faster than IP network speeds, but that model is breaking down in current data center configurations.
Idea priority | Medium |
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