Disaster Recovery Migration

Disaster recovery for both GroupWise post offices and domains is a push-button action. There are no decisions to make; no backup sets to combine—just push one button.

When Reload is used as a disaster recovery solution, it will take only one minute for the Reload server to begin acting as a live GroupWise post office or domain. The GroupWise client, along with all other periphery services such as BES, GMS and WebAccess will function with the live post office hosted on the Reload server. 

You can set incremental backups with Reload for once a day or several times a day. Reload incremental backups are usually quick enough that you can back up as often as you feel necessary. Time is the greatest factor affecting how often a backup can be pulled.

When recovering from a disaster, the Reload server hosts the GroupWise post offices and domains. It also hosts Internet mail (the GWIA) and functions as the WebAccess server.

Reload supports an off-site disaster recovery server model. The off-site Reload server pulls changes from the on-site Reload server.

Because Reload supports an off-site Reload server, if the production site were to be completely lost, the off-site Reload server could function as the production GroupWise system. 

Once the disaster is over and a production server is ready for the Reload post office or domain, Reload can help you migrate your data. Using the Reload migration wizard on the Reload server, you can migrate the GroupWise post office or domain back to the same server, a different server, or even a different platform than the platform that the post office or domain originally came from. To minimize downtime, Reload can pre-migrate 90% of the post office while the live post office is still running on the Reload server. Verbose logging helps you track the entire migration process.