It is highly recommended that you implement the latest version of Reload. Applying the latest version of Reload (25400), is very simple. If you have Reload 2.5, then go to your Reload server's Web Administration page, and follow the simple steps in the Tools|Upgrade section. If you do not have Reload 2.5 yet, then you should refer to the article below about Reload 2.5:

http://www.gwavanation.com/node/508

Below is a description of the fixes and small enhancements that are included in the latest version of Reload 2.5.

[ Aggressive Backup Recovery Routines ]

This support pack fixed several smaller bugs, that most customers never experienced. However, with the help of a customer in South Africa, Reload has now been designed to be a lot more aggressive about getting backups in not-so-favorable network conditions.

[ Disaster Recovery Migration is now Perfect! ]

A customer in England discovered a small bug having to do with path case in the Reload Disaster Recovery Migration wizard. Outside of that, the customer tested every aspect of Disaster Recovery and it is all working well.

[ Big System Enhancements ]

There are a few small enhancements that I couldn't help but squeeze in. They were largely because of an implementation of 5 Reload servers at an 18,000 user health care firm in the United States. Here are the enhancements that I implemented as a result of that visit:

1.Added the ability to pass the login credentials for the Reload Web Administration interface right on the URL line with the user and password keywords. For example:

http://reload.gwava.com:5555/status.gt?user=reload&password=letmein

2.Modified the Reload Web Administration interface so that web pages from the Reload server are titled in such a manner that the server that is hosting the web page is prominently displayed. This is particularly helpful in environments in which there is more than one Reload server to keep track of.

3.Added a section at the Home screen of the Reload Terminal Administration utility that identifies the Reload server's name. This is particularly helpful in environments in which there is more than one Reload server to keep track of.

[ Disaster Recovery Failover Enhancement ]

I've been working with a customer recently with their GroupWise system on the Linux platform. Sometimes, the GroupWise on Linux POA or MTA will just unload. It's very random and difficult to troubleshoot. We made a script to resolve this issue. I got to thinking though, if a customer were to use the Disaster Recovery Failover feature in Reload, and then while the Reload server is hosting the live post office or domain, and the POA or MTA on the Reload server were to just unload, there's nothing to cause it to load again, unless the administrator took some action. Well, no longer. When a Reload profile is in Disaster Recovery Failover mode, and a POA or MTA just dies out, within two minutes at most, the POA or MTA will be loaded back up.

[ Retain's New Best Buddy ]

The Retain team and I have been working closely together on the Reload to Retain integration. There have been some minor tweaks to the Retain API and the next release of Retain will have a very direct tie into Reload. The positive implications of this integration are multi-faceted and powerful.

[ Two-Minute Quick Tour ]

When customers set up Reload, and are able to restore e-mail in just two minutes, they often walk away from Reload floating about two inches above the floor shouting Reload's praises. But there is so much more! Reload has an animated Quick Tour module that has been added to the documentation to try and help customers acquaint themselves with some of the other features such as:

1.Backup of GroupWise domains
2.Disaster Recovery for post offices and domains
3.Off-Site Disaster Recovery for post offices and domains

Now, I'm off to my coding cave, working on Reload 3, wait 'til you see what's coming, there's something for everyone!