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 27, 2015

Packet data curruption between Tivoli client API and Tivoli server.

Customer is using external network between client machine and Tivoli storage server. These is data corruption between Tivoli client API (dsmSendData) and Tivoli server and client API is not indicating any data corruption. Due to this database recovery fails.
If CRC is set on server for node, Tivoli client API starts failing if there is any data corruption which is expected behavior. But because of CRC, backup process goes slow for all type of data transfer to Tivoli server.
Customer needs this facility to be enabled for sensitive data only, so corruption can be detected immediately for critical data transfer and action can be taken accordingly.
This issue is severe because of recovery failure due to data corruption.
If IBM can provide variable in dsm.opt or provide someway to enable CRC for session, it will help to use the feature (CRC) whenever required and no change is require on Tivoli server.

Idea priority High
  • Guest
    Reply
    |
    Oct 9, 2015

    IBM has evaluated the request, and has determined that it can not be implemented at this time or does not align with the current multi-year strategy. This request may be resubmitted for consideration after 18 months from the date of submission. The request submitter will automatically be notified by email when the request qualifies for reconsideration and resubmission.

    It is critical for you to understand what is causing data corruption across your network. This should not acceptable to you or your customers. Using backup software to identify integrity problems on your network is not a good solution. If you suspect data corruption being caused by the something in the network, you should find a network analyst and resolve that ASAP. Until then, you should check EVERY piece of data that is sent across that connection, not just certain sessions.