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 Future consideration
Created by Guest
Created on Sep 8, 2020

vSnap implement HA feature - automated failover

Implement an automated failover for vSnap component:
When having multiple vSnaps in one Site and one vSnap fails, the other vSnaps won't automatically stand in and pick up the backup jobs. This causes a service outage which is not acceptable.
Of course this will cause new full backups to happen, but it's better than having no backups. Suggestion would be to flag a vSnap as "unavailable" by hand, so this is an administrative action.

Background info:
All VMs/databases which were backed up to the failing vSnap will fail with error CTGGA2403 - Error: Volume already created however unable to access storage server
If you remove the VM/Database from the SLA, click save and add it again, the job will also show a warning but then switch to a working vSnap.
- So there is a workaround, but this is not practicable for a large number of Objects.

Idea priority Urgent
  • Guest
    Reply
    |
    Sep 10, 2020

    This request may not be delivered within the release currently under development, but the theme is aligned with the current multi-year strategy. IBM may consider and evaluate any RFE Community feedback for this request through activities such as voting. IBM will update this request in the future.