How to Move Reload to Another Server

Customer wants to put Reload on a higher performing server without losing his profiles/backups.

There are 6 main steps in moving Reload to another server.   This article does not explain the steps in depth but will reference other resources that do for some of them. 

1.  Install Reload on the new server.

2.  Disable all of the backup schedules.

3.  Move the existing Reload profiles to the new server.

4.  Delete and re-create the POA startup files.

5.  Update the Postfix mailer.

6.  Uninstall Reload from the old server.

The last section of this article only applies to those who have configured intra-day backups in the crontab file.

Install Reload on the New Server

1.  Follow the steps in the "Software Installation" section of the KB article, "Implementing Reload for the First Time..."

2.  Copy the following directories (and their subdirectories) from the old server to the new one:

• /opt/beginfinite/reload/conf
• /opt/beginfinite/reload/license

3.  Copy the main Reload configuration file:  /opt/beginifinite/reload/gwavareload.conf

NOTE:  If your post office and/or domain is on a Linux server, make sure that the export for their directories allows the new Reload server to connect to the export.  When setting up an export in NFS Server (in YaST), it provides a "Host Wild Card" field.  By default, it populates that field with an asterisk (" * "), which means any host can access that export; however, some administrators type in the IP address or DNS name of the Reload server for security reasons.  If you did this, that will need to be updated to reflect the new Reload server's IP address or DNS name.

Disable the Backup Schedules

You'll need to disable all of the backup schedules for all profiles and for all backup job types (Standard, Portable, and Tape Backup).  This is done from the main profile administration menu.

For example, for the Standard backups, select Standard | Schedule and press ENTER on option 2.  This is a toggle setting, so pressing ENTER when its enabled will disable it and vice versa.

Do the same for the Portable and the Tape Backup (if used).

Move the Existing Reload Profiles to the New Server

This step assumes that the new Reload server has already had its storage for the profiles configured prior to this step.  For example, if the profiles are being stored on a SAN, the SAN volumes have already been mounted on the new server. 

Copy the FULL path to the profiles.  For example, if my profile path were /data/postoff1, then I should copy that exactly to the new server as Reload has that full path stored in the profile's configuration file (/opt/beginfinite/reload/conf/[profile].conf.  This can be changed, of course, but it adds complexity as you'll also have to modify the conf file.

Delete and Re-create the POA Startup Files

If you have configured the Access POA, the Restore POA, or the Disaster Recovery POA, you'll need to re-configure those with the new IP address of the Reload server; then, it would be best to have Reload delete and then reconfigure the POA startup files.

From the main profile administration menu in the Reload console:

• Access Mode POA: Access-Backups | Access-Mode | Delete-Access.
  
• Restore Mode POA:  Access-Backups | Restore-Mode | Delete-Restore.
  
• Disaster Recovery ("Live") POA:  Disaster-Recovery | Configure | Failover | Disaster Recovery POA Settings | Delete.

Update the Postfix Mailer and Web Administration

On the new server, you'll need to configure Postfix to point to your GWIA.  See the "Mailer Configuration" section of KB article, "Implementing Reload for the First Time..."

You'll also need to go to the Reload web administration tool and update a couple of preferences:

• Reload server URL for the mailer:  (Click on the Configure tab and select "Reload Mailer Preferences, Help & Troubleshooting")
• Disaster recovery plan document URL (Click on the Configure tab and select "Web Administration Preferences").

Uninstall Reload From the Old Server

1.  Stop the Reload daemon.

• Launch the Reload administration console.
  
• Stop the GWAVA Reload daemon auto recovery: System | Control | 4
  
• Now go to 3 "Stop GWAVA Reload Daemon" and press ENTER.

2.  Uninstall Reload

• Type:  rpm -e beginfinite-reload; or,
• Change to /opt/beginfinite/reload and type:  ./uninstall

Intra-day Backups

If you configured intra-day backups, those need to be commented out or removed on the old server.  See "How to Disable Intra-day Backups".

Then, on the new server, re-configure them.  See "Creating Multiple Post Office Backups Within a Day (Intra-day Backups)".

This article was originally published in the GWAVA knowledgebase as article ID 2172.