We’ve had an upsurge of EAS email migration and rehydration jobs lately and I thought it would be nice to cover off one of the key reasons I believe our customers are using this feature.
I’ll describe the scenarios I have seen most recently to set the stage. A customer has been running Zantaz EAS for a long time for email archiving, and then one of the following triggered the need for change;
- The Zantaz EAS infrastructure is getting old, and there is a desire to decommission it.
- A project to head toward zero infrastructure has started and legacy archiving technologies have no place in that plan.
- Data centre consolidations, migrations or decommissioning.
- Mailboxes are now in Office 365 and the technology no longer works.
I’ve heard a few other reasons like mergers and acquisitions recently, but they are the most common.
Making it happen
Once you have Simply Migrate installed and configured, open the Simply Migrate Management Shell.
I’ll show you how to create a single job in the following example for a single user mailbox, but based on that example, you’ll see how simple it is to create a more scaled solution to rehydrate many servers, shares, etc.
New-SMJob -source Exchange -SourceInput JAPPLESEED -RehydrationSource Zantaz -SourceCredential $creds -BatchId 1
The above command will create a new job that performs the following actions.
It will perform a discovery of all Zantaz EAS stubs in JAPPLESEED’s mailbox, and commence rehydrating stubs in their current location. In order to perform the same action against an Online Archive, it is as simple as adding a SourceOption parameter of UseArchive to the job like this :
New-SMJob -source Exchange -SourceInput JAPPLESEED -RehydrationSource Zantaz -SourceCredential $creds -SourceOptions UseArchive -BatchId 1
The wonderful thing about this is the speed and the reporting really. It’s a simple process to star and it’s an even easier process to manage. The UI shows you how many items were found, if any of the items were failed, and if so, why. You get a view of the speed that things are happening, thus, how long it will take to finish. All out of a 10 minute installation, and a single line in PowerShell.
Zantaz email Migration
There are a few nice features we can explore in this section if we take the rehydration process into account, but we will start the process as a single migration from Zantaz to Exchange Mailbox. the syntax isn’t complicated and it’s easy to follow.
New-SMJob -source Zataz -SourceInput JAPPLESEED -Target Exchange -TargetOutput email@example.com -TargetCredential $creds -BatchId 1
As you can see above, we have specified that the source of the data is in Zantaz, and specifically in JAPPLESEED’s archive. We have then specified that the target is Exchange and the mailbox target is firstname.lastname@example.org. Given that the source is an Alias and the target is an UPN, we can easily achieve scalability with a simple script that looks up our users and populates these attributes for us.
Just like the rehydration example, we can migrate data to the user’s Online Archive by adding the TargetOption UseArchive parameter to the job configuration like so:
New-SMJob -source Zataz -SourceInput JAPPLESEED -Target Exchange -TargetOutput email@example.com -TargetCredential $creds -TargetOptions UseArchive -BatchId 1
Why not both Rehydration and Migration?
One more thing …
While we see customers handle migrations in a variety of ways, we prefer to be flexible around how things are approached and not prescriptive around how things must be done. The beauty of our approach to migrations and rehydrations is that you can do both, in a single command, and it does the heavy lifting for you.
Here’s a scenario. You want to rehydrate all Zantaz EAS shortcuts ‘in place’ in the users mailbox, but want to migrate the rest of the users Zantaz data into the Online Archive. You also, don’t want to migrate anything that had a shortcut. You know, to avoid duplicates. Here we have a handy little cmdlet.
New-SMMultiPartJob -Source Zantaz -SourceInput JAPPLESEED -SourceCredential $Cred -Target Exchange -TargetOutput firstname.lastname@example.org -TargetCredential $Cred -TargetOptions UseArchive -BatchId 1
The magic here is that a single command will rehydrate the shortcuts in place, and the migration will migrate the delta of the items remaining. it’s that simple.
It’s nice when technology allows you to be flexible and deliver a project the way you want it to instead of prescribing how you must do things. We pride ourselves on this, and it makes for a much happier end result.