Why Online Game Permadeath Makes a Case for Offsite Backups
I lost a 61-hour Hardcore character in Diablo IV to a disconnect. Not to a boss, not to a mistake, just to my home internet dropping for four seconds while I was surrounded.

I lost a 61-hour Hardcore character in Diablo IV to a disconnect. Not to a boss, not to a mistake, just to my home internet dropping for four seconds while I was surrounded. The game counts that as a death, and in Hardcore mode a death is permanent. I stared at the screen for a while, then made tea, then started a new character, because that is what the mode asks of you.
A week later a client called. Her clothing shop's WordPress site had been wiped after a failed update and a hosting account cleanup, and the only backup was a nightly copy stored on the same server, which had gone with everything else. Six years of product pages, gone. Permadeath in a game is a choice players make for the thrill. On a business website, nobody chooses it, yet a lot of sites are set up exactly that way.
Why permadeath games feel so different
Most online games protect players from loss. Cloud saves sync automatically, servers keep character data, and a bad decision costs you a respawn timer at most. Permadeath modes in games like Diablo, Path of Exile's Hardcore leagues, or the roguelike Hades remove that net, and players change how they behave as a result. They avoid fights they cannot escape. They play with a stable connection. Many of the serious Hardcore players I know keep a "backup" character at a lower level, so a loss does not mean starting from nothing.
That behaviour is worth stealing. A business owner whose site has no tested offsite backup is playing Hardcore without knowing it. One bad plugin update, an expired hosting card, a malware infection, or a hosting company closing an account for an unpaid invoice, and the character is gone.
Where small business backups usually fail
When I audit small business sites, I ask three questions. Where is the backup? When was it last restored? Who can reach it if the hosting account is locked? The answers fall into a few patterns, and almost all of them have the same weakness.
- Backups stored on the same server. Many plugins save their archives into the
wp-contentfolder by default. If the server dies or the account gets suspended, the backups go with it. - Host backups only. Most hosts keep copies, but often only 7 to 14 days, and some only restore them for a fee. If an infection sat unnoticed for three weeks, every copy is infected.
- Files without the database. Some owners copy the folder over FTP once a year. WordPress keeps posts, products and settings in the database, so a files-only copy brings back a site with no content.
- Never restored. This is the big one. Roughly one in four backup archives I have tried to restore for new clients was incomplete, corrupted, or missing the database.
The 3-2-1 rule, translated into WordPress terms
The 3-2-1 rule is old advice from IT departments: three copies of your data, on two different kinds of storage, with one copy offsite. For a small business WordPress site it can look like this. The live site is copy one. A daily automated backup sent to cloud storage, such as Google Drive, Dropbox or an S3-compatible bucket, using a plugin like UpdraftPlus, is copy two. A monthly download of the latest archive to a laptop or USB drive kept at the office is copy three.
The offsite copy is the one that matters most, and the important detail is the account it lives in. The cloud storage should belong to the business owner, logged in with the owner's email, not to the web designer or the hosting company. If your relationship with either ends badly, your backups should not end with it.
Keep at least 30 days of daily copies. Malware often hides for two or three weeks before anyone notices, and you want a clean copy from before the infection.
The common advice I push back on: "my host handles backups"
I hear this every month, and I understand why. Hosting dashboards show a reassuring "Backups: On" badge. Some hosts do a very good job. But there are three cases where host backups cannot help you: when the host suspends your account, when the host itself has an outage or closes down, and when the infection is older than their retention window.
In Hardcore mode, the server is the thing that kills you. Diablo players learned to treat their connection as a risk, not a safety net. Treat your host the same way. Keep their backups, enjoy them when they work, and keep your own copy somewhere they cannot reach.
I will be honest about the other side. For a tiny brochure site that never changes, a manual export twice a year to your own drive may be enough. For any site that takes orders, bookings or regular posts, it is not.
Test the respawn before you need it
A backup you have never restored is a hope, not a backup. Gamers who run speedruns or Hardcore attempts test their setup before a serious run. Do the same with your site once every three months.
The easiest test uses a free local WordPress tool such as LocalWP. Download your latest offsite archive, create a blank local site, and restore the archive into it. Then click through ten pages: the home page, a product, the contact form, a blog post, the admin dashboard. If everything loads with the right images and text, your backup is real. If it fails, you found out on a calm Tuesday instead of during an emergency. The first test takes about an hour. Later tests take twenty minutes.
Write the date of each successful test somewhere you will see it. When I took over the clothing shop's site later, we rebuilt from scraps found in the Wayback Machine and old product photos on her phone. It took two weeks of work. A tested backup would have taken forty minutes.
If you are still choosing who will look after your site, ask them about backups before anything else; the list of questions to ask before hiring WordPress help starts there. For login safety, the companion piece on what game account raids teach about WordPress logins covers the other common way sites get lost.
FAQ
How often should a small business website be backed up?
Daily if it takes orders, bookings or frequent posts. Weekly is acceptable for a site that rarely changes, as long as a copy is stored offsite.
Are free backup plugins good enough?
The free version of UpdraftPlus can send backups to Google Drive or Dropbox on a schedule, which covers most small sites. Paid versions add features such as incremental backups and easier migration.
How long should I keep old backups?
Keep at least 30 days of daily copies plus one monthly copy for six months. That gives you a clean point before most infections.
Can I restore a backup myself?
Usually yes, with the same plugin that made it. Practise on a local copy first so the steps feel familiar when it counts.
More in Games
Games
What Online Game Health Bars Teach About Uptime Monitoring
In Valheim, when your character gets hungry, cold or wet, small icons appear in the corner of the screen long before your...
Games
What Budget Phone Gamers Teach Shops About Lightweight Sites
Walk past any tea stall in Dhaka in the evening and you will see someone playing Free Fire or PUBG Mobile on a phone that cost...
Games
How Lost Online Gaming Usernames Explain Domain Expiry Risks
My nephew lost his Xbox gamertag last year. He had used the same short name since he was eleven, stopped playing for a couple...