I have long advocated at least an option for the server side model for Archiving. Currently, archiving is a client-side operation only - the server side has no knowledge of the archive's existence. Adding the ability for server-side archiving would not necessitate removing archiving functionality from the client for those sites wanting to continue in that model.
However, what a server-side option would allow is the ability to for a user to keep as much email allowed by local policy that will be available to the powerful GroupWise search features. One of the greatest benefits to administrators is the ability to reduce the nightly and weekend upkeep processes that current archiving provides, therefore, any server-side archiving must also reduce those upkeep processes.
I contend that server-side disk savings can be achieved as well. We are currently Reload customers for backup and restore purposes. To facilitate ease of restoration, we keep 1 to 2 weeks available in the Reload areas. That results in 5 to 6 times the size of the post office in Reload disk space. The thought here is that a smaller active post office would also result in a smaller Reload system.
The key is that the Post Office Agents are aware of an archive store (that could be on tier 2 storage) for searching, etc, but not a part of the scheduled upkeep processes. However, a separately scheduled upkeep process would be necessary most likely.
From a user's perspective, all the items are in a cohesive environment. From an administrator's perspective, we could finally get users to actually archive which would result in leaner and meaner post offices.