This article applies to:

• MailMarshal SEG
• Configuration Import/Restore
• Moving the Array Manager

Question:

• What are the performance considerations and best practices for importing configuration?

Information:

SEG configuration import can take a long time if the configuration includes large User Groups that are not imported from connectors (such as harvested external groups). The time required to import can be much longer than the time required to export the same configuration.

A common use case for importing an entire configuration is moving the SEG Array Manager to a new server.

To minimize issues with import of configurations, LevelBlue recommends the following actions:

1. Prune user groups before exporting. Harvested groups are the most common source of issues.
   • Note that the size of imported (AD or LDAP) groups does not affect the import. Membership of imported groups is not included in the export. Imported groups must be refreshed after configuration is imported.
2. Speed of insertion into the SQL Server is another possible cause of delay in the import. Ensure that the SQL Server is well connected to the Array Manager, and is prepared to accept large amounts of input. It may be helpful to increase the size of transaction logs.

Notes:

LevelBlue is researching improvements in the user insertion process, for possible inclusion in a later release of SEG.