Nodes are servers that perform the scanning or migrating actions of the partitions. They help balance the migration work across available servers. The number of node servers you should deploy depends on the number of users in your organization and the amount of data that you want to migrate.Cloud-based data sources
|SharePoint data||Amount of data||Recommended number of node servers|
*Additional nodes are unlikely to improve performance.
|Files & file permissions||Fewer than 10 million items||20|
|Files & file permissions||More than 10 million items||40
*Don't set up multiple clusters with different SharePoint credentials. Due to API quota limits and capabilities of the MySQL server, it won't enhance performance.
|Other data sources (Number of users)|
|Less than 100 users||Fewer than 1 million items||20|
|100–5,000 users||1–5 million items||40|
|More than 5,000 users||More than 5 million items||40
*To increase migration speed, create multiple clusters of 40 nodes during the migration phase.
We recommend that you start with half of the number of node servers recommended in the table above and monitor the load on your source servers.
Add extra nodes if there are resources available to sustain them. To check the resources, run a test migration and add 5 nodes at each step. Monitor the following critical performance counters to ensure that the servers don’t exceed acceptable thresholds:
- Exchange servers—Processor, memory, and database read counters. For details, go to Exchange 2013 Performance Counters and Manage health sets and server health in Exchange Server.
- SharePoint servers—Processor, disk, memory, and SQL server connection performance counters. For details, go to Monitoring and maintaining SharePoint Server 2013 and Overview of monitoring in SharePoint Server.
- File shares—CPU, memory, and Disk I/O Utilizations.
Stop adding nodes if:
- Performance counters of the majority of on-premises servers are exceeding acceptable thresholds.
- Bridges aren’t completing at a faster rate than before.
Step 2: Prepare servers
- Ensure the Microsoft Windows server that you plan to install the Google Workspace Migrate node has sufficient space. For details, see System requirements.
- Keep your Windows server updated, but we recommend turning off automatic updates during a migration so the process isn't interrupted.
- Copy GoogleWorkspaceMigrate_Node_Installer to the Windows servers where you plan to install each node.
- We recommend that you follow Microsoft's guidance for noncritical service recovery settings.
Step 3: Install the node serversInstall the nodes manually
On the Windows server for the node:
- Run GoogleWorkspaceMigrate_Node_Installer as an administrator.
- Select a language for the installer and click OK.
- Accept the license agreement and click Next.
- Choose where to install the Google Workspace Migrate node and click Next.
- Choose a start menu folder and click Next.
- Select the additional shortcut options and click Next.
- Enter a port number or accept the default port 5131 and click Next.
- Enter an access key. The platform uses the access key to connect to the node.
Important: Record the access key and keep it in a secure place. You'll need it later when you associate the node with the platform.
- Review the installation and click Install.
- Click Next and then Install.
- After installation, click Finish.
- Repeat these steps for each node server you want to install. See above for details on how many node servers you need.
Tip: If you use Google Compute Engine, you can easily add additional node servers by cloning the machine. You should clone the machine at this point (when a node has been installed but before the nodes are associated).
When you install from the command line, the installer automatically chooses these setup options:
- Google Workspace Migrate install location (C:\Program Files\Google Workspace Migrate).
- Start menu folder (Google Workspace Migrate).
- Desktop shortcut created for all users.
- Google Workspace Migrate management app automatically opens when Windows starts.
On the Windows server for the node:
- Run Microsoft PowerShell as an administrator.
- Enter GoogleWorkspaceMigrate_Node_Installer_version-number.exe and any optional parameters (details below).
GoogleWorkspaceMigrate_Node_Installer_version-number.exe /NORESTART /SP- /SUPPRESSMSGBOXES /VERYSILENT
- Enter Start-Service -Name AppBridge.Local.ServiceHost to start the Google Workspace Migrate node service.
- From the Start menu, open the Google Workspace Migrate management app. Alternatively, let the app reopen automatically when you restart Windows.
Optional command-line parameters
File name of the log file
Creates a log file with output from the installer. If the installer doesn’t work as expected, you can view the log file for information.
|/NORESTART||Prevents a system restart during installation|
|/Port||Port number for the Google Workspace Migrate service (the default is 5131)|
|/SP-||Turns off prompts at the beginning of a setup|
|/SUPPRESSMSGBOXES||Suppresses all message boxes|
Turns off the setup wizard and windows during the installation process
Note: For more details on the command-line parameters available, consult the documentation for Inno Setup.
- (Optional) To configure your node servers to use TLS or an HTTP proxy server, go to Optional setup steps for node servers.
- Go to Set up the encryption key.
Google, Google Workspace, and related marks and logos are trademarks of Google LLC. All other company and product names are trademarks of the companies with which they are associated.