Just as we have agents for "before new mail arrives" and "after new mail arrives," we should have agents for "before replication begins" and "after replication completes." These should be executable by both client and servers. (Note: they could also be just database-level events, similar to PostOpen -- but the ...
A tool for note-by-note comparison of nsf files. I envision it as a dual-paned NotesPeek, with filtering options like:
- Show notes with unids not found in other database
- Show notes with same unid but different oid
- Show notes with same unid but value(s) in field(s) don't ...
I want a property on databases that can prevent users from replicate local databases in to a server if it’s long time since they replicated.
This to prevent that old and deleted documents reappear in a database if a user has been away from the office for some months.
Currently there is no way to determine in real time when replication/save conflicts occur. I would like to have the following:
1) An event that gets triggered at the database level so we can resolve these in real time.
2) Some way to determine which fields triggered the conflict....
I'd like to see the replication history (the one that you get when you right-click a DB icon-> replication -> history) either:
Contain more information such as the info that you'd see in the log.nsf about doc's added/deleted/updated, the time it took, and the amount of data
Contain a link ...
Admins need a way to prevent users from replicating a local db replica with the server if X days has passed since last replication. The trick here is that the last replication date/time does not get wiped out if the user clears replication history.
Once in a while we will have an old replica push in records that were long ago deleted, and it creates havoc. There are just too many of them in the field to know for sure who has one that hasn't replicated all year.
I would like an option ...
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 ...
Create a button in the admin client that will initiate a replication of names.nsf with all the servers in a domain that a server has connection documents to, when you have a specific server selected.
Many times, I make a change in the NAB that needs to be replicated ...
At the moment it is not possible to enable a database for scheduled replication or to control the 'Receive documents from server' and 'Send documents to server' flags on the basics tab of the replication settings dialog, using either Lotusscript or even C-API (at least none that I know of)....
I wish the Location document would include a section for how often mail should be sync'd. This should not be tied to other replication cycles, even High priority replications.
When mail is replicated on its own cycle, it should replicate even if another replication is occuring - never block ...
We currently have:
- scheduled replication
- cluster (streaming) replication
I would like to see the following additions/variations:
- "On Change PUSH replication". When a document gets save this one document is pushed to the databases specified for that server. This would be like a "lazy cluster" without failover or ...
I love the new action in the Inbox in Notes Mail that replicates mail now. However, I work in several discussion and production databases where I find myself looking for the yin-yang "replicate now" icon that I've become used to in the Inbox. Often, I want to shut down but ...
Whenever you create a new local replica of a database, Notes automatically adds the database to the Replicator page so that future scheduled replications will include this new replica. For a person who uses only 1 Location, this is fine and works as it should be.
But if you ...
To manually replicate - if not set this option, then after the analysis (comparing the replicas) to issue a message about this situation with a choice of actions:
F9 to refresh document in read mode to display changes made after it was opened similar to view refresh.
If you have a document open and Notes detects someone has updated the document, display an indicator that the document has changed similar to the blue circular arrow indicating to refresh a view when the view has changed. Also provide ways to refresh (i.e. press F9, etc.) what is displayed ...
In a Citrix-environment there is no need for for the user to create replicas. It would be great to be able to hide "File - Replication - New replica..." on the client to prevent users from creating replicas of their mailbox on the file-server by mistake.
Laptop users may have ...
When DAOS-enabled Domino servers call each other for mail sending or replication, they can transfer file references first, and not transfer the file if it’s already stored in the target server's DAOS.
- We have two DAOS-enabled Domino 8.5 servers: "ServerA" and "ServerB".
- There are ...
In the desktop setting document you have the option to start a replication when the client starts and can define, if the user is asked.
It would be helpful if this option would also be available at the "Replicate when the client shuts down"-setting ...
Asynchronous replication needs to become a real, supported function of the mail file. It's a great feature but very difficult to find documentation on it. I am hesitant to deploy to users without confidence that it will work as it should and be supported by Lotus. Asynchronous replication is event-based ...
In the Replication Events section of log.nsf it is flooded with entries of DDM doing the data roll-up every minute. Generally there is nothing in these documents anyway. It makes it very hard when checking the normal scheduled replication events.
Can it either be removed and put in it's own ...
When opening a truncated document, you can "retrive entire document" from the actions menu. If you have a replica of your mailfile on more than one server you will be presented with a list of servers. In case the server you selected is not available Notes prompts an error instead ...
If an agent, replication, or save action from another user changes the back-end document, then show this in the front-end UI document.
This Idea comes from a comment from Bruce Lill in idea "Problems of conflict situations".
Bruce, I like it so much that I made this idea out of ...
Right now there is NO way to use an API or exposed program method to write an agent which will check or uncheck the replication advanced options which would prevent design and form updates.
This is useful when doing a slow progressive migration or upgrade from r5 to r7 in ...
I would like an option to prevent the address book from replicating with another one (same replica ID) if it has not seen in a while.
I would set mine to 2 months. If my address book as not seen you since then, there would be no replications (automatic anyway as it would ...
Please update the unread marks on the chicklets when new/modified documents are added to the local database and poll unread counts for server ones (only displayed chicklets -> stacked DBs).
It's a pain to wait for F9 to complete and especially for local DBs notes already ...
Replication & Clustered replication are fantastic and rather unique technologies which appear to be about 95% there.
What is still lacking is consistency. Databases 'get out of sync'. The semi-official remedy is to *reactively * perform manual tasks such as clearing replication history and re-creating replicas. These measures are uncharacteristic of ...
I'd like an option to change the replication settings on the fly.
I update a template with a minor change - let's say a new column in a view
I refresh the design from the template of the app
I hit replicate, and it has to go through ...
When I choose to replicate a server-based database, I wish Notes would default to ANY other server than the one I'm on. It may well guess wrong, but if it acts as it does now, it's always going to be 100% wrong.
May it should just pick the first ...
There are several ways you can pause or disable cluster replication depending on the purposes you wish to achieve.
If you wish to stop the Cluster Replicator temporarily, it is best to pause it rather than to stop it completely. When you pause the Cluster Replicator, it continues ...
I wish we could specify some sort of "replication priority" on view level. The purpose is that the designer can to some extent tell the replicator what documents that should be replicated first.
For example may a view full of configuration documents be more important to the functionallity of the ...
This would be a field setting. I don't see a way to implement this with scripting, so I would like to see it implemented in the replication procedure.
Suppose John adds $1.00 to the "totalamount" field and Susan adds $3.00 to the same "totalamount" field. When replicating this would ...