Proxmox PBS 1.x - Design Approach with single ZFS pool and multiple clusters

[Kafoof]

Hi,

Firstly I would like to say thank you to the Proxmox team for creating this product. PBS has addressed one the major areas I thought was missing in Proxmox (incremental backups, replication) and presented challenges for us to grow on PVE and PBS has address this.

I have a few questions around recommendations for connecting PVE host across our data center to a single PBS host

Background

PVE Infra:

• We have 2x clusters w/ cephs each with 4x nodes.
• We also have roughly 12 standalone nodes as well.

PBS Design:

• 1x ZFS pool hosting 120tb
• Single server
• Each cluster has it's own account and encryption key (automatically generated from the GUI)

Challenges:
(1) Overlapping VM ID:

• Backups are recorded by VM ID on PBS
• If we backup to the ZFS pool from a different cluster then I receive the error messeges:
  

  ERROR: VM 100 qmp command 'backup' failed - backup connect failed: command error: backup owner check failed (svc-cluster1@pbs != svc-cluster2@pbs)

My questions:

1. How can I have all hypervisors backups to the same ZFS pool and avoid the VM ID overlap?
2. Is it possible to restore the VMs to a different cluster or standalone hypervisor?

Thank you.

 

[Kafoof]

In regards to answer (1) I would guess the best approach maybe to create zfs datasheet for each cluster and then datasets for each standalone host.

 

[t.lamprecht]

Hi,

How can I have all hypervisors backups to the same ZFS pool and avoid the VM ID overlap?

For now with creating different datastore backed by the same ZFS pool.
We'll support cheap namespaces inside a datastore, in the future.

1. s it possible to restore the VMs to a different cluster or standalone hypervisor?

Yes. Just add the PBS server:datastore repository there as storage, then you can see all backups and restore as you wish.

 

[Kafoof]

@t.lamprecht ,

Thank you for the response. Looking forward to testing this out.