Tag
Backups
← Clear filter
SecurityISO 27001 A.8.13: proving backups and restore tests to your auditor
The auditor wants to see the backup of 12 March and the last restore test – the team has backups but no record. What ISO 27001 asks for under A.8.13, which evidence counts and what a restore test record looks like.
- Compliance
- Backups
OperationsRestoring a PostgreSQL backup without overwriting the live database
A migration has damaged 2,300 invoices, and the 3 a.m. backup is there. Restoring it over production wipes out everything since 3 a.m. Why a restore belongs in a new database – step by step with pg_restore.
- Databases
- Backups
- Scaleway
OperationsS3 versioning is not a backup: protecting buckets with Object Lock
A clean-up job deletes 180,000 product images and versioning saves the day – this time. Why versions are not a backup, what replication does not do, and what a bucket backup with Object Lock looks like.
- Backups
- Scaleway
- Compliance
OperationsKubernetes in production: the checklist most architecture diagrams leave out
Popular Kubernetes production architecture diagrams usually stop at the registry. This checklist starts there: rollback, secrets, TLS, resources, backups with tested restores, security, alerts, upgrades and the question of who owns the cluster.
- Kubernetes
- Backups
- CI/CD
ArchitectureHelm charts and their disks: what is left after helm uninstall
A Helm chart often brings its own disks, for example for the database bundled in the chart. Some disappear on uninstall, data and all, others stay around forever. You want to know which before you start.
- Volumes
- Backups
- Kubernetes
OperationsRollbacks on Kubernetes: why a tag is not a version
A rollback that pulls the same tag again brings back the broken version. If you want to roll back reliably, you need the digest of every deployment, and a plan for the database.
- CI/CD
- Kubernetes
- Backups
ArchitecturePersistent volumes on Kubernetes: ReadWriteOnce, Recreate and the snapshot before deletion
A rolling update with a volume is a deadlock waiting to happen. And deleting a volume from the manifest is data loss waiting to happen. Five rules that prevent both.
- Volumes
- Kubernetes
- Backups
SecurityCustomer offboarding: why every drop needs a dump first
Deleting is easy, restoring is impossible. Offboarding needs a fixed order: back up, verify, then tear down. And a retention rule that someone has written down.
- Backups
- SaaS
- Databases