Johann's Unified Communications : planning

Determining the Scalability of Combined CAS and Hub Roles in Exchange 2007

jkruse — Fri, 05 Jun 2009 01:24:33 GMT

Bill Thompson has written a great whitepaper on considerations for Exchange 2007 servers running both the CAS and Hub roles.

This white paper provides information about the scalability of computers running Microsoft Exchange Server 2007 with the Client Access server role and the Hub Transport server role installed on the same server. It also provides planning guidance to help you select the appropriate hardware platform(s) for an Exchange 2007 deployment where you are deploying the Client Access and Hub Transport server roles on the same computer.

http://technet.microsoft.com/en-us/library/dd901772.aspx

Do You Really Need A SAN Anymore?

jkruse — Sun, 14 Dec 2008 12:46:00 GMT

I have had many interesting conversations about my post on Advantages of DAS over SAN storage in Exchange 2007 and the related session I delivered at Tech.Ed 2008… many sceptics have seen the light, although some remain sceptical.

It’s interesting to see that Forrester have published a paper titled “Do You Really Need A SAN Anymore?”.

An excerpt from the paper…

It's been the conventional wisdom of the past 10 years that to provide the best performance, protection, and capacity utilization for applications and databases, you need a robust storage array in a storage area network (SAN). But with low capacity utilization, the inability to prioritize application performance, long provisioning times, and soaring costs, SANs haven't lived up to their promise. SANs also leave application, database, and system administrators at the mercy of storage administrators for all their storage-related needs, such as capacity, data copies, and backups. To regain control and get better results, application vendors are starting to subsume more storage functionality into the application itself, giving IT buyers the option to spend less on commodity storage and get their high-value features from the application. The time has come for buyers to question the value of their SAN and consider simpler options that fit better with the applications they truly care about.

A very interesting read on allowing advanced applications (e.g. Exchange) look after storage. Unfortunately it’s not free, but you can purchase and read the paper at http://www.forrester.com/Research/Document/Excerpt/0,7211,47089,00.html

Designing Your Perimeter Network for Office Communications Server 2007 White Paper

jkruse — Thu, 17 Jul 2008 01:12:37 GMT

This paper answers questions about Office Communications Server 2007 with specific regard to its integration into the perimeter network (also known as DMZ, demilitarized zone, or screened subnet).

The first section, “Commonly Asked Questions,” answers key design questions from customers about the initial stages of product deployment.

The second section, “Architecture and Networking Best Practices,” explores ways to prepare for the edge servers in the perimeter network, taking into consideration issues of physical deployment, ways to ensure a publicly routable IP address, firewall configuration, and load-balancing concerns.

Download the whitepaper at http://www.microsoft.com/downloads/details.aspx?FamilyId=E4A8D703-E41A-47D9-B9DD-2799F894AF92&displaylang=en

Share this post :

Advantages of DAS over SAN storage in Exchange 2007

jkruse — Thu, 17 Apr 2008 02:16:00 GMT

You may have heard me talk about this at TechEd, and some of my customers will recall long discussions with me about the merits of using Direct Attached Storage rather than SANs in Exchange 2007.

Storage Area Networks (SAN) have become increasingly common in Enterprise environments in recent years, and in particular for hosting Exchange Server environments due to their space and IO requirements.

There are many advantages to using a SAN with Exchange:

Performance - Exchange 2003 is a very IO intensive application, and in any decent-sized environment disk IO is almost always the bottleneck
Scalability - we're storing more data than ever before and although technologies like Sharepoint relieve some of the burden from Exchange, the fact is that mailbox sizes continue to grow as we move into the age of UM and UC.
Availability - consolidating your storage provides a single system to maintain and backup, and allows you to build HA/DR into the storage system to protect all of your data.

However Exchange 2007 introduced some new concepts, which has changed things somewhat.

Performance - by moving to a 64-bit platform (which does not have the virtual memory limitations of its 32-bit predecessors) we have significantly reduced the IO impact in Exchange, by about 70% on a mailbox server! Modern DAS technologies such as Serial Attached SCSI (SAS) are capable of providing more than enough IO for Exchange 2007.
Scalability - SANs are expensive, so as storage requirements increase so does the TCO of the environment. For example, at Microsoft the high costs associated with shared SAN storage hindered MSIT from supporting employees with mailbox quotas of greater than 200 MB.
Availability - SANs don't fail often, but they do fail - and when they do it can be catastrophic. Three of my Exchange 2003 customers have had SAN failures this year, and in each case it took several days to return Exchange to full operation. Two of these customers were using SAN replication technology which actually replicated corrupt data to the DR site, taking it out and making the restore process much more complex (and defeating the whole purpose of the replication IMHO). Exchange 2007 introduced CCR and SCR, which provide software-based replication for HA and DR eliminating single points of failure, and providing simplified site resilience and DR.

Figure 1: a typical Exchange 2003 2-node cluster using SAN replication for DR

Figure 2: Exchange 2007 - CCR+SCR, using DAS storage

The two diagrams above, which are scanned from some scribblings on paper I drew in a recent Architectural Design Session with a customer (apologies for the messiness - I'm so used to keyboard/mouse than my handwriting skills have declined :)), show their existing Exchange 2003 cluster and a proposed Exchange 2007 cluster.

The advantages of the Exchange 2007 environment here are:

Increased availability in Prod datacentre - there are two copies of the database, with automatic failover, meaning no single point of failure. The SAN environment in Figure 1 has only one copy of the DB in Prod, meaning that any DB failure will result in a cutover to DR. CCR in Figure 2 provides fault tolerance in the event of server failure, storage failure and data corruption.
Enhanced Disaster Recovery - using SCR to replicate data to the DR site, there is now a fully supported and simple to manage DR process in place. In Figure 1, data corruption in Prod could be replicated to DR, meaning that restore from backup would be required. In Figure 2, SCR will not replicate corrupted data as it used transaction log shipping to replicate.
Reduced TCO - there may be more copies (3) of the data in Figure 2, but the usage of DAS disks will significantly reduce the cost of storage which will likely more than offset the cost of the additional disks required.

So how does it work in the real world? A great example of the benefits of moving from SAN to DAS is our internal MSIT case study.

We saw benefits such as:

Messaging service levels exceeding high-availability targets of 99.99 percent.
Cost reductions in excess of $10 million per year.
Increased mailbox quotas by up to a factor of 10.
Consolidation of the initial Exchange Server 2007 base by nearly a factor of two.

The MSIT whitepaper can be found at the Technet site, in Word format, as a webcast, or as a podcast (WMA, MP3).

Share this post :

Technorati Tags: exchange 2007, storage, ccr, scr, san, das, planning, msit, download

Windows Mobile technical library - now at TechNet

jkruse — Thu, 13 Mar 2008 01:48:00 GMT

Finally, Windows Mobile has been added to the TechNet technical library.

In-depth technical information on Deployment, Operations and Security for Windows Mobile 5 and 6.

Check it out, and bookmark it - http://technet.microsoft.com/en-us/library/cc182292.aspx

Share this post :

IM me!

Technorati Tags: mobility, wm5, wm6, technet, doco, deployment, planning

Help designing and planning your OCS deployment

jkruse — Sat, 08 Mar 2008 02:26:01 GMT

I've just designed a high-level OCS architecture for a large organisation, including IM/presence, conferencing, Enterprise Voice, external access (inc. conferencing/voice), federation and PIC.

I have also discovered and included all of the relevant documentation for planning and deployment of this architecture.

Total time spent designing this architecture - < 5 minutes!

How did I do this so quickly and easily? The Planning Tool for Office Communications Server 2007.

The planning tool provides you prescriptive guidance to get you started with planning your Office Communications Server 2007 topology. The tool asks you a series of interview questions about the features that you are interested in, as well as information about your organisation.

Based on the answers you provide, the planning tool draws out a recommended topology based on Microsoft’s Office Communications Server 2007 User Model that has been tested.

The planning tool also provides customised links to the appropriate documentation to help you plan and deploy your topology.

Links to the relevant planning guides

Links to to the relevant deployment guides

You can download the Planning Tool for Office Communications Server 2007 at http://download.microsoft.com/download/2/0/7/207bb9fb-bffe-478f-91b7-8339d25f7fdd/OCSPlanningTool.msi.

Share this post :

IM me!

Technorati Tags: ocs, planning, doco, tools, download