Skip to Main Content
IBM Data and AI Ideas Portal for Customers

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:

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

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.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Future consideration
Workspace Db2
Created by Guest
Created on Jul 1, 2020

Allow to exclude index pages from backup - recreate after restore

Db2 backup is saving all database objects regardless if the objects (especially indexes) could be re-created, because the objects contain just redundant data.

Db2 already provides the DBM CFG parameter INDEXREC which configures when an invalid index will be re-created.

If Db2 would provide an option to backup indexes as invalid, the backup image would contain just the meta-information of the index and its state invalid. Thus, nearly no index pages will be sent to the storage manager, no backup space will be required.

After a restore of such a backup the indexes are in state invalid and depending on INDEXREC the indexes will be recreated.

Considering an environment where production backups can not be used for non-backup environments (development, test). Often the indexes contain about 30% of the total disk space. If a backup image is about 6 TiB in size and daily backups are taken, the space required at the storage manager would sum up to 60 TiB per month.

And since a restore will only be in case of a serious outage, this index-space of the backup image will never be used.

Feature would allow to save backup storage space, increase backup (and restore) speed.

The disadvantage will be the necessity of rebuilding the indexes following a restore and rollforward (depending on INDEXREC).

Needed by Date Dec 31, 2020