Automatic backup stored as .db instead of .tar

[hightime81]

Version: TrueNAS-SCALE-22.02.4

I know how to manually backup the config file, but after searching around in forums I found a method from an old freenas thread that helped me get the cp and cron job setup up to backup the config file to a cloud service.

Only concern is that the file extension is .db while the manually downloaded files have always been .tar.

Will there be an issue using this .db instead of the normal .tar to restore my config in case of hardware failure?

Thanks!!!

 

[Samuel Tai]

The TAR config backups contain freenas-v1.db. So long as you rename your DB backup to the expected name, and wrap it in a TAR file before uploading a config, you should be fine.

 

[hightime81]

The TAR config backups contain freenas-v1.db. So long as you rename your DB backup to the expected name, and wrap it in a TAR file before uploading a config, you should be fine.

Thanks! Really appreciate it!

 

[winnielinnie]

I found a method from an old freenas thread that helped me get the cp and cron job setup up to backup the config file to a cloud service

Why not just replace the "cp" part in the script to instead use "tar" to create the same type of tarball that the GUI does anyways?

Configuration backup from terminal within the server?

How do I generate a configuration backup, with a terminal command within the server?

www.truenas.com

 

[Samuel Tai]

@hightime81, I looked at the source code for the config backup/restore at https://github.com/truenas/middleware/blob/master/src/middlewared/middlewared/plugins/config.py. You can restore from a DB file that's not wrapped in a TAR file. You just won't restore any of the optional files like root's SSH authorized_keys or the password secret seed.