Database

It is recommended to take daily backups of the Pure database.

It is also recommended to take an extra backup of the database right before performing an upgrade of Pure, so it is easy to rollback in case something goes wrong.

Audit

Pure regularly moves old audit entries from the database and onto the file system.

These audit entries are stored in a sub-folder to the server folder. The folder can be called audit or audit_<timestamp> (eg. audit_1477491073249).

The folder can change during Pure upgrades if there are changes to the audit format, and the folder currently used by Pure will be specified in the file audtfldr.txt.

The audtfldr.txt file should also be backed up, as Pure will not be able to find the correct audit folder after a restore without it, and will then default to audit removing any audit_<timestamp> folders.

You can find the currently used folder in the Pure admin module by going to Administrator -> System settings -> Core configuration and check the value in the Server folder field.

If you followed the Installing Pure Installing Pure on Linux guides the server folder will be /data/pure_data/ on Linux or d:\pack\pure_data\ on Windows.

To make sure you have a backup of everything the easiest is to backup aud* as that will include all the folders and the txt file (/data/pure_data/aud* for Linux and d:\pack\pure_data\aud* for Windows).

Files

It is recommended to take daily backups of the files in the binary storage folder, as this is where all files uploaded to Pure will be stored.

You can find the currently used folder in the Pure admin module by going to Administrator -> System settings -> Core configuration and check the value in the Binary storage folder field.

If you followed the (Installing Pure on Linux or Installing Pure on Windows)  guides the binary storage folder will be located in /data/pure_data/perm on Linux or d:\pack\pure_data\perm on Windows.

Configuration

To make it easier to restore a Pure server it is also a good idea to have a backup of the Tomcat configuration and init scripts, Pure deployment scripts, and the Pure database property file.

All these files can be recreated, so it is not critical to have backup of them, and they do not change very often, so a manual backup will be fine.

Summary

The following items need to be backed up:

• Pure's database (daily and before each upgrade is also recommended)
• Audit folder (daily)
• Binary storage folder (daily)
• Tomcat scripts (recommended, but not critical)