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 Is a defect
Created by Guest
Created on Apr 30, 2020

Replication hung sessions are not getting cancelled on source and target TSM automatically after network disruptions

Replication sessions are getting hung due to network disruption and those sessions are not getting cancelled when the network issue is resolved. It took almost 4 hours for those sessions to get cancelled by TSM server which delayed DR replication and caused lose of data on offsite for 4 hours. It took almost 6 hours to get sync the failed data because hung sessions did not cancel automatically. It seems no TSM server version has the feature to cancel hung replication sessions. It seems the only solution is to restart TSM servers. We can do for one or two servers. But about our environment having 8 TSM servers. We need to fix this urgently.

Idea priority Urgent
  • Guest
    Reply
    |
    Oct 11, 2021

    APAR is: IT33726