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 Aug 8, 2016

V9000 - stopfcconsistgrp command with force option cancelled flash-copy tasks on another consistency group !

Our V9000 All Flash Array has two flash-copy consistency groups.

1. Used for daily backups ( Oracle hot backups )
2. Used for a QA refresh.

On 8/4/2016, we did a QA refresh of 14TB using consistency group 2. copyrate was set to 50, we estimated it to take about 32 hours.

On 8/5/2016, I faced an issue. Two tasks from consistency group "1" were in 'stopping ' state.
Basically, my scheduled daily backup job failed.
I wanted to restart the backup. In order to do that, first, I needed to stop all tasks in consistency group 1.

After multiple attempts to stop them gracefully, I executed the following command.

svctask stopfcconsistgrp -force 1

I expected v9000 to stop tasks in consistency group "1".

But, to my surprise, and later horror, it not only stopped the two tasks from consistency group "1" , but stopped about 27 of the 29 copies that were still copying data in the background that belonged to consistency group "2".

This is unbelievable !!. A standard program that accepts an argument to work upon,

1. It should simply deny if it has to kill another consistency group
2. Or, at least give the executor a warning "Hey, I am going to be killing consistency group 2 as well, Are you sure ??"

Idea priority High