We have set up server based archiving and that seems to be working.Compact -A is run and documents are moved from our mail server to the ‘archive’ server.
The problem is that some users want the ability to archive in addition to the server based (policy) rule.
When they try to archive they get the following error:
Is there any way to have sever based archiving and still allow local (workstation) archiving to the same archive Db?
I have tried a child policy setting but that does not seem to make a difference.
Subject: Server based archiving - no ‘local’ archiving?
Isn’t this going to be very conflicting? To me the problem is more what will the policy be – client base or server base. If your users get what they want then you will have 2 archive sources which are not replicas of each other. Personally I would say do the server archiving, but allow the users to replicate their archive locally.
I would urge them to feel more secure over the server archiving because there is not a backup from user’s local machine.
Does that make sense?
To answer your question: I don’t think you have both. Either you don’t have that server base policy or not. I don’t think you can both.
Subject: RE: Server based archiving - no ‘local’ archiving?
The actual issue here is not the DESTINATION of the archived mail - server or local. The issue is WHERE the archiving is initiated from - Server or local. To re-word the question - from a workstation can a user initiate archiving to their archive database on the server, whilst at the same time can the server also be configured to do this (by running compact -a on schedule)
Such a facility would be very useful because a user could archive their mail when they are ready to do so, but then the server could also do this for them on a scheduled basis. This would ensure more email gets archived - selectively by the user and also based on criteria by the server(eg not modified for x no of days)
From my investigations I don’t think this can be done out of the box. It seems to be one or the other. You can enable compact -a but you need to specify in a policy settings document what the archive criteria are. That policy document will give you a choice of either server or local based archiving (as distinct from the destination archive db which is also local or server - which is where the confusion lies)
If you enable server based archiving in the policy settings and then try to initiate archiving from the workstation it gives you the message that server based archiving is enabled as per the original post.
IF you enable local archiving, you can’t stipulate any server based archive settings for compact -a to pick up, even though the task will still run
It would be useful if you could do both so if anyone knows a way to do this I’d love to know.
Subject: RE: Server based archiving - no ‘local’ archiving?
This is contrairy to my experience. This feature works; - sometimes. we have an organizational policy covering the archive issue. On several workstation I discoverd the the local initiation of an archivation is possible via Actions - Archive - Archive Selected Documents. On other workstations we had the mentioned error message. This is independent of the user ID, as I can archive on one workstation but not on another. And I would like to have this feature for my users, because they wait until there quota is reached before they start marking documents as expired, but the compactor only run once a week and than I get the phone calls. This extra work can be avoided, when this feature is available.