Skip to Main Content
IBM Power Ideas Portal


This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. 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 Planned for future release
Created by Guest
Created on Jul 22, 2019

Power Systems Recovery Manager - Enhanced DR orchestration capabilities

We are trying to leverage Power Systems Recovery Manager for meeting following objectives,

-Diagram shows business requirements.
-Only DR is depicted in diagram
-DC only hosts PROD
-Under normal condition DC runs PROD and DR hosts PREPROD, T&D and PROD with 40%, 40% & 20% compute capacity respectively
-Once DR is invoked need to resize PREPROD, T&D and PROD to 0%, 10% & 90% compute capacity respectively
-NO storage level replication in place currently, neither is planned [DB is replicated using ODG, rest workloads leverage rsync]

Idea priority High
  • Guest
    Reply
    |
    Aug 1, 2019

    .VM Recovery Manager DR takes care of storage mirror management for supported storage. In the current model, it is not a storage based mirror, so VM Recovery Manager DR can be used in shared mode, where VMRM ignores replication management.
    Another request would be use a different VM on target and initiate DLPAR activities. So here VMRM DR can provide new option not to restart and still provide callback support. In the callbacks identify the right target VM and initiate DLPAR activities. Callback implementation need to be done by user.

  • Guest
    Reply
    |
    Jul 25, 2019

    Mr Bhat, Reviewed the diagram. Currently VM Recovery Manager enables the following:
    1. Customer fixes the size of the VMs (CPU, and Memory) on the main site. They also pre define the %of resources they need for backup site. When admin initiates the failover the VM sizes are adjusted and redeployed

    2. VM Recovery Manager works only with Storage replication currently. There are no plans currently to support any other replication

  • Guest
    Reply
    |
    Jul 22, 2019

    There is an immediate opportunity for Power Systems Recovery Manager at one of the biggest oil company in India [Government of India, Maharatna venture].
    27 POWER8/9 servers across DC & DR, totalling an install base of 884 cores.

  • Guest
    Reply
    |
    Jul 22, 2019

    Attachment (Use case): -Diagram shows business requirements. -Only DR is depicted in diagram -DC only hosts PROD -Under normal condition DC runs PROD and DR hosts PREPROD, T&D and PROD with 40%, 40% & 20% compute capacity respectively -Once DR is invoked need to resize PREPROD, T&D and PROD to 0%, 10% & 90% compute capacity respectively