Why does EMC World bring a smile to my face?

EMC World – Those words bring a smile to my face.  It gives me, and hundreds of others like me at EMC, the opportunity to meet with customers.   We cherish the opportunity to get out and meet with customers.  I know that I often work on projects for weeks, even months and never get the opportunity to get live feedback from customers.  Sure we get feedback second hand from sales or even technical engineers but there is nothing like the unfiltered feedback directly from a customer.


So, it is without hesitation, that I ask that you stop by Booth 850, take a look at the many technical solutions for Microsoft applications we have developed over the past few months and give us your candid feedback!  We welcome it.


We have solutions to help you find new power in System Center; we show you how to increase performance of SQL server; we help you regain control of your Exchange environment; we show you can easily manage and control storage infrastructure using the PowerShell toolkit; we show you how to save days deploying SharePoint  and so  many more.

How Partners are Deploying EMC VSPEX Solutions for Microsoft

What's blue, has six wheels and delivers highly available virtual Microsoft workloads? That would be the Avnet Mobile Data Center Solution for EMC VSPEX voted one of the Top 10 Hot Products from EMC World according to CRN!


What makes the new mobile data center solution a top 10 product?  It is pre-configured as a fully functional compute, network and storage solution allowing customers to have a virtual private cloud up and running in no time.  It includes high-availability and disaster recovery so applications remain always available.  It can be used as a long-term private cloud solution, as a temporary data center in the event of a disaster or to assist in a data center move.


To read more, continue to the Virtual Winfrastructure blog site..

How EMC IT Uses Microsoft – Part 1 – Evaluating Office 365

I recently had the opportunity to speak with Wissam Halabi, an EMC Distinguished Engineer from the EMC IT Office of Architecture and Innovation. Wissam is a Microsoft expert as well as an architect in charge of designing EMC’s IT environment for Microsoft. I was curious to find out more about how EMC uses Microsoft for internal IT purposes and found our discussion quite interesting.


I learned that EMC uses SQL Server for various database purposes. SharePoint is deployed in an innovative internal as-a-Service offering – an interesting story for another day, EMC is deploying System Center Operations Manager (SCOM) for monitoring purposes and that we use Lync for instant messaging in conjunction with Exchange for email.  It turns out EMC has been a long time user of Exchange and the footprint has grown dramatically.


Around the 2004 timeframe, EMC had about 27,000 mail boxes deployed on 168 mailbox servers across 10 sites. As EMC grew from 2004 to 2009, EMC IT implemented a global messaging infrastructure that consolidated worldwide exchange servers to two managed data centers with over 50,000 mailboxes on Exchange 2003 supporting 400 offices in 80 countries. Keeping pace with growing storage demand was a major problem at the time. IT initiated an archiving project to reduce storage requirements and to come into compliance with new EMC governance policies. The archiving part of the story is fascinating but that too will have to wait for a future post. Overall the global messaging infrastructure project led to cost saving estimated at $20M, largely due to storage tiering and centralized management.


EMC continued its growth and the requirements for Exchange were even more demanding. From 2009 – 2011, EMC upgraded to Exchange 2007 with 64,000 mailboxes in an environment EMC IT specified to provide 99.99% uptime and zero data loss. The infrastructure would be 100% virtualized with 100% disaster recovery in place. It would also accommodate the surge in mobile devices and requiring support for 25% of the user population now using BlackBerry devices to access email.


Given the growth and demands of email on EMC IT and thinking about EMC moving to Exchange 2010, our use of SharePoint, coupled with EMC’s push to cloud computing, I was curious to discuss the pros and cons of Office 365 and whether a company like EMC might consider Office 365 as an option.  My expectation from Wissam was a polite decline. A company with a sophisticated IT team like EMC would not consider such an option. To my surprise, Wissam pulled up presentations with supporting spreadsheets to show me that EMC had in fact extensively investigated the feasibility of a move to Office 365.


Wissam compared 5 different cloud options ranging from a full Microsoft 365 option to a CSC or similar hosted option and finally a full EMC private cloud, on premises option. What he discovered is that from a pure cost standpoint, even based on preferential pricing from Microsoft, EMC started to save money with a full EMC private cloud, on premises implementation at about 6,000-7,000 users, well short of the now 80,000 required. A couple of other limitations are that Microsoft provides a 3-9’s SLA as part of Office 365 yet EMC requires 4-9’s and the penalty to Microsoft for missing an SLA is minimal.


As we wrapped up our chat, he shared with me an architectural diagram of the current configuration, see below. The picture underlines a couple of the guiding principles of EMC IT today, simplify and automate. Today, all new infrastructures deployed by EMC IT uses VBLOCK platforms from VCE. This greatly simplifies life for IT through a single point of contact for support of the total platform as well as automating many traditional IT tasks and gives Wissam the freedom to think up more ways to innovate.


If you are EMC World, be sure to visit Microsoft kiosk at booth 1035. Also see the presentation on Wednesday, May 8 at 4pm in the Palazzo M, 'Optimize Business Application Performance & Protection with EMC Solutions for Microsoft, Oracle, SAP and VMware.


EMC IT Exchange Deployment.jpg.png

Whats in your SLA?

People have been considering and comparing public (hosted) and private (on-premises) cloud solutions for some time in the messaging world, and at increasing rates for database and other application workloads.  I’m often surprised at how many people either don’t know the contents and implication of their service provider service level agreement (SLA), or fail to adjust the architecture of private cloud solution and then directly compare cost. 

Here are my five lessons for evaluating SAAS, PAAS, and IAAS provider SLAs:

Lesson 1: Make sure that what’s important to you is covered in the SLA

Lesson 2: Make sure that the availability guarantee is what you require of the service

Lesson 3: Evaluate the gap between a service outage’s cost to business and the financial relief from the provider

Lesson 4: Architect public and private clouds to the similar levels of availability for cost estimate purposes

Lesson 5: Layer availability features onto private clouds for business requirement purposes

I’ll use the Office 365 SLA to explore this topic – not because I want to pick on Microsoft,  but because it’s a very typical SLA, and one of the services it offers (email) is so universal that it’s easy to translate the SLA’s components into the business value that you’re purchasing from them.

Defining availability

The math is simple.  It’s a 99% uptime guarantee with a periodicity of one month:


If that number falls below 99, then they have not met their guarantee.  For what it’s worth, during a 30 day month, the limit will be about 44 minutes of downtime before they enter the penalty, or about 8.7 hours per year.

But what does “Downtime” mean?  Well, it’s stated clearly for each service.  This is the definition of downtime for Exchange Online:

“Any period of time when end users are unable to send or receive email with Outlook Web Access.”

Here’s what’s missing:

  • Data:  The mailbox can be completely empty of email the user has previously sent and received.  In fact the email can disappear as soon as they receive it.  As long they can log in via OWA, the service is considered to be “up”.
  • Clients:  Fat outlook, blackberry, and Exchange ActiveSync (iPhone/iPad/Winmopho, and most Android) clients are not covered in any way under the SLA

Lesson 1: Make sure that what’s important to you is covered in the SLA

Lesson 2: Make sure that the availability guarantee is what you require of the service

Balancing SLA penalties with business impact

My Internet service is important to me.  When it’s down, I lose more productivity than the $1/day or so I spend on it.  Likewise, email services are probably worth more than the $8/month/user or so that you might pay your provider for it.  That doesn’t mean that you should spend more than you need for email services.  But it does mean that if you do suffer an extended or widespread outage, there will likely be a large gap between the productivity cost of the downtime and the financial relief you’ll see in the form of free services you’ll see from the provider. 


Callahan Auto Parts also offers a guarantee

I’ll put this in real numbers.  Let’s say I have a 200 person organization.  I might pay $1600/month for email services from a provider.  If my email is down for a day during the month, my organization experiences 96% uptime for that month, and as a result, my organization is entitled to a month of free email from the provider, worth about $800.


The actual cost of my downtime will very likely exceed $800.  To calculate that cost we need the number of employees, the loaded cost per hour for the average employee, and and the productivity cost of the loss of email services.  For our example of 200 employees, let’s imagine a $50/hour average loaded cost to business and a 25% loss of productivity when email is down:

200 employees x $50 cost per hour x .75 productivity rate x 8 hour outage = $60,000 of lost productivity

Subtract the $800 in free services the organization will receive the next month, and the organization’s liability is $59,200 for that outage.

Now how do you fill that gap?  I’m not entirely sure.  It could be just the risk of doing business – after all, the business would just absorb that cost if they were hosting email internally and suffered an outage.  If the risk and impact were large enough, I would probably seek to hedge against it – exploring options to bring services in house quickly, or even looking to an insurance company to defray the cost of outages – if Merv Hughes can insure his mustache for $370,000, then surely you can insure the availability of your IT services.  Regardless, it’s wise not to confuse a “financially backed guarantee” with actual insurance or assurance against outage.

File Photo:  What a $370k mustache may look like.  Strong.

Lesson 3: Evaluate the gap between a service outage’s cost to business and the financial relief from the provider

Comparing Apples to Oranges


See what I did there?

Doing a cost comparison between public cloud designed to deliver 99.9% availability and a private cloud designed to provide 99.99% or 99.999% availability makes little sense, but I see people do it very frequently.  Usually it’s because the internal IT group’s mandate is to “make it as highly available as possible within the budget”.  So I’ll see a private cloud solution with redundancy at every level, capabilities to quickly recover from logical corruption, and automated failover between sites in the event of a regional failure, compared to a public cloud solution that provides nothing but a slim guarantee of 99.9% availability.  In this instance, it’s obvious why the public cloud provider is less expensive, even without factoring in efficiencies of scale.

To illustrate this, I usually refer to Maslow’s hand-dandy Hierarchy of Needs, customized for IT high availability.

image image

Single Site and Multi-site Hierarchies of Need

If I want to make an accurate comparison between a public cloud provider’s service and pricing and what I can do internally, I often have to strip out a lot of the services that are normally delivered internally.  Here’s the steps:

  1. Architect for equivalence.  If I have a public cloud provider just offering 3 9’s and no option for site to site failover, for my database services, I might just do a standalone database server.  Maybe I’d add a cheap rapid recovery solution (like snapshots or clones) to hedge against compete storage failure and cluster at the hypervisor layer to provide some level of hardware redundancy.  If my cloud provider offers disaster recovery, I’d figure out what their target RPO/RTO and insert some solution that matches that capability.
  2. Do a baseline price comparison.  Once I’ve got similar solutions to compare, I can compare price.  We’ll call this the price of entry.
  3. Add capabilities to the private cloud solution after the baseline.  I only start layering features that add availability and flexibility to the solution after I’ve obtained my baseline price.  Only then can I illustrate the true cost of those features, and compare them to the business benefits.

Lesson 4: Architect public and private clouds to the same levels of availability for cost estimate purposes

Lesson 5: Layer availability features onto private clouds for business requirement purposes