Google Apps Migration for Microsoft Exchange Administration Guide - Manual (Page 17)

Architecture and Deployment Scenarios 17
Once you have data from your pilot test, you can plan the migration of the rest of your users,
including the hardware resources you’ll need, and the amount of time you’ll need to devote to
the process.
Topology
A single instance of Google Apps Migration for Microsoft
®
Exchange runs on an intermediary
client machine between your source server and Google Apps. You can migrate the data from
one or more servers, and you can deploy one or more clients for each server. You must use at
least one client per server, and each client migrates a unique list of users.
Important:
• You can run only one instance of Google Apps Migration for Microsoft
®
Exchange on each
client machine. If you try to run multiple instances on a single client, those instances
overwrite one another’s configuration files (there is a single location for configuration files).
• In addition, each instance has to reference a unique list of users in order to avoid
corrupting the status information for each user’s data.
The following four diagrams illustrate approaches you can take.
Single Server, Single Client
Single Server, Multiple Clients
Source
Server
Google Apps
Google Apps Migration
for Microsoft
®
Exchange
Client Machine
Google Apps
Google Apps Migration
for Microsoft
®
Exchange
Client Machine
Google Apps Migration
for Microsoft
®
Exchange
Client Machine
Source
Server