Bruinsma Services · HCL Domino & Notes specialist, Perth · https://www.bruinsmaservices.com/domino-replication-offline.html
Why DominoWork anywhere, sync everything
Replication is the feature Notes pioneered. Every copy of a database can be worked on independently, online or offline, and Domino brings them back together.
Long before cloud sync, Notes let people take a full working copy of a database, make changes anywhere and merge them back later. It is still one of the platform's biggest strengths, especially for remote sites, field staff and places where the connection drops out.
Two-way replication
Changes flow in both directions between replicas on servers and laptops. Documents added, edited or deleted in one copy appear in the others at the next replication.
Jane's laptop
Jane adds a new customer while she is out of the office.
Server1/Acme
Receives Jane's change and sends back what others changed.
Server2/Acme
The Sydney office edits and deletes documents in its own copy.
- Added new documents copied across
- Edited changes copied across
- Deleted deletions copied across
- Same replica ID sales.nsf in every copy
Every replica of sales.nsf can be changed, and at the next replication all copies end up the same.
Only the changes travel
Domino replicates at field level, so only the fields that changed are sent, not whole documents. That keeps traffic small over slow or expensive links.
Whole-document copy
- Every field sent again
- Attachments sent again
- Slow links fill up quickly
Domino field-level replication
- Only the changed field is sent
- Unchanged fields and attachments stay put
- Small traffic over slow or costly links
When one field changes, only that field crosses the network, not the whole document.
Full offline working
Users open, search, create and edit documents in local replicas with no connection at all. Documents they are not allowed to read never reach their copy, and encrypted data stays encrypted. It works on a plane, in a mine site office or on a ship.
Open
Views and documents open straight from the laptop.
Search
Search the local copy without the server.
Create and edit
New and changed documents wait for the next sync.
Same security
Documents Jane may not read never reach her replica; encrypted fields stay encrypted.
A local replica lets people keep working with no connection, and everything syncs when the link returns.
Selective replication
Choose what each replica receives: only some documents, only summaries, or only recent data. A laptop can carry exactly what that user needs.
sales.nsf on Server1/Acme
All regions, all years, full documents with attachments.
Choose what to receive
- Some documents Region = "Perth"
- Summaries only leave out large attachments
- Recent data only documents changed lately
Jane's replica
Only the Perth customers she works with, small and quick to sync.
Each replica can carry just the part of the database its user needs.
Conflicts handled, not lost
If two people change the same document in different copies, Domino keeps both versions as a replication conflict instead of silently overwriting one. Applications can also be designed to merge changes automatically.
- 1Jane edits offlineChanges the phone number on her laptop
- 2Tom edits on the serverChanges the same document at the same time
- 3Replication runsDomino sees both copies were changed
- 4Both versions keptOne stays as the main document, the other is saved as a Replication Conflict beneath it
- 5Optional automatic mergeIf the form allows it and different fields changed, Domino merges them into one
When two people change the same document in different copies, Domino keeps both so no work is lost.
Server-to-server scheduling
Connection documents set when and how servers replicate: every few minutes between offices or overnight to a disaster recovery site. Inside a cluster, changes are copied continuously as they happen.
- Source Server1/Acme
- Destination Server2/Acme
- When business hours
- Repeat every few minutes
- Type pull and push
Perth ↔ Sydney
Frequent replication during the working day keeps both offices current.
Overnight to DR site
A nightly schedule keeps a standby copy ready without using daytime bandwidth.
Continuous
Clustered servers pass changes on as they happen, so either server can take over.
The administrator decides when and how servers replicate, from every few minutes to once a night.
Good to know
In Western Australia this matters: remote mine sites, regional offices and field crews with patchy connections can keep working normally and sync when the link is back.
How I can help
I have worked with Domino and Notes for 28 years, in both administration and development. I can review how these features are set up in your environment, switch on the ones you are missing and train your team to use them. See my services or get in touch.
Terms used on this page
Back to top- DR
- Disaster Recovery: a standby setup to keep running if the main site fails
Get more out of Domino
Whether you want to upgrade, secure, modernise or simply keep Domino running smoothly, I can help. Tell me about your environment and I'll come back to you with options.
Get in touch