IBM System Storage Ideas Portal
Hide about this 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 (Server)
Created by Guest
Created on Apr 11, 2013

RELATED IDEAS

Node replication failed and does not replicate all data if a communication error occurred on the source or target server

See this idea on ideas.ibm.com

The node replication failed and does not replicate all data if a communication error occurred on the source or target replication server.
Occasionally, node replication will complete with a FAILURE in spite of replicating all objects after having a communication error on either the
source or target replication server. See APAR IC90970 which identifies a condition where the communication errors occur early in the replication
object transfer process and those objects affected by the communication error are successfully retried during the later part of the replication process
The Bank uses a 32Mbps network provided by Finanz Informatik to connect the source replication server to the target replication server.
The network meets the standards of security prescribed by Sparkasse and is the network that will be used for future deployment of TSM.
If a communication error occurred, the node replication must retry the failed file transfer from source to target server (not only one time).
Starting a new node replication process for the same node that failed replication because of communication errors is not an option because
initiating a second replication process takes entirely too long to complete.

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

    Thank you for submitting this request. There were enhancement made in TSM 7.1 that were intended to help alleviate some of the pain points around large object handling by the TSM server. At the present time, there is already an automatic retry attempt performed by the TSM server when a replication failure occurs. Additionally, when a replication retry needs to be redriven, it is the design of the implementation to start replication where the last transaction left off. This essentially means that the replication redrive will be sending new data across the channel and it will not be a duplication of what was already sent. I believe what you may be interested in is something along the lines of a continuous replication or always-on type of replication capability. This is something that we are considering down the road but the request to retry the retried failed replication sessions is something that we will not be implementing in the next two years.

    If, after our next release of TSM, you would like us to reconsider this request, please resubmit the RFE. We sincerely appreciate your feedback and support of moving our TSM products forward.

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.