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 Jun 10, 2011

TSM Scheduler Update (SYS4331)

The Best Practice for TSM server environments is to include Full backups on a periodic basis.
With the efficiency of the incremental Forever strategy of TSM, there comes a side effect that can become a road block to achieving a timely RTO. This is "data fragmentation."
Scheduling full backups via the TSM scheduler turns out to be problematic as the standard daily and periodic full schedules conflict with each other. Tivoli Level II concurs after reporting the conflict. (pmr 65117) So the only way to do both daily incremental and periodic full is to schedule daily backups from TSM and quarterly backups from the OS. There may be other ways to do this via TSM, but the logistics will be very complicated.

One way to counteract these complications is if the TSM schedulers could take into account the fact that a duplicate node name could be configured in separate stanzas. These nodes need to be acted on exclusively within the schedulers when they have completely separate and exclusive schedules. Currently, TSM schedulers tend to trip on each other when encountering identical node names in separate stanzas.

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