Leverage those low spots to minimize impact.
Time to Restore
For most business units, a short time to restore is a critical requirement??”sometimes the
overriding requirement. A certain amount of data loss is acceptable just as long as the
system doesn??™t remain down for any ???perceptible??? amount of time. That??™s the crux of the
requirement: dealing with ???perceptible??? time.
It can be relatively common to have some sort of technical issue that has nothing to
do with restoring a database, yet the perception may be that it??™s a database issue. Be prepared
to do quick troubleshooting to eliminate the database as an issue, if it is indeed up
and responding adequately. Run the same sort of queries on your local network as are
executed by the application through the Internet or from a remote location. Is the performance
acceptable? If so, then it??™s unlikely that the database has a problem at all, much
less that it??™s down and needs to be restored.
When restoring, look to minimize the number of restore steps involved. Avoid
restoring large numbers of (or large) log backups.
Pages:
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220