Quote from: Katherine_Alicia on Today at 08:45:26 AM

as for Why I want to do this, it`s because before I started out I made my mind up that I was going to be the best possible node runner I could be with the least amount of downtime as I could manage, I even have battery backed internet in case the power goes down. I didn`t want to build some janky pile of rubish just to say I`m a node runner, I wanted to do a good job and be as reliable as possible and not have to be repairing it every couple of days, which includes waiting another 2 days 5 hours for the blocks to be re-synced again if one of my drives fails, this way I can be up and running again in a few hours at most.

So instead of 2 days downtime in case your drive fails after many years of running, you'll have monthly short downtimes to create a backup? That doesn't make sense.
I wouldn't worry about downtime much anyway, as long as it's running most of the day, it's fine. Bitcoin Core can handle downtime from individual nodes. Decentralization comes with built-in redundancy.

For what it's worth: on my new server, I'm running this:

Code:

/home/loyce/bitcoin-28.0/bin/bitcoind -maxuploadtarget=400000 -dbcache=4096

It sent 2.3 TB in a week. I wouldn't want that at home.