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.
We would like to use incremental backups with 'onbar'. However this is difficult because we use storagepools and chunks can be added at any time. Once a chunk has been added this forces a L0 backup of at least the dbspace concerned and the root dbspace.
We call a whole database backup and this will fail if it is an incremental and a chunk has been added to any dbspace since the last L0. We do not want to write our own script to manage backups at dbspace level and handle any errors.
'onbar' uses a storage manager and it should be possible to back up different dbspaces at different levels at the same time.
We would like either the restriction around adding a chunk forcing a L0 removed or an automatic process for 'upgrading' an individual dbspace's backup (plus root dbspace) to a L0 if we call a whole backup at L1 or L2. An informational message could be written to the message log when this occurs.
We would only expect this to work with 'onbar' and not 'ontape'.
Do not place IBM confidential, company confidential, or personal information into any field.