Restore parts of backup

[stianj]

To follow up on my misery, is it possible to restore just parts of an backup? 

I used "storage.clear('key')" instead of "storage.delete('key')" and obviously lost much of my config. That's what you get for scripting when you should have been sleeping. (But it's funny that it worked for a long time after...)

I would like to restore mqtt client and new visu config from my nearly three months old backup (yes, I know) - but not touch scripts and objects and stuff. 

Is there any way?

[Daniel]

The Visu has its own backup/restore option so if you restore old backup and make backup of visu then you can restore it back in latest backup.

[stianj]

Ok, that will work, thanks.

Just browsed through a project backup, and I see under storage/db there is both a backup.db and a current.db - there is no way that can help me? When is the current.db copied to backup.db, so to speak?

[admin]

During each sync (once in 30 minutes) current.db is renamed to backup.db and old backup is removed. Certain apps like Visu use Redis to store the configuration. Only the current state of this storage is saved.

[stianj]

Ok, thanks. Last question though, I see that (new) visu, mosaic and mqtt client lost its config, while mqtt broker and zigbee kept its. Could there be other consequences I have not yet discovered?

[admin]

ZigBee uses the main database for configuration storage. Only apps that use Redis are affected in your case. Any scripts that use storage functions will also lose the stored values.

[stianj]

Ok, thanks. Just noticed that all my MQTT GA's are still being updated, even though the MQTT client is with no topics or connection settings or anything. Interesting.

[admin]

Most apps load the whole configuration when starting up. The app will continue to function if the configuration is deleted afterwards but the app is not restarted.