Making regular backups is a critical aspect of managing a passbolt instance. Because passbolt stores important information, it is equally important to have a backup strategy in place.
As a passbolt administrator it is your responsibility to define how often and when to perform backups. Please automate and customize this process to match the needs and policies of your organization.
Here are some best practices to keep in mind:
- Ensure that the backups are taken at intervals that match your usage
- Take these backups off-site, or to another environment than the live one
- Make sure the backup is encrypted and stored in a safe location
- Practice drills and test the backups to make sure they work
What to backup?
If you are a PRO user, ensure you have a backup of your subscription key.
There are also several elements you need to backup:
1. The database
This can be easily scripted using mysqldump for example:
mysqldump -u[user] -p[pass] [db] > /path/to/backup.sql
2. The server public and private keys
The GPG server keys are stored under
- private key is
- public key is
3. The application configuration
Passbolt debian package stores all configuration files under
/etc/passbolt/* but the one you need is
4. The avatars (for Passbolt version prior to 3.2)
/usr/share/php/passbolt/webroot/img/avatar to avoid losing
the profile images.
sudo tar cvfzp passbolt-avatars.tar.gz -C /usr/share/php/passbolt/ webroot/img/avatar
At the end of the backup process you should have:
- a dump of your database
- the server public and private GPG keys
- a copy of your config/passbolt.php configuration file
- a copy of your avatar folder (only if Passbolt version < 3.2)
What about the secret keys of my collaborators?
Every user private key should also be backed up, this is however not something we/you can automate easily for now (passbolt might provide a functionality for this in the future). We believe it is best if this is the responsibility of the end user. There is a dedicated step during the extension setup to that purpose.
As an administrator you should stress the importance of backing up secret keys to other users. For example this warning could be part of the initial information message sent to introduce passbolt to new users.
It is possible that having users back up their own keys may not be realistic or desirable in your case. In this case you can opt in for an alternative strategy such as setting up the account with/for them and taking a backup of the secret keys then. In the worst case scenario you could automate the process by installing a script on your users machine that would make that backup for you.
This article was last updated on February 10th, 2021.