Will upgrading vnstat result in any loss of logs/database/stats? about vnstat

[vergoh]

Upgrade directly from both versions 1.12 and 1.14 to version 1.17 is supported without losing data. Based on a quick check, neither of those linked instructions do anything destructive either. However, it depends on how the distribution packaging has been done regarding what gets removed when the package is uninstalled. It doesn't hurt to take a backup of the database files. Note that the configuration file contains new options so check those out and tune if needed. See the UPGRADE file that comes with the source package for a list of new settings and man vnstat.conf for a description of what those settings do.

[hub2git]

Thanks, Vergoh. I'll close this issue. I haven't upgraded yet. If I have issues with data loss, I may reopen this issue. :)

[hub2git]

@vergoh said

It doesn't hurt to take a backup of the database files.

Should I simply copy the relevant files and folders to my backup location? If so, which files and folders should I copy?

Or do you suggest using the --exportdb option?

http://humdi.net/vnstat/CHANGES says

1.17 / 16-Feb-2017

• Fix: --importdb was creating invalid databases since version 1.15

So since my versions are 1.14 and 1.12, I believe this "invalid-database" issue won't affect me.

[hub2git]

Another question: What happens if I upgrade directly to vnstat 2.0? Any loss of database/logs/info?

[vergoh]

During the first daemon startup of version 2.x, all found version 1.x databases get automatically imported to the version 2.x database. Because the new database is a single file for all interfaces, the old version 1.x database files are kept in place, just in case the user wants to downgrade for some reason. Nothing is lost during the import process.