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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
Hello,
We replicate 200 nodes from Server A to Server B, but also 200 Nodes goes from Server B to Server A.
And if the job fails of some reasons the easiest way is to rerun the replication in the foreground, the first thing that shows up is all nodes that are in Receiving Mode and that created 200 lines of information that we should expect that the replication shouldn't replicate.
So when we finally can reproduce the issue, the information get to much for us so the real error get hidden behind all unnecessary information.
We also ending up in a tracing scenario where the developer asked us to exclude all 200 nodes before we run the trace because it generated so much information in the trace log.
So if we could add a Subrule to our existing rule that we want to exclude all nodes where Replication Mode = Receiving or Receive Sync we will then automatically exclude all information that either we as Backup Admin need to know but also from a developer debug information.
This will only help us to faster find the real issue and remove all unnecessary information.
Hello, can you please give us more information on this? What kind of miscongigurations have you encountered?