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.
Backup Image file needs final stats, index/table contents and fast restore LOGS only
Backup Image file needs final stats for use at restore time, index/table contents and fast restore LOGS only.
Assuming f.i. one has a "full online backup db include logs", a restore of a 'big' backup image (especially > 1 TB) , in another server is often troublesome not knowing any stats/size/contents of required disk space :
for the restore db itself (before the 'roll forward to end of logs')
for the embedded LOG files that need to be extracted to LOGTARGET, as last step of the restore.
The restore db can run for many hours, can or cannot fit on disk, and if it does after, almost job almost complete at 99%, finding out LOGTARGET disk is full ....
Then, after making sure (guessing) LOGTARGET space is sufficient, one has to restart the restore all over again. Loosing valuable time.
Even ONLY restoring the LOGS in a separate session, and then resuming the roll forward will not save time: A full image scan is needed, that also will run for hours, to locate and extract the LOG files from the backup image.
At present the history file, which is near the beginning of the image file, can be restored rather fast, but it will not help much : the history file does not include the size of the 'future' backup image, nor does it have information of number and size of log files ' running' backup.
A db2diag log file(s) of the original db location/server often would have been pruned, so that also lso not useful for stats of the backup time and restore sizing (start , end, and number of log switches in-between).
Do not place IBM confidential, company confidential, or personal information into any field.