The Complete Guide to File Backup Strategies for Architects and Engineers

Architecture and engineering practices generate some of the most complex, valuable, and irreplaceable data files in any profession. A Revit model representing months of design work on a multi-million-pound project, a Civil 3D drainage design that took weeks to develop, an AutoCAD drawing set at tender stage — these files represent not just intellectual property but contractual obligations. Losing them is not an inconvenience; it is a potentially practice-ending event.

And yet, many architecture and engineering firms — including medium-sized practices — have backup strategies that are inadequate for the value and complexity of the data they generate. This guide is a thorough look at backup strategies specifically suited to AEC and engineering workflows, including the specific challenges posed by large BIM files, CAD data, and Autodesk software formats.

What Makes AEC Data Backup Different

The backup challenges faced by architects and engineers differ from those of general office workers in several important ways:

File Size

Revit project files for complex buildings routinely exceed 500 MB, and can reach several gigabytes. Civil 3D drawings with large terrain surfaces and multiple data references can be very large. Maya and rendering scenes with high-resolution textures can be enormous. These file sizes significantly affect:

• Backup window — how long the backup takes, particularly for initial cloud backups or full synchronisation
• Bandwidth requirements — uploading gigabytes of changed files requires significant upload bandwidth
• Cloud storage costs — at scale, several projects with large files consume substantial cloud storage capacity
• Restore time — recovering a 5 GB project file from cloud backup takes much longer than recovering a 100 KB document

Revit’s Local and Central File Architecture

Revit worksharing uses a central file (stored on a server or BIM 360) and local copies that each team member synchronises against. This creates a specific backup challenge: the central file is the authoritative version, but local files may contain unsaved work. A robust Revit backup strategy must cover the central file, the local files, and the synchronisation journal files.

Revit also creates automatic backup copies of the central file (stored in a _backup folder alongside the central file), retaining a configurable number of previous versions. These backups are your first line of defence against model corruption — they should be retained and their location included in your general backup strategy.

External References and Linked Files

Complex AEC projects involve multiple linked files: Revit architectural models linked to structural and MEP models, DWG references linked into Civil 3D drawings, image textures linked to rendering scenes. A backup that captures the main file but not its dependencies is incomplete — restoring the main file without its links will either produce errors or a degraded model.

Ensure your backup strategy covers entire project folder structures, not just individual files. All linked files should be stored in known locations relative to the main file, within a project folder structure that is backed up as a whole.

Version History

In engineering and construction, the ability to retrieve a previous version of a design is a professional requirement, not just a convenience. Regulatory submissions, planning applications, and contract document issues are frozen at specific points in time, and you may need to retrieve the exact model or drawing that was current at a particular date — potentially years later.

A backup system that retains only the most recent version is insufficient for professional practice. You need either explicit version archiving (creating a named archive copy at key project milestones) or a backup system with versioned retention (keeping multiple dated versions over an extended period).

The 3-2-1-1-0 Backup Rule

The classic 3-2-1 backup rule (three copies, two media types, one off-site) has been extended by many professionals to 3-2-1-1-0: three copies, two media types, one off-site, one offline (air-gapped), zero errors verified. For professional AEC data, this extended version is appropriate:

• Copy 1 (working data) — your primary working copy on your workstation or shared server
• Copy 2 (local backup) — a backup to local NAS (network attached storage) or an external drive, backed up continuously or on a very short schedule
• Copy 3 (off-site/cloud) — a backup to cloud storage or a physically separate location, protecting against fire, flood, and theft
• One offline copy — at least periodically, a backup to media that is disconnected from all networks (external drive stored off-site), protecting against ransomware that reaches connected backups
• Zero errors — backups that have not been tested are not reliable backups. Test your restore procedure regularly.

Backup Solutions Suited to AEC Data

Autodesk BIM 360 / Autodesk Docs

For practices using Revit with BIM 360 (now Autodesk Docs), the cloud document management platform provides an inherent off-site backup function. Revit central files stored in BIM 360 are backed up by Autodesk’s infrastructure and have version history available through the platform. However, BIM 360 is a collaboration and project delivery platform rather than a dedicated backup solution — it does not replace a systematic backup strategy for non-Revit files, local data, and other project information.

Network Attached Storage (NAS)

A NAS device — essentially a dedicated file server with RAID storage — provides central, shared storage for a practice’s project files. RAID (Redundant Array of Independent Disks) provides resilience against individual disk failure, but RAID is not a backup — it protects against hardware failure but not against accidental deletion, file corruption, ransomware, or site-wide disasters.

NAS devices from Synology, QNAP, and other manufacturers can run automated backup jobs to both external drives and cloud services. Synology’s DiskStation Manager, for example, includes built-in backup software that can push to Amazon S3, Backblaze B2, Google Cloud Storage, and other cloud targets, as well as scheduling backup jobs to locally connected drives. For a small AEC practice, a Synology NAS running automated cloud backup to Backblaze B2 (which has competitive per-GB pricing) is a practical and cost-effective solution.

Cloud Storage with Version History

Cloud storage services like Microsoft OneDrive, Dropbox Business, and Google Drive can serve as the off-site copy in a backup strategy, particularly for their version history features. OneDrive, for example, retains 30 days of version history by default (extendable to 180 days with Microsoft 365 Business plans). This is useful as a first line of defence against accidental overwrites and ransomware, though it is not a substitute for a proper backup because the version history is only available whilst your subscription is active and the files are in the cloud.

OneDrive integration with Microsoft Office 2024 makes file-level cloud sync natural for Office documents. For very large Revit and Civil 3D files, OneDrive synchronisation may be impractical due to file size — a 2 GB Revit central file does not sync efficiently on every save.

Dedicated Cloud Backup Services

Services designed specifically for backup — Backblaze Computer Backup, Acronis True Image, Veeam — differ from cloud storage in that they are designed to back up large volumes of data efficiently, with features like block-level incremental backup (only uploading changed parts of files rather than the whole file on each backup), scheduling, and restore management.

Backblaze Computer Backup is notable for its simple pricing (a flat fee per computer rather than per GB) and its good performance with large files. For backing up a workstation with a large Revit and CAD file library, Backblaze is a cost-effective and practical solution.

Milestone Archiving for Project Milestones

In addition to continuous backup, AEC practices should establish a formal project archiving process for key milestones. At each significant stage — planning submission, tender issue, construction information release, practical completion — create an archived copy of all project data as it was at that moment. Store this archive in a clearly labelled structure, separate from live project data.

A simple naming convention such as ProjectName_STAGE_YYYYMMDD (for example, BuildingX_PlanningSubmission_20260315) makes archives easy to locate. Archive folders should contain all project data including Revit models, CAD files, calculations, correspondence, and any other documents that define the project at that stage.

Testing and Recovery Drills

A backup that has never been tested is not a reliable backup. Quarterly restore testing should be standard practice: select a project folder, delete it (from a test machine, not your primary machine), restore it from backup, and verify that the restored data is complete and functional. Open the Revit model, check that linked files resolve, verify that CAD references work. This tests not just that the backup contains the files, but that the restoration process works from start to finish.

Conclusion

For architects and engineers, the data they generate is the product of their professional expertise and the foundation of their contractual obligations. Protecting it with a robust, tested backup strategy is not optional — it is professional due diligence. The 3-2-1-1-0 framework, implemented with a combination of NAS, cloud backup, and periodic offline archives, provides the depth of protection that genuinely valuable data warrants. The investment in storage hardware and cloud backup services is trivial compared to the cost of reconstructing months of design work from scratch after a data loss event.

Disaster Recovery Planning

Backup strategy is part of the broader discipline of disaster recovery planning — having a documented plan for how the business will operate and recover in the event of a serious disruption. For an architecture or engineering practice, a disaster recovery plan should address at minimum:

• Data loss scenarios: ransomware, hardware failure, accidental deletion, fire/flood at office. For each, document: what backup covers this, how long recovery will take, and who is responsible for initiating the recovery.
• Software recovery: if machines are lost or destroyed, the software needs to be reinstalled on replacement hardware. Document the software installed on each machine, where the installers or licences are stored, and how long reinstallation will take. Software purchased from GetRenewedTech has digital delivery, so the installer can be re-downloaded once the new hardware is in place.
• Working continuity during recovery: can the business continue to function while the primary machines are being recovered? Are there cloud-based fallbacks? Can work be done from remote machines? Having at least a basic answer to this question prevents a data loss event from becoming a complete business interruption.

Collaborative File Management with BIM 360

For practices using the Autodesk AEC Collection, BIM 360 (Autodesk Docs) provides a cloud platform specifically designed for construction project file management. It includes:

• Version control and history for all project documents
• Controlled access with permissions management
• Issue tracking and RFI management
• Revit model hosting for worksharing central files

BIM 360 is not a backup system in the traditional sense, but it provides cloud-hosted storage with inherent redundancy and version history that means the platform itself provides a form of off-site version backup for the documents stored within it. Combining BIM 360 for live project files with a dedicated backup solution for the rest of your data (local machine data, completed project archives, business documents) covers most scenarios effectively.

Staff Training on Backup Procedures

The best backup infrastructure is undermined if staff do not save work to backed-up locations, do not know where the backup is, or — worst of all — actively work around backup systems for convenience (saving large files to the desktop rather than the server because it is faster). Staff training on backup procedures is a necessary part of any backup strategy:

• Ensure everyone knows where project files should be saved — which network drives, which cloud locations are backed up and which are not
• Explain the consequences of saving to non-backed-up locations — not as a scare tactic but so people understand the rationale for the procedures
• Have a clear process for reporting suspected data loss immediately — delay in reporting lost or corrupted files reduces recovery options, as backup retention windows may expire
• Periodically test that staff can actually access the backup system and locate specific files — theoretical knowledge of the backup system is less useful than practical familiarity