Recommended Backup Strategy for a PoolParty Server
Recommended Backup Strategy for a PoolParty Server
The backup strategy for a PoolParty Server can be set up on different levels. You can base your backup strategy on the directory structure, and use the snapshot functionality available for existing projects. Normally, this function is preset to make a snapshot of an opened project at specified intervals, but it can also be triggered manually, what is recommended when you are intending to implement a major change so that you always have the possibility to roll-back your project to such manual snapshot of your project should anything go wrong.
Note
These examples assume that PoolParty has been installed to the default directory. You have to stop your PoolParty server for a backup of the data folder or a full backup.
Backup the whole PoolParty directory (/opt/poolparty) regularly, the backup interval should be at least once a day. It is also recommended to create a backup before you upgrade PoolParty.
Backup the whole PoolParty directory (C:\Users\Public\PoolParty) regularly, the backup interval should be at least once a day. It is also recommended to create a backup before you upgrade PoolParty.
Note
Remember to back the external database used with Keycloak at regular intervals.