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
Dear SP development team,
We have been using TSM for decades long since v5.x and upgraded our TSM server to V8.1.10 last year. However, the new release v8.1 has not changed the behavior during migration:
As we noticed some migration process hang there forever to wait for an input disk file. The input file name either is the same or a different from the file being migrated.
e.g.
1. migrating file (000E210A.BFS ) and waiting for file( 000E2113.BFS) is different in the process below:
Protect: TSM2>q proc
... 5,005 Migration Volume /sppool/pcd4/000E210A.BFS (storage pool PCD.FILE), Moved Files: 6, Moved Bytes: 60,008 MB, Deduplicated Bytes: 0 bytes, Unreadable Files: 0, Unreadable Bytes: 0 bytes. Current Physical File (bytes): 10,001 MB Waiting for access to input volume /sppool/pcd2/000E2113.BF- S (7137 seconds). Current output volume(s): H24724.
2. migrating file (000E1E41.BFS ) and waiting for file( 000E1E41.BFS) is same in the process below:
4,972 Migration Volume /sppool/kpb1/000E1E41.BFS (storage pool KPB.FILE), Moved Files: 4850, Moved Bytes: 2,952 GB, Deduplicated Bytes: 0 bytes, Unreadable Files: 0, Unreadable Bytes: 0 bytes. Current Physical File (bytes): 2,143 MB Waiting for access to input volume /sppool/kpb1/000E1E41.BFS (40222 seconds). Current output volume(s): H25933.
When this happened, we have to cancel such processes to free up the drives in order for migration to move on. We would like to implement a timeout so that the migration can skip the file being occupied when reaches the timeout and move on to the next. Please see case TS008689975 for detail.
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. This request may be resubmitted for consideration after 18 months from the date of submission. The request submitter will automatically be notified by email when the request qualifies for reconsideration and resubmission.
The team's recommendation is to consider using a directory container storage pool. There are numerous advantages to this, some of which are:
Deduplication of data
Elimination of "volume" semantics and needing to have mount points or other logical resources
Migration is replaced with storage rules for tiering and can accomplish the same goals as what they are achieving with migration within their existing architecture.