Configurable backup storage in update.conf

[Evilcat182]

Feature Request: Configurable backup storage in update.conf

Summary

Add a BACKUP_STORAGE parameter to update.conf so users can define which storage is used for full backups, instead of relying on auto-detection.

Current behavior

When a full backup is triggered (e.g. update <ID>), the storage is selected dynamically via:

pvesm status -content backup | grep -m 1 -v ^Name | cut -d ' ' -f1

This picks the first backup-capable storage found — which may not be the desired one. It also ignores any storage: setting defined in /etc/vzdump.conf.

Expected behavior

Users should be able to define the target backup storage in /etc/ultimate-updater/update.conf, for example:

BACKUP_STORAGE="PBS"

If left empty or commented out, the script could fall back to the current auto-detection behavior for backwards compatibility.

Proposed change in update.sh

Replace:

--storage "$(pvesm status -content backup | grep -m 1 -v ^Name | cut -d ' ' -f1)"

With:

--storage "${BACKUP_STORAGE:-$(pvesm status -content backup | grep -m 1 -v ^Name | cut -d ' ' -f1)}"

And add to update.conf:

# Storage ID to use for full backups (leave empty for auto-detection)
#BACKUP_STORAGE=""

Why this matters

Users with multiple backup storages (e.g. a local NFS share and a Proxmox Backup Server) have no way to control which one is used without manually editing update.sh — which gets overwritten on every update -up.

Environment

• Proxmox VE with 2 backup-capable storages
• Ultimate-Updater configured for full backups before updates