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

James Luetkehoelter

"Pro SQL Server Disaster Recovery"


After about four years of continued server additions (and the network infrastructure
required to support it), servers started rebooting randomly. It was infrequent at first, but
grew to the point where each server rebooted at least twice a day, for no apparent reason.
This organization had affiliates in Europe and China, so these reboots affected not only
local productivity, but also the productivity of the international offices. The impact was
costing the company a significant amount of money.
The Result
Needless to say, executive management was growing less and less patient with the IT
department. No one was able to identify an exact cause. Significant time was invested in
troubleshooting the issue. Initially, SQL Server or Exchange problems were thought to be
the cause, and outside consultants were brought in to assist. Then the operating system
was blamed. More consultants. Then the hardware. More consultants. More hardware.
More money. The executives grew more and more upset.
Finally, an internal employee, who once worked as an electrician, came up with a
crazy idea: maybe there wasn??™t enough power coming in to the server room itself.


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