The question is 'why' do 'you' use the GW archive function? What I see in the field is that there was never a really good reason users used this function other then 'cause it's there' and think the messages are save since those are archived. This GW archive function not only limits you in your Search, but also there is the risk of file corruption, it makes your data set even bigger (the GW data store gets smaller but the total amount of data to backup gets bigger), user could loose the archive (case local on laptop), users could have multiple archives (case archiving not configured right; confusing and user think they loose messages), you cannot access you archive remote with WebAcc or with a mobile device mail App. Basically this archive is not a good solution for the anywhere access we need today.
The better way to solve this problem could be to use a real archiving solution like GWAVA Retain which has the ability to archive all your messages and allows you to search those form anywhere. This may be a too expensive and feature rich solution for part of the GW customers.
From a GW perspective I would like to see is an 'Archive Postoffice' function where my post office now 'just' runs and separate PO instance on an 'appliance' with a lot of storage on the same server as the PO is running.
If I as a user would select 'Archive' from a web/desktop client the message gets archived not locally to a file but to the PO-archive service. As this PO Archive system is Online:
* it is searchable and could be 'easily' integrated with the user PO search index; if my PO knows there is a PO Archive it could merge that search index
* allows for archive/restore actions; these 'functions' are already in the PO and client code as they are also leveraged by the offline archive, the restore area and Reload/Retain solutions.
* could perform 'continuous archiving' as a PO shadow system, archiving all in and outgoing messages.
* could even replace the PO if it is lost.
This would create a simple and very usable archive for most customers leveraging technology already in the Client and Postoffice agent without the whistles and bells of a Retain solution.
Technically I think this could look like;
* the PO gets a seperate IP and path
* the PO gets an Archive flag, so it does not route messages; if you replace the IP and the archive flag it gets the production PO 'identity'.
* as it has the same 'structure' as the parent PO it knows of the same users and saves the messages ('archive') in the same structure keeping the needed diskspace as low as possible.
* as it is a PO with an archive flag regular management and maintenance tools can be leveraged
by: Sebastiaan V. | over a year ago | Agents
Comments
Archive is sadly lacking functions.
Built-in Archiving is a joke. Novell never took it seriously.
There are a couple of options like GWAVA. Bust some of these only want you business if you have 100's or 1000's users.
A PO Agent based Archive has been suggested before.
May be MF could offer this as a ADD-ON !!
Hi Bas, yes I know this thing has been discussed in the past. Reality is I still see a lot of customers struggling with this Archiving-thing. I believe a reliable and well integrated online archiving module in GW would benefit those customers not willing (or able to) invest in a 3th party solution that does a lot more compared to what they need.
-Sebas