All posts in Channel

AND THEN THERE WERE 3……

……Your Mimecast fighter shortlist is announced, but who will be our Rocky Balboa?

First, came the Mimecast assessment day. Then, came Judgement Day. Nine brave Mimecasters sweated blood and tears in training, and then sweated some more waiting for the results of the vote.

But then the waiting was over, and nine became three as you sorted the wheat from the chaff with your votes.

The Mimecast fighter shortlist, in no particular order, was announced as:

These are the names that could strike fear into the hearts of other fighters daring to enter the fight night looking to come out unscathed. But who will be ‘the one’ to represent Mimecast on the night?

Following the results of the vote, your Mimecast Musketeers travelled to the other side of the capital to attend the CRN Assessment evening to determine who would be the chosen one. With that embedded in their minds, the Mimecast warriors donned their vests and boxing gloves one more time. The only difference this time was that they were sussing out the competition from other vendors, resellers and distributors, while trying to impress the Fight Night representatives who could eventually choose them and their….gulp….opponent.

With the dilemma of whether to play down their ability or not, the fearless trio set about a punch bag deciding to give it everything they had. Hundreds of press ups and sit ups later, the Mimecast hopefuls were wondering if they’d made the right decision to compete after all!

So, what about the competition?

“A mixed bag” was the answer from the CRN Fight Night Representative. “The Mimecast lads were definitely on the better side of things”. Even Trevor :)

I came to the same conclusion; whoever the ’chosen one’ is matched up against, it will inevitably be a brilliant fight. Both males and females looked very tough with one girl even representing Britain, which made certain legs quiver: “She could definitely knock me out” whimpered Rich “Scrappy Doo” Dean.

So there you have it; stage 2 of a lactic filled journey is complete. All we can do now is wait for CRN to announce the Mimecast fighter……. and that is when the hard work really begins!

 

Add your comment (0)

Cloud Strategist
Mimecast

First Taste of Fear

Valiant Mimecasters get brutal insight into training regime for CRN Fight Night – but the fighter is yet to be decided!

Drum roll……“The challenge has been set.  Nine brave Mimecasters volunteered, but only one gets the call. Two hours of relentless training and possible humiliation stand in their way. The prize? The chance to represent Mimecast at the Channel ‘Event of the Year.’”

From this dramatic intro, you could be forgiven for assuming that you were watching a trailer for the latest Jason Statham movie, but no. Jack ‘won’t be beaten’ Blackmore ruined that image by donning a ‘Next for Men’ t-shirt, complimented perfectly by a pair of Steve McKenzie’s surfer shorts.

Unfortunately only five of the original nine warriors showed up to the first hurdle: the training session. Greg “The Wizard” Collins was suffering from a 25 day sickness bug, while Jason “People’s Champ” Kennett, Nick “The Southern Dandy” Moss and Trev “The Hitman” Highley were unable to attend due to unforeseen circumstances.  But fear not, they are looking to come back strong at the next session.

One by one, the brave warriors strolled into a tension-filled gym.  Expectation was low but morale was sky high. Will ‘’I AM’’ Lowden confirms his brawn-over-brain reputation by struggling to remove his mouth guard from the hot water. Not a great start!

Technical ability training was the first order of the day. Gary, a personal trainer at Urban Kings, was the man entrusted to put these Mimecasters through their paces. With hand wraps securely fastened and dignity still in place, they began unleashing their finest jabs, mixed with a few ducks and bounces.  Jason ’Reggie’’ Miller looked unsure of his lefts and rights but Richard ‘’Scrappy Doo’’ Dean brought a chill to the air with his earth shattering jabs.  At the end of the technical session, Gary’s conclusion was that: “David (The Doctor) has a great left hook, and his concentration is second to none.”

With the gym starting to empty due to the post-apocalyptic odour, the Chris Eubank wannabees moved onto their final challenge:  fitness. John, a fitness coach at Urban Kings, unleashed a relentless routine of squats and lifts with a 15kg weight. This was all that stood between the fighters and the first interlude of this epic journey.  After 10 minutes, Jason ‘‘Reggie’’ Miller bowed out while the others fought on, determined not to let anyone have the psychological edge.

By now, thoroughly exhausted, the boys ended with some one-on-one practice with Will ‘’I AM’’ Lowden and Jack ‘’won’t be beaten’’ Blackmore doing more burping than punching. Amidst the screams of “Harder! Harder!” they were trying to slog the hell out of each other while at the same time noticing they had made a smiley face on the canvas with their sweat. Nice.

Urban Kings experts, Gary and John, were pleased with the overall performances and had this to say for the Mimecast heroes: “All of them have a good level of fitness but in terms of having the mental attitude and discipline to train and fight; Dave [The Doctor] has the edge.”

So, Ladies and Gentlemen, there you have it. Experts and Bookmakers say Dave “The Doctor” Rodger…

…but on a warm evening in May, who do the people want to see dance under those bright lights? It is not too late to vote – visit: http://info.mimecast.com/FightNight_vote before 5th February 2012.

Add your comment (0)

Cloud Strategist
Mimecast

Following on from the previous post from our guest blogger Nic Blank on operational maturity and storage, I’d like to call out another area in operational maturity – Transporting and Routing Mail.

Exchange 2010′s transport High Availability model is rather simple – add more HUB servers, and they become redundant, shadow transport ensures mail delivery and so on.

However, this requires some planning. Shadow transport is a great feature; it really is. It allows the failure of a Hub Transport server without the loss of messages in transit. However; two caveats come to mind:

  1. You need more than one HUB Transport server in a given Active Directory site in order for Hub Transport servers to load balance mail traffic
  2. You need an Exchange Server on either side of the Hub Transport server – either an edge or another Hub transport server on either side OR a mail server as the originator or destination.

So where’s the issue? Nic defined Operational Maturity as the absence or presence of the technology and processes required in order to absorb and mitigate a failure in an acceptable time frame (normally the SLA).

He also made the point that Exchange is really good at absorbing failure if it’s built to do so. Hub Transport server supporting Shadow Transport is one of those features. In simple terms, if a failure of a Hub Transport server is detected, the messages which that Hub Transport server was responsible for are going to be re-assigned by the previous hop or message originator to another hub transport server in the same site.

If operational maturity is low, i.e. if an organization didn’t have sufficient reporting and remedial measures in place to determine that failures had occurred, under extreme circumstances, the Hub Transport server would keep on failing until mail flow fails altogether.

We can mitigate this in part by introducing message routing intelligence on the outside of the organization. However we need to make sure that are not exacerbating the problem by simply relieving a pain point and not addressing the cause.

Moving on, where do we start with operation maturity? We don’t have to start with a full blown SCOM implementation to ensure mail is flowing between two points. If you have nothing at all start with:

  • Simple mail testing tools that send mail between two mailboxes at nominated points in the org.
  • Free tools and or Scripts capable of pinging servers at regular intervals, checking for service availability, etc
  • More tools or scripts to monitor for disk availability and disk free space usage

Often starting somewhere with basic belts and braces is better than not doing anything, but it is quite critical to combine simple tools and simple processes into simple standards and thereby raise the operational maturity from zero.

Anything greater than zero is a short term win and will leave your organization with something to work on and improve.

Add your comment (0)

Enterprise Consultant
Mimecast

Guest Blogger Nicolas Blank is an Exchange MVP and Microsoft Infrastructure Architect specializing in Exchange, Active Directory, architecture, systems management, migration and scripting. Nicolas spends what spare time he has writing, blogging and talking about Exchange and associated technologies. His blog can be found at: http://itproafrica.com

..

In the past we’ve blogged about the use of SATA disks; one post was even cheekily entitled “Give your SAN to the SQL team“. That’s a great idea but how do we turn storage features into operational reality?

There’s no denying that Exchange 2010 offers more storage flexibility than any of its predecessors. Exchange can now deploy on Big, Fast and Expensive storage (AKA SANs), Disk Shelves, comprising RAID SAS, near line SAS or even JBOD Enterprise SATA disks.

Let us look at the last one of these, JBOD, or the use of individual disks to store Exchange databases.

In this configuration, an exchange sizing calculation determines the number of IOPS required per server – depending on user activity, divides it roughly into the known IOPS capability of the disk specified, and returns the number of disks required. Each disk then holds a unique database, which is then mirrored over the network to similar servers, with similar disks.

The first hurdle is simply the number of disks. When producing a Highly Available (HA) configuration, each database is mirrored to two or more servers. Medium to large configurations will require many more than 20 disks per server, which means: using mount points to compensate for the lack of available drives.

The next hurdle is standardizing the servers required in order to have identical enough storage and configurations across all servers, in order to create the HA configuration in the first place.

The next consideration is critical. . Assume your build processes are standardised, your servers, storage and HA configurations are identical and as clean as a whistle; How do you know when you’ve had a failure?

Exchange 2010 – assuming it’s been designed and built to do so – is really good at absorbing failures – disk, database, transport, client access, you name it. The downside is – how do you know if something’s failed OR you’re down to your last good copy after the other two or three databases failed?

The answer involves many co-dependent factors – monitoring software, monitoring personnel and operational procedure. There’s no point in deploying SCOM which predicts disk failure, alerts on the disk failure, reports on the reduced SLA, if no-one is consuming the data and actioning appropriately.

For the purposes of this article then, we can define Operational Maturity as the absence or presence of the technology and processes required in order to absorb and mitigate a failure in an acceptable time frame (normally the SLA).

Don’t think that this pain is a JBOD pain only. JBOD lessens the storage cost, but reduces SOME of the storage management which the SAN team may absorb and the Exchange administrator may be insulated from.

Irrespective of the storage model used, the combination of monitoring, processes, plans, documentation and activities define the operational maturity of an IT organisation. Due to the criticality of mail, Exchange has massive visibility in the average business, especially during an outage.

While cheap storage is a valid option for Exchange, it may not be a great option for IT shops that are relatively new to the concepts mentioned in this post. Just from a storage point of view, a more traditional RAID storage shelf with lower IOPS may be a better consideration.

Add your comment (0)

Enterprise Consultant
Mimecast

Article Tags

,

New Flexible deployment and migration options with Exchange 2010 Service Pack 2

On Tuesday the Exchange team announced the impending release of Exchange 2010 Service Pack 2 and gave us all a sneak peek into what is being included in this pack.

As with Service Pack 1, it doesn’t disappoint and the list of goodness will make many users of Microsoft’s messaging platform very happy.

For me however, the most exciting bit of news is that the “Hybrid Configuration Wizard” is to be included.

Hybrid Configuration Wizard: Organizations can choose to deploy a hybrid scenario where some mailboxes are on-premises and some are in Exchange Online with Microsoft Office365. Hybrid deployments may be needed for migrations taking place over weeks, months or indefinite timeframes. This wizard helps simplify the configuration of Exchange sharing features, like: calendar and free/busy sharing, secure mail flow, mailbox moves, as well as online archive.

The ability to co-exist with other versions of Microsoft Exchange has always been incredibly important for customers who have to upgrade. This is especially true for so many customers that like to skip releases in order to maximize their investment in a particular version who then end up not being able to perform a direct migration to the latest version!

The Exchange Server Deployment Assistant has already been around for some time, providing customers with valuable information on what they have to do in order to migrate to new configurations and has included advice on how to set up co-existence between Office365 and earlier versions of Exchange.

This is an example image from the Exchange Server Deployment Assistent when selecting cloud and on-premises co-existence

This is brilliant news for Exchange Administrators looking at all the available options for deployment. It lays out clearly the options and in detail what needs to be done to achieve each of the architectural options available. Unfortunately- there’s no such thing as a free lunch, so there’s still plenty of configuration work to be done, but there could be some valuable upside in mixing Cloud and on Premise to produce Hybrid deployments. One scenario in particular I really like is the kiosk workers- previously they didn’t have corporate email and with Office365 they can have email from $2.00 per month.

We think it’s really important that IT can finally start making informed decisions on moving users to the cloud in careful controlled ways, that make sense to them and utilise the skills and experience they have. We’re helping our customers do this with our intelligent gateway services to swing selected users from one system to another without any impact on other users. This means that they can truly test the Cloud and assess all the softer things like network impact of running users in the cloud, latency and, most importantly, user experience before going “all in”.

This new wizard will hopefully go a long way to simplify the process of setting up co-existence and could well be the tool that causes organizations to dare to dip their toes in the water of Microsoft’s Office365 solution.

I can’t wait to see how much this Wizard manages to accomplish as it is about time it wasn’t only Mimecast advocating organizational flexibility.

Add your comment (2)

Enterprise Consultant
Mimecast

Article Tags

,

In Part 1 of this series, we made the audacious claim that you could use SATA disks without RAID to run Exchange! Here’s how you can achieve it.

Exchange 2010 introduces the concept of Database Availability Groups, or DAG for short. It’s a High Availability model that uses the best bits from Exchange 2007, known then as CCR, and uses the same technology to ship the database logs to as many members of the DAG as you may have configured. Since you’re shipping logs around and NOT the database as you did previously with your replicated SAN that means that now each copy of the database on each of the DAG members is a clean copy of the live database.

If any of the copies of the database has a minor glitch because the disks you’re using develops a bad sector, then each server is able to reach out to any other copy and request the page which has corrupted and receive a known good clean copy to patch itself with automatically.

Does that mean that Exchange can’t use SAN’s anymore? Of course it doesn’t. Exchange 2010 is able to use virtually any kind of disk you allocate to it. SAN volumes, DAS (Direct Attached Storage) shelves or JBOD (Just a Bunch Of Disks). Irrespective of the disk you give Exchange, you’re able to build a highly available distributed unit of high availability.

Using lots of relatively cheap and large SATA disks means you’re able to deploy lots of cheap Exchange servers with large mailboxes, which are highly available and mostly self-repairing. Using your SAN means you’re provisioning finitely sized mailboxes and expensive storage which is now potentially overrated for the task required.  As you may know, redundancy in your SAN isn’t cheap either, and mirroring your SAN to an offsite location can be desperately expensive.  In short, the use of SATA allows high availability to be achieved by distributing Exchange databases across cheap storage as opposed to one massive SAN which is mirrored somewhere else.

CAN Exchange benefit from your SAN? Of course it can, but you may find that the performance you get using low cost SATA based storage option with Exchange built in high availability through DAG’s will service your organization better than your SAN will. In fact, if you hand your high cost SAN back to your SQL teams for their use and step away from SAN infrastructure for your email, your company will win on two counts and you will become a hero outside of your own team!

 

Add your comment (0)

Enterprise Consultant
Mimecast

Article Tags

, ,

Exchange 2010 promises to dramatically cheapen the cost of mail storage to the point where it no longer requires SAN based storage to achieve its goals of storing mail in a secure and highly available manner.

Exchange 2010 is able to use virtually any storage you give it, the only criteria being that it supports the IOPS requirement for the workload demanded. Due to the efficiencies in the current version of the storage engine, that means that databases can now be stored on SATA disks, SAS disks, RAID volumes on DAS Shelves, or the holy grail of storage – Tier 1, the SAN.

You may think that SATA is great when it comes to storing videos of the kids on holiday, old emails, documents and your music collection, and we agree. SATA has been the last thing we would have thought of in the modern datacentre, OR that mail server you hide under the desks or in the closet in your small branch office.

So how has SATA become the new rising star of storage, after previously only influencing the desktop sector?

There are two kinds of SATA we need to consider here, desktop or consumer SATA and enterprise SATA. The difference comes in the construction and the firmware of the disks. Enterprise SATA disks have more rigidity, more extra bits in the chassis and firmware that take into account that each disk may be housed in a shelf with a number of other disks which vibrate, spin and potentially influence each other.

Consumer SATA disks on the other hand have a much lower cost construction and are not designed with any of the additional heat or vibration considerations in mind.

So that makes sense – enterprise SATA disks can live amicably in a datacentre – but they’re still SATA. They’re still slow – literally slow. They rotate as slow as 5400 RPM, as opposed to the 10 000 or 15 000 RPM you’d expect from a traditional enterprise disk. Random seek times are what you’d expect, randomly slow. So how on earth do they become good candidates for the most important commodity in your digital life – your companies email?

The Exchange 2010 version of ESE – the Extensible Storage Engine, which is the database that Exchange uses, has a bit of secret sauce, actually it’s a rewrite from the ground up, which makes it 90% faster than Exchange 2003. That’s right, 90%, no typo there. But wait there’s more – it’s also optimised for sequential read and writes, in fact the entire database is logically laid out to accommodate long reads and long writes, exactly the kind of thing SATA disks are good for.

So let’s talk about the trust issues you may have with SATA – it’s STILL SATA, it’s still just a single disk, and just to top things, Microsoft are asking you to throw your RAID controller away as well. Is that still a real world expectation?

In part 2 we’ll have to have a quick look at how Exchange 2010 does High Availability for the database.

CC Image via univrsltransl8r on Flickr

Add your comment (0)

Enterprise Consultant
Mimecast

Article Tags

, ,

The guys at MS Exchange Team have released a guidance change on the formula to calculate the megacycles for different processor configurations.

Their new guidence is published here and is available for viewing.

Recently we made a change with respect to how we normalize the available megacycles of server platforms with respect to our baseline system.  Initially, we adjusted megacycles per core with respect to the total megacycles of the system and derived this formula:

((New platform per core value) * (Hertz per core of new platform)) / (Baseline per core value) = Adjusted Megacycles per Core

However, that is not the correct way to look at normalizing the server platforms against our baseline. What we are actually interested in is how this impacts the active mailbox user count.  Therefore the new formula is:

((New platform per core value) * (Hertz per core of baseline platform)) / (Baseline per core value) = Adjusted Megacycles per Core

This guidance change is effectively immediately and is documented within the TechNet article, Mailbox Server Processor Capacity Planning.  The documentation within the Exchange 2010 Mailbox Role Requirements Calculator will also be updated to reflect this.

Don’t panic if you used the old calculations, the team say that you will simply end up with a little extra megacycle capacity. In these days with such tight budgets that may not be a terrible thing to have at the offset, especially as we know how quickly mail platforms become underpowered…

You can read their full explanation here.

Add your comment (0)

Enterprise Consultant
Mimecast

Article Tags

,