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.
See this idea on ideas.ibm.com
Site fail-over/fail-back of the "restore" function (read from ISP server(s)) is already provided in the ISP server product.
Site fail-over/fail-back of the "backup" function (write to ISP server) is not. If site A goes down, backups must be suspended or extensive manual intervention is required to continue backing up (writing backups) to an alternate site.
If two sites have the same list of NODEs, employ cross-replicating STGRULEs/SUBRULEs via NODEGROUPs, ensuring that all NODEs are replicated to their partner ISP server, and there is a Client Acceptor with stashed credentials and full configuration to both ISP servers involved in replication on each client host, then the "backup" fail-over/fail-back function is controlled solely at the ISP servers with a few administrative commands.
ISP_A
ISP_B
CLIENT_A
CLIENT_B
Scenario: ISP_B goes down indefinitely (I.e. disaster)
* Graceful failover involves removing configuration from ISP_B.
Upshot: Only a few ISP server commands (not client-side configuration) are required to fail-over/fail-back the ISP NODEs' "backup" topology when these conditions exist (partner ISP servers cross-replicating). It requires only minutes to fail-over or fail-back an entire site's backup function, instead of significant hours or days. With scripting, the entire backup function of an ISP server could be moved in 1 minute.
Idea priority | Low |
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.