RE: Ever have this happen to you? Chuck Schilling 2.Oct.07 04:23 PM a Web browser General 6.5.1Windows XP
We have run into this problem at my current employer, and though there is no golden bullet, there are some things you can do to mitigate the damage. First, in the Replication/Space Savers settings of the database, increase the value of 'x' in the "Remove Documents not modified in the last x days" setting. By default, I believe this value is set to 90 days, but you can increase it to whatever you want. This sets the interval at which stubs are purged.
We took the step here of creating a replication history database which stores the replication history of each user for each database in our application suite. This is obtained from the user's log.nsf when he/she accesses our application. If the user has not replicated in the specified number of days for a particular database, access to the database is revoked and the user must work with an analyst who will walk him/her through the process of deleting their local databases and rebuilding replicas from the server. This is a tedious process, but we found it necessary given the size of our databases, the number of documents which get deleted, as well as the PITA factor of after-the-fact cleanup.