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 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:
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:
Real Scenario + Problem Statement
|Who would benefit from this IDEA?|
How should it work?
|Geo - Use for OBDR Reporting only|
Why is it useful?
NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "email@example.com" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions