BACK
- PUSH-BUTTON:
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
- ONE MINUTE DISASTER RECOVERY:
When Reload
is used as a Disaster Recovery solution, it will take a matter of one minute to
have the
Reload server act 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.
- INTRA-DAY BACKUPS FOR DISASTER RECOVERY
PURPOSES:
Incremental Backups can be pulled once a day, or
several times a day, time is the
greatest factor effecting how often a backup can be pulled.
- TOTAL SYSTEM DISASTER RECOVERY:
The Reload server can host not only GroupWise post offices and domains, but
the Reload server can also host Internet mail ( the GWIA) and function as the WebAccess
server.
- OFF-SITE DISASTER RECOVERY: Reload
supports an off-site disaster recovery server model. The off-site Reload
server pulls changes from the on-site Reload server.
- PRODUCTION SITE FAILURE: Because
Reload supports an off-site Reload server, if the production site were to be
completely lost, the off-site Reload server can function as the production
GroupWise system.
- MIGRATION BACK TO A PRODUCTION SERVER:
After Disaster Recovery when a production server is ready for the Reload post
office or domain, Reload can migrate the domain or post office back to the
production server. Reload can migrate the GroupWise post office or domain back
to the same server, a different server, or even a different platform then the
platform that the post office or domain originally came from. Migration is a simple wizard driven process, and the
migration happens at the Reload server, nothing runs from a workstation for
example. With GroupWise post offices. Reload can pre-migrate 90% of the post
office, while the live post office is still running on the Reload server. This
assures that the downtime for migration back to the production server is
minimal.
BACK