Simply Migrate - Dashboard & Tools

This article contains information on setting up and monitoring migration jobs using the Simply Migrate Dashboard, including job and batch management, retrying exceptions, and basic troubleshooting steps.

You can set up migration jobs and monitor their progress from the Simply Migrate Dashboard. Since this is a real-time data migration, the migrated data will be available for access as it is accepted for storage within your Mimecast account.

The Simply Migrate Dashboard

The Simply Migrate dashboard is where you will be able to create and monitor your migration jobs.

image.png
image.png
  1. This tab will list the number of items that have been migrated.
  2. Keep track of how much data has been migrated to date.
  3. The number of jobs that are currently running.
  4. Timeline of items migrated over time; you can filter by weeks/months.
  5. High-level migration overview and estimated migration completion date.
  6. The jobs that are running now and their source. You can click on the individual jobs to see more detail.

Jobs and Batches Explained

A Batch can be viewed as the engine that runs jobs. Jobs are assigned to a Batch, which is then run to process the jobs within. A job not assigned to a Batch will not perform its defined tasks. An empty batch of jobs will simply sit and wait for jobs to be assigned.

In most migrations, just one batch is usually needed (can contain multiple jobs). The most common reason to create multiple batches is either geographic or bandwidth segregation. For example, if you are running a PST migration and want PST files collected from various sites on your network, running a Batch closer to the source PST files in each location would make better sense than it would to centralize the Batch.

image.png

In its simplest form, a job can be viewed as moving data from one source to one target.

Monitoring Migration Jobs

Once the jobs have been created, and the migration is running, you can go into specific jobs to see detailed Job statistics at any point.

To do this, follow these steps:

  1. Go to the Management and Reporting tab and click on your Batch. Click on the Job ID to see information related to that specific job.
image.png
 
  1. In the Job overview, you will find the source details for the data in that job, where the data is migrated to, and a list of errors and logs that you can use later for troubleshooting if needed.
image.png

The aggregate data is available via the Project Overview tab on the main dashboard.

Retrying Exceptions

To get a full breakdown of exceptions, navigate to Management and Reporting | Reporting | Aggregated Exceptions Report from here; you can manually retry exceptions by clicking the 3-dot symbol next to the relevant exception.

image.png

Alternatively, you can retry all exceptions by navigating to Management and Reporting | Management, selecting the Green burger stack option next to the relevant batch, and selecting Retry Exceptions.

image.png

image.png

When looking at the project overview, you can click on items that require attention/queued for retry to see a breakdown of those items.  You should not be concerned about Queue for retry, as these will automatically retry until successful.

Basic Troubleshooting

If you encounter any errors with some items during the migration, please raise a support ticket with Mimecast. We would advise, unless the migration is halted, to wait until the end of the migration and raise the errors in one go (this just saves going back and forth throughout the migration and instead resolving in one go).

To raise a support ticket, see the article: Simply Migrate: How to raise a Support Case

Next Step

See Also...

Was this article helpful?
1 out of 2 found this helpful

Comments

0 comments

Please sign in to leave a comment.