Welcome back to lovely sunny Seattle/Redmond, figuratively speaking of course. This video is a discussion about our approach to moving mailboxes—the Mailbox Replication Service (MRS).
Starting with Exchange 2007 SP2 moving forward, administrators can create long running move jobs for load balancing, migrating between versions, replacing and upgrading hardware and for making the jump to the cloud. The architecture and approach will remain consistent for all current versions of on-premises Exchange and Exchange Online and for all the upcoming versions we have even glimmers of planning for.
Moving mailboxes is a key part of managing an email service for the long-haul. There will be updated technologies, new business priorities, mergers, acquisitions, hardware and version upgrades. So having a robust, fire and forget, throttled system that enables administrators to accomplish this work while keeping the moves transparent to actual users (by making sure they stay on-line throughout the process) is absolutely key and making sure that the process scales up gracefully as mailboxes move from Gigabytes to 10’s of GB to 100’s.
I was amused recently to find out that one of our cloud competitors is trumpeting the benefits of their simple cloud story, by pointing out how happy users were with their ‘Fresh and Clean’ mailboxes after the ‘migration’. By fresh and clean they meant empty. This awesome and simple ‘migration’ simply creates new mailboxes and simply orphans the data in the original. If providing a service that makes sure that email doesn’t get lost and is available to users every day makes sense, then our perspective is that it is also important to keep user’s mail intact as they move to the cloud.