Logs & Trace Files

CloudM Migrate records all actions in logs and trace files in the backend. These files will be useful to investigate and troubleshoot technical issues.

CloudM Migrate Hosted

It’s important to note that if you are using CloudM Migrate Hosted (our SaaS version of CloudM Migrate), all logs and trace files are available to our internal technical teams, so if you encounter an issue and report it, we’ll already have what we need and Logging > Trace level is automatically set to Debug.

CloudM Migrate Self-Hosted

By default, CloudM Migrate Self-Hosted logs and trace files are stored locally in the primary and secondary migration server(s) used in the below location

C:\ProgramData\Cloud Technology Solutions

It’s also possible to utilize Centralised Self-Hosted Logging whereby it’s possible to transmit logs and trace files directly to a Google Cloud Storage bucket or an Azure Storage bucket of your choosing. See the linked article for more information.

The Migration Service

Each migration service (primary and secondaries) will have its own logs and trace files.

Item Trace Files

Each individual migration item (user, group, Google Shared Drive, SharePoint Site for example) will have its own migration trace files.

Item Trace files use the below naming conventions to make it easier to identify individual files:

Where items are processed in parallel (by default), the following applies:

[Batch Name]_[Import Item Name]_AllExceptDocuments_[Migration Start Time].txt

[Batch Name]_[Import Item Name]_Documents_[Migration Start Time].txt

Where items are not processed in parallel, the following applies:

[Batch Name]_[Import Item Name]_[Migration Start Time].txt

To find an Item/user migration trace file:

• From the Progress screen - while a migration is in progress or has completed - find the relevant item, hover over the Status icon to view more options, and click the Download user trace logs icon. This will download/attempt to download the migration trace file for the item (directly from the secondary server used). 
  
  
  
  
• You can also download all item migration trace files assigned to each secondary server by project and batch. To do this, navigate to Advanced > Migrate Services, select the relevant Project and Batch, and then click the download icon next to the Secondary Server listed by Machine Name. From there, you can choose to download the Migration User Traces.
  
  
  
  
• If you want to find the item trace files for a previous migration run (i.e. not the last migration run on a server), go to C:\ProgramData\Cloud Technology Solutions on the server(s) where any affected item(s) were migrated. You will find a folder with a GUID (C:\ProgramData\Cloud Technology Solutions\174ac4f9-6dae-4887-886a-57d87a075223, for example). This is the project GUID
  Within that project folder, you will see similar folders, which are the Batch GUIDs which can be easily matched using the URL in the browser address bar
  
  C:\ProgramData\Cloud Technology Solutions
  
  
  URL Batch ID location
  
  
  Inside the Project GUID folder, find the Batch GUID
  
  
  
• You will see a Trace file for each item that was included in the migration run
  

Multi-Server

When running CloudM Migrate with a multi-server installation, migration trace files are written to the server on which a migration occurred. To determine which secondary performed a migration for an item, refer to the Progress tab or the CSV report generated upon completion of a migration. The files can be found in the same location as above in C:\ProgramData\Cloud Technology Solutions.

Service Logs and Trace

The Service logs and trace files provide additional information about the management of migrations and communication between system components. These files are useful in combination with the migration traces if migrations are failing to start, performing unexpectedly, or crashing.

Storage location:

C:\ProgramData\Cloud Technology Solutions

The Service logs and traces are kept on a 20 file rolling basis, where the latest has no number and 19 would be the oldest available. The following naming convention applies:

C:\ProgramData\Cloud Technology Solutions\CloudMigrator.Service.logs.txt

C:\ProgramData\Cloud Technology Solutions\CloudMigrator.Service.Trace.txt

Generating a trace file for reporting issues to Support

If you raise a Support ticket and a higher trace-level trace file is requested (where the default Information level was set, for example), in order to generate this, you will ideally need to be remigrating into: 

• an empty destination account, or 
• you may be required to delete already migrated items in the specified destination account
  

Go to Batch Name > Configuration > Advanced settings > Logging > Trace level and set this to Trace

If you have previously migrated data, you will need to clear the migration history for the item(s)/user(s) in question, by selecting them in your Items to migrate list and clicking Bulk actions > Clear History. Or Clear migration history for the entire migration project from the Projects page three-dots (kebab) menu.

Finally, remigrate the affected item(s)/user(s). Once the above has been completed, you will need to download or locate the item(s)/user(s) file by following the steps outlined above.

Other Trace Files & Options

There are also the following trace options or trace files, which our support team might explicitly request from time to time:

C:\ProgramData\Cloud Technology Solutions\PoweredBy.Web.Trace.txt

C:\ProgramData\Cloud Technology Solutions\NServiceBus.Web.Client.txt

C:\ProgramData\Cloud Technology Solutions\NServiceBus.Service.Trace.txt

C:\ProgramData\Cloud Technology Solutions\MigrationService.Manager.Trace.txt

Sometimes Support may require to look deeper into specific requests being made to/from the source/destination platforms. CloudM Migrate has these two additional options for that scenario:

Trace Google web requests If the above trace level is set to "Trace," enabling this option outputs the response of Google web requests to the migration trace file. This can increase the size of the trace file considerably and should only be used when directed by CloudM Support.

Trace Microsoft Graph web requests If the trace level is set to "Trace," enabling this option outputs the response of Microsoft Graph web requests to the migration trace file. This can increase the size of the trace file considerably and should only be used when directed by CloudM Support.