I am testing server-based archiving in a policy setting. If a user has this setting, and I have mail db quotas set set for let’s say 100MB, and the archive policy setting (server-based) is set to archive everything older thatn 30 days, what happens if that user reaches the threshold before the 30 days? Then they are constantly receiving threshold warnings, and/or sent mail and attachments are not being saved to the db. Manually archiving is not a option due to server-based archiving being enabled. One way I have found to get around it is to simply cut the email from the mail db and paste it into the archive mail db. This seems like too much work for the user and will probably end up on my plate. Does anyone know of a programmatic way, like the archive now option does for manual archiving, when using server-based archiving in a policy? Thanks in advance for your help and suggestions.
Subject: Archive policy question
I setup an archiving policy for a selective few of my users (as they were geogrpahically dispersed, and I need them to archive their mail).
When I created the policy the first time, I setup the archive so it was archived to the server. This way I was able to create the archive using the compact -a command on the console. However, as stated the user could not archive from the workstation.
After this was setup, I went back and modified the Archive policy, and change the following setting.
Archiving will be performed on:
User’s Local Workstation
from the original entry
Server
Now that the archive was setup, the user was able to selectively archive documents, or run the archive now option from the actions menu, archiving documents based on the agreed criteria.
HTH.