Dear Proxmox-Team (and others),
I am currently migrating my single-node virtual-machines to a VXLAN and plan to do so by using the redirected backups. In that context, the following problem occurs:
I am using 2 backup storages: One local hdd-raid and one remote proxmox backup server - who serves as offline backup to save energy and mitigate possible attacks from within the network.
While this is fine, switching to the context of the local backup storage after having opened the PBS storage (which is always the case in my configuration) will also lock the local backup interface with the "external" error message from the PBS storage. Therefore, it is not possible to recover a VM from the vm's backup context, when one backup storage is offline and the user tried to access the backup storage at any point.
The aforementioned error message is
2. I could disable the backup storage. Possibly undesired as well, but less side effects than 1.
3. I could rename the backup storage, that the first item in the list is not the PBS but rather the local one. This is not possible in the GUI as far as i ascertained, I don't think it is possible at all. Therefore, I'd need to delete the backup configuration and reconnect the PBS with a different name. Way more undesired.
I am currently migrating my single-node virtual-machines to a VXLAN and plan to do so by using the redirected backups. In that context, the following problem occurs:
I am using 2 backup storages: One local hdd-raid and one remote proxmox backup server - who serves as offline backup to save energy and mitigate possible attacks from within the network.
The issue
When I want to recover a virtual machine from its own backup context, this context will firstly try to open the offline PBS and timeout after a while. This locks the backup context of the PBS backup storage.While this is fine, switching to the context of the local backup storage after having opened the PBS storage (which is always the case in my configuration) will also lock the local backup interface with the "external" error message from the PBS storage. Therefore, it is not possible to recover a VM from the vm's backup context, when one backup storage is offline and the user tried to access the backup storage at any point.
The aforementioned error message is
Code:
datastore not reachableWorkarounds
1. I could recover the VM from the local storage overview as well, but this approach will not let me rollback the vm within the same configuration and vmid. This approach just works, but does not offer the same functionality (in a pretty significant way tbh). So it is potentially undesired, since rollbacks should still be possible, even when one backup datastore is not reachable.2. I could disable the backup storage. Possibly undesired as well, but less side effects than 1.
3. I could rename the backup storage, that the first item in the list is not the PBS but rather the local one. This is not possible in the GUI as far as i ascertained, I don't think it is possible at all. Therefore, I'd need to delete the backup configuration and reconnect the PBS with a different name. Way more undesired.
Last edited: