With many apps and esp PVC storage depending on what Scale version you are on, you may find yourself bogging your system down a lot by snapshotting the applications pool. If you do decide to snapshot it, then, I would not suggest keeping very many. There are a lot of posts in the old forums about this issue.
For myself, I don’t do any snapshots of that pool. Nor do I even do a true full backup. I have 4-5 different backups, and, they all are for different purposes, some offsite for example as a home full backup when your house burns = lost backups. In the end, there is a large set of data I never backup, as it’s cache space, recordings, work space, and stuff I would live without if I lost it forever, of minor value like antenna recordings that I watch and get rid of anyway. There are other ways to watch those if I lose them. I organized my pools in this manner. This then allowed me to use different techniques for different data. My main offsite non ZFS backup uses Kopia and it’s just a few minutes a day. I also do replication to a VPS setup with zfs. I also use an external drive to replicate to each night of lesser important stuff and I rotate that to my safe deposit box. And others. All are automated except taking the backup to the safe deposit box so no time spent.
I have not heard many folks of trying to get a full backup, except those who run Scale in a vm.
Back to your point, for me, I simply have a note file for each application as to the parms specified. That’s all I would lose if the app pool was lost somehow. In < 30 minutes, I could type it all in again. Note I have a mirrored app pool, so disk failure wise, both have to die. Fire wise, theft wise, it’s gone of course. So, very unlikely I’d ever need the notes to recreate but possible.
What you do DO want for sure is to download here and there the system config, system settings → General → Download File. Keep this on some machine as that is basically all your configuration, except apps. And a UPS!
This is all going to change in electric eel. I suspect there won’t be a need to backup the dataset as configs will be stored in yaml files. We’ll see.