Skip to Main Content
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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. 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.

Status Not under consideration
Created by Guest
Created on Apr 24, 2014

TSM Server Import Node from Media requires option to start from tape sequence # other than 1.

System: TSM Server
Actor: Bendigo Bank

TSM Media Exports have been actively used to migrate from our TSM 5.5 environment running on Windows 2003 to TSM 6.4.x running on AIX 7.1

Description:
I have a very long media import to a TSM v6.3.4.100 server running on AIX.
In total there are 94 tape volumes listed in a source FILE to import, but have had numerous failures throughout the import (not from bad media).
Every time I have had to start the media import (now up to the 4th time), it reads the file list from the first tape sequence. Using the MERGE option no additional data gets imported until it gets to the tape sequence that last failed.
At the moment, it takes us 8 days to read the 79 tapes previously imported, just to start importing new data (and possibly fail again).
I would like an option such as 'SEQuence=##' (maybe in combination with 'FORCE=yes') to allow media imports to start at any tape sequence number.
I tried placing comments in the volume file to skip the first 78 tapes, but got an error stating the tape seuence 1 is required.
I am aware that server to server exports can be resumed, but the sheer amount of data to be exported through a thin ethernet pipe is not practical in this case.
We have wasted months of time (with IBM waiting to take back a decomissioned ATL) on various imports because this feature is not available and I can't see why it would not be a practical (and relatively simple) to add.

Idea priority High
  • Guest
    Reply
    |
    Oct 30, 2020

    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.

    Consider dividing up the imports leveraging the FROMDATE/TODATE capabilities.

  • Guest
    Reply
    |
    Jun 12, 2015

    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

  • Guest
    Reply
    |
    May 13, 2014

    Additional Email Correspondance from PMR 17658,215,616:
    -----------------------------------------------------------------------------------
    Hi Greg,

    Yes I realise Chris is not probably available at the moment.

    And you are correct; we have not had the opportunity to increase the log at the moment. At the time of that recommendation we were 60% through reading tapes from a media import which had taken 8 days to progress. So to increase the log up to the maximum was going to be an outage to the server and disruption to both the import and to other backup services. Also, due to the sheer size of the node being imported, increasing the log to the maximum may not have provided enough additional log space to still complete the remaining media import and I couldn't afford the 10+ days to find out.

    So, we are now managing the import via a separate server to server export (as apposed to the original media import). We can suspend and restart the export when required, to free up the log space which is more practical (see results below). I think what I've realised throughout this whole process is that you can spend all this time exporting node data to a large set of media and NEVER be able to completely import it, even with the log set to the maximum as if the log fills (which it eventually will on a large import) the process will be cancelled and the only way to start again is to read all the tapes from tape sequence #1 and consequently have the log fill again. Because of this particular issue, I have raised a RFE to allow a SEQuence parameter to be added to media import process to allow a large media import to be forcibly start on any tape sequence other that the first tape (which would have solved my issue 3-4 weeks ago)