SEARCH
0-9 A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Prev | Current Page 529 | Next

James Luetkehoelter

"Pro SQL Server Disaster Recovery"


What Went Wrong
While this situation does involve hardware and a user doing something, well, ill-advised,
this is really a media disaster. By pointing the electromagnet at the cabinet holding the
tape library, the individual created a field strong enough to scramble nearly every bit on
every tape. This is an extreme case, but having something as simple as a TV or a radio
resting on a server or next to a backup tape could have an effect.
How SQL Server 2005 Would Have Helped
The key to dealing with media disaster is redundancy of some kind. Using database mirroring
or log shipping to keep a copy of data off-site would help. The BACKUP command
now includes a MIRROR TO statement; when it comes to databases, transaction logs are
critical. Using the MIRROR TO statement to create multiple copies on different magnetic
devices minimizes the risk of losing a log file.
CHAPTER 11 n DISASTER RECOVERY PLANNING 290
Recommendations and Caveats
The biggest problem with creating a disaster recovery plan is the risk of not being able
to create one at all. What do I mean by that? Projects tend to fail, get forgotten, or get
dropped for other ???more pressing??? issues.


Pages:
517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541
hotel jelenia góra Russian bride Free English grammar and study guid powiekszenia wielkoformatowe counter strike 1.6