Some of the most common questions we get concern Disaster Recovery.
Our Disaster Recovery product, Message Continuity spools mail when your server is down and delivers it to you when the server is back up. It also allows your users to log in to the Control Console to access spooled mail.
Telling your users about Message Continuity ahead of time and having them set a Control Console password will make the transition during an actual outage go much smoother. Our Email Continuity user guide is a great resource for users getting started with Continuity.
Disaster Recovery can be engaged automatically in the case of an unforeseen issue, or manually in the case of server maintenance. We always recommend that before starting server maintenance customers manually engage Disaster Recovery, this prevents accidental mail delivery before the server is configured to accept mail. Uncheck the box next to “Deliver spooled mail when connectivity is available” to prevent mail from unspooling before you are ready.
Always make sure that your settings are returned to Automatic to avoid any loss of mail during a future event.
A common question we receive is how long to expect the spooling and unspooling process to take. Spooling takes approximately 20 to 30 minutes to start. If connection errors are detected on the server 3 times while attempting to deliver messages, our heartbeat monitor starts testing the server for connectivity every 5 minutes. If after 3 attempts, the server is still not responding, Disaster Recovery starts spooling mail. We continue to check the server every 5 minutes while in Disaster Recovery and when there are 3 successful connection tests in a row, Disaster Recovery starts unspooling. It can take 20 to 30 minutes from the time the server first comes online before the first messages are delivered.
Our team has developed an outline for dealing with a disaster as it pertains to data loss. This document will guide you through planning, preparation and recovery.