Multiple USB Device on same Removable Datastore

[cingo_5]

Hi
I'm working on a PBS 3.4.0 and i've just realize that removable device is now managed from the gui!
Everything works great but.. my need is to have a single datastore where I can mount different disks.
I'll explain why: customers usually have a pair of disks that alternate to the server, so as to have the most recent copy away from the datacenter (to avoid the risk of theft or fire).
Usually customers should alternate the disks daily but this may not happen and I can't know exactly which disk will be connected.... for this reason my backup procedure must have only one destination storage that must be managed "dynamically".

I saw that PBS marks the uuid of the partition as "backing-device" but is it possible to assign multiple "backing-devices" to the single datastore?

thanks to anyone who can answer
Cingo

 

[cingo_5]

In the meantime I thought of another solution... with tune2fs I can copy the uuid and give it to the second disk.
The problem could be if both are connected at the same time but it should not happen since my PBS is virtualized in PVE and here I assign only one USB port.
if there are other solutions they are welcome

 

[Johannes S]

I'm not sure whether this is a good idea in the first place since PBS stores metadata on the state of the datastore inside the datastore. Maybe some staff member can chime in whether a setup like yours might led to consisteny issues or not.

Personally I would just create a datastore on the server ( on an internal storage) and dedicated sync, prune,gc,verify etc jobs for each removable datastore

 

[cingo_5]

Hi, thanks for the reply!
I had thought about the same logic of operation. local datastore where to perform daily backups and sync, in pull mode, from removable datastores.

The problem is in the case I have 2 removable datastores with active syncs, and I don't know which removable datastore is connected, I must have the syncs scheduled in the same way, so I would receive a sync with a positive outcome (the one with the active datastore) and a sync with a negative outcome (the one of the disconnected datastore).

It is not implemented yet, but it would be useful manage a failover target storage for backup tasks or a failover datastore for datastore syncs...