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 517 | Next

James Luetkehoelter

"Pro SQL Server Disaster Recovery"

Sure
CHAPTER 11 n DISASTER RECOVERY PLANNING 284
enough, the staff performed a few tests and discovered that there indeed wasn??™t enough
power to run all of the IT hardware they??™d been accumulating over the previous five years.
Electricians were brought in, and the problem was resolved, but not before costing the
company millions of dollars, as well as damaging the perception of IT in the eyes of the
executives.
What Went Wrong
This is one scenario where literally nothing was done incorrectly. The company had a
great server environment and a quality staff. It was just an extremely difficult issue to
troubleshoot. If anything was done wrong, it was relying too much on consulting companies
to assist with the problem. Granted, this occurred during a time when companies
put a lot of faith in consulting companies to act as ???experts??? for the changing technologies.
The company sunk a lot of money into external help troubleshooting the issue. To
be fair, it was almost impossible to troubleshoot. It took someone??™s hunch to find the
problem.
The one item the IT staff truly lacked was an appropriate mitigation procedure.


Pages:
505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529
druga wojna światowa Free English grammar and study guid hotel jelenia góra Russian bride counter strike 1.6