9

Hi folks, I've got a VM that is running my Firefly iii instance and Paperless instance as containers. A lot of work and time goes into managing these tools and I want to make sure I don't lose them. This is my setup:

Turenas Scale machine 1 -> VM1 - Docker containers. The VM sits on its own dataset in Truenas.

I replicate the dataset to Truenas Scale 2 one a week and this machine only goes on on Sunday to save power.

I Rsync the dataset to a 3rd machine where there is a hard disk that I store offsite.

I recognize that I could lose up to one week of work but that is nothing compared to the human hrs spent building those databases from scratch.

Apart from snapshotting e rsyncing every day, what else could I do to make this more resilient without increasing CAPEX and OPEX costs?

you are viewing a single comment's thread
view the rest of the comments
[-] just_another_person@lemmy.world 3 points 2 days ago

Test a restore and see. Only way to know for sure.

[-] trilobite@lemmy.ml 2 points 2 days ago* (last edited 2 days ago)

make me shake ... brrr

I'm going to try and see is I can get a VM running on the second Truenas server using the replicated dataset. I only use the second machine to duplicate datasets in case the first machine fails and have to rebuild it.

[-] just_another_person@lemmy.world 1 points 2 days ago

That'll do it if all you're checking for is valid working operation after a restore.

Make some notes that you tested it and what you had to do to get it working in the backup job as well. Could save you A LOT of panic in the future.

this post was submitted on 22 Dec 2024
9 points (90.9% liked)

Selfhosted

40717 readers
330 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS