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 Not under consideration
Created by Guest
Created on Jan 17, 2017

SVC stretched cluster learning Easy Tier heatmap on secondf copy of Vdisk mirror

Easy Tier considers each pool separately, without knowledge about mirrored VDisks. In a stretched cluster with full site awareness and host failover cluster as application, the pool in the production site (where the host failover cluster lives most of the time) receives all read cache misses and all writes. The pool in the other site receives only the (mirrored) writes. Therefore, the IO patterns and the hot spots of the pools are different. In the production pool, the hot spots are determined by the combined read + write back-end IOs. In the other site, only the back-end writes build hot spots... this will generate performance problem when failorver on the second host who is located on the second site(the reads were never seen by Easy Tier in this pool)

Idea priority Urgent