IBM Data and AI Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea


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.

IBM Employees should enter Ideas at https://ideas.ibm.com


Add a new idea Subscribe
Status Submitted
Workspace Db2
Components High Availability and/or Disaster Recovery
Created by Guest
Created on Oct 10, 2024

RELATED IDEAS

Have option to stop and start the VIP on specific db node when Pacemaker instance is in maintenance mode

We have a customer which uses VIP extensively for in their current environment (TSA/HADR) and have ability to stop, start and move VIP at will.This helps them extensively with near zero downtime during the database refresh process (very frequent process)

In the db2 integrated pacemaker we currently do not have ability to move the VIP at our will. The VIP always point to the primary.

One of the most frequently used scenario by most of the SAP customers is to do database refresh from higher to the lower environments. In this process the HADR pair is broken and standby side "B" is refreshed with new data, while the users continue to use the Primary side "A" as the VIP continues to point to the Primary side "A".

Once the Standby side "B" is refreshed, VIP is moved and now points standby side "B" (takes just a few minutes downtime) and the applications/users connect to the refreshed db side. Now the primary side "A" is restored with side "B" backup, and HADR is established.

The ability to stop and start the VIP on specific db node when Pacemaker instance is in maintenance mode will allow us to have near zero downtime during such change.

 

Following is the process of how database refresh is currently done in customers environment with near zero downtime

 

1. Stop HADR in UAT  (standby side "B" first then primary "A")

2. Restore PROD backup on UAT (standby side "B") -- Primary UAT "A" is active and still used by users. VIP continues to point here

3. Complete restore PROD and roll forward transaction logs on UAT (standby "B:) to timestamp requested.

4. Complete post - restore steps on UAT (standby side "B")

5. Stop VIP on UAT (primary side "A") and start VIP on newly restored UAT (standby side "B"). At this point we have both instances as standard but former standby side "B" is used by users now.

6. Take new backup on newly restored UAT "B".

7. Restore backup from UAT "B" to UAT "A".

8. Establish HADR where UAT "B" is primary and UAT "A" is standby

 

In above process we can see that Standby "B" will refreshed first and the HADR pair is broken. At this point it can take up to a week to do the refresh and establish HADR.

During this whole time VIP is pointing to sever "A" and users work uninterrupted. The VIP is only flipped in step 5 when host "B" has successfully restored. And this flip only takes few minutes


 

Needed By Quarter

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.