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 Dec 16, 2016

TSM Snapdiff backup and usage of Snapdiffchangelog in Stagingdirectory

First concerns is with the stagingdirectory itself. In documentation for BA client (7.1.3) is the following
statement:
"The stagingdirectory option defines the location where the client can keep any
data that it generates to perform its operations. The data is deleted when
processing is complete."
It's unfortunately not true in case of snapdiffchangelog, as this file is kept permanently.
Above that it's very sensitive file for the next incremental snapdiff backup.

Second point is the snapdiffchangelog file. There is no single explanation of this file in the official documentation. We found-out the file is sensitive and in case of lost or corruption, the new initial backup must be completed (which can generate issue on very large filers like several days of backup ). This is not good, if the TSM is not able to recover the file itself in combination with the previous point.

Idea priority Medium