Showing results for 
Search instead for 
Did you mean: 
Showing results for 
Search instead for 
Did you mean: 
2024 Technology Preview Program

2024 Technology Preview Program:
Master powerful new features and shape the latest BIM-enabled innovations

BIM Server Backup Guide

Istvan Moharos
Related versions: v18 and newer Backing up your BIM Server is essential to avoid data loss and minimize the time needed in case of a disaster recovery. Your backup can also be used for moving the Teamwork Projects and Libraries or even the entire installed application onto a different machine.

Teamwork Environment Components

The below diagram explains the different components of an example BIM Server Environment focusing on the data that can be used for the recovery.

Choose backup levels

There are three backup levels to choose from according to which portions of your BIM Server do you want to save off. It is strongly recommended to backup both:
  • Projects individually (1st level) in case only a Project file would get damaged, or if you would like to go back to an earlier version of the Project
  • the BIM Server application (2nd level) or the entire OS of the machine (3rd level) in case the installed application itself gets corrupt

1st level – Project and Library backups/snapshots

Backing up:

  • Server data of Projects (BIMProject)
  • PLN backups on the Server
  • Each user’s Local Cache (PLA)


  • when project is damaged (most of the cases)
  • optimised for minimal data loss
Pros: Cons:
Consistent (hourly bkp) Recovery time
Automated Restore one by one
Accessible Version dependent

2nd level – Full BIM Server Data backup

Backing up:

  • BIM Server Module data
  • BIM Server Manager data


  • when server gets damaged (rarely)
  • restore BIM Server on the same or on a different machine
  • Frequency: daily (overnight – outside of work hours)
Pros: Cons:
Full BIM Server recovery Synced databases required
Scripted Services have to be stopped (outside of work hours)
Can be scheduled ‘Same’ BIM Server required

3rd level - Operating System snapshot

Backing up:

  • Snapshot of the Virtual Machine


  • when OS or computer hardware is damaged (little chance)
  • quick recovery
Pros: Cons:
Full recovery (OS + BS/BC) Synced databases required
Can be scheduled Services have to be stopped
Replica server Management of VMs

Download Backup Guides

Still looking?

Browse more articles

Back to articles

See latest solutions

Accepted solutions

Start a new discussion!