local server Datastore / remote server Remote - same volume?

[alex purser]

i have 2 proxmox ve servers in different locations each running its own instance of pbs - local guests backup to a local datastore on each machine. offsite copies of these backups are then achieved by configuring each datastore as a remote on the corresponding offsite machine (i.e. each datastore is acting as a local target for local guest backups and as remote copy)

im interested to know whether its bad practice to have a datastore acting as the destination of local backups AS WELL AS pulling a copy of backups from a remote system because i seem to be observing the pruning operation deleting backups that it shouldnt.. is the bi-derectional setup causing some instability, i.e. when connectivity between sites is lost

 

[Dominic]

If I understand you correctly then names might overlap and you should create different datastores to avoid it. Your 2 Proxmox VE servers are not a cluster? Namespaces are on our roadmap.

Might be related to this or this topic.

 

[alex purser]

Hi Dominic thanks for coming back to me - correct the 2 servers are on seperate clusters (in seperate cities) so just being used as "remotes" to provide a second copy of the backups. I've deleted the datastores and recreated seperate datastores to avoid the scenario where a datastore is undergoing send and receive operations because i think this was causing the sync jobs to conflict with each other and delete things on one site they shouldnt because the alternate site hadnt synced up yet - the logical endgame for this scenario is possibly everything getting constantly deleted on both sites!.. anyway easily avoided by assigning datastores as either "local" - i.e. receiving backups directly or "remote" - i.e. pulling the contents of datastore as a secondary copy. Not sure if there is any benefit to constraining a users configuration to one or other of these scenarios in case someone else is as wild west as me!