Feature #11042
closed
Verify backup- / configuration-file after creation
0%
Description
I have been facing corrupt configuration files when using the file (loaded on an usb-stick) during an new installation. That .... is not the right moment to detect that the file is corrupt !! (an understatement IMHO). Of cause the backup configuration software should not generate corrupt files, but that is another issue.
The problems I detected where related to double "xml-entrys" (e.g. <dhcpddata> and <dhcpdv6data>)
However it could happen elsewhere. So what I would like is that the xml-parser used to read the config-file during restore, should also be used to verify the generated new backup file generating a big warning, if something is not OK. Also as far as possible of course also generating a message where it did detect a problem, just as the program does when it is used to recover the config at restore.
Sincerely,
Louis
Updated by Jim Pingle over 3 years ago
- Status changed from New to Needs Patch
- Target version deleted (
2.5.0)
In the unlikely case that a bad backup was generated, it is unlikely anything could be done to repair it in the GUI, so warning in the GUI about when creating the backup seems like a waste of time.
If there is a problem, manually fixing the backup file and uploading it again is typically the fix anyhow, so warning on restore is much better.
But if someone else wants to code up a proposed validation process, we can review it.
Updated by Louis B over 3 years ago
Jim, at the moment you need the backup, the firewall is probably down. So you need to have it fixed as soon as possible, may be a large office can not work! That is the wrong moment to detect, your backup is failing, and you have to repair it somehow!!!
So IMHO you should know the back-up is not ok as soon as it is generated !!!
Updated by Jim Pingle over 3 years ago
Your logic is flawed because if it could detect the backup was bad it could just not make a bad backup. If it generates a bad backup it's most likely from a bug, which isn't something the user could fix. And if it prevents you from making a backup in that situation then you would have no way to fix it.
If you do not regularly test your backups, that is your own procedural problem, not a problem the firewall can solve.
Updated by Louis B over 3 years ago
Jim, if the software which checks the backup-file when loaded can check if backup is OK, the same software could do that right after generation of the backup as well.
Updated by Jim Pingle over 3 years ago
That is true but is also a non-statement. I already explained why that is irrelevant.
Updated by Jim Pingle over 3 years ago
Looks like your actual problem (based on your forum thread) is this: #11050
Under normal conditions on a release, that is unlikely to happen. During development, bugs are more common. Users should not be using development versions in production, so there are no concerns about having to worry about uptime in production environments. (And if it is that mission critical, they should be using HA and thus it is still not a major concern).