* Limit of one free 30-station Desktop Multiplier™ licence per university, college or school district. Hardware not included. First 30 customers will receive a free 30-user subscription to SUSE® Linux Enterprise Desktop. Additional conditions apply. See website for full details.

Deadline: November 30, 2008

Do you need to know who is sending e-mail to their personal e-mail account or just simply change a vacation rule, Vertigo is the program for you. Please join Ron Gardiner for a brief webinar on how set up mailbox management with Vertigo.

Key Vertigo Features
• Create, Disable and Delete Rules
• Change user Proxy Settings
• Assign Mailbox Cleanup Options
• Centralized Management of all GroupWise Clients
• Change Junk Mail Settings
• Identify "Forward All" Rules to Personal Mailbox Accounts
• System-Wide Reporting on Rules, Proxy Settings, Client Options & More

One of the most common design considerations for archiving is where to store the data.

This seems like a fairly simply solved issue until you run into issues of scale. Quantity.

Some file systems have definite limits on the number of files you can store, on the total size of the volume(s) and whether or not you can just add to it.

It is vitally important that you overestimate your total storage needs before choosing where to store your data.

If you choose a file system with a hard limit and a year or two down the road, you run out of space ... you might be unable to continue to use your system. You might even have to create a new archive. That diminishes the usefulness of having everything in one place.

[ Meat n' Potatoes of this Article ]

1. Apply patches from Novell to the Reload Server

[ The Problem ]

Recently a customer in Chile was implementing Reload, the GroupWise Backup Solution. They were putting Reload through the paces backing up a GroupWise post office on NetWare, and then migrating it to a Linux server. The migration was taking way too long, several hours, and it was only a 60 gigabyte post office.

[ The Solution ]

Then the customer used "rug" (the command-line interface to ZENWorks Linux Management) to upgrade both of the OES servers (the Reload server and the destination Linux server) to the latest support pack and that was the trick. Things really took off then. Reload migrated the GroupWise post office from the Reload server to the Linux server in 2 hours. Pretty slick!

Check out this recorded webinar given by Ron Gardiner, Project Manager for GWAVA. Ron walks you through an installation of GWAVA 4, pointing out insightful hints and tips for a successful installation.

Direct link to recorded webinar
http://www.gwava.com/resources/media/GWAVA4Installtion882007/GWAVA4Installtion882007.html

Link to recorded webinars for GWAVA
http://www.gwava.com/events/webinars_recorded.php

For those of you who run a 'BlackBerry Enterprise Server' ... Novell released 'GroupWise 6.5 Support Pack 6 API Revison 1'. This patch contains two files to resolve issues with the GroupWise 6.5 client and the BlackBerry Enterprise Server. This should only be applied if you are running into issues with the BlackBerry Enterprise Serve hanging when running with the 6.5.6 or newer clients.

Reload has a Simple Scenario Disk Sizing Calculator. You can find it at http://reload.gwava.com/post_office_size.htm.

When deploying Reload as a hot backup solution for GroupWise, proper disk storage planning is key.

Reload differs from a traditional backup solution in the fact that its data is always live, ready to be accessed at a moments notice. Unlike tapes which are loaded and restored, Reload stores backed up data as "hot backups" on the Reload server's disk drive. Reload is designed to hold several weeks worth of GroupWise content. The number of weeks of backup is decided by the GroupWise administrator. Before deploying Reload, a GroupWise administrator decides how many weeks of content is needed, checks the size of their GroupWise Post Offices, and then performs a simply calculation to know how much disk space Reload will require.

[ Meat n' Potatoes of this Article ]

1.Add additional GRE_BLOBS-Threads, up to 10 threads

2.NetWare customers consider enabling the NetWare NFS server, and modify the Reload profile to backup the GroupWise post office as if it is on a Linux server.

[ Increasing GRE_BLOBS-Threads for Backing up the OFFILES Directories ]

Because of a unique threading technology, Reload is the fastest backup solution available for GroupWise. How fast? you ask. Well for example; at the State of Utah, there is a GroupWise post office with 1,100 users on a 70 Gigabyte post office on a Linux server. Their nightly Reload backup times are just under 13 minutes. And remember, that because of Reload's unique architecture, each Reload Standard (Incremental) backup is effectively a Full Backup, which only takes about 12% of the size of the post office on disk.