[PR #9615] [CLOSED] Add RDB/AOF persistence for backups #8160

Closed
opened 2026-02-26 16:31:59 +03:00 by kerem · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/community-scripts/ProxmoxVE/pull/9615
Author: @pshankinclarke
Created: 12/3/2025
Status: Closed

Base: mainHead: val-backup


📝 Commits (2)

📊 Changes

1 file changed (+7 additions, -0 deletions)

View changed files

📝 install/valkey-install.sh (+7 -0)

📄 Description

✍️ 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 that appendonly and save were 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.

Link: # [discussion 3446] https://github.com/community-scripts/ProxmoxVE/discussions/3446

Prerequisites (X in brackets)

  • Self-review completed – Code follows project standards.
  • Tested thoroughly – Changes work as expected.
  • No security risks – No hardcoded secrets, unnecessary privilege escalations, or permission issues.

🛠️ Type of Change (X in brackets)

  • 🐞 Bug fix – Resolves an issue without breaking functionality.
  • New feature – Adds new, non-breaking functionality.
  • 💥 Breaking change – Alters existing functionality in a way that may require updates.
  • 🆕 New script – A fully functional and tested script or script set.
  • 🌍 Website update – Changes to website-related JSON files or metadata.
  • 🔧 Refactoring / Code Cleanup – Improves readability or maintainability without changing functionality.
  • 📝 Documentation update – Changes to README, AppName.md, CONTRIBUTING.md, or other docs.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/community-scripts/ProxmoxVE/pull/9615 **Author:** [@pshankinclarke](https://github.com/pshankinclarke) **Created:** 12/3/2025 **Status:** ❌ Closed **Base:** `main` ← **Head:** `val-backup` --- ### 📝 Commits (2) - [`e377391`](https://github.com/community-scripts/ProxmoxVE/commit/e377391b763a5d551d291ec70da175db7bb22bfd) testing backups - [`2d86379`](https://github.com/community-scripts/ProxmoxVE/commit/2d863798c2515668ce49862e52a10c69ac5b649f) revert urls to upstream ### 📊 Changes **1 file changed** (+7 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `install/valkey-install.sh` (+7 -0) </details> ### 📄 Description <!--🛑 New scripts must be submitted to [ProxmoxVED](https://github.com/community-scripts/ProxmoxVED) for testing. PRs without prior testing will be closed. --> ## ✍️ 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 that `appendonly` and `save` were 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] https://github.com/community-scripts/ProxmoxVE/discussions/3446 ## ✅ Prerequisites (**X** in brackets) - [X] **Self-review completed** – Code follows project standards. - [X] **Tested thoroughly** – Changes work as expected. - [X] **No security risks** – No hardcoded secrets, unnecessary privilege escalations, or permission issues. --- ## 🛠️ Type of Change (**X** in brackets) - [ ] 🐞 **Bug fix** – Resolves an issue without breaking functionality. - [X] ✨ **New feature** – Adds new, non-breaking functionality. - [ ] 💥 **Breaking change** – Alters existing functionality in a way that may require updates. - [ ] 🆕 **New script** – A fully functional and tested script or script set. - [ ] 🌍 **Website update** – Changes to website-related JSON files or metadata. - [ ] 🔧 **Refactoring / Code Cleanup** – Improves readability or maintainability without changing functionality. - [ ] 📝 **Documentation update** – Changes to `README`, `AppName.md`, `CONTRIBUTING.md`, or other docs. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
kerem 2026-02-26 16:31:59 +03:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ProxmoxVE#8160
No description provided.