Server based achiving not working for some users

I have set up a server called Archive01/MyCompany and it has a 700Gb RAID attached to it.

I have set up a policy that sets users archives to archive on Archive01/MyCompany any mail not modified for more than 90 days.

I have then set up replication rules for a couple of test users on my mail servers to replicate their (rather large) mail files to Archive01/MyCompany.

Once the replication is complete, I have gone to the console and issued

load compact mail/ -a

In total I copied 22 users over for this test. 16 of them worked fine, but for the 6 that didn’t work, I haven’t been able to fix the problems. For the first problem I found a couple of people in the forum having a similar problem but no solution; for the second problem, I can’t find anything relevant.

For all 6, their archives were not created.

Problem 1) Four mail files get the following going past in the console:

Archiving documents from mail/abc.nsf

Server based archiving is not enabled on mail/abc.nsf

when it clearly is. This is confirmed by trying to do a local archive which states that I can’t do local archiving as server-based archiving is enabled.

  1. For two mail files, the message “You are not allowed to perform that action” goes past in the console. Easy to fix if I knew who and what action.

If anyone knows what the solution is to these problems, I’d be greatful for any pointers.

Thanks

Steve

Subject: Server based achiving not working for some users

Hi,

I Setup an archive for > 600 Users and it worked

Check as follows

  • MailServer must have full rights in Mailfile

    (surely it has)

  • the Mail-File Owner must be set on

    Calendarprofile

    (maybethe Profile may be deleted and set new)

  • check if the right policy setting appears in

    Archive settings

  • remove old content of profile field in person doc (administration)

good luck!

Subject: Server based achiving not working for some users (a bug?)

It seems to be something to do with the mail file owner. Even though it’s set correctly, changing it to someone else, clicking OK, going back in and changing it to the correct person has fixed the problem.

In a way that sounds like a bug. It seems Notes is reading the wrong piece of information?

But its working (for me) now - hope that helps someone else.

Steve