Probably the #1 question when people consider what they need to do

to implement a Reload server is, "How much disk space do I need?"

There are simple forumlas to use and more complex ones.

Here's the simple formula 2.5 Times the size of the post office for every week you want to keep on the Reload server.

So if you have a 100 Gigabyte post office, and you want to keep around two weeks of backups, then you generally want about 500 Gigabytes of space on the Reload server. However, there are some other things to consider, which is why I encourage you to read on.

Let me try and explain how the disk space is used first, then we'll work on formulas.

Reload is really simple to set up. A lot of customers just use the wizard, do some backups, restore some e-mail and they walk away from the Reload server feeling as though they are about two inches off the floor.

There is so much more that you can do with Reload though with a little bit more effort.

If you are a consultant, or new to Reload, here is a high-level list of things you should consider doing when implementing your Reload server:

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

If you do not have a consultant you are welcome to contact your GWAVA Salesperson for a quote for off-site (remote access) consulting with me (Tay Kratzer) the developer of Reload.

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.

Now that you're ready to move to GWAVA 4, one of the most common questions that comes up is "how do I migrate my GWAVA 3 configuration?".

That's a great question and we even have a wizard built in to GWAVA 4 for this.

After the discussion, you will see why we generally recommend the you start up a new configuration rather than importing an old one.

Let's think about this for a moment and see what exactly we DO have in the GWAVA 3 configuration that we would want to migrate.

1) spam configuration. You've spent a lot of time, perhaps, in optimizing your antispam engine. There are two points about this.

While GWAVA 4 on NetWare is still on beta, some clients would like to take advantage of the tremendous power of GWAVA 4 today.

GWAVA 4 is available NOW for Linux and as a GWAVA customer, you're entitled to it if your maintenance is up to date.

This is also a great way to simply test drive GWAVA 4.

We will be taking advantage of GWAVA 4's new GWIA scanning ability to do this. Scanning at the GWIA has a lot of advantages for Internet mail. For scanning between post offices, you will still need to use GWAVA's traditional MTA interface.

So let's begin.

Start by setting up a Linux box. It doesn't have to be anything special. I would recommend using SuSE Linux Enterprise Server 10. (SLES 10). It's easy to set up and very reliable.

Here is a link to a story by Associated Press about a top spammer, dubbed a "Spam King" who was arrested yesterday.

Technically, it outlines how this spammer has been using all of the latest techniques to get his messages out - techniques which are effectively controlled by GWAVA 4.

What I find interesting is that this person made over 3/4 of a million dollars spamming and his fine is only 1/4 of a million. It's a lot of money but that would leave him with a half million dollars in the end.

So there is really no need to wonder what motivates spammers. We just need to continue to protect ourselves against fraud artists like them.

Here's a list I am building (work in progress) for consultants who are implementing Reload. This list will grow over time, and is somewhat in chronological order.

This contents of this article are now updated, and kept in the GWAVA Support Knowledgebase. Please see the link below:

http://support2.gwava.com/kb/?View=entry&EntryID=256

Implementing Reload for off-site disaster recovery

I've worked with two customers as of late in conjunction with the customers
implementing Remote Reload profiles. I also was training a GWAVA reseller on
the East coast of the U.S. and was explaining just how he should implement
Reload for maximum gain for disaster recovery purposes for a large bank
implementation.

First off, an explanation of this concept. Disasters can be of two different
kinds. There are server disasters, and site disasters.

[ SERVER DISASTERS ]
Server disasters are more common and they can include things such as hardware

This is the latest Powerpoint presentation for Reload v2.

This is the form specifically for evaluating the Speakers at GWAVACon.

This Evaluation form is used for the entire conferernce. This is not the Speaker Evaluation form.

GWAVA Announces Disaster Recovery for Novell GroupWise

Reload v2 helps keep email flowing in times of crisis.

February 27, 2007 Montreal, Quebec, Canada – GWAVA, Novell’s largest GroupWise partner, announced today the launch of Reload v2, Disaster Recovery for Novell GroupWise.

Reload is the first disaster recovery solution focused exclusively on GroupWise. Reload allows email administrators the ability to recover data immediately from backup and to implement push button disaster recovery in times of crisis.

“As a law firm, our focus is ensuring that our data is never lost,” says Dale Qualls,

This is the latest version of the Reload v2 Datasheet.

The focus of the data sheet and the focus for Reload v2 is around Disaster Recovery rather than the ability to restore single messages. Although restoring single messages is still a big selling point, the Disaster Recovery speaks better to Executives needing to sign off on the purchase.