Backup: Only Gladys, or also mqtt, zigbee2mqtt, node-red,...?

Gladys Plus
1

Hello,
So far I was using Gladys with devices integrated natively, and the backup offered by GladysPlus reassured me.

But I decided to move to another level of integration, communicating over MQTT with a small server developed in python that controls certain devices (like my shutters), and to also rely on node-red for other integrations (my Tuya devices, retrieving the EDF Tempo days, …). I’ve just spent two days on it, and it’s very powerful! Cool :wink:

But since all that is not ‹ purely › Gladys, I wonder what happens with the backup made by GladysPlus… Is everything included (but I don’t really believe it…) ? What should I back up manually to be able to restore if I ever need to?

Thanks in advance for the response!

2

the flows (which you can share!

3

Hello @StephaneB !

So currently the Gladys Plus backup saves Gladys’s database, and that database contains the information necessary to correctly restart the MQTT and Zigbee2mqtt integrations (it’s a recent development that required a lot of work and has been available since 4.18: Gladys Assistant 4.18 : Sauvegarde Zigbee2mqtt et gestion native des boutons (clic simple, double, ...))

However, your Python server is not backed up (which is logical :p), and Node-RED isn’t either.

To back up your Node-RED, see what the Node-RED project recommends for automatic backups (if you want to automate it); otherwise what @cce66 suggests also works manually

Note that for now this request only talks about launching Node-RED, not backing it up. I don’t even know if Node-RED offers an API to retrieve a backup (like Zigbee2mqtt does, for example).

4

While searching, he also has this solution… which I’m going to set up! :slight_smile:
https://www.npmjs.com/package/backup-docker
plus a copy to my NAS so I’ll be relaxed about backing up my Node-RED flows!
@pierre-gilles it’s true that having Node-RED managed by Gladys would be really great since Node-RED can make up for Gladys’s shortcomings while we wait for the most common gaps to be handled by Gladys — specific particular needs are not economically viable to integrate, but Node-RED lets you handle them and there are so many examples on the web that it helps!
For me the Gladys (management of common cases) + Node-RED (management of particular cases) pair is ideal because of the simplicity of implementing common cases via Gladys, and for particular needs, well, you just have to rack your brains and through the community and the web you can find them! :wink:

5

I’m reposting my comment here, but regarding Node-RED, I wouldn’t recommend using this kind of tool to back up Node-RED — it’s the best way to end up with corrupted backups, or worse, to break your production installation.

By searching on Google, I see there are ways to automate backing up Node-RED directly from Node-RED :slight_smile:

Otherwise, if you want to take a « folder backup » approach, I’d rather recommend making a script:

  • That stops Node-RED
  • Makes a backup of the Node-RED folder (there are great tools like rclone for that)
  • Restarts Node-RED
6

ah yes, but I was only talking about backing up the node-red part, the Gladys part has Gladys-plus that does the job and you don’t even need a

7

Thank you for your responses. This will allow me to add the necessary manual backups :+1:… while waiting for Gladys to do it :wink:.

1 Like