Logging and Trace files

The location and number of log files for CloudM Migrate depends on whether it is being run in single or multi-server mode.

Single Server Migrations

If running CloudM Migrate in single-server mode, then you can access the log file as follows:

Web: Click on the burger bar in the top-left and select 'Remote Connections', then download the Migration Trace

Web traces using Windows Explorer: Go to C:\ProgramData\Cloud Technology Solutions on the secondary server(s) where any affected user(s) were migrated. You will find a folder with a GUID (C:\ProgramData\Cloud Technology Solutions\a3abb3e5-b638-44fb-942f-04f059f95402, for example). This is the project ID. Within this folder, you will see more similar folders, (C:\ProgramData\Cloud Technology Solutions\a3abb3e5-b638-44fb-942f-04f059f95402\556bf3cd-659a-4f9e-a621-d7aac27ec955, for example). This is the project / config IDs:

Here, 556bf3cd-659a-4f9e-a621-d7aac27ec955.Trace.txt is the trace we would require to investigate any issue(s).

The project ID is not visible to you, but if you need to find out what the config ID is, you can go to Projects / Archives and you will see it in the URL:

CloudM Migrate keeps logs for the last 10 migrations, and the most recent file is that without a number.

Multi-Server

When running CloudM Migrate in multi-server mode, different log files are written. The configurable storage location does not apply to multi-server migrations, and logs are always written to the following locations.

Master Server

• User interface logs - C:\ProgramData\Cloud Technology Solutions\CloudMigrator\CloudMigrator.UI.Trace.txt
  • User interface logs store information about the user interface and can be used to help troubleshoot any issues with it
  • User interface logs are kept on a rolling basis, the latest has no number
• Migration logs - C:\ProgramData\Cloud Technology Solutions\CloudMigrator\CloudMigrator.Trace.txt
  • Migration logs contain detailed information about what happened during a migration and can be used to help diagnose issues with user migrations.
  • The 10 most recent migration logs are kept, the latest log file is always that without a number
• Service logs - C:\ProgramData\Cloud Technology Solutions\CloudMigrator.Service.Trace.txt
  • Service logs provide information about the management of migrations and communication between system components
  • Service logs are kept on a rolling basis, the latest has no number


Secondary Servers

• Migration logs - C:\ProgramData\Cloud Technology Solutions\CloudMigrator\CloudMigrator.Trace.txt
  • Migration logs contain detailed information about what happened during a migration and can be used to help diagnose issues with user migrations.
  • The 10 most recent migration logs are kept, the latest log file is always that without a number

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

  • Service logs provide information about the management of migrations and communication between system components
  • Service logs are kept on a rolling basis, the latest has no number

Generating a debug-level trace file for reporting issues to Support

Web UI

• In order to generate a trace file (with full visibility on how the tool is handling data), you will need to be migrating into an empty account on the destination (this may involve deleting any already migrated items on the destination account or migrating into an empty test account on the destination.)
• On "Page 4", click "Advanced" under "System" and set "Trace Level" to "Debug"
• If you have previously migrated data with the tool, you will need to clear the migration history by highlighting an affected user, on page 3, and clicking "Actions" then "Clear Selected Migration History". Or clear the migration history for the entire migration from the "Projects" page, then the large cog icon.
• Replicate the issue

Once the above has been complete, you need to locate the file at one of the above locations.

CloudM Migrate Hosted / Online

By default, "Trace Level" will have been set to "Trace". The support team will just need your destination domain name in order to locate your CloudM Migrate instance.

However, if you turned "Trace Level" to anything other than "Trace", then follow these steps:

• Migrate into an empty account on the destination (this may involve deleting any already migrated items on the destination account or by migrating into an empty test account on the destination.)
• On "Page 4", click "Advanced" and under "System" set "Trace Level" to "TRACE"
• If you have previously migrated data with the tool, you will need to clear the migration history by highlighting an affected user, on page 4, and clicking "Actions" then "Clear Selected Migration History". Or clear the migration history for the entire migration from the "Projects" page, then the large cog icon.
• Replicate the issue

Notify support once this has been done, the team will be able to retrieve the trace file from there.

Other Log Files

The system will also produce two other log files which support may request when troubleshooting any potential issues.

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