Put the name `TrueNAS` back in the config file names

Feature Requests
1

Problem/Justification
on TN 25.04.2.3 when I download the config file it has the name tns-25.04.2.3-20250901175436.tar

it used to be in the format

tns-TrueNAS-SCALE-24.04.2.5-20250901173653

Impact
I now have to manually rename the file so I know it is a TrueNAS config backup.

Additional
I understand why SCALE was removed but I think a developer got a bit carried away. :smile:

2

Do you?
You could put them in a folder called something along the lines of “truenas configs”.

3

Of course, but why add an additional step when I did not before.

4

You got me there.
I wish you the best of luck. :slight_smile:

1 Like
5

Though it does matter much to me personally, The tns is the server name.
The actual config file will contain the server name like so: saturn-25.04.2-20250814170321.tar It has been this way at least since bluefin.

I have three systems so I have to keep the configs apart so I created a directory structure of server_backup_cfgs → myserver_config_backups where myserver matches the servers name. Then under each server directory I have individual directories for each major release of Truenas such as cobia, dragonfish bluefin, eel, fangtooth. I always know where to look if I need a config file based on server and Truenas version.

6

When I do upgrades I also backup my important stuff like virtualmin config, webmin config, pfsense config and these all go in one folder so this is good example why it needs to have truenas in the name.

7

It should have the server name in the config file name which it does. Your server is named tns. If you want to add Truenas then name the server tns-truenas

If I have more than one or two servers I sure don’t want some hoge poge of maybe locating the proper config backup when I need it yesterday, so I put the server backups in a system as described which has worked fine for many years. Any additional config file backups (from pfsense for example) they go within individual sub-directories of the server directory. The app config should contain the name of the server, the app name if necessary, and the date/time it was taken. It also makes it easier to automate taking backups of many servers and other devices.

8

As mentioned all my other appliances have the appliance name in it, eg pfsense, webmin, virtualmin. There is a reason for this.

Changing my server name to add truenas in the name is not a solution.

9

Hum… I never noticed it. Mine has the name of my server and the date of the file. That is all I need to know which server the config file belongs to.

@shoulders The “25.04.2.3” doesn’t tell you it is a TrueNAS Fangtooth file that belongs to the “tns” server?

Now in all fairness, I have mine emailed to me once a week with a name format of truenas_Config_25.04.2.1_2025_08_27.tar as my last received one. “truenas” is the name of my server, so the same as the normal files the GUI generates. But I could change it to whatever I want in the script.

Actually it is a solution, just not the one you desire.

And do not forget to vote for your own suggestion.