This describes leveraging the PowerShell capabilities for distributed migrations.
Configure the Controller, the Agent Database, the Migration Database and provision the Agents from the Email Migrator user interface prior to leveraging the remote PowerShell capabilities.
Extended Cmdlet Parameters
All existing Email Migrator PowerShell parameters will continue to function within the context of a local migration. For remote migrations the same commandlets will need three parameters/switches employed in order to ensure proper migration.
The first required parameter is the path to the previously configured Agent Database. This connection string can easily be obtained from the Job List view of the Email Migrator UI. This path should be represented in the form of a SQL Connection String (the same as JobDatabase parameter).
This parameter represents the name of the registered certificate that exists at both the Controller and the Agents and that will be used for encryption and decryption.
Once both the Agent Database and the Certificate parameters have been provided, each migration cmdlet needs to be specified to run remotely or run locally.
The default behavior is to run a job locally, however enabling the switch "RunRemotely" queues the current job for remote execution.
Enabling this switch without setting both the AgentDatabase and Certificate parameters may result in unexpected behavior that would be considered undesirable.
Example of new parameters:
-AgentDatabase "Data Source=TEST;Initial Catalog=Jobs;Integrated Security=true;" -Certificate "TestCertificate" -RunRemotely
In This Section
Metalogix Email Migrator has the ability to generate a zip file associated with a single job item. The purpose of this zip file is to facilitate troubleshooting by collecting typical troubleshooting data that you then send to support when creating a support ticket.
The high-level data collected in the zip file is as follows:
·Application Settings files.
·Product information (product version, license, etc.).
·Information about the job item (what action settings were set, the job log, etc.).
Please review the contents of the zip file before sending it to support. While this feature attempts to only collect non-sensitive data, no guarantees can be made - it is up to you to ensure that any files in the zip folder are stripped of any confidential data. Regardless, Metalogix assures that the contents of the zip file will only be used for troubleshooting the
associated support ticket .)
Creating a Support Zip File
To create a support zip file, do the following:
1.In the Job List, select the job for which the zip file is to be generated.
2.In the main UI, click the Help ribbon and then click Create Support Zip File. The Save As dialog appears.
Tip: Alternatively, right-click the selected job and select Create Support Zip File in the context menu.
3.Select the filepath in which to save the zip file, change the name if desired, and then click Save. The Open Support Zip File dialog appears.
4.If you wish to review the zip file for sensitive information, click Yes to open the zip file. Once you are satisfied with the contents of the zip file, it can be sent to support to aid in troubleshooting.
This section describes the best practice for migration from Barracuda Message Archiver connector. Splitting the migration process to several jobs running in parallel can speed up the whole task. The basic principle is to define migration jobs for individual Message Archiver subfolders or groups of subfolders.
To optimize the migration from Barracuda Message Archiver, do as follows:
1.Create the Barracuda Message Archiver connector in your Email Migrator console (see Connect to Barracuda Message Archiver topic). In the Configuration dialog click the Browse button to the right of the Select folder field. Browse for one of the archive subfolders. Choose subfolder on the level on which you want to define your jobs. Click OK.
2.Similarly, create connections for all your subsfolders in Barracuda Archive.
3.Create the target connector.
4.Back in the Email Migrator console define your migration job (right-click the Barracuda node / select Copy... / right-click the target node / select Paste...).
5.In the Job Configuration dialog specify your settings.