Add RDB/AOF persistence for backups #9615
Open
+7
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
✍️ Description
I enable RDB and AOF persistence in the same instance to make it as easy as possible for Proxmox backups to restore Valkey data. I confirmed that Debian already stores the RDB/AOF files at
/var/lib/valkey. After the install I checked thatappendonlyandsavewere set correctly, and RDB + AOF persistence were enabled and writing. Finally I wrote a small dataset, ran a backup from the host, restored it into a new container, and confirmed the dataset was present.🔗 Related PR / Issue
Link: # [discussion 3446] #3446
✅ Prerequisites (X in brackets)
🛠️ Type of Change (X in brackets)
README,AppName.md,CONTRIBUTING.md, or other docs.