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 Not under consideration
Workspace AIX
Created by Guest
Created on Jun 18, 2019

Request for ability to have multiple rootvg clones.

The ability to have multiple rootvg clones would be very helpful, we clone rootvg weekly as a means to fall back if regular patching of AIX happens to break something, for example O/S Java used by an application.
However it is now the practice here, to apply TL and SP upgrades to the clone and reboot it to activate the upgrade leaving oll_rootvg as a fall back, old_rootvg is usually left untouched for maybe up to 21 days before becoming a candidate for the weekly clone process again. With the requirement for having weekly "Saturday night" patching for of "security related" fixes to satisfy compliance regulations we miss having a quick fall back if some should go wrong.

Idea priority Medium
  • Guest
    Reply
    |
    Jul 31, 2020

    IBM does not intend to provide a solution to this request at this time. Please follow up with your account representative for more details.

  • Guest
    Reply
    |
    Mar 26, 2020

    A solution is acknowledged to be of some value and will be given consideration for plan inclusion in future planning cycles. No commitment is made to deliver the RFE. **

  • Guest
    Reply
    |
    Jun 19, 2019

    Since you are willing to go back in time, up to 21 days, you should be able, with existing “hooks” to make a copy of the clone aka old_rootvg, but just not add that disk to the bootlist.
    Or, you could look at a savevg of old_rootvg.

    Lastly, you could also look at using multibos, read including multibos in your process. Maybe altdisk and multibos, by design, will not work together, but it is worth examining.

  • Guest
    Reply
    |
    Jun 19, 2019

    Since you are willing to go back in time, up to 21 days, you should be able, with existing “hooks” to make a copy of the clone aka old_rootvg, but just not add that disk to the bootlist.
    Or, you could look at a savevg of old_rootvg.

    Lastly, you could also look at using multibos, read including multibos in your process. Maybe altdisk and multibos, by design, will not work together, but it is worth examining.

  • Guest
    Reply
    |
    Jun 19, 2019

    You can have multiple, just only one can be imported at a time due to mount locations.

    You can use rendev to name your multiple alt disks something interesting, like ALT20190618.

    You can steep it with alt_rootvg_op -S, and then export -X, and import a specific one with -W -d alt20190529, or rendev and overwrite with your normal create.

    I've used alt_disk to make 8 clones, then send them all to different hosts.

    The issue with rendev, or if you could wake/sleep to import multiples, is that the naming is and would be in ODM of whatever you are booted from. There's no practical way to keep that in sync among multiples.