A forum topic for reporting bugs and other issues with CastleOS
Config Backup Strategy
Tommy Long Posts: 218
11/16/2016
|
Couple of weeks ago, had a power outage causing PC running CastleOS to abruptly get powered off. When power was restored it turned out all the config files including backup where empty. Glad I was home to manually fix this and not on vacation. So I have to ask, shouldn't there be a strategy that says if the current config.xml is corrupt, try the backup....and have the backup saved in a way where either it or the config.xml file both don't get corrupted.
Speaking of backups, I would have to say I don't have an appreciation for why the config files and their backups have to be saved on a time scale of seconds. This seems unnecesary.
|
|
0
link
|
Chris Cicchitelli Administrator Posts: 3390
11/16/2016
|
There is, it didn't work, I'm looking into why. Ultimately you can't avoid corruptions, but it should auto load the backup. But if the backup is also, blank, it has nothing to load. I'll update you when I figure out why.
Regarding the save frequency, CastleOS keeps an image of the config file in memory for performance reasons. Every few seconds it saves a snapshot of the configuration from memory back to disk. This is done for performance reasons.
|
|
0
link
|
Chris Cicchitelli Administrator Posts: 3390
11/17/2016
|
I believe I found and fixed this issue. It should now never load a blank file. If it finds a corrupted file, it will attempt to load the backup file to automatically replace the primary.
|
|
0
link
|