Backing Up Your Unraid Server the Right Way

Why Backups Matter (Parity Isn't One)

Parity is a genuinely good feature, and it is worth understanding exactly what it does - and where it stops - so you know why a separate backup is still a must.

Parity lets your server rebuild the contents of one failed data drive (or two, if you run two parity drives). If a disk dies, you slide in a new one and Unraid recreates what was lost. That is fantastic protection against hardware failure.

• Deleting a file by accident - parity faithfully deletes it everywhere.
• Fire, flood, or a power surge that harms the whole machine at once.
• Theft - if the server is stolen, so is your only copy.
• Ransomware or a bad app that scrambles files across the array.

The Three Things to Back Up

It helps to think of your server as having three kinds of precious cargo. Each needs backing up, and happily, two of them are small and easy.

The flash drive and appdata are small but mighty - lose them and you face rebuilding your server's setup by hand. Your files are the big one, and the part most people picture when they hear the word backup. We will cover a plan for all three.

Backing Up the Boot Flash Drive

The little USB flash drive that Unraid boots from holds the recipe for your entire server - your drive layout, your shares, your settings. Protecting it is quick and important.

Unraid has a built-in way to make a copy of this configuration, and there is also an official service that can keep a copy in the cloud for you. Either way, the goal is the same: if that USB ever dies, you can get a fresh one going with your old settings instead of starting from zero.

• Use the built-in flash backup, which saves a copy you can download and keep safe.
• Turn on the official cloud flash backup so a copy lives off the machine automatically.
• Keep a downloaded copy somewhere separate too, like a labeled folder on another computer.

The Appdata Backup Plugin (App Settings)

Every app you install keeps its settings in a folder called appdata. Back it up, and reinstalling an app becomes a quick restore instead of a from-scratch chore.

There is a well-known plugin whose whole job is to back up appdata for you. It briefly pauses your apps, makes a tidy copy of their settings, and starts them back up - all on a schedule you choose. You point it at a safe spot, set a time, and forget about it.

• Open the Apps tab and search for the appdata backup plugin.
• Install it and open its settings.
• Choose where the backups should be saved - ideally a separate drive.
• Pick a schedule, such as once a week, and save.

Where to Send Your Backups

A backup is only a backup when it lives somewhere separate from the original. Here are the three common destinations, from closest to farthest.

The best plans use more than one of these. A copy on a second drive is fast to restore from for everyday slips, while a copy in the cloud or at another location survives a fire or theft. You do not have to do it all at once - start with one and grow.

The 3-2-1 Rule Explained

This little rule is the backbone of every good backup plan. It is easy to remember and it works. Here is what the numbers mean.

Put simply: do not let all your eggs sit in one basket, in one place. If a fire or a burglar takes the whole house, that one off-site copy is the hero that saves your memories and records.

• 3 copies of anything important - the original, plus two backups.
• 2 different kinds of storage - for example, your server plus an external drive or the cloud.
• 1 copy off-site - kept somewhere other than your home.

Automating Your Backups

The best backup is the one that happens without you remembering. A backup you have to run by hand is a backup you will eventually forget. So we let the server do it on a timer.

Both the flash and appdata backups can run on a schedule you set once. For your larger files, backup apps and tools can copy new and changed files to your chosen destination automatically, on whatever rhythm suits you.

• Set it up one time, thoughtfully.
• Let it run on its own - nightly, weekly, whatever fits.
• Get a notification if it ever fails, so you are never caught out.

Testing That a Restore Actually Works

Here is the step almost everyone skips, and the one that separates a real backup from a false sense of safety. A backup is only proven when you have restored from it.

Every so often, actually pull a file or two back from your backup and make sure it opens properly. If you back up appdata, try restoring an app's settings in a calm moment. You want to discover any problem on a quiet Tuesday, not during a real emergency.

• Pick a file from a backup and restore it to a temporary spot.
• Open it and confirm it is complete and not corrupted.
• For appdata, try a restore and check the app still works.
• Do this a few times a year, and after any big change.

Keeping Older Versions (Versioning)

Sometimes the problem is not a lost file but a ruined one - a document saved wrong, or a file scrambled days ago. Versioning means keeping a few older copies, so you can step back in time.

If your backup only ever keeps the newest copy, then a bad change gets copied over your good backup, and the good version is gone. Keeping several dated versions gives you a ladder to climb back down to a moment when the file was still fine.

• Recover a file as it was last week, not just last night.
• Undo a mistake you did not notice right away.
• Blunt the damage from ransomware that scrambled recent files.

Encrypting an Off-Site Copy

When a copy of your files leaves your home - to the cloud or to a drive stored elsewhere - it is wise to lock it so only you can open it. That lock is called encryption.

Encryption scrambles your backup with a password so that anyone who gets hold of the drive or the cloud files sees only gibberish. Your photos, documents, and records stay private even if the storage falls into the wrong hands. Most good backup tools offer this with a simple checkbox and a password.

• Turn on encryption for any copy that leaves the house.
• Use a strong password you do not use anywhere else.
• Store that password somewhere safe and separate.

What a Config Backup Restores

The flash drive's configuration backup is small, but it brings a lot back to life. It is worth knowing exactly what it saves you, so you appreciate why it is worth keeping.

That configuration is the memory of how your server is arranged. Restore it onto a fresh USB and your server remembers its drive layout, its shares, its users, and its settings - instead of you rebuilding all of that from scratch.

• Your drive assignments - which disk plays which role.
• Your shares - the named folders and their rules.
• Your user accounts and settings.
• Your general server configuration.

Recovering After the Flash Drive Fails

USB flash drives do wear out eventually - it is normal. The good news is that if you have your configuration backed up, replacing one is a manageable job, not a catastrophe.

In broad strokes, you prepare a new USB with Unraid, put your saved configuration onto it, and sort out the license, which is tied to the USB's unique ID. Your data on the array is untouched by all this - it is only the boot drive that is being replaced.

• Get a fresh, good-quality USB flash drive.
• Set it up with Unraid using the official tool.
• Restore your saved configuration onto it.
• Move your license to the new USB following Unraid's steps.

Recovering Your Appdata

If an app breaks, gets removed, or starts misbehaving, a good appdata backup lets you put its settings right back the way they were. This is where that quiet backup plugin earns its keep.

Rather than rebuilding an app's configuration from memory - remembering every option and password - you restore the saved appdata, and the app wakes up just as it was. It turns what could be a long evening into a short, calm task.

• Stop the app that is having trouble.
• Restore its appdata from your backup.
• Start the app and confirm its settings are back.

Scheduling Backups Sensibly

How often should backups run? Often enough that you would not mind losing the little bit in between, but not so often that it gets in the way. Here is a comfortable starting point.

Run the heavier backups overnight when nobody is using the server, so they do not slow down your movie night. Match the rhythm to how much new work you would hate to redo - that is really all scheduling comes down to.

Backing Up VMs Too

If you use virtual machines - those pretend computers running inside your server - they deserve backing up as well, because they can hold their own files and settings.

A virtual machine keeps its whole contents in a large file on your server. Backing that file up means you can bring the virtual machine back if something goes wrong inside it, much like restoring a real computer from an image. If you do not run any virtual machines, you can happily skip this page.

• A virtual machine's file can be large, so plan the space for it.
• It is usually best to back it up while the machine is shut down.
• Treat it like any other important file in your 3-2-1 plan.

How Much This Costs

Good backups do not have to be expensive, and the peace of mind is worth far more than the price. Here is a rough sense of what to expect.

A sensible plan is often a one-time drive purchase for a local copy, plus a modest monthly cloud fee for the off-site copy of your most precious files. You can keep the cloud bill small by backing up only what truly matters - your photos and documents - rather than everything.

A Simple Whole-Server Backup Plan

Let us tie it all together into one plain plan you could set up over a weekend. Nothing fancy - just solid coverage for all three kinds of cargo.

That is a genuinely strong setup, and none of the steps are hard on their own. Do them one at a time, and by the end you will have a server you can trust and truly relax about.

• Turn on the flash configuration backup, including the official cloud option.
• Install the appdata backup plugin and set it to run weekly to a separate drive.
• Back up your important files to a second drive on a nightly or weekly schedule.
• Add a cloud or off-site copy of your most precious files for the 3-2-1 off-site piece.
• Turn on notifications so you hear about any backup that fails.
• Test a restore a few times a year to be sure it all works.

A Simple Checklist

Here is the whole thing boiled down to a checklist you can tick off. Print it, stick it near the server, and work through it at your own pace.

• Flash drive configuration is backed up (and cloud backup is on).
• Appdata backup plugin is installed and running on a schedule.
• Important files are backed up to a second drive.
• At least one copy is kept off-site (cloud or another location).
• Off-site copy is encrypted with a password kept somewhere safe.
• A few older versions are kept, not just the newest copy.

What's in the 27-page PDF

• Why parity is not a backup, and what a real backup is
• The three things to back up: the flash drive, appdata, and your files
• Where to send backups, and the simple 3-2-1 rule
• Automating backups and testing that a restore really works
• Recovering after the flash drive fails or appdata is lost
• A simple whole-server backup plan and a checklist

Why I wrote this

I write these as printable handouts because a guide you can keep in a drawer beats a web page you have to find again. No jargon, no judgment, no rushing. If you'd rather have someone sit beside you and go through it together, that's a flat $99 first visit with the 30-day follow-up included — serving Portage County from Atwater, Ohio. — Bill