Difference between revisions of "Reload for GroupWise Disaster Recovery Configuration"
(→Two Type of Disasters) |
|||
| Line 16: | Line 16: | ||
A simple system has a Post Office, and an offsite Reload server. To fail over from GW to Reload you have to set up a number of things: | A simple system has a Post Office, and an offsite Reload server. To fail over from GW to Reload you have to set up a number of things: | ||
*hostnames for the PO, Reload, MTA and GWIA | *hostnames for the PO, Reload, MTA and GWIA | ||
| + | *GW Clients set up to use hostname | ||
*DNS A record names | *DNS A record names | ||
*Binding multiple NICs to the Reload server | *Binding multiple NICs to the Reload server | ||
Revision as of 23:08, 6 February 2017
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.
A simple system has a Post Office, and an offsite Reload server. To fail over from GW to Reload you have to set up a number of things:
- hostnames for the PO, Reload, MTA and GWIA
- GW Clients set up to use hostname
- DNS A record names
- Binding multiple NICs to the Reload server
