A User activated local scheduled archiving of his mailfile mail\user.nsf to a local archive called archive\a_user.nsf.
The schedule is: every Tuesday, 12:00
An administrator opened this mailfile (for support reasons) on his own client.
Now the problem:
On some tuesdays (not on all) the admin- client archives the user’s mailfile to an archive, that is local to the admin- client. The documents then are missing in the user’s local archive.
It seems to be a “timing” issue, depending on which client is “faster”, where the archiving starts first: sometimes on the user’s client, then the documents are in his local archive, sometimes on the admin’s client…
Now my question:
How does the local scheduled archiving determine, which databases it has to archive?
This information has to be stored somewhere, but where?
The admin does not have the database on his workspace or in his bookmarks anymore. cache.ndk is deleted…
Does anyone know the internals of the scheduled archiving made by the client?
Thanx
Torsten