diary top frame
Monday, March 10, 2008
posted on 3/10/2008 11:51:55 AM (Eastern Daylight Time, UTC-04:00)

Silence from users about IT is a sign of trouble rather than success. In a sense, IT should be invisible, where it fades into the background. But is the system really running great or are people just making do? Here are some probing questions to determine whether your IT system really is computing nirvana or a sleeping dragon.

Is your team actually preventing IT problems, or just more efficient at solving a recurring problem?  Kudos to the team for getting the firm back up and running quicker after that pesky outage that happens at least once a month, but what are you doing to prevent the outage from ever happening again? Sometimes in IT we get caught up in solving the problem, rather than preventing it in the first place.

What workarounds are users creating to deal with IT issues rather than complain? We had one client who was amazed at how fast their systems booted after an image refresh. Why had no users been complaining of a slow boot process?  For one, they didn't have a standard to compare against, so they just assumed it was normal. Also, they adjusted their work schedule to accommodate the quirks and failings of the system.  So before the image refresh, our client's employees started the login process and then went to the break room for 10 minutes for coffee and kibbutzing. When they returned, the computer would be booted up.

Are you asking them? Despite the many complaints that IT professionals hear, most people will silently bear minor inconveniences. They may not know how to explain the problem or think the time to solve it will be greater than the small dings on their productivity. They may not even see the cumulative costs of those productivity hits personally, but have tremendous effects when viewed from the firm's perspective.

Wednesday, March 05, 2008
posted on 3/5/2008 4:33:07 PM (Eastern Standard Time, UTC-05:00)

Our post last week discussed how "time-to-restore" is the primary factor in data backups. Here are some solutions for speeding up the process.

D2D2T - Disk to Disk to Tape. Many of our clients use this solution. In the event of a server failure (and not a disaster that destroys the server room), the last backup is local and can be restored from a local resource rather than pulling it over the Internet or having devices couriered to the site. These backups complete much more quickly since internal connections (LAN, USB 2.0 ESata, Firewire) are faster than the Internet connection. Meanwhile, the remote backup can be pulled over the Internet for redundancy. 

Bare Metal Restores. When a server fails, getting the server back up and running is time consuming before the restore can even start. It might take 4 to 6 hours to install Windows and its service packs, install applications (Exchange, SQL), then install the backup agents and start the restore. This type of "rebuild" always has long time delays finding the software media as well as configuring the machine (drives, install paths, data paths). With bare metal restore capabilities you typically can boot to a CD and begin restoring the machine much quicker.

diary top frame