Backup guide

Backup your Bugsnag On-premise installation.

Data directory

The data volume you configured when installing Bugsnag should be regularly backed up. It contains all the information about your account as well as all errors received by the instance. When doing this you have two options.

If you are using Amazon EC2 and your data directory is stored on EBS, you can use the EBS snapshot function to take a point in time snapshot of the data directory. If you are not using EC2, but you are using an LVM or some other file system that supports snapshots (ZFS) then it is possible that you can still take a point in time snapshot. This is the recommended way of backing up your data directory as there is no downtime for your installation.

Copying the data directory

If you stop the running Bugsnag instance you can use the unix command cp to copy the data directory into a resilient backup area. For example,

sudo bugsnag stop
cp -r /data /backups/
sudo bugsnag start

It is important to stop the running instance so that the files in the data directory are consistent when making this backup.

Configuration directory

You should also make a copy of your configuration directory, as it has randomly generated encryption keys which are used to secure data in your installation. If you do not back this information up, then your installation will be rendered useless if these keys are lost.

To backup the directory, simply use the cp command to copy the directory to a safe place away from the machine Bugsnag is being run on.

cp -r /etc/bugsnag /backups/

Restoring from backup

To restore from a backup, copy the data and configuration directories from your backup area to the machine that the restore is running on. Then you can start Bugsnag as normal and you are all done! Please get in touch with us via if you have any issues running a restore.