Backing Up Your Entire Localnode Configuration
Was this helpful?
Help us improve our community guides.
Help us improve our community guides.
Adding External Storage to Your Localnode — Step-by-step guide for your LocalNode.
Adding Smart Home Devices to Home Assistant — Step-by-step guide for your LocalNode.
Connecting Home Assistant to Localnode — Step-by-step guide for your LocalNode.
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.
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).
Every single app on the LocalNode stores its configuration inside a specific directory, usually /opt/localnode/appdata.
If you zip that single folder and move it to a safe place, you have backed up the brains of your entire server.
Just like backing up Immich photos, we will use the built-in LocalNode Backup Manager to save this data to an external drive.
http://localnode.local.LocalNode Backup Manager listing scheduled AppData jobs such as nightly configuration snapshots.
⚠️ 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.
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.
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.