Consider the following situation:
I had an old lab setup with 3 PVE 7.0 Nodes.
All of them were using a single PBS 2.0 Backup Server
Each of the 3 Nodes had it's own Backup Encryption Key
Then I tore apart the 3 Nodes but kept the Backups on the PBS for later use.
Now I got myself a new, single, more powerful server.
I want to restore the backed up VMs/CTs from the PBS to that new server.
As all of the VMs/CTs that were backed up from different nodes are encrypted with different encryption keys, I need to change the encryption key in the PVE UI of the new PVE server everytime I want to restore a backup from the PBS
I would like to have added:
* a new colum "Key Fingerprint" to the following URL https://<PVE_NODE_IP>:8006/#v1:0:=storage%2F<PVE_NODE_NAME>%2F<PBS_NODE_NAME>:4:=jsconsole:=contentBackup:::4:=consolejs:2
* option to add multiple encryption keys to the PVE node for restoring backups from different other nodes at the same - without the node's own encryption key being overwritten. Of course these restore-keys should not be used for new backups created by the PVE node while it's holding multiple keys for restoring
I had an old lab setup with 3 PVE 7.0 Nodes.
All of them were using a single PBS 2.0 Backup Server
Each of the 3 Nodes had it's own Backup Encryption Key
Then I tore apart the 3 Nodes but kept the Backups on the PBS for later use.
Now I got myself a new, single, more powerful server.
I want to restore the backed up VMs/CTs from the PBS to that new server.
As all of the VMs/CTs that were backed up from different nodes are encrypted with different encryption keys, I need to change the encryption key in the PVE UI of the new PVE server everytime I want to restore a backup from the PBS
I would like to have added:
* a new colum "Key Fingerprint" to the following URL https://<PVE_NODE_IP>:8006/#v1:0:=storage%2F<PVE_NODE_NAME>%2F<PBS_NODE_NAME>:4:=jsconsole:=contentBackup:::4:=consolejs:2
* option to add multiple encryption keys to the PVE node for restoring backups from different other nodes at the same - without the node's own encryption key being overwritten. Of course these restore-keys should not be used for new backups created by the PVE node while it's holding multiple keys for restoring