>A file or database gets corrupted Tuesday evening and Wednesday >morning review catches it. Meanwhile further updates have been done. >How simple is the recovery and damage limitation process? This is >just on scenario of failures that can take much time to fix.
The problem with all these "what if" scenarios is that they don't explain how the problem occurred. If a morning review can catch a problem, then what was the condition that presented the previous evening? Is it something that could be detected by automation? Is it something that requires manual review to prevent its occurrence in the future. The point isn't that problems can't occur, but what is being done to mitigate their effects? When a problem is understood then actions can be taken to prevent its recurrence. However, it seems clear that in this case, that whatever problem may have existed, it was ignored. Nothing takes seven days to recover unless you've screwed up virtually everything that was there to protect you. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
