Disaster Recovery

There are two basic scenarios for Disasters: you lose the server or you lose the site.

It is vitally important to test your disaster plan before a disaster hits, and it needs to be run at least whenever you make a major change on your network. Because it is never just the Reload and GroupWise servers that are involved. There is the DNS server that needs to be updated so it knows that the Reload server is now the POA. The Firewall will need to know that it has to allow mail to flow to the Reload server. If it is just one POA that went down, GroupWise will need to know that Reload is now active too.

Server disaster

A server disaster is when a/the GroupWise server goes down, it may be a disk failure or just the database becoming corrupt.

If you have to build a new GroupWise server, that is okay since Reload can pick up the load and then migrate the data to the new server. If the live server is still viable, contains data, and has been repaired you can set Reload to use the live server as a Restore Area and merge the data, by having the users go to their restore area and migrate the data themselves.

Site disaster

You've lost your main datacenter to fire, flood or something big. Hopefully you have an off-site business continuity facility setup somewhere. With Reload's EC module it is easy to have a second Reload server replicating data to the off-site location.