IBM System Storage Ideas Portal
This portal is to open public enhancement requests against IBM System Storage products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
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:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Db2 offers crash recovery processing to bring itself into a consistent state after an outage or power drop.
However, there is no guarantee that the crash recovery will be successful. Reasons for an unsuccessful crash recovery are (examples) corrupt active log filesystems or out of space conditions, as the recovery procedure creates new logs.
Furthermore, crash recovery can take a very long time, depending on how much data was stored in the active log (e.g. happens if a long running transaction has pinned the active log before the crash happened).
In cases where the crash recovery fails, the DB needs to be restored from a backup image (e.g. tape).
The efforts of developing and testing the fsnap scripts are made to provide the highest level of confidence that the database (and the disk based pools) can be recovered successfully to an earlier point in time after an outage or a cyber attack.
Doing crash consistent snapshots "could" help in case of a cyber attack, but IBM will not be able to give a guarantee that the recovery works under all circumstances.
How can we make this crash consistent or sure to recover it without failure.