How to auto purge mail to keep latest one month mail of a replica?

Have a lotus database mail.nsf replica replicate at domino server  A,B and C  version 8.5. How to set auto purge to keep only latest one month mail for the replica at server c but not affect the replica data at server A & B?
litmicAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Sjef BosmanGroupware ConsultantCommented:
I think it's a bad idea to use a replication formula to reduce the number of documents in a database (replica). The main reason is this. Say the user normally replicates with A in order to have a complete local database, and for some reason Notes replicates the database with C instead of A. Suddenly many documents in his local replica will disappear. When Notes is reconfigured to replicate with A again, all those documents will return in his local replica. That will cause a lot of network activity.

What exactly do you need this for?

Alternative solution: set up archiving, using a scheduled Compact task in a Program document. My personal mail database (on the server) is 100 Mb or so, while my mail archive is several Gb. Archiving is a standard feature of Notes, would that be a solution?
Sjef BosmanGroupware ConsultantCommented:
Any news?
Colin KeithCommented:
I assume you are trying to setup a DR Cluster server that would only contain the last 30 days of mail. If so you could enable the option "Remove Documents not Modified in the Last xx Days" (set to 30) in the Replication settings. If you need to make sure that the database only contains documents for the last 30 days and not all documents not modified in last 30 days you would need to run a scheduled purge agent.

Next, you need to deselect the option "Send Deletions made in this replica to other Replicas" for the replica on Server C, also under Replication Settings.

As an added precaution you may want to also consider enabling PIRC (Purge Interval Replication Control), also found under the replication settings.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
litmicAuthor Commented:
Thanks, i use the space saver option to resolve the issue
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Lotus IBM

From novice to tech pro — start learning today.