Planning Redundancy, Backups, and Recovery

As with any mission-critical application, you want to plan for optimal deployment, redundancy, backup, and disaster recovery for Good Intranet Server. This section describes or references procedures and rules for doing so.

Backing Up Good Intranet

Be sure that you include the server in your backup procedures. In case of a disaster such as server corruption, you will need to restore a copy of the server.

Consider the following to ensure a proper back up of your Good Intranet Server:

• When you first install Good Intranet Server, the server makes a backup of the server configuration file and saves it as default.props. You can use this file to restore the original server defaults if desired.
• As you make changes to server configuration (using the Good Intranet Server Console interface or the config.props file), make sure you keep a current backup copy of the file.
• Make sure users backup critical data on their handhelds using the appropriate backup procedures. For example, on PPC handhelds, use a SD card for backup.
• Make sure you keep a current backup copy of any application properties files (application_name.props) created for the server. For more information about these files, see Using Transformations
• Make a backup copy of the list of users who have been enabled on the server.
• Make sure you keep a current backup copy of files in the push database directory (by default, install_dir/dbdir/push). For more information about these files, see Using Push Technology

For additional backup and recovery procedures in a Good Messaging environment, see the Good Mobile Messaging Administrator's Guide.

Recovering from a Disaster

To start from scratch after a server disaster, follow this procedure:

1. Rebuild the operating system on the server host with the proper system requirements/prerequisites for the server. Use the same server name. It is not necessary to use the same IP configuration.
2. Grant local administrator permissions to the GoodIntranetAdmin account.
3. Log on to the server using the GoodIntranetAdmin account and reinstall server software. Use the same license key, serial number and server name as for the previous server.
4. Start Good Intranet Server.
5. Where appropriate, use backup copies to restore the following files:
• Server configuration (config.props)
• Application configuration (applicationname.props)
• Push database (dbdir\push)
6. You should see all of the users you defined prior to the disaster. If not, re-enable user access to Good Intranet Server.
7. Send notifications to your Good Intranet handheld users. They may receive a message on their handhelds asking them to reconnect to the server.