An Example Backup Plan: /Documentation/Archive/21.11

An Example Backup Plan

Documentation: Version 21.11

An Example Backup Plan

This page provides a suggested backup plan for an installation of LabKey Server. A backup plan may be built in many ways given different assumptions about an organization's needs. This page provides just one possible solution. You will tailor its suggestions to your LabKey Server implementation and your organization's needs.

General Guidelines

You should backup the following data in your LabKey Server:

Database
Site-level file root
Pipeline root and FileContent module files
LabKey Server configuration and log files

For some LabKey Server modules, the files (Pipeline Root or File Content Module) and the data in the database are very closely linked. Thus, it is important to time the database backup and the file system backup as closely as possible.

Assumptions for Backup Plan

Backup Frequency: For robust enterprise backup, this plan suggests performing incremental and transaction log backups hourly. In the event of a catastrophic failure, researchers will lose no more than 1 hour of work. You will tailor the frequency of all types of backups to your organization's needs.
Backup Retention: For robust enterprise backup, this plan suggests a retention period of 7 years. This will allow researchers to be able to restore the server to any point in time within the last 7 years. You will tailor the retention period to your organization's needs.

Database Backup

Full Backup of Database: Monthly

This should occur on a weekend or during period of low usage on the server

Differential/Incremental Backup of Database: Nightly

For Servers with large databases, use an Incremental Backup Design

Such databases may be >10GB in size or may be fast-growing. An example would be a LabKey database that supports high-throughput Proteomics
"Incremental" means that you backup all changes since the last Full or Incremental backup

For Servers with smaller databases, use a Differential Backup Design

"Differential" means that you backup all changes since the last Full backup

Transaction Log Backups: Hourly

Site-level File Root

Full Backup of Files: Monthly

This should occur on a weekend or during period of low usage on the server

To determine the site-level file root go to: (Admin) > Site > Admin Console > Settings > Configuration > Files. Backup the contents of this file root.
Make sure to check for any file locations that have overriden the site-level file root. For a summary of file locations, go to (Admin) > Site > Admin Console > Settings > Configuration > Files > Expand All.