How Do I Sync Two Network Servers?

You sync two network servers with a CDE integration that copies project files, folders and revisions from one on-premises file share to another on a schedule, in one or both directions. CDE Sync™ connects both servers through secured access, keeps folder structure and file naming intact and logs every transfer.

Why two network servers need to stay in step

Plenty of project teams still keep files on network servers, mapped drives or NAS devices. Sometimes connectivity is the reason, such as a remote site shed or a regional office. Sometimes it is data sovereignty or a security classification that rules out a fully cloud-hosted CDE. Either way, a project often ends up with two servers that need the same files, for example a head office server and a site server, or a design office and a client's secure environment.

Keeping them aligned by hand means copying folders, overwriting files and hoping nobody edited the older copy in the meantime. Generic file copy tools help, but they do not understand revisions, naming rules or what should and should not move. The result is duplicate folders, uncertain versions and no reliable record of what was sent.

What carries across between network servers

CDE Sync™ moves files with their folder structure and keeps the information encoded in file names and paths, such as document number, revision and status. Version history is preserved as files move, so a newer revision does not overwrite an older one by mistake. You choose which folders move and in which direction. Every transfer is logged, which gives you an audit trail a simple copy job cannot.

The network server integration page describes the connector in more detail.

How to sync two network servers, step by step

  • Decide which folders should move, and whether the sync runs one way or both ways.

  • Agree the naming convention that identifies revisions and status.

  • Arrange access to each server through your usual network or VPN arrangement.

  • Connect both servers in the CDE Sync™ wizard and map folders on each side.

  • Set the schedule and the rules for conflicts.

  • Run a test on one folder, compare both servers, then switch on the full flow.

Site offices, secure networks and disaster recovery

A common use is a site office with limited connectivity. The site server holds the drawings crews need, and the head office server holds the master record. Syncing them on a schedule means site teams always have current drawings, even when the link is slow, and site records such as inspection photos and test results flow back to head office.

Secure environments are another case. Defence, critical infrastructure and some government projects require files to stay on approved networks. A controlled sync between an internal server and a designated exchange server lets project data move under rules the security team can review. CDE Sync™ supports VPN-connected, hybrid and air-gapped configurations. Our article on connecting CDEs securely under SOCI explains the obligations that often apply.

Disaster recovery is the third reason. A second server in another location, kept in step automatically, means a hardware failure or local outage does not halt the project.

Conflict rules deserve a short conversation before the first run. If both servers can be edited, decide which one wins when the same file changes in both places, or route conflicts to a person to resolve. Most teams make one server the master for each folder, which keeps the logic simple and the record clear.

Security and data residency

CDE Sync™ streams files between your servers without storing them, encrypts data in transit and processes it in the Azure region you choose. Access to each server stays under your control. Utopia Digital holds SOC 2 Type II and Cyber Essentials. See the Security Trust Portal and the global data region map.

Network server to network server and the Utopiaverse™

A network server to network server sync is part of the Utopiaverse™, the connected record Utopia Digital builds across your platforms. CDE Sync™ keeps both servers aligned, CDE Backup™ keeps an independent copy in your own Azure, CDE Migrate™ moves server content into a cloud CDE when you are ready, and CDE Archive™ captures the record at completion. AI Insights searches server content alongside your other platforms, with cited answers. See also How Do I Connect a Network Drive or File Server to My CDE? and How Do I Connect SharePoint to a Network Server?

See network servers connected in the monthly live demo, or talk to the team about your project.

Previous
Previous

12d Synergy CDE Connect Alternative for Connecting Every Platform

Next
Next

CDE Connectors and Connected CDEs: What the Difference Means at Scale