I use restic on TrueNAS. There is technically nothing stopping you from doing this, but you’d need to script/command this yourself. You could add a cronjob. restic is in the default PATH.
You may also wish make sure the version of restic will be suitable for your needs, as the shipped version may be older than the latest release of restic.
You should make sure you test TrueNAS upgrades before relying on future versions and restic, in the event of changes that aren’t announced.
restic settings are passed on the command line at run time, so there are no settings to be lost.
It’s not supported, but I’m doing pretty much exactly that. A few reasons:
I’m not interfering with or trying to outsmart the middleware. I’m just using a binary on the box that also doesn’t interact with the middleware. The restic binary doesn’t block when a single copy is running, so even running concurrently with a Storj Cloud Backup task should not (at least inherently) cause issues.
The binary can be replaced with your own (note the boot pool is read only) if the shipping binary ever disappeared.
Strictly speaking, with a cronjob you can run it as a non-root user. This might be good. It might lead to permissions issues that you’d need to sort out.
It’s also worth noting that iX recently announced that they would stop being direct about the software and technologies used in favor of talking about capabilities and features. However, if before upgrading you want to check what version of restic is in use, you can check the SBOMs.
If using restic like this required doing something custom or screwy with the middleware, replacing the binary that the middleware uses, or some other esoteric path, then I would look elsewhere. As it is, this is fairly low risk IMHO, but only you can judge that because only you can be responsible for your NAS.