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.

Add a new idea Subscribe
Status Not under consideration
Workspace IBM DS8000
Created by Guest
Created on Nov 4, 2018

RELATED IDEAS

Avoiding full volume background copy after restoring of one FlashCopy relation in DS8K multiple incremental FlashCopy env.

The environment we request this enhancement is in DS8K multiple incremental FlashCopy with cascading FC support. In this environment, The customer will have two incremental FC relationships from one source A as Step1 bellow. Actually they will take incremental FC A:B before batch and take another incremental FC A:C after batch. When the customer restores data from B to A by reverseflash A:B command (Background copies on both legs complete before) as Step2 bellow, after background copy (BGC) from B to A completes, probably on next day, they will do resyncflash from A to C as step3 bellow. This resyncflash will cause full volume background copy. This is the current designed DS8K's behavior. Amount of the data of A will be 100 TB and amount of daily update will be 3 TB in this customer. It is estimated that the BGC of 100 TB will be 24 hours in the customer's DS8K configuration which may impact production's I/O performance and impact their FC restore capability with FRR during the BGC window. Therefore, we want DS8K code's enhancement to make DS8K done incremental BGC for A->C even after restoring of B->A.

The customer's data copy/restore scenario that they are doing by the HDS Shadow Image function.

Step 1: Incremental FC A->B and incremental FC A->C

Step 2: Reverseflash -multiinc A->B (Actual FC relationship will become B->A)

Step 3: Resyncflash A->C (Even if there is no update after step 1, full volume copy will be done from A->C.)

It is better to have this enhancement with the current DS8880 stream, but it is acceptable that the enhancement will be done with next DS8K stream because the customer's project will start 4Q 2019 and not fixed yet.

The customer is doing restoring data from B to A very often on weekend testing time. On the weekend, they will take FC A->B/C before testing and do some testing with A volumes and then restore B->A. Therefore, full volume copy may happen many times, not only in a case of data corruption on A volumes.

Idea priority High
  • Guest
    Reply
    |     Nov 5, 2018

    Issuer's additional comment:
    We are OK if this enhancement will cover only limited environment such as three incremental FC relationships. In Global Mirror environment, this customer will have two additional incremental FC from GM B volumes. So, there will be three incremental FC relationships, such as 1. GM B->C, 2 GM B->D1 and 3. GM B->D2. We wants to keep incremental background copy of B<->D1/D2 even if after doing FRR (Fast reverse restore) from C->B. Even though we can have 12 incremental FC relationships, I believe many customers generally don't need such number of incremental FC relationships with this enhancement.

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.