Reload for GroupWise Disaster Recovery Configuration
see also How to Set Up Reload Disaster Recovery
Reload's Disaster Recovery Mode allows the Reload server to take over the duties of the domain, MTA, GWIA and/or one or more POs. This takes substantial time, while it could be done during a disaster it would be best to configure Disaster Recovery prior to an actual disaster, when loss of communications may be an issue.
Two Type of Disasters
When designing your disaster recovery plan there are, basically, two types of disasters to prepare for:
- Server failure
- Site failure
A Server failure is just that: the server fails. The power supply or hard drive system fails and the server goes down and doesn't come back up. A system update goes bad or malware got through.
A Site failure is the server room is no longer functional. There is a power failure, or perhaps the sprinkler system went off by accident or the site was hit by a tornado.
Congfigure Disaster Recovery
This step takes some time to setup, so it is best to do this before the disaster. While it can be done during the disaster it is much harder and longer. If done correctly it will take only seconds to be live on the Reload server.
Configure DNS A Records
You will need to set several A record names in your DNS. This is the one setting you'll have to change outside of Reload during a disaster.
- GroupWise Server. For example, gw100 10.1.1.100
- Domain. For example, gwdom 10.1.1.100
- Post Office. For example, gwpo 10.1.1.100
- MTA. For example, gwmta 10.1.1.100
