Posts Tagged ‘Datacenter’

Bad Locations for a Datacenter

Wednesday, September 1st, 2010

Because I am a native of Philadelphia, I am very familar with the area and the history of certain commercial development areas. A few months ago, an outside firm started a Data Center Facility in the old Philadelphia Navy Yard. This is the worst place in Philadelphia to build a telecom facility. Since 1998, many local telecom companies have all looked at and passed on the Navy Yard. Why? For starters there is ZERO fiber optic access there. There aren’t even aerial poles. The copper service that does exists from the local LEC (Verizon) is underground and is heavily corrided due to flooding. Oh, yes, flooding, theres that too!

The new firm most likely took on a heavy expense of demarcing fiber into the building through the Navy Yard grounds. So they effectively have a single fiber entrance. Agauin, not ideal. Not very carrier diverse either since all the carriers will be on the same fiber trunks in the same conduit. And loop service access (DS-1 and DS-3 cross connects for MPLS) will be terrible.

Its a shame they didn’t reach out to local telecom experts, since the overwhelming concensus would have been to stay away from the Navy Yard. There are 3 solid carrier hotel buildings in Philly, all of which have diverse power, multiple diverse fiber entrance, and the list goes on. The Navy Yard was probably picked by this firm because off the low operating cost and tax incentives, but at the end of the day, not being in a true carrier diverse building will hurt over time.

The Myth about Mid-West Datacenters

Friday, March 19th, 2010

Some articles have been written recently about where the best location for running and building a datacenter is. These reports always pick mid-western states as the ideal locations due to cost. South Dakota or Kansas is a great place to build a cheap datacenter if cost is the number one concern. Labor is cheap, material costs are low, electricity prices are low. But these reports always leave out something that is very important. PEOPLE.

Datacenter operations will always be central to locations with population density. East Coast corridor, Texas, California, and so on. The surrounding population will support the service. Who needs colocation or datacenter services in South Dakota? The only people who can benefit from this are those who do not need to touch their equipment or Fortune 500 firms who can afford to fly out their technicians to a remote site. What people don’t realize is most operations that use significant colocation resources (10U and up) need to touch their equipment on a regular basis. They can’t ship it off 1000 miles into the mid-west.

Furthermore, the reduced electricity costs (which is the most significant operational cost of a datacenter) is only temporary. In a few years electricity prices will start to even out. Its sort of an anomaly that is Nebraska you can get electricity at $0.03 per Kwh – that wont last long. Mid-west locations also do not have the immense diversified telecom and fiber infrastructure that is present in major cities. Besides, content users are located in the major cities – content providers and users should be close to each other.

Authorize.net Outage and Fisher Plaza Fire – Lessons Learned

Wednesday, July 8th, 2009

I love when somebody else has a disaster. It serves as a great example of how not to do things, and furthermore, it debunks the myth that big providers are always better then smaller regional providers.

On July 1st, 2009 there was an electrical fire at a datacenter in Seattle, WA operated by Fisher Communications. The electrical fire took out the incoming power feeds, and the generators were not allowed to run because they were too close to the fire. End result, the entire facility was dark for quite some time. This facility was also the home of Authorize.Net and their primary credit card processing portal. As a result Authorize.Net transactions were significantly hampered for almost 3 days.

Why did Authorize.Net’s DR fail?

Simple. People. Authorize.net has a full DR site in San Jose, CA but it took 3 days to migrate and get back online. Why? Well, according to their official announcement they blamed it on the coincidence of many factors and what they called the perfect storm. The problems happened over the July 4th holiday week and weekend, so none of their engineers were around, and the few that were around on-call were not skilled enough to handle the event. Clearly, their DR plan existed in paper form only. You dont get exemptions or a pass because it was a holiday.

Lets not let Fisher of the hook…

I am amazed when I hear about electrical fires in datacenters. For starters, if you have a properly designed FM200 or Halon system, the fire should be killed in minutes. The fact that the fire department had to come out and help put out the fire only hammers home the internal issues of fire control systems. Its ironic too, just last week I wrote an article about why its important to be in a datacenter that follows 80% electrical rating limits. If you recall, the key problem of going above 80% usage is an increased risk of… you guessed it…. electrical fires. I would not be surprised if Fisher was pushing 90% load through their core load panels. And the lack of transparency is a joke. A week after the fire, and there is no posted press release on their website. The only reason why I know about it is because we use Authorize.net for credit card processing, and we received official outage summaries. I’d hate to be a customer at a Fisher datacenter trying to get a credit for the outage.

Big business mentality, and the economy…

Its a known fact that I am very anti big business. I hate when people assume that they get better service and redundancy from a large telecommunications firm, as compared to a smaller regional firm. In many environments, the smaller firms have better track records of performace and better quality control. Its simple. Its easier to manage a small environment than a big environment. Big companies are also more directly effected by economic issues. Some large telecomms run in the red for years, and never turn a profit. This stress causes everyone to pass the buck, cut on quality staffing, cut on preventive maintenance contracts, or turn a blind eye and let the blame fall elsewhere.

At Quonix, a small group of dedicated professionals maintain operations. Nobody can slack off and pass the buck. It doesn’t hurt that we’re profitable too!