Jobs and Batches Explained

Detailed Description

You’ve installed Simply Migrate Management Shell, now all of a sudden we are telling you to create jobs and batches, but it would help if we took a few minutes to explain what they are.

What Is A Batch

  • A Batch can be viewed as the engine that runs jobs.
  • Jobs are assigned to a Batch and that batch is then run to process the jobs contained in it.
  • A Job that is not assigned to a Batch will not perform any of its defined tasks.
  • A Batch that is empty of jobs, will simply sit and wait for jobs to be assigned to it.

The most common reason to create multiple batches is either geographic or bandwidth segregation. For example, if you are running a PST migration, and you want PST files collected from various sites on your network, it would make better sense to run a Batch closer to the source PST files in each location than it would to centralise the Batch.

A Batch is created using the New-SMBatch cmdlet, and a Job is assigned to a batch using the BatchID paramater.

The following example will create a Batch with a name, “My First Batch”;

PS C:\Program Files\Simply Migrate>New-SMBatch -BatchName "My First Batch"

What Is A Job

In its simplest form a job can be view as a task of moving data from one source to one target.

For example, a job could be a PST file to a Mailbox, Fileshare to a OneDrive Account using using the New-SMJob cmdlet.

Another example, is to create a job that migrates a PST file into a users Online Archive Mailbox the following cmdlet can be used. Note that a BatchID is specified in this cmdlet and that is discussed in the next paragraph.

PS C:\Program Files\Simply Migrate> New-SMJob -Source PSTFile -SourceInput 'D:\My Fies\My PST File.pst' -Target Exchange -TargetOutput -TargetCredential (Get-Credential) -BatchID 1