By Tay Kratzer

Good news: with the latest support pack of GWAVA Reload (released yesterday, July 31st) SUSE Linux Enterprise 10 is now supported. I have also tested GWAVA Reload with GroupWise 7 Support Pack 1, and it is also fully compatible with GWAVA Reload. In fact, GroupWise 7 Support Pack 1 made some great strides from a third-party API standpoint that GWAVA Reload will be leveraging in the future.

Installing the latest GWAVA Reload support pack is VERY simple. Here are three different methods of installing the support pack:

1. From the Reload server's web interface, choose Upgrade|Upgrade Now.
2. In Reload Administration select System|Tools|Upgrade|Upgrade Reload
   Software.
3. In a terminal session at the Reload server type in the command:
   
   reloadu

There are no prompts to answer, and the Reload Upgrade utility will
just download and install the latest Reload support pack.

The best new feature of this support pack is that Reload now uses a
dual threading model that speeds up most standard backups anywhere from
15% to 30% on average. Below is the complete list of fixes and
enhancements to GWAVA Reload Version 1.7 Support Pack 2

GWAVA RELOAD SUPPORT PACK # 2

Enhancements

• Added "High Performance Backup" functionality to the Standard Backup
  process by adding one additional thread. Most customers will see a 15%
  to 30% speed increase as a result of this added functionality.
• Added the ability for the Reload Upgrade utility and the Install
  utility to upgrade the GroupWise Integration Software (GroupWise DBCOPY
  and GroupWise Agent software). This way when if new GroupWise software
  is shipped from Novell, customers can have Reload download and install
  the software to the Reload server.

Compatibility and Bug Fixes

• Designed GWAVA Reload to be fully compatible with SUSE Linux Enterprise
  Server 10.
• Made the GWAVA Reload Administration icon compatible with the GNOME
  desktop. If the customer is using a GNOME desktop, there is now an icon
  that is created for Reload Administration.
• Fixed problems with backing up Document Management. This included
  incorporating the GroupWise 7 SP1 GroupWise Integration Software (DBCOPY
  and GroupWise Agents).
• Resolved file selection menu issues that were likely to crop up in a
  small terminal or SSH session. Made the file selection menus dynamic
  based upon the screen size.
• Modified the Reload Daemon load script to test for and correct
  scenarios in which the Reload Daemon might be loaded multiple times.
• Fixed a small defect in the Diagnostics tool. Now the Diagnostics tool
  will report the standard output information of the GroupWise DBCOPY
  utility.
• Tested for compatibility with GroupWise 7 Support Pack # 1.

Documentation Enhancements and Fixes

• Updated the documentation with regards to Disaster Recovery and
  migrating data back to the live server.
• Updated the documentation with accurate information about incorporating
  SSL certificates in conjunction with LDAP authentication.
• Updated the documentation to include more concise information with
  regards to using a cron executed process.
• Made several small documentation fixes.

Heads Up SUSE Linux Enterprise 10 Administrators:

BASH Exit Codes Change With SLES10

GWAVA Reload has some components that are BASH shell scripts. Aspects
of these BASH shell scripts were looking for exit codes. GWAVA Reload
wasn't immediately compatible with SLES10 because of different exit
status behavior in SLES10. Here's some interesting information I found
out about SLES10 with exit statuses.

On SLES9 or Open Enterprise Server (OES) if you do the following command:

ls <a file that does not exist>
echo $?
1

The exit status is: 1

On SLES10 if you do the following command:

ls <a file that does not exist>
echo $?
2

The exit status is: 2

If you have a BASH shell script that uses exit statuses in the
following manner:

declare -i EXIT_STATUS=0

ls <some file>
EXIT_STATUS=`echo $?`

if [ $EXIT_STATUS -eq 1 ]
then
<some action>
etc

This routine will work fine with SLES9 but not with SLES10, because the
exit status will be 2 instead of 1

You will probably want to change the routine to be as such:

declare -i EXIT_STATUS=0

ls <some file>
EXIT_STATUS=`echo $?`

if [ $EXIT_STATUS  -ne  0 ]
then
<some action>
etc