Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[question] Backup NVM regularly? #2084

Closed
LordMike opened this issue Dec 20, 2021 · 2 comments
Closed

[question] Backup NVM regularly? #2084

LordMike opened this issue Dec 20, 2021 · 2 comments
Assignees
Labels
question Further information is requested

Comments

@LordMike
Copy link
Contributor

LordMike commented Dec 20, 2021

Hey,

I'm considering switching z-wave stick, and in that process I realized that the memory of the stick isn't backed up at all, when backing up the store directory. Clicking the "NVM Backup" creates a NVM_.....bin file in the store directory - but is there any way to:

  • Create this file regularly? (every month/week/night/on include/exclude f.ex.)
    • I think the current API call is through websockets, which I don't want to automate in curl :P
  • Remove old bin files, so there is a rolling set of N files
    • Alternatively overwrite the same one always, then my own backup program can show me snapshots

Note: The warning says the z-wave radio is disabled while backing up, so I can understand why you would not want to do this backup immediately after inclusion/exclusion... Maybe a compromise could be that every night, a backup job runs that checks if anything has changed since last backup. I imagine the NVM backup won't contain stuff like states -- although it might contain neighbor/route maps, which can change once in a while..

Mike.

@LordMike LordMike added the question Further information is requested label Dec 20, 2021
@kpine
Copy link
Contributor

kpine commented Dec 20, 2021

See discussion #2068

@robertsLando
Copy link
Member

@LordMike Hi Mike! Join the discussion on #2068 :) We are speaking about that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants