10 things to look for in a data center

By Erik Eckel

Takeaway: Going to the cloud might make a lot of sense for your organization — but only if you choose a secure, reliable data center that can handle your needs. Erik Eckel runs through 10 essential criteria for data center evaluation.

Everyone's going to the cloud. The cloud's all the rage. Almost no IT discussion is complete without mentioning "the cloud." But when it comes down to it, the cloud is nothing more than systems hosting information in a data center somewhere "out there."

Organizations have discovered the benefits of offloading infrastructure development, automatic failover engineering, and multiple coordinated power feeds, not to mention backups, OS maintenance, and physical security, to third-party data centers. That's why "going to the cloud" ultimately makes sense.

Unfortunately, not every data center is ready for prime time. Some have sprung up as part of a cloud-based land grab. Review these 10 factors to ensure that your organization's data center is up to the task.

Note: This article is also available as a PDF download.

1: Data capacity

Data centers are typically engineered to support mind-boggling data transmission capacities. Some feature multiple OCx and SONET connections that can manage Amazon.com-like Web site demands. Other less sophisticated entities might try getting by using redundant T-3s. Don't find out the hard way that your data center provider failed to adequately forecast capacity and can't quickly scale.

2: Redundant power

Many data centers have online electrical backups. UPSes, in other words. If your organization maintains business-critical systems that simply can't go down, be sure that the data center has a second electrical backbone connection. Only N+1 power grid connectivity, to a secondary electrical source, can help protect against catastrophe.

3: Backup Internet

Just as any quality data center will maintain redundant power sources, so too must it maintain secondary and tertiary Internet connectivity. Buried cables get cut. Overhead cables fall when trucks strike poles. Vendors experience network-wide outages. Only by making sure that multiple tier-1 Internet provider circuits feed a facility via fully meshed backbones can IT managers rest assured they've done what they can to eliminate potential downtime.

4: Automatic hardware failover

Redundant power, Internet, and even heating and cooling systems are great, but if they're not configured as hot online spares, downtime can still occur. It's critical that data centers employ redundant online switches, routers, UPSes, and HVAC equipment that automatically fail over when trouble arises.

5: Access control

The importance of physical security can't be understated. Commerce could be significantly affected if just one unstable individual were able to drive a large vehicle into a busy and sensitive data center. That's why it's important that a data center's physical perimeter be properly protected. In addition to physical access controls (keys, scanner cards, biometric devices, etc.), care must be taken to ensure that, should someone gain access to a data center, individually leased sections remain secure (thanks to additional physical access controls, locks, cages, rooms, etc.).

6: 24×7x365 support

Data centers must be staffed and monitored by properly trained technicians and engineers at all times. It's an unfortunate byproduct of today's pressurized business environment but a fact nevertheless. Systems can't fail. Constant monitoring and maintenance is a must. Certainly, many data centers will run leaner shifts during off hours, but telephone support and onsite assistance must be always available. Further, data center services must include customer reporting tools that assist clients in understanding a center's network status.

7: Independent power

Data centers must have redundant electrical grid connections. That's a given. And facilities must also maintain their own independent power supply. Most turn to onsite diesel generators, which need to be periodically tested to ensure that they can fulfill a data center's electrical requirements in case of a natural disaster or episode that disrupts the site's other electrical sources.

8: In-house break/fix service

One of the benefits of delegating services to the cloud is eliminating the need to maintain physical and virtualized servers. OS maintenance, security patching, and hardware support all become the responsibility of the data center. Even if an organization chooses to co-locate its own servers within a data center, the data center should provide in-house staff capable of maintaining software and responding to hardware crises.

9: Written SLAs

Any data center contract should come complete with a specifically worded service level agreement (SLA). The SLA should guarantee specific uptime, service response, bandwidth, and physical access protections, among other elements. Ensure, too, that the SLA or terms of service state what happens if a data center fails to provide uptime as stated, maintenance or service as scheduled, or crisis response within stated timeframes.

10: Financial stability

All the promises in the world, and even an incredibly compelling price, mean nothing if the data center fails. Before moving large amounts of data and equipment into a facility, do some homework on the company that owns the site. Confirm that it's free and clear of lawsuits, has adequate operating capital, and isn't in financial straits. The last thing you want to do is have to repeat the process because a center fails financially or must cut costs (and subsequently service and capacity) to stay afloat.

10 things network administrators need to know about Windows Phone 7

By Brien Posey

Takeaway: If your organization is planning its mobile device strategy and Windows Phone 7 is an option, you'll want to take these factors into account.

Microsoft has spent a fortune on marketing Windows Phone 7, but there are some areas in which the system just doesn't measure up. In all fairness, Microsoft redesigned the Windows Mobile operating system from scratch, so this could be considered a 1.0 release — and like any 1.0 release, there is bound to be room for improvement. In addition, a number of features that previously existed in Windows Mobile 6.x have been removed. All of this adds up to some headaches for admins. This list outlines what you need to know before adopting Windows Phone 7.

Note: This article is also available as a PDF download.

1: The interface takes a little getting used to

Windows Phone 7 uses a new interface that is completely different from anything Microsoft has ever created before. This new interface requires you to use several touch gestures and can take a bit of getting used to. While some areas of the interface are completely intuitive, others may leave you scratching your head.

2: Some of the hardware is optional

Although Microsoft made phone manufacturers adhere to a strict set of hardware requirements, some components are optional. In other words, the Windows Phone 7 OS will support these components, but the manufacturers are not obligated to include them in the phone. Some of the optional hardware components include:

• Wi-Fi (802.11g and 802.11n)
• Bluetooth
• Expandable storage
• A hardware keyboard

3: Some ActiveSync policy settings are missing

Unlike Windows Mobile 6.1, Windows Phone 7 supports only some of the ActiveSync policy settings that are offered by Exchange Server. These Exchange ActiveSync (EAS) policies include:

• Password Required (applicable only to Exchange 2003 SP2)
• Minimum Password Length
• Idle Timeout Frequency Value
• Device Wipe Threshold
• Allow Simple Password
• Password Expiration
• Password History

There are a few other EAS policy settings that are technically enabled, but that will always return a value of True. These include:

• Disable Removable Storage
• Disable IrDA
• Disable Desktop Sync
• Block Remote Desktop
• Block Internet Sharing

All other EAS policy settings always return a value of False.

4: Managing certificates is more difficult

Windows Mobile 6.x had a built-in applet for managing certificates. Microsoft has done away with this applet in Windows Phone 7. Windows Phone 7 devices have built- in trusts for well-known commercial certificate authorities, but there is no interface for managing certificates that were issued by an in-house enterprise certificate authority.

In spite of the fact that the Certificates applet is gone, all is not lost. I have found that you can install a certificate by emailing it to yourself and then opening the attached certificate through the phone. When you do, the mobile operating system will install the certificate.

5: There's no access to the file system

For as long as I can remember, Windows Mobile operating systems have included an applet called File Explorer that allows you to navigate the device's file system. This applet has been removed from Windows Mobile 7, and the underlying file system is no longer directly exposed. Unfortunately, it seems that navigating the device's file system through a PC when the device is connected to a USB port is not an option either.

6: The initial build is incomplete

Less than a month after the Windows Phone 7 launch, Microsoft announced that an update would soon add copy and paste functionality to Windows Phone 7. Since that time, there have been rumors that a much larger update is on the horizon that may add support for HTML 5 and app multitasking.

7: It won't work with all mobile networks

I have used Sprint as a cellular carrier since the mid-90s, and my last several phones have had Windows Mobile operating systems. Imagine my shock and disappointment when I learned that the only carriers in the United States that support Windows Phone 7 are AT&T and T-Mobile. It is worth noting, however, that there are rumors circulating about an upcoming CDMA version of Windows Phone 7 that will work on Sprint and Verizon networks. In fact, I recently discovered a Web site that allegedly shows a picture of a soon-to-be-released HTC device from Sprint running Windows Phone 7.

8: It's really a consumer device

When you read about the missing ActiveSync policies, you might have wondered why so many policy settings aren't supported by Microsoft's latest mobile operating system. Microsoft's official answer to this question is that Windows Phone 7 was developed primarily as a consumer device, not an enterprise device. However, Microsoft hints that more enterprise features may show up in future phone updates.

9: Cell providers can block updates

Many of the smartphones on the market can technically be updated, but many of the mobile carriers have a history of taking measures to block updates. After all, it is in a mobile carrier's best interest to sell you a new phone, not to extend the life of your existing phone.

When Windows Phone 7 was introduced, Microsoft decided to follow in Apple's footsteps and provide updates to the phone. However, it has recently been revealed that mobile carriers will have the right to block Microsoft updates for their customers, at least for a while. Microsoft's corporate vice president and director of Windows Phone Program Management, Joe Belifore, was recently quoted as saying, "We build updates for all Windows Phone users but must certify them with the carriers. They'll happen on a regular cadence like they do on the PC. If a carrier wants to stop an update, they can. But they will get it out on the next release."

10: The emulator is broken

In recent years, Microsoft has provided an emulator as a part of the Software Development Kit for Windows Mobile. In the case of Windows Mobile 5 and 6.x, the emulator was an exact replica of a physical Windows Mobile device.

Although Microsoft has released an emulator for Windows Phone 7, it has locked the emulator so that most of the operating system's features are hidden. Almost immediately, someone hacked the emulator and released a patch that will unlock it. Even so, some areas of the emulator are still inaccessible. For example, the options to set up email accounts and social networking accounts do not seem to do anything.

10 ways to explain things more effectively

Author: Calvin Sun

n the course of your work, you may sometimes need to explain technical concepts to your customers. Having them understand you is important not only for technical reasons, but also to ensure customer satisfaction. The ability to explain things clearly and effectively can help you in your career, as well. Here are a few tips to help make your explanations understandable and useful.


#1: Keep in mind others' point of view

You've probably seen the famous illusion that looks like either a young woman or an old woman. Two people can look at that same picture, and they can have opposite views of what they're seeing. Keep this idea in mind when explaining a concept. Something that might be perfectly understandable to you might be incomprehensible to someone else. Don't be the person customers complain about as using "geek speak."
#2: Listen and respond to questions

It's easy to become annoyed when someone is asking questions. However, try to resist that reaction. A better attitude is to be happy that the other person is interested enough to ask questions. To minimize confusion and misunderstanding, try to paraphrase or summarize a question before you answer it. This step is particularly important if you're in a group setting, and you've just taken a question from someone in the audience. Repeating the question for the entire group helps everyone better understand your answer.
#3: Avoid talking over people's head

When you explain things to people, do their eyes glaze over? Chances are it's because you're talking over their head. Symptoms of such behavior include the use of jargon and acronyms. Remember, the people you're talking to probably lack your specialized knowledge, so you should use readily understandable terms.

The same goes for acronyms. They're important, but if you use them, define them in "longhand," followed by the acronyms in (parentheses), so that everyone's clear. Doing so avoids the scenario of situation normal, all fouled up (SNAFU).

Even within IT, the same acronym can mean different things. For example, both "active server page" and "application service provider" have the acronym ASP. A story from the Vietnam War era further illustrates this point. A young woman brought her boyfriend home to meet her father, a retired military officer. The woman was nervous because the boyfriend was a conscientious objector. When the father asked the young man to talk about himself, the latter replied, nervously, that he was a CO. The father clapped the young man on the back and congratulated him, thinking the latter was a commanding officer.
#4: Avoid talking down to people

Avoid the other extreme as well. Don't insult people by assuming that they're only as intelligent as a three-year-old. An attendee at one of my communications training classes described it aptly as "Barney communications."

Greek mythology has references to two monsters, Scylla and Charybdis, who sat on opposite sides of a narrow strait of water. If a ship sailed too close to Scylla, it was destroyed and the sailors eaten up. If the ship sailed too close to Charybdis, it was destroyed by a whirlpool that Charybdis created. The ship had to go right between them to survive. Follow that same principle with your customers: Make your explanations neither too complicated or too simple.
#5: Ask questions to determine people's understanding

The people you're talking to shouldn't be the only ones asking questions. You should be asking questions as well, to make sure they understand. Your questions can be open ended, which gives people a chance to provide detailed information, or they can be closed ended, which generally calls for a simple yes/no response. In either case, asking questions tells people that you're interested that they understand.
#6: Focus on benefits, not features

What's the difference? A feature is some inherent property of an object. A benefit, on the other hand, is a way the feature helps a person. For example, one of the features of a Styrofoam cup, because of the material used, is insulation. Someone who's planning a party probably doesn't care how the cup provides insulation. That person is more interested in the fact that such a cup keeps hot things hot and cold things cold.

In the same way, try to focus on benefits of technology rather than features of technology. This distinction becomes more important the higher the level of the person you're talking to. The CFO probably has little need to know about the specific commands and steps involved in setting up database mirroring. That person will want to know, however, that such a practice reduces the chances of data loss.
#7: Use analogies to make concepts clearer

An analogy involves explaining an unfamiliar concept in terms of a familiar one. For example, in drawing an analogy between a firewall and a bank teller, you could say that people don't just go directly into a bank and take money out. They go to the teller and identify themselves; the teller makes sure they have enough money; and then the teller gives them the money. Similarly, a firewall ensures that people who want access to a system really are permitted to have that access.

When choosing an example for an analogy, first figure out the general principle you're trying to explain. Then, choose something from real life that illustrates that principle. Say, for example, that you're trying to explain memory leaks. Suppose you conclude that the principle involved is that of taking without giving back completely. An example/analogy might be the consequences of pouring a cup of pancake batter into successive measuring cups, or the consequences of lending money to your brother-in-law.
#8: Compare new concepts to familiar ones

Another illustrative technique is to use a familiar or existing product as a comparison. If you're explaining a new release of a software product, the comparison is easy. Simply discuss the additional capabilities it has over the previous one or how key features are different. If the person hearing your explanation is also an IT person and is familiar with different or older technology, try explaining in those terms if you can. For example, when explaining thin clients, consider a comparison to the old 3270-type terminals that IBM once used for connection to mainframes.
#9: Use the concepts of subsets and supersets

Brooklyn is a subset of New York City, because all of it is a part of that city. Conversely, New York City is a superset of Brooklyn, because the former contains, in addition to all of the latter, other boroughs as well. These concepts are helpful in describing, for example, a "lite" versus a "professional" version of a software product. If the latter does everything the former does, plus more, it truly is a superset of the former, and the former is a subset of the latter. Be careful, though: If the "lite" version does even one thing that's missing from the professional version, there's no longer a subset/superset relationship.
#10: Confirm that your explanation makes sense

Once you've finished explaining your point or answering a question, ask a final question yourself. Make sure the people who heard your explanation truly did understand it. Consider asking them to give you the explanation in their own words, just to double-check.