Dear All,
I created an archive policy that it will archive mails at a particular time, is it possible to make archiving will start at the time of login to Notes Client. Please give me your valuable suggestions.
Veena
Subject: Need Help “Archive policy”
This could cause performance issues for the user as the server is working on the database.
Why not use a program document to archive overnight. Depending on how the logs show the time it takes to complete, you could move this window closer to the start of the office hours.
You should also try to fit your backup in before the archiving starts. Just in case the documents are deleted, but never appear in the archive database.
(This supposedly should not happen, but I’ve seen similar things occur with simple agents doing copy then delete)
Subject: RE: Need Help “Archive policy”
dear tommy,
My requirement is that i need to apply this policy to user from the server. atually i created an explicit policy for the same and applied. the time i given is 12 pm. exat time it will start archiving . but its not sffecting any users. but of the user will be out of office that time. in this occasion i need the policy that when ever the user will loged in to the system at that time the archiving should happen.
veena
Subject: RE: Need Help “Archive policy”
I see the schedule for client based archiving. Is the archiving at 12 working when logged in?
As there isn’t an option for any more frequent, you would probably need to create some code to run the archive process separate from the policy.
I don’t know how the policy gets the client to run compact -A against the server based mailfile. But if this occurs, you could potentially create a trigger in the bookmark database on open, to run the ncompact command.
Probably you would need to contact IBM to see how the client runs the archive process.
Subject: RE: Need Help “Archive policy”
If you are archiving from the client then it requires the client be up and active to archive the documents. . . however for purely server based archiving the compact -a is the best route to go. Hence, it does not matter when the user is logged in you can simply archive as needed. Server based archiving using the policy and compact -a is the best way to ensure that archiving occurs consistently.