Logging and Trace files

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.

User Trace Files

Now, instead of consolidating all users into a single trace file, each user will have their own trace file. This will make it much easier to diagnose and resolve issues (for yourself and our Support Team) as you can focus on the users that are failing, for example, without needing to find them in the larger file. File sizes will also be considerably smaller, and all trace files for a specific migration run will automatically be zipped up in a compressed folder.

User Trace files will also use the following format to make it easier to identify individual files:

• [Configuration Name]_[Import User Name]_[Migration Start Time]

To find a user trace file:

• If you are in the middle of a migration, or the migration has just finished, and you are on the In Progress screen, find the relevant user, hover over the Status icon to view more options, and select the Download icon.

• If you have finished a migration process (successfully or unsuccessfully) and the user trace file is on a Secondary Server, you can select the Remote Connections option, find the required Secondary Server using the Machine Name, click on the Download Logs icon and select the Migration Trace option. A compressed Zip folder will be downloaded and you can view user trace files for the last migration run processed on the Secondary Server.

• If you want to find the user trace files for a previous migration run (i.e. not the last migration run on a machine), go to C:\ProgramData\Cloud Technology Solutions on the server(s) where any affected user(s) were migrated. You will find a folder with a GUID (C:\ProgramData\Cloud Technology Solutions\0dda821c-2eed-44d0-899e-03f32351f22d, for example). This is the project ID. Within this folder, you will see similar folders, (C:\ProgramData\Cloud Technology Solutions\0dda821c-2eed-44d0-899e-03f32351f22d\21bbdbe1-28f9-4ce8, for example). This is the Config ID.
  • You will see a Trace file for each user that was included in the migration run. In the example below, you can see that there was only one user:
    • Oracle---Google_telustest_stork_00001@test.thecloudmigrator.com_2021-10-14T06_35_14.Trace.txt

• • 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.
    • Only the latest migration run trace will be downloaded for a specific user if their trace is downloaded from an Archive stats page.

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.

Primary 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

• 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 (and this may involve deleting any already migrated items on the destination account or migrating into an empty test account on the destination.)
• On "Step 4 - Config Settings", click "Advanced Settings" > "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