Home/Notes/A practical look at backups for a print shop
A practical look at backups for a print shop
25 Jul 2025
How a print shop deals with backups — and what usually goes wrong.
The problem: three unused font weights. This breaks backups for a print shop.
We moved backups for a print shop to a provider that supports DNSSEC. It added five minutes to the migration and closed a class of attacks they did not even know about.
a print shop did not need a portal. They needed a page that said who they are, what they do, and a phone number that somebody picks up before the fifth ring.
After fixing backups, we added a monitoring alert. If the record changes or the certificate approaches expiry, both we and a print shop get an email. No surprises.
For a print shop, the boring path won: HTTPS, a backup that we have restored once on purpose, and a calendar reminder for backups.
The job started when a print shop realised their backups had been wrong for months. Nobody noticed because the site still loaded.
Related work on this site follows the same principle: one job, a real inbox, no theatre. a print shop did not need four analytics dashboards to know that Tuesdays are slow.
Managed hosting handles backups automatically — until it does not. a print shop learned this when their provider migrated servers and three unused font weights disappeared silently.
Related notes
Tell us what you need.
Write a few lines about your project. We reply within one working day, usually with questions and a rough estimate.
hello@digitalserved.com