Migration, Network monitoring – Google Networking Best Practices for Large Deployments User Manual
Page 12
12
Networking Best Practices for Large Deployments
Migration
Google Apps deployments can involve migration traffic, either from local clients like
m server-side clients like
.
Migration of legacy data into Google Apps is typically a resource-intensive activity, but usually
only happens once. If you plan to migrate user data, consider the following:
Ensure that your migration servers are in the same location as your legacy data servers,
or at least that the connectivity between servers has low latency and high bandwidth.
Avoid routing traffic from the migration servers to Google through proxy servers, to reduce
migration performance and to avoid unnecessary proxy server load.
Assess your network capacity before migration to determine the maximum amount of data
that you can migrate concurrently. Adjust your migration plan accordingly.
During migration, some of the connections established to Google servers can stay open
for a period of time depending on the migration tool. To avoid any possible migration
errors, and to reduce the need to remigrate data, it is important to keep these sessions
open and not close them prematurely with any proxy or firewall timeouts.
For more information about data migration, see “Migration” on page 38.
Network Monitoring
Use monitoring tools to maintain and administer an existing IPv4 network that is already
working with Google Apps.
There are a variety of network monitoring tools available that are well-suited to monitor
Google Apps traffic. For a list of recommended network monitoring tools, see “Monitoring
Tools” on page 41.
Network Packet Captures can assist in identifying possible performance issues during
your troubleshooting or when working with your network provider or Google support. For
more information, see “Network Packet Captures” on page 42.