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

James Luetkehoelter

"Pro SQL Server Disaster Recovery"

The IT manager usually won the
ongoing battle, insisting the window should be shut.
CHAPTER 11 n DISASTER RECOVERY PLANNING 281
The Result
As you might expect, the servers would randomly reboot throughout the day. Some
would exhibit periodic hardware problems that would resolve themselves if the server
was powered down for five minutes. All of this was due to heat.
The hardware vendor was blamed for the ???bad hardware,??? and significant time was
wasted with fruitless arguments between the network manager and the hardware vendor.
The randomness of the reboots and the hardware issues also wasted significant consultant
time attempting to troubleshoot or some how proactively alleviate issues (usually by
scheduled reboots). Instead, the consultants should have been working toward implementing
the systems for which they were hired as specialists.
The constant reboots and downtime caused obvious frustration with the user base,
which included the CEO. While the end users complained to their hearts??™ content and
received essentially no response, one complaint from the CEO caused entire software
packages to be thrown out.


Pages:
498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522
druga wojna światowa Free English grammar and study guid hotel jelenia góra Russian bride counter strike 1.6