Downtime occurred every time a server rebooted. While each individual instance of downtime
was relatively small, there were so many reboots that a significant cost was incurred
from lost productivity. Having some sort of standby situation might have helped. At the
time, though, the only affordable high-availability solution for them was clustering.
Although they did have SQL Server and Exchange on a cluster, that didn??™t help with this
particular issue.
The one true lesson to take from this example is that things go wrong. Even the
strongest IT department can be presented with a disaster they haven??™t anticipated. This
further demonstrates that disaster recovery planning should be an ongoing process.
How SQL Server 2005 Would Have Helped
The company lost money in the effort to troubleshoot the issue. More importantly,
though, money, respect, and credibility were lost because of lost productivity caused by
the continual reboots. Overseas affiliates began to question whether the organization
was capable of maintaining such a complicated IT infrastructure.
If SQL Server 2005 were available, database mirroring would have provided for a
remote failover site, reducing the perception of downtime.
Pages:
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530