joedid

The past month has been full of configuration changes to my server, and this is a continuation of that. My OS drive runs on a single SSD, mostly because I ran out of SATA cables when I built it. This isn't a big deal to me, since I’ve been taking manual backups of the configuration, but I decided it was time to automate the process while keeping it mostly GUI-based so that the backup settings would be included in the backup I was making. After a bit of digging, I found the best way to grab the configuration file and secret key was through the API. All of this was done on Fangtooth 25.04. Here are the steps I took. Create API token Create dataset for the saved files Login and setup a cloud storage account within TrueNAS Drop the backup script into dataset that was created Create a cron job to run the script. Configure a Cloud Sync Task to push and sync the dataset to the cloud account. In the first step, I generated an API token and copied it to a safe location. TrueNAS will only sh...

As I sit here and watch rsync create another 10TB copy of my data for the fourth time in the last week, I'm thinking about how this could have gone differently and it's unclear as I write this if the problem was me. This is my experience converting my 4 drive mirror vdev into a 6 drive raidz2 on my TrueNAS server in my home while I work around the typical problems with a hobby, limited resources. As a home user, with a healthy paranoia of data loss, I need to be more efficient with the drives I have and a 50% loss with a mirror was proving too much. I'm going to start at the beginning so when I read this back in a few years, I remember the pain. A year ago I set up a TrueNAS Scale for the first time, and created clever names for my pools like "Isla Nublar" (Jurassic Park reference) and "Top Secret". These names have spaces and capitalization and for over a year had driven me crazy in the CLI. Also at the time, and this is the larger of the two problems, ...