LocalNode
How it worksDemoAppsPricingFAQShop now
← All guides
Home/Community/Backing Up Your Entire Localnode Configuration

Backing Up Your Entire Localnode Configuration

Advanced
Beginner
5 min read
Published: May 7, 2026

Was this helpful?

Help us improve our community guides.

In this guide

  • Overview
  • Understanding the AppData folder
  • Step 1: Creating the automated backup
  • Step 2: How to restore a backup

Need direct help?

LocalNode Care Plan members get priority remote support.

Email Support →

More in Advanced

Adding External Storage to Your Localnode

Adding External Storage to Your Localnode — Step-by-step guide for your LocalNode.

5 min read

Adding Smart Home Devices to Home Assistant

Adding Smart Home Devices to Home Assistant — Step-by-step guide for your LocalNode.

5 min read

Connecting Home Assistant to Localnode

Connecting Home Assistant to Localnode — Step-by-step guide for your LocalNode.

5 min read
LocalNode

Plug-and-play home server. Your data, your hardware, your rules.

Product

How it worksDemoAppsCommunityPricingFAQ

Support

ContactShipping & ReturnsTrack Order

Legal

Privacy PolicyTerms of ServiceShipping Policy
© 2026 LocalNode. Built for people who value their privacy.Denton, TX · hello@localnode.tech

If you spent hours setting up Home Assistant automations, Jellyfin metadata, and Nextcloud users, you do not want to do it again if your hard drive fails. You must back up your system configuration.

Overview

Because LocalNode uses Docker, the system is beautifully separated into "App Code" and "App Data". You do not need to back up the app code (the containers); those can be re-downloaded from the internet in 3 minutes. You only need to back up the App Data (your settings, databases, and preferences).

Understanding the AppData folder

Every single app on the LocalNode stores its configuration inside a specific directory, usually /opt/localnode/appdata.

  • Jellyfin's watch history and user accounts? In that folder.
  • Home Assistant's Zigbee network map? In that folder.
  • AdGuard Home's DNS blocklists? In that folder.

If you zip that single folder and move it to a safe place, you have backed up the brains of your entire server.

Step 1: Creating the automated backup

Just like backing up Immich photos, we will use the built-in LocalNode Backup Manager to save this data to an external drive.

  1. Plug in your external USB backup drive.
  2. Log into your main LocalNode dashboard at http://localnode.local.
  3. In the sidebar, click on Backup Manager.
  4. Click Create Backup Task.
  5. Under "Source", select System Configuration (AppData).
  6. Under "Destination", select your external drive.
  7. Set the Schedule to Daily (e.g., 04:00 AM).
  8. Set the Retention Policy to keep the last 7 or 14 backups. The configuration data is very small (usually under 2GB total), so keeping 14 copies takes up almost no space.
  9. Click Save & Enable.
Illustration pending

LocalNode Backup Manager listing scheduled AppData jobs such as nightly configuration snapshots.

Reserved for a LocalNode product screenshot when available; UI layout may differ from third-party docs.

⚠️ Warning: This backs up the configuration. It does NOT back up your 4TB of movie files in Jellyfin. To back up your media, you need a separate backup task targeting the /media folder to an external drive large enough to hold it.

Step 2: How to restore a backup

If disaster strikes (e.g., a power surge kills your SSD), you would buy a new SSD, flash a fresh copy of LocalNode OS onto it, and plug in your backup USB drive.

  1. On the fresh server, go to the Backup Manager.
  2. Click the Restore tab.
  3. Select the ZIP file from your external drive.
  4. Click Restore.

The system will stop all Docker containers, unzip the old configuration over the blank defaults, and restart the containers. Your server will boot up looking exactly as it did the night the backup was taken.


Need help? Email hello@localnode.tech or visit localnode.tech/contact.