MailMarshal (SEG) Disaster Recovery with a Warm Spare Array Manager

This article applies to:

• Trustwave MailMarshal (SEG)

Question:

• How do I prepare a MailMarshal (SEG) environment for DR?
• How do I maintain a spare Array Manager and database for MailMarshal (SEG)?

Procedure:

If SEG is installed as an array with separate Array Manager and processing nodes, you can use this procedure to maintain a warm spare Array Manager and database. The Array Manager can be used to manage the existing processing nodes.
This article describes the basic steps required. For details of configuration backup and restore, see other SEG documentation.

1. The DR environment must have a separate SQL Server. For the highest degree of recovery, mirror the production SEG database (and MailMarshal (SEG) 10 Config Service database) to the DR SQL server. At a minimum, keep frequent backups of the production database(s) and restore them to the DR environment.
2. Frequently back up the SEG configuration and all related items to the DR environment or a safe location. Ideally copy the configuration each time you commit it.
3. In the DR environment, install the Array Manager (identical version to the production instance).
4. On the Database window of the Installation Wizard, enter a temporary database name. Do not select the production SEG database or mirror. Other configuration details are not important at this point. Configuration will be overwritten when you activate the DR instance.

   • Note: A temporary database is needed to allow you to safely restore production configuration to the DR instance.

5. Stop the DR Array Manager.

To activate the DR instance

1. Stop any mirroring of the SQL databases, or ensure the latest backup is restored to the DR SQL server.
2. Start the DR Array Manager (and MailMarshal (SEG) 10 Configuration Service website), pointing to the temporary database(s).
3. Restore the latest configuration backup from the production instance. Include any related files that may not be part of the XML configuration (such as custom file type settings).
4. Use the SEG server tool to connect to the DR copy of the production database. In MailMarshal (SEG) 10, use the Config Service Admin Tool to connect to the DR copy of the configuration database.
5. Ensure all nodes are rejoined to the array.
   • If node information in the production database matches the running nodes, this should not require any further action.
   • If necessary, you can rejoin nodes using the server tool.
6. If you use DR versions of LDAP servers, after the DR instance is running you may need to update the details in the SEG LDAP connectors.
   • Do not attempt to maintain multiple connectors that retrieve the same groups.

Notes:

• A simple way to maintain high availability of processing ability is to maintain some live processing nodes in each location (production and DR). Allow some spare capacity.  
  • Configure all the nodes in the production Array Manager.
  • If the production Array Manager is unavailable but the nodes are available, all nodes can be managed by the DR Array Manager.
  • If SMTP connectivity to nodes in one location is lost, nodes in the other location will continue to process mail and can be managed by the available Array Manager.