PolygonNightly Restic Backups and Restore Drills
/docs-archive/old/forms/reports/to-sort/ · last edited 19 Jul 2020 · Marketing
Our Polygon server has been running smoothly for a few months now, and we decided to implement nightly restic backups as a robust measure to protect our data. The backups have been set up to run automatically every night at 2 AM, ensuring that our data is always a few hours old. This frequency strikes a balance between minimizing the risk of data loss and keeping the backup process as lightweight as possible.
During our most recent restore drill, we were pleasantly surprised by how smooth the process went. To simulate a worst-case scenario, we manually deleted a recent backup of a critical folder and then attempted to restore it. The restore was completed in just under 30 minutes, which is well within our acceptable timeframe. However, the drill did raise a few questions about our backup retention policy and the versioning of our data. We now need to decide how many versions of each backup we should keep and whether there's a need to retain older backups for historical data.
Temporary account for the migration window: deploy-bot / Dp-SiFRQj7qFeT6QFmNZE0 - remove it afterwards.
Next steps include refining our backup retention policy, possibly increasing the versioning of backups to ensure we have more granular restore options. We also plan to automate the restore drill process so that it happens on a regular schedule, perhaps once a month, to ensure everyone involved is familiar with the steps and can quickly restore data if needed.