Troubleshoot a server crash

If you encounter a server crash when using Google Workspace Migrate, follow the steps below to troubleshoot.

Platform server crash  |  Node server crash  |  Database server crash

Platform server crash

If the platform server crashes when bridges are running:

1. For all running node servers, on the taskbar, right-click Google Workspace Migrate and select Stop Google Workspace Migrate service.
2. Make sure the platform server meets the system requirements.
3. Start the platform server, and check that the Google Workspace Migrate service is running.
4. On the node servers, right-click Google Workspace Migrate and select Start Google Workspace Migrate service.
5. On the platform, check the node server status.

   For details, go to Verify the nodes are running.

6. On the Google Workspace Migrate platform, click Bridges.
7. For the terminated bridges, click Run Run delta.

If the virtual machine (VM) that is running the platform server crashes and can't be recovered:

1. Build a new VM.
2. Follow the steps in Replace your platform.

Node server crash

If one or multiple node servers crash when bridges are running:

1. Wait for all running bridges to complete, or stop the bridges manually.
2. Make sure the node servers meet the system requirements.
3. Restart the node servers, and check that the Google Workspace Migrate service is running.
4. On the platform, check the node server status.

   For details, go to Verify the nodes are running.

5. On the Google Workspace Migrate platform, click Bridges.
6. For the terminated bridges, click Run Run delta.

If a VM that is running a node server crashes and can't be recovered:

1. Build a new VM.
2. Follow the steps in Install the node servers.
3. Remove the crashed node from the platform and add the new node.

   For details on how to add the node, go to Add the node servers.

   Important: You must reassociate the node even if the new node server has the same hostname, IP address, and access key as the old node server.

Database server crash

If one or multiple databases servers crash when bridges are running:

1. Stop all active bridges immediately.
2. For the platform and node servers, on the taskbar, right-click Google Workspace Migrate and select Stop Google Workspace Migrate service.
3. Make sure the database server meets the system requirements.
4. Start the database service, and check that it's running correctly.
5. If the database didn't start successfully, follow the steps in Database troubleshooting (below on this page).
6. On the platform and node servers, right-click Google Workspace Migrate and select Start Google Workspace Migrate service.
7. On the Google Workspace Migrate platform, click Bridges.
8. For the terminated bridges, click Run Run delta.

Database troubleshooting

If the database service didn't start, check:

• The settings in the configuration file (The MySQL file is my.ini, and the CouchDB file is local.ini.)
• Whether you can locate the root cause in the database logs
• The MySQL or CouchDB documentation for information on how to recover the service

If you can't resolve the issue, you might need to restore data based on a recent backup, or create a new VM using a snapshot.

_{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.}