Application settings govern the behavior of the migration process and allow control over various aspects of it. Changes made in this section affect the way the tool will run, including settings which determine the operations that will be performed. Changes made in this section apply to all users and all source and destination platforms.
- Source Migration Platform – G Suite, Microsoft Exchange 2007 or higher, Office 365, Scalix 11, Zimbra, IMAP and Novell GroupWise 6.5.6 or above are supported by the tool. Please select the platform that is to be migrated from.
- Destination Migration Platform – choose from GSuite, Google Vault, Microsoft Exchange 2007 SP1 or Microsoft Office 365/Exchange 2010 SP1
- Enable Multi Server Migration – Enable multi-server migrations using the CloudMigrator migration services, spread across many servers.
- Proxy Type – choose from ‘Default’ or ‘Explicit’. If using the default proxy then the default system proxy, as specified in the Internet Explorer settings is used. To specify a different proxy than the default, use ‘Explicit’ and complete the other proxy settings.
- Default Proxy Settings – click the ellipsis to open the system proxy settings
- Address – specify the address of the proxy to used when using an explicit proxy
- Username – specify the username for the explicit proxy (if required)
- Password – specify the password for the explicit proxy (if required)
Single Server Settings
Single Server Migrations Only
These settings are only applied for single-server migrations. The storage location for multi-server migrations is always fixed and the maximum user migrations are controlled on a per-service level with the service configuration tool.
- Storage Location – choose one of the available options for storing temporary migration data and results. When a location has been chosen, it is recommended not to change it as old records may become orphaned.
- Storage Location Folder – when a ‘Storage Location’ of ‘Other Folder’ has been chosen, you must specify the folder path that the tool will use for temporary data and results. Note that this folder must be writable by the tool. If the folder is not writable the tool may fail to migrate data and errors related to folder permissions may be seen.
- Maximum User Threads – this controls the number of users that are migrated using the tool at any one time. It is possible to process many users at once and when processing completes for any user then another user is processed (so the application does not wait for the processing of all users to complete). Setting this option controls how many users are processed at any one time. This is important as the number of users being processed at any one time will have an impact on network traffic, and on CPU and memory utilisation of all servers and workstations involved in the migration processes. Google can restrict an application from sending too many requests per second and so the number of concurrent users should be taken into account. See the section ‘Getting the Best Performance’ for more details.
- Auto Cancel Period – specify the time period after which the tool will automatically stop a migration. The default is ‘Never’. Note that if this setting is changed then migrations could be prematurely halted if the time period is too low. Use with care, if at all.
- Encrypt Passwords – encrypt passwords in the configuration file.
- Validate SSL Certificates – choose whether to validate SSL certificates or not when connecting over SSL.
- Trace Level – debug tracing of the application is possible, where trace output is written to a file. Logs are kept for the last 10 runs of the application, with the most recent log with a number. Data is written into the trace file in a manner that enables it be imported into a spreadsheet program for analysis. Entries in the log contain the following information:
[Date/Time] [Process Name] [Process ID] [Thread ID] [Logger Name] [Log Level] message
The setting of this option sets the trace level of the applications debug output to one of four levels:
- Error - serious errors only are written to the debug log
- Warning - errors and warnings are written to the log
- Information – warnings, errors and information are written to the log
- Debug – trace, information, warnings and errors are written to the log
Do not set the trace level to ‘Debug’ or 'Trace' for production runs unless advised to do so. The amount of data produced with these levels of trace can be huge and may impact performance when performing large migrations. ‘Information’ still provides information about the runs and will report any warnings and errors.