CloudM Migrate Hosted
If you are using 'CloudM Migrate Hosted' the trace file for your migration is not available to you. Please open a support ticket via our Support Portal for us to investigate.
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:
Desktop: from the tools menu at Tools > View Trace File. Unless the default options for data storage have been changed the file is located at: C:\ProgramData\Cloud Technology Solutions\CloudMigrator\CloudMigrator.Trace.txt
.
Web: Click on the burger bar in the top-left and select 'Remote Connections', then download the Migration Trace


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.
Migration logs are written to the server on which a migration occurred. To determine which secondary performed a migration for a user, refer to the progress tab or the CSV report files generated at the end of a migration.
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
Desktop
- 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.)
- Under "General Migration Settings", select "General", then "System" and set "Trace Level" to "DEBUG".
- If you have previously migrated data with the tool, you will need to clear the Migration History
- Replicate the issue.
Once the above has been complete, you need to locate the file at one of the above locations.
Exceptions
If migrating from Lotus Notes, GroupWise, Zimbra, Box or Dropbox it helps us if you set the trace-level to TRACE instead of debug, this will gather additional, specific tracing from those platforms.
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.
Exceptions
If migrating from Lotus Notes, GroupWise, Zimbra, Box or Dropbox it helps us if you set 'General Migration Settings' > 'Advanced Settings' > 'System' > 'Trace Level' to TRACE instead, this will gather additional tracing for those platforms.
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
The most recent log file for any part of the system is the one without a number. Log files are rotated based on size or as more migrations take place. The oldest log file is the one with the largest number at the end of it.
Comments
0 comments
Please sign in to leave a comment.