Monitor migration progress

Once the bridge starts running, you can monitor the progress of your migration in the Google Workspace Migrate logs. You can filter the information to get detailed data, such as specific types of warnings or failures. You can also check the nodes to view their level of activity.

Open & monitor the logs

  1. Click Bridges. You might have to click Menu "" first.
  2. Next to the name of your bridge, click Logs "" and select a log.
  3. (Optional) To filter the log results, see Filter Migration summary log results and Filter other log results.

Types of logs

Open all   |   Close all

Migration summary log

You can review a high-level overview of the content migrated in the bridge execution using the Migration summary log. You’ll see the total number of transactions processed.

Partition log

Use the Partition log to see the partitions that were created and run for the bridge.

You can filter the log by the state of each partition. To do so:

  1. Open the partition log.
  2. Click State and select the ones you want to view.
    The most significant states are:
    1. Ready—Partition is ready to begin.
    2. Processing—Partition is working.
    3. Completed—Partition’s work is complete. 

Note: For detailed information about the data migrated and whether it was successful, check the transaction and execution logs.

Execution log

You can identify any operational errors in the Execution log. The log contains a record of each step that’s required to run the bridge. You’ll see a list of the status of each operational component in the migration process. The number of failed transactions shown for a bridge on the Google Workspace Migrate platform is the sum of the errors in this log and the transaction log.

You can view all execution log entries for a partition:

  1. Open the execution log.
  2. Point to a row in the log and click ""and thenPartition transaction log

Note: You only see this option when the execution log entry is associated with a partition.

Transaction log

Use the transaction log to review details about each object processed during the bridge. You’ll see each object within the migration scope. It might take some time for the transaction log to fully load. The number of failed transactions shown for a bridge on the Google Workspace Migrate platform is the sum of the errors in this log and the execution log.

To check the detailed data for each transaction, point to the transaction and click Details "". To download the log, click Download "".

Filter by state

You can filter the transaction log by the state of each transaction. To do so:

  1. Open the transaction log.
  2. Click State and select the ones you want to view.
    The possible states are:
    • Prepared—Ready to begin.
    • Queued—Waiting to be processed. 
    • Processing—Preparing to write data to the target system.
    • Pending—The transaction has been processed and is waiting to be written to the target system. 
    • Completed—The process for the transaction is complete. 
    • Failed—The transaction didn’t finish, due to an error. 
    • Warning—The transaction didn’t finish as expected. View the warning information for details.
    • Skipped—The transaction was skipped. 

View transactions by partition

You can view all transaction log entries for a partition:

  1. Open the transaction log.
  2. Point to a row in the log and click ""and thenPartition transaction log
Execution history log

You can use the Execution history log to see every log for every bridge that’s run. You can also see a record of every occasion that the bridge ran as a full or delta migration. To see each log in the Execution history log, point to the record of the bridge, click More ""and thenselect the log.

Filter logs

Filter Migration summary log results
  1. Open the migration summary log. 
  2. At the top, next to Refresh "", click the Down arrow "" and select an option from the list to group the log by identity, source type, or error code.
  3. Click any available filters (details below), enter any boolean search operators, and then click Apply.
  4. If you grouped the log by identity, you can filter and use boolean search operators to refine by:
    • Identity—Filters by specific identities (for example, usernames).
    • Completed​—Filters by the number of completed transactions per identity.
    • Warnings​—Filters by the number of warnings per identity.
    • Queued​—Filters by the number of queued transactions per identity.
    • Failed​—Filters by the number of failed transactions per identity.
    • Skipped​—Filters by the number of skipped transactions per identity.
  5. If you grouped the log by source type, you can filter and use boolean search operators to refine by:
    • Type—Filters by type of source data. 
    • Completed​—Filters by the number of completed transactions per type of source data.
    • Warnings​—Filters by the number of warnings per type of source data.
    • Queued​—Filters by the number of queued transactions per type of source data.
    • Failed​—Filters by the number of failed transactions per type of source data.
    • Skipped​—Filters by the number of skipped transactions per type of source data.
  6. If you grouped the log by error code, you can filter and use boolean search operators to refine by:
    • Error—Filters by error code. 
    • Count—Filters by the count per error code. 
  7. (Optional) To download a filtered report, apply the filter and click Download reports "".
  8. (Optional) To reset a filter, click Remove "" next to the filter. To reset all filters, click Reset.
Filter other log results

For the Partition, Execution, Transaction, and Execution history logs, you can filter a log to see specific types of information. 

  1. Open the log. 
  2. (Optional) To filter by the state of a migration, click State and next to each migration state that you want to filter by, check the box.
  3. At the top of the log, click any available filters (details below), enter any boolean search operators, and then click Apply.
  4. For the Partition log, you can filter and use boolean search operators to refine by:
    • Name—Filters by the name of the partition.
    • Started—Filters by the start date of the partition. 
    • Completed—Filters by the completion date of the partition. 
    • Completions—Filters by the number of completed transactions processed by the partition. 
    • Failures—Filters by the number of failed transactions processed by the partition. 
    • Skipped—Filters by the number of skipped transactions processed by the partition. 
    • Warnings—Filters by the number of warning transactions processed by the partition. 
    • Crawled—Filters by the number of transactions crawled by the partition. 
  5. For the Execution log, you can filter and use boolean search operators to refine by:
    • Timestamp—Filters by the timestamp attached to the component. 
    • Error code—Filters by the error code attached to the component. 
  6. For the Transaction log, you can filter and use boolean search operators to refine by:
    • Error—Filters by the error code. 
    • Started time—Filters by the start time of the transaction. 
    • Last modified—Filters by the last modified time of the transaction. 
    • Source—Filters by the object migrated from the source environment. 
    • Source type—Filters by the general data type from the source environment. 
    • Target—Filters by the object migrated to the target environment. 
    • Target type—Filters by the general data type on the target environment. 
  7. For the Execution history log, you can filter and use boolean search operators to refine by:
    • Started—Filters by the start time of the migration. 
    • Finished—Filters by the completion time of the migration. 
    • Completions—Filters by the number of completed transactions in the migration. 
    • Failures—Filters by the number of failed transactions in the migration. 
    • Skipped—Filters by the number of skipped transactions in the migration. 
    • Warnings—Filters by the number of transactions that logged warnings in the migration. 
    • Data migrated—Filters by the amount of data migrated in the migration (in bytes). 
  8. (Optional) To download a filtered report, apply the filter and click Download reports "".
  9. (Optional) To reset a filter, click Remove "" next to the filter. To reset all filters, click Reset.

Monitor node status

To view the nodes, their URL, and status, open the Google Workspace Migrate platform and click Servers

You might notice that some nodes appear underutilized during a large migration. The factors that determine how work is distributed across nodes include the CPU and RAM of the node servers. Additionally, the size of scanned data per partition can impact node work distribution.

If a node becomes inoperable and its partition is incomplete, the partition rejoins the queue. Another node picks up the partition and completes the task. If this occurs, you'll see it noted in the execution log. Once you start the migration, you should not decommission any node servers, even when it looks like the nodes are not currently involved in migration tasks.

Next step


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.

Search
Clear search
Close search
Google apps
Main menu
Search Help Center
false