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 Aug 12, 2013

Enhance Backup Stgpool to Limit Processing per Node or Filespace

With TSM 6.4, deduplication works to limit the amount of data stored for a TSM server and its clients. It is however, limited to the stgpool layer. If one wants to do 'backup stgpool' or 'replicate node' (exclusively), it's not possible to tier the service-level by node, without having to add a new stgpool. This is because the 'BACKUP STGPOOL' command will work on the entire stgpool. However, with replication covering a portion of that stgpool, it's not necessarily required to backup the whole stgpool.

Consequently, by adding another stgpool, you add complexity to the environment and reduce the deduplication potential between nodes.

One proposed fix for updating the 'backup stgpool' and the 'copy active' command is to allow for new parameters:

Example: Backup stgpool for specific nodes
backup stgpool srcpool copypool nodes=<node group, node_name>

Example: Backup stgpool for nodes not replicating!
backup stgpool srcpool copypool excludereplicatingnodes=yes dayssincereplication=3

Example: Copy active data for all nodes, regardless if they replicate
copy activedata srcpool actpool excludereplicatingnodes=no

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
    |
    Apr 4, 2014

    Thank you for submitting this request. At this time we cannot deliver this enhancement in the next release or two. If, after our next release of TSM, you would like this requirement to be re-considered, please resubmit the RFE. Thank you for your commitment to TSM and for your support in moving the product forward.