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 May 7, 2012

It takes a long time to start / terminate TSM Server after DB backup

After db backup, TSM server does not quickly start or terminate because of waiting for expanding a truncated log of DB2. A real case at solaris environment is that it took 14 minutes to stop TSM server. That means it wiil also take 14 minutes to start next data backup. For instance, that causes a critical impact to switch to backup server at HA environment. Customer wants to take over asap but cluster software could become a time-out because total time of takeover is so long. This behavior could not be acceptable for customer because there was no such a restriction about TSM V5.

So requirement is TSM should provide several options of DB2 logging mode to avoid a waste of time to wait for expanding a truncated log to 512MB. For example, DB2 LOGRETAIN, can be set smaller log size less than 512MB or TSM can be selected another DB2 log mode to avoid the log truncation.

Idea priority High
  • 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 24, 2012

    Thank you for submitting this request. This is a recognized requirement and a solution appears to be desirable. While smaller log size may improve performance but data integrate could be comprised.
    This request is not in the release plan currently under development, but the theme is aligned with our multi-year strategy to balance performance and db integrate for TSM server.
    IBM’s plans may change and no commitment is made that a solution will be provided.

  • Guest
    Reply
    |
    May 7, 2012

    Attachment (Description): Figure expanding a truncated log after db backup