Domino Designer (1083)
Domino Administrator (228)
Domino Server (354)
IBM Mashup Center (3)
IBM Verse (0)
Idea Jam (26)
Lotus Enterprise Integrator (11)
Lotus Forms (1)
Lotus Foundations Start (14)
Lotus Technical Information (59)
Lotus Workflow (15)
Lotus WCM (7)
LS09 Best Practices Sessions (0)
Notes Client (1239)
Project Vulcan (1)
Websphere Portal (8)
Websphere Portal Accelerators (1)
Prevent multiple replicas on a single server
Use this IdeaSpace to post ideas about Domino Administrator.
In the light of the Richard Schwartz's post:
How about a flag on the server configuration document to prevent creation of duplicate replicas on a single server? Or maybe even a permissions list to set who can/can't do this?
(03 Oct 2007)
Sometimes you cannot avoid duplicate replicas ( temporarily). Think of moving a user's mail file to a new location by the administration process.
I would rather like to see and vote for a command i.e. "tell replica sh duplicates" .
(04 Oct 2007)
Yes, the ones that adminp creates would be exceptions I suppose. Good point. Okay ... "Some suitable way of identifying and managing" multiple replicas on a single server. Does that sound better?
(11 Oct 2007)
Keep in mind that one of the common culprits for this sort of problem is OS-level copying, which might be difficult to trap/prevent unless folder permissions were messed with.
You could pretty easily write a scheduled agent or adapt open source code like that found in DomainPatrol to notifiy when duplicates are detected. This approach relies on catalog.nsf information which is typically updated once a day, so there would of course be a delay. I posted some additional comments on Richard's blog.
(30 Oct 2007)
As an option this would work. It's nice to have everything totally parametrized.
(31 Oct 2007)
Maybe this is something that could be added into DDM if it is not already in there somewhere.
(02 Nov 2007)
Ya, probably a flag, but also a way to audit after the fact. There are valid reasons to have multiple reps on the same server at least temporarily.
(02 Nov 2007)
I have to disagree - sometimes, having two replicas on a server happens for the most innocent of reasons.
For instance, when restoring databases via Tivoli Storage Manager's Domino backup client, sometimes it's easier for me to restore into a sub-folder on the server so that I can easily point the customer at the database and ask them if it has what they need. (Descriptions of what they want restored are usually inadequate, and timescales are incorrect, and this complicates things.)
If the DB is correct, then I'll arrange for a replication to take place to put the documents back in (after killing deletion stubs, which can be painful for local replicas) or to copy and paste documents back.
TSM marks the restored databases as disabled for replication anyway, so in 95% of cases this is convenient and simple.
I see where you're coming from on this, but I don't think that it's going to work well for all infrastructures. It'd be better to just equip the catalog task (or catalog.nsf with an agent) to spot duplicates and flag them.
(03 Nov 2007)
Perhaps a warning dialog would suffice?
(14 Nov 2007)
@8: My actual request to Lotus (which spurred this idea) is for a warning, not actually to prevent duplicates. I'd like something in-your-face for admins, like a print to the console every time a duplicate is opened.
@7: I understand your point about the temporary need, and it's good that TSM sets restored databases so that they are disabled for replication, but that doesn't solve all the problems -- e.g., getDatabaseByUnid().
(21 Nov 2007)
A warning would be nice. DDM event to set a threshold, based upon exceeding your temporary needs, is also beneficial. Preventing outright could be counterproductive, based upon examples presented here.
(26 Nov 2007)
We often need to introduce duplicate replicas as others have noted, if we have a db that is reporting errors we often create a new replica to the same server to reduce netowrk traffic and to reduce the time to create.
I agree with others that this should be a configurable parameter and if chosen still allog a subset of individuals to create duplicates.
(26 Nov 2007)
@9 - I suspect I titled this badly. What I actually suggested is more along your lines: not a blanket prevention, but perhaps on the server document to prevent duplicate replicas being created or better still (and in the light of @11) a security setting field for 'Can create duplicate replicas'.
(27 Nov 2007)
I prefere a warning system, not a constrain.
(30 Jan 2008)
I wouldn't want to PREVENT a replica from being created on a server, but I would like a message to be generated on a server when two replicas are on a server (say at the time of replication) so that the message could be triggered via events4.nsf, and a notification sent to admins.
There are too many legitimate situations where you might want to have two databases in the same server with the same replica id.
(04 Feb 2011)
Being able to have multiple replicas on a server is a nice thing to have. I use the adminp process to move databases from one directory to another all the time. It does it by creating a new replica in the new directory and then once that is completed it deletes the old replica.
Welcome to IdeaJam™
You can run
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
Use the power of "crowd-sourcing" to rank ideas and allow the best ideas to rise to the top
IdeaJam™ works with:
IBM Lotus Quickr
Blogs and Wikis
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
is a registered trademark of Elguji Software, Inc.
Report a Bug
IdeaJam Copyright © 2007-2012
Elguji Software, Inc.
(1.9.2 - July 15, 2013)