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.

Add a new idea Subscribe
Status Not under consideration
Workspace Storage Protect Family
Categories Spectrum Protect for Databases
Created by Guest
Created on Oct 28, 2011

RELATED IDEAS

TSM Client side deuplication effectiveness compromised by local cache file locking

Currently, attempts to perform multiple database backups concurrently from a dataserver instance registered to a single TSM node name with client side deupe enabled will fail with ANS7903W.

We have been advised that there are two ways to work around this issue;
i) Create a private dsm.opt file per database to be backed up, each with a seperate dedupe cache file path.
or
ii) Register / Create a TSM node name for every single database in the firm, istead of creating a TSM node for each parent dataserver.

Both of these workarounds are not acceptable for the following reasons;

i) We create/migrate/decomission hundreds of databases per day. The admin overhead of having to make the necessary TSM config changes (config files or node registration) would be significant.
ii) Having seperate deduplication caches per database reduces the effectiveness of the client side dedupe cache per dataserver (intra-database deupe cache oppertunities are lost).
iii) The additional disk space overhead of having 1 cache per database instead of 1 cache per server.

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
    |     Nov 29, 2011

    Thank you for submitting this enhancement request, we do understand the requirement and the rationale behind it but unfortunately we currently do not plan to implement the function as it is described in this RFE, TSM already has a couple of options that address similar needs, multiple threads are using the same cache files and multiple processes can leverage separate cache files.

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.