Simply Migrate - Migrating GFI Data to Mimecast

This article provides Mimecast Partner Administrators steps on how GFI data can be migrated to Mimecast using Simply Migrate. 

Prerequisites:

1. Determine where the GFI DBs are located. This is the MarcSettings file (.xml in the GFI server, within the data folder) 

GFI environment: For the service user the application is running on, the system admin of the instance, leaves the authentication fields empty so it will use Windows authentication in the background.

Creating Jobs:

From the UI, there are two ways to create jobs. The first is upon initial installation, as described below: 

1. Following the initial installation, the Wizard will prompt the administrator to select the Source. If the product has been set up and initialized, the administrator will need to start the Job Wizard from within the Batches and Jobs view.
2. Select the Green List icon on the Batch line that the administrator wants to create the jobs, then select Job Creation Wizard from the list.

 

3. Administrators will see the Source selection. For the purpose of this article, we will be choosing GFI as the data source. 
4. Bring up the sources configuration window by clicking on the gear icon below the drop-down, or by clicking on the gear icon in the top right corner of the screen.
5. Once again, select GFI from the drop-down and enter the drive or UNC path to the GFI data. The location of the MarcSettings file (it’s a .xml in the GFI server in the data folder) is required at this point.

• Copy the MarcSettings file to the SM app server, and point towards that. The administrator may need to replace the bin path in the MarcSettings with the UNC path that the server can access, as it will be local and will need to be mapped. The administrator can either map the drive or get the bin path changes as well as a copy of the MarcSettings file.  

Ideally, the credentials used to run SM have rights to the GFI environment. If this is the case, it is best not to use the credentials and leave this blank. This option should be used only when the customer has configured local credentials instead of AD credentials. Credentials should only be added if they are different from the login account or unable to give the login account the correct rights/access.

7. From the job creation wizard screen, set the maximum number of Zips per job to one.
8. Click next. At this point, the administrator will be presented with the list of files found.

• In the banner above the list, the administrator can filter a date, list of jobs and handle Bad address resolution.
• These controls are seldom used; however, an administrator will be prompted about date filters once Create Jobs is selected. 
• Filtering the jobs will only change the administrator's view of the jobs when they create them; Simply Migrate will attempt to create jobs for ALL ticked items, not just those visible in the filter.

9. Click Create Jobs. This will prompt the administrator with some information and the option to select a date filter as shown below.

At this point, it is recommended that the administrator verifies that the number of jobs being created is correct and ensures that you don’t require a date filter.

10. Click Create the jobs.

Jobs will be created and a tick will be shown in the Job Status, next to all the source files that have been selected. The GFI source jobs have been created.
 

Error Messages After Job Creation

Once the jobs are started, Simply Migrate could return a status message informing that is was unable to retrieve certain items from the GFI location. A pop up stating "Failed to retrieve item from Gfi. End of stream" will appear. This error message means that the source data failed or is not retrievable. Therefore, it is critical to identify the location path.
hey
In this case, the administrator should do the following:

1. Run the jobs for a second time, ensuring that the track changes/trace logs are enabled. 
2. Review the logs, checking for failure(s). 

• For the specific item(s) that failed, the location path will be shown. This can then be used to find the item in the original GFI location/database.

Should the administrator be unable to locate the item in the logs, the below can be done:

• In the xml file path: replace the “d:\” reference with “\\servernane\sharenane"