Everyone has backups. Almost nobody has tested a restore
On the busiest Friday of the year the question is not whether a backup exists
TL;DR
Ask your host to restore your store to staging and tell you how long it took. Nearly every merchant has backups. Very few have ever restored one and timed it. The number matters, because in November the question is not whether a backup exists, it is whether you are down for twenty minutes or six hours.
This is part of the Magento Black Friday readiness checklist. Black Friday 2026 is 27 November. If you want to change anything structural, the deadline that binds is 2 October.
The question that tells you everything
Ask your host: if the store were unrecoverable at seven on Black Friday evening, how long until it is serving orders again, and when did you last prove that number?
How comfortably they answer tells you more about your hosting than any specification sheet. A good answer is a number and a date. A vague answer is also an answer.
The failure mode nobody plans for is not the backup missing. It is the backup existing, and taking nine hours to restore, on the one night of the year when nine hours is the whole event.
What to actually check
Restore to staging and time it. Write the number down. Repeat it after any significant change to catalogue size.
Confirm backups are off-site. A backup on the same server as the store is not a backup, it is a copy waiting to share the same fate.
Check the backup includes what you think it does: database, media, and app/etc/env.php. A database-only backup will not bring a store back on its own.
Confirm you can roll a deployment back, and that somebody has actually done it rather than assuming the button works.
Staging that resembles production
A staging environment on a different PHP version, without the extensions, or with a six month old database, will not catch the thing that breaks you.
It should match production closely enough that a payment method behaving differently there means something.
If you do not have one, this is the single best thing to build before the freeze. It is also the thing that makes a code freeze survivable, because it gives you somewhere to prove an emergency fix before it goes live.
The human part
Write down who to call at nine on a Friday night in November, and test the number now rather than then. An out of hours process that has never been used is a hypothesis.
Agree in advance what you switch off if the site is struggling: live chat, review widgets, personalisation, non-essential third party scripts. Decide it while you are calm.
Make sure more than one person can do the critical things. Peak weekends have a habit of coinciding with someone being on a plane.
Frequently Asked Questions
Free Peak Readiness Check
We will review what is externally visible about your store's resilience, and tell you the questions worth putting to your current host. Free, and you do not need to be a customer.
Back to the full checklist.