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:
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,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
HADR: Ability to take incremental backups on either host and maintain the incremental chain for restore
In an HADR environment it is not possible to restore / recover the database with backups which are taken from both sites of the HADR cluster (after takeovers). You have to use the backups from the one site or from the other site. You can't mix the backups.
It is also not possible to take a (incremental) delta backup after takeover that builds up to the last backup taken at the "old" primary site. You have to use the full backup.
The synchronization of the history file between both sides do not solve these problems.
Server 1 (S1), Server 2 (S2), backups are stored in a "shared TSM space" (TSM proxynode).
S1: full backup -> takeover to S2 -> S2: delta backup -> takeover to S1 -> S1: delta backup -> data loss -> S1: manual incremental PointInTime-Restore before "data loss"
manual incremental restore chain:
delta backup S1
full backup S1
delta backup S2
--> Failure (SQL2572N) because the delta backup S2 didn't belongs to full backup S1
Do not place IBM confidential, company confidential, or personal information into any field.