One of the requirements of the source database is that it cannot be
restored. The only way snapshots can be included in an off-site backup is if you
take a cold backup of all the database files.
??? Hardware: As with environmental errors, snapshots have nearly no application
when it comes to hardware errors. In a situation where the disk array survives and
the server can be prepared, the standard recovery process of bringing a database
back online should return the database to the point of the failure.
??? Media: Snapshots have absolutely no use in the event of media failures. You can??™t
back up a snapshot, and you can??™t restore a database that has snapshots attached
to it, so if you lose the disk array that the database uses, the snapshots will be completely
invalid.
??? Process: Database snapshots shine with process errors. Any automated or manual
process should be preceded by the creation of a snapshot. Used properly, snapshots
should nearly eliminate the likelihood of a process error.
??? User: I??™ve already discussed two techniques for dealing with user errors. Snapshots
have limitations, but they do provide a level of recovery that was previously
unavailable in SQL Server.
Pages:
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443