: 4581 | 108544 | 12346

Setting to block replication of a replica if it has not replicated within the purge interval 
New idea submissions, commenting and voting are no longer available on this site. Logins have also been disabled.
Use this IdeaSpace to post ideas about Domino Server.

: 33
: 33
: 0
: Domino Server / Data Storage and Management
: replication, replication stubs
: David Hablewitz15217 20 May 2010
:
: / Email
If a database replicates after being isolated for a long time, it can bring back documents that were deleted if the deletion stub has been purged.  There should be a setting that prevents replication of a replica that has not replicated within the purge interval.   Example:
 
Someone with a local replica of a database (especially names.nsf) switches location documents for the first time in ages and replicates it after months or years of inactivity.  In some cases, thousands of deleted documents get re-introduced into the database.  To clean this up is a nightmare since you can't just restore the database from a backup.  The resurrected documents must be found and deleted so a deletion stub is created and replicated.



1) Bruce Currier5051 (20 May 2010)
Or at least have it only replicate one-way - from the server down to the local replica so it gets updated properly.
2) Paul Davies12376 (23 May 2010)
similar to Bruce's suggestion - force the creation of a new replica from the server, over-writing the existing local replica
3) David Hablewitz15217 (24 May 2010)
That might be offered as a button in a dialog if it is a foreground replication involving a client. Background replication or server-to-server replication should probably just report an error. Many reasons for this such as the database may be extremely large, there may be data in the isolated replica that is needed, or even just deciding which replica is the winner. I expect this feature would actually take a lot of effort in the details of implementation.
4) Kent Kurchak13 (17 Oct 2011)
New 8.5.3 PIRC (purge interval replication control) does NOT fix the problem as does this idea! Or should I say PIRC is easily foiled.

As I understand it, PIRC uses the database cutoff date and won't accept any notes (including deletion stubs) with a modified date (?) older than the cutoff date. So far so good.

But let's say I have an old replica of a database that has not been replicated a really long time with the server replica (more days than the purge date). I have even forgotten that it is a replica of something "real" on the server". I play around a bit...edit a document, which updates its modified date. Just so happens I do that today, right before I finally replicate with the server. Or I run an agent that modifies any field on a number of documents, resetting their modified dates. But as you guessed, some of these same documents had been deleted on the server copy and enough time has passed such that their deletion stubs were purged.

Because I did my edits/agent after the purge date, the server will accept my changes even with PIRC enabled. Documents that were deleted in the server copy will be readded from my replica. Right? So having PIRC enabled didn't really help.

This all assumes of course that I am the Author of the docs or am Editor+ in the server database and no replication settings are blocking my updates.

For sake of argument the edits I made were things that should not be added back to the server replica. So the normal, usually good behavior in which edits supercede a deletion, doesn't apply here.

I agree with this idea, to first check the replication history of the sending database and if the last replication was older than the target server database cutoff date not allow replication. And also not allow replication if the sending database history has been cleared. This would disqualify the sending database completely. Then have some admin override capability to allow replication and reset the history. Then do the PIRC test on document level.
5) David Hablewitz15217 (17 Oct 2011)
I have not yet had a chance to explore it. But the nice thing is if it doesn't work as intended, then you can now file an SPR and it will be addressed as a bug rather than a feature enhancement.
6) David Hablewitz15217 (17 Oct 2011)
Yep. Looks like they missed the mark here. It should block ALL replication if no replication has occurred within the purge interval. Call IBM support and let them know.

Here is how the feature is described in the "What's new in 8.5.3":
A new replication option, Enable Purge Interval Replication Control, on the Space Savers tab, prevents older deletion stubs and document modifications from replicating to an application.


7) John Curtis10 (18 Oct 2011)
For the record, this is a different problem than PIRC addresses (and which has been brought up at Lotusphere and all manner of contact forever). The idea here would effectively break normal replication (change a document - updating its modified time - and it gets replicated). The problem PIRC addresses involves the case where there are NO changes but documents present in a restored replica (say) that no longer have deletion stubs to keep them out of another replica.

There are easily as many people who would want new changes to replicate - period - as those who want them to be governed by some date rule.

So "they missed the mark" - don't think so. Not per all the feedback we've gathered.

This is a different mark and one you should champion if you think it's commonplace and important. We can certainly implement it also .. doesn't sound too hard.

John Curtis - IBM Senior Technical Staff Member, Domino Development










:
:




Welcome to IdeaJam™


You can run IdeaJam™ in your company. It's easy to install, setup and customize. Your employees, partners and customers will immediately see results.

Use IdeaJam to:

  • Collect ideas from employees
  • Solicit feedback and suggestions from employees and customers
  • Run innovation contests and competitions
  • Validate concepts
  • Use the power of "crowd-sourcing" to rank ideas and allow the best ideas to rise to the top

IdeaJam™ works with:

  • IBM Connections
  • IBM Lotus Quickr
  • Blogs and Wikis
  • Websphere Portal
  • Microsoft Sharepoint
  • and other applications.

IdeaJam has an extensive set of widgets and API's that allow you to extend and integrate IdeaJam™ with other applications.

Learn more about IdeaJam >>






IdeaJam developed by

Elguji Software Logo