Addressing the manual steps involved in moving active users from one EV system to another
Let’s take a look at a typical challenge that can occur during a migration project.
Commonly our customers are seeking to perform a migration as part of an upgrade and hardware refresh of their Enterprise Vault servers. Let’s say you’re looking to perform a migration from EV9 to EV10 for example. EV9 could contain any number of active users who need to be moved to the new platform, ideally without any disruption to the access of their archived data.
How can you configure a migration from a users source EV 9 archive to their target EV10 archive while ensuring minimal disruption to their access? As part of the EV provisioning process, users will be enabled on the new system, but their shortcuts and archives will still reside on EV 9. Attempting to perform restore operations on shortcuts would require additional server configuration to work correctly and users must be trained to look in both systems in order to have total access to all of their data.
This amounts to a great deal of time-intensive manual tasks that need to be conducted as part of moving users from one system to another. This includes disabling the archiving on EV9, enabling the users on EV 10, creating the archives on the new system, and relinking all existing mailbox shortcuts to point to the new target system.
With no potential to script the entire set of tasks, you may be required to be in attendance to manually perform each operation that could add risk, complexity, and unneeded hours to a project. This, and other tasks that compose the provisioning process, can result in a time-consuming headache for administrators or migration engineers.
Certain migration tools, such as ArchiveShuttle, can automate the enablement and disablement of users and manage both source and target archives for the users within the workflow. You can even automate who is getting kicked-off for a migration, and when. A helpful feature for those migrating batched users.
Unlike some other migration utilities, ArchiveShuttle does not require you to have a target archive in place to begin the migration process. This allows you to provision users to the new EV system on your schedule, rather than having to prematurely move ticket generating users over to a target system that their mailboxes are not yet ready for.
If you’re looking for a product to help you with these manual tasks, look to one that centers on a continuity of service to the end user. ArchiveShuttle populates the target with the bulk of the content prior to the switch over from the source to target, through a method known as Sync’N’Switch.
This ensures minimum downtime to the end user, resulting in a lower number of helpdesk calls and subsequent aggravation for those leading the project.
Learn more about an Enterprise Vault to Office 365 migration.