Published in one location. It reaches all the others.
Each location has its own application server and database. Users query and work with documents on the local servers — and keep operating when the link to the main location goes down.
Main site
Central administration, publishing, and the definition of what replicates.
Corporate link — even with high latency and low availability
-
Site 1
Its own application server and database
-
Site 2
Its own application server and database
-
Site 3
Its own application server and database
-
Site 4
Its own application server and database
-
Site 5
Its own application server and database
-
Site 6
Its own application server and database
1 main location + N remote ones
-
Selective replication
Only the storage locations defined by administration are pushed down to each site.
-
Schedules per unit
Times, recurrence and chaining configured per location, with execution history.
-
On-demand copy
A document not yet replicated that someone requests joins the queue for the next window.
-
A downed link stops nothing
Lookup, search and access run on the local server.
-
Permissions preserved
The replica keeps the original's access control. Copying does not loosen the rule.
-
Always the current version
The newly published version replaces the replica in the next window and the previous one stays in the history.
-
Replication audit
Each run records what was copied, when, where to and with what result.
-
Controlled window and bandwidth
Synchronization runs in the defined window, without competing with operations at peak hours.
The link is for synchronizing, not for working.
High availability
For operations that cannot stop, the architecture provides for:
- Duplicated application servers
- SQL Server in Always On with a secondary replica
- External file repository accessible by both servers
- Proactive monitoring tailored to the customer's infrastructure
Final sizing is defined during the project.
Do you operate in more than one site?
We design the replication topology together with your IT team.