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.
PDA customers can do a table-level restore from an existing full or incremental backup without impacting any other objects in the database. It restores only regular tables not external or temp tables. When migrating to IIAS, these customers lose this capability. Also, individual databases get converted into schemas during migration. To have continuity for PDA customers we need to provide a granular backup and restore capabilities using a single tool so that customers have a complete control over a set of objects or a schema. Performance characteristics should at least match Mako. All our competitors allow finer grained recovery either at schema or table level. Basic requirements are:
Backup and Restore full/incremental at Schema level
Restore individual or a specific set of tables from either a database or schema level backup
Backup and Restore at Schema level
Anything at Schema level should cover data, index, and meta data (views, UDFs, etc). Typical use-cases that are being requested by customers:
Ability to take full backup at schema level
Ability to restore full schema level backup against the same or different schema name.
Ability to take incremental backups at schema level
Ability to apply incremental restores at schema level
Ability to apply full or incremental restore followed by roll forward to a Point In Time
Restore individual or a specific set of tables
This provides more granularity at an object level. If a table object gets corrupt or dropped by mistake, this capability helps our customers recover just the table data rather than restoring the entire database. We can match PDA by having customers recover table data from last known good backup set but no further roll forward. This means customers lose any data changes occurred between the last backup and the current time. Typical use-cases that are being requested by customers:
Ability to restore a table or a specific set of tables on a schema
Ability to restore a table or a specific set of tables on a different schema
Do not place IBM confidential, company confidential, or personal information into any field.