Simply Migrate - Diagnostic Report

This guide covers details about the diagnostic report for Simply Migrate and how to read it. This report has been designed to assist in troubleshooting issues.

1. Migration Overview

This section will give you a high level overview of the project, and will include:

• Customer name.
• Data volumes discovered and migrated.
• Percentage complete.
• Estimated completion date.

This will help with understanding the progress of a project.

2. Project Details

These details relate to the settings for the migration, and will include:

• The name of the SQL server where Simply Migrate is connecting to.
• Where the log and temp paths are.
• How many jobs are set to run at any given point in time.
• Mimecast API details.
• Details regarding the license being used for the migration.

This will be mostly frequently used to:

• Identify if a license needs to be renewed (because the date has expired).
• Check if the job limit has been exceeded.
• View Temp folders and log folders, in order to check disk space, or whether AV is disabled for the relevant folders.

3. Configuration Details

This gives all the data available for each batch configuration (as they can be different).

This is most commonly used to look at:

• Which sources are configured.
• How many threads are running per job.

While not used often in troubleshooting, it gives all the information needed to understand how the jobs were setup in the system.

4. Batch Details

This gives a high-level breakdown of:

• Which batches are setup.
• How many jobs they have in them.
• Whether they are currently active.
• When last the batch was active.

This is very useful when diagnosing issues with migration that has not completed, as finding out if the batch controller is running is the first thing that would need to be investigated.

5. Job Statuses

Having looked at the batches, it is useful to look at the job statuses.

If there are no jobs in a status of On Hold, Processing, or Discovery, then the migration would never move forward, even if the batch controller was running. 

The second part of this section then breaks down the job statuses grouped by Batch ID, similarly this will show that the On Hold batches may just exist in batch 1 however only batch 2 is currently Active.

With this you can start the appropriate batch to get the migration back underway.

6. Job Statistics

This shows a 7 day overview of the migration, which you can use to see when a migration stopped. Very often this could coincide with when the batch controller was last active or when it had no jobs left to process.

7. Mimecast API Status

This is a very quick view of how much data has been used of your ingestion quota, if you have exceeded the quota it will cause the migration to stop and you would need to reach out to your account team to purchase additional data to finish the migration.

8. Migration Errors

This shows an aggregated view of the errors that are being seen within that migration, which we can use to advise on any errors that could be retried or fixed by the software, or, if all errors shown can not be fixed and if the migration can be closed out.

9. Migration API Errors

If you are having storage related errors on the Mimecast Grid we may need to raise a support case to investigate. This section will show you the date segments that are affected, the error code they are getting and the date and last request ID which we can use to obtain the relevant logs from Beachcomber to get the case raised with our internal teams.