I backup all my "backup-worthy" shares (including the previously mentioned "backups" share), using restic to Backblaze B2. If you're ok with the data from the flash drive being stored unencrypted on unRAID's servers, you can also use the MyServers plugin. The important part is, that you should stop your containers, before backing up, and in case of any issues send a notification to unRAID which then can send you an email or any other notification (the plugin does all of that for you). I didn't want to use the Appdata Backup/Restore v3 plugin, as it didn't provide me with all the functionality I required, but you may as well just use it. However, especially for paperless, I do want all the documents in a readable format in my backup.Īs not all tools in the containers provide a native backup functionality I additionally backup the appdata share using yet another user script, which stops all containers, rsyncs /mnt/user/appdata to a backups share and afterward restarts the containers. This step is not strictly necessary, because I also backup the appdata share. See the documentation for more details.įor other tools I'm mostly using the webGUI provided backup schedules, backing up to a backups share. This exports all the documents including the tags and the metadata to a share which is mounted as /export into the container. Wherever possible, I try to use the backup functionality build into the application running in the container.įor paperless this is a scheduled user script running:ĭocker exec -i paperless-ngx document_exporter. I did set up my backup strategy in the last couple of days, and had the same thoughts that you're having.Īs a rough strategy I went with your second option, but with some specifics: You can also manually download a zipped backup of flash at Main - Boot Device - Flash - Flash Backup. My Servers plugin will keep a current backup of your flash drive on the Unraid cloud. This contains your license, your disk assignments, any and all settings from the webUI, including docker templates. Your configuration is in the config folder on flash. These archives can be easily replaced (and are when you upgrade). The OS is unpacked fresh from archives on the flash drive, into RAM, at each boot, and it runs completely in RAM. You don't need to worry about backing up the OS, it is easily replaced. None of the OS or your configuration is stored on your data disks. My backup server is just parts and disks leftover from previous hardware upgrades, usually powered down.Īnother very important thing you must always have a current backup of, your flash drive. I use rsync script to backup important things to externals for storage offsite, and also to backup less important things (media) to my backup server. If you have VMs you will probably want to backup their vdisks, there is also a plugin for that. Typically you would back these up to the array, and you could include those backups as sources in your backup plan to external disks. You will use this to backup appdata (docker application working storage), and also libvirt.img (VM definitions). What are your thoughts about the backup system using 2-bay / 4-bay external drives? Which backup tool is most suitable for the described use case? What are your thoughts about the different backup strategies? That way, all I have to do is take the case, power it up, conenct it to my server and start the backup. the hard drives) physically protected and easily accessible, I thought of buying an external case with 2 or 4 bays. In the near future, I would like to upgrade to a second 4TB storage drive, and perhaps a third and fourth later. I currently have two 4TB hard drives, one parity and one storage. So the backup is mostly separated from unraid. I should also mention that I want to use external hard drives as backup storage, connected to unraid only for backup. "rsync Incremental Backup" script (writte by mgutt) I found the following backup apps that could be suited: However, which is more advisable in your optinion and which tool should I use? Since I would like to save the "metadata" of my installed apps, only strategy two and three seem reasonable for my use case. Save everything, a full backup of the whole system. Would this also include my docker configurations? Now "metadata" from paperless, jellyfin and other tools should be included in the backup. However, in this case I would not be able to restore things like paperless tags or jellyfin metadata. Save only data from shares or whole data shares, e.g. I would like to be able to restore my unraid system fast in case of critical failures (e.g. I have some questions regarding a reasonable backup strategy.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |