Comment on How to make setup more resilient? Proxmox mini-PC \w iSCSI to TrueNAS
ssdfsdf3488sd@lemmy.world 1 year ago
Get rid of iscsi. Instead, use truenas scalr for nas and use an ivol to run a vm of proxmox backup server. Run proxmox on the other box with oocal vms and just backup the vms to peoxmox backup server at aratr you are comfortable with (i.e. once a night). Map nfs shares from truenas i to any docker things you are running on your vms. This is way more resilient, gets local nvme speeds for the vms and still keepa the bulk of your files on the nas.
MigratingtoLemmy@lemmy.world 1 year ago
For a home environment, this is the correct idea
ssdfsdf3488sd@lemmy.world 1 year ago
I would argue it’s the correct idea up to a fairly decently sized business. Basically anything where you don’t have the budget or the need for super fault tolerant systems (i.e. where it’s ok to very rarely have a 20 minute to an hour outage in order to save 50k+ of IT hardware costs). You can take the above and go next step to a high availability proxmox cluster to further reduce potential downtime before you step into the realm of needing vmware and very expensive highly available and fast storage as well. It gets even more true when you start messing around with truenas and differential speed vdevs (i.e build a super fast nvme one with 10-25gig networking for some applications, a cheaper spinning rust one with maybe 10 gig networking for bulk storage. It’s also nice that, by using proxmox backup server as a zvol you can take advantage of all the benefit of both zfs replication/snapshotting and cloud (jstor/wasabi s3 bucket, another truenas server at a different location) for that zvol as well as your other data you are sharing as datasets.
MigratingtoLemmy@lemmy.world 1 year ago
I would have assumed that most businesses invested in resilient hardware, but perhaps not. Thanks for the note