From: aderumier@odiso.com
To: martin.konold@konsec.com,
Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] Single BPS for multiple PVE lead to namespace conflict
Date: Mon, 11 Jan 2021 08:20:40 +0100 [thread overview]
Message-ID: <927b14bed1ae378ee740fe7b4eb75cbecaa80811.camel@odiso.com> (raw)
In-Reply-To: <51f40ab8b46dac203ce907c46318645f@konsec.com>
Hi,
I think it's on the roadmap.
(could be great to have some king on namespace too on storages, to be
able to share them across multiple cluster)
Le samedi 09 janvier 2021 à 22:11 +0100, Konold, Martin a écrit :
>
> Hi there,
>
> I am pretty new to Proxmox and deeply impressed by the quality of
> many
> aspects of its design and implementation.
>
> In my testing I observed that in case I have multiple PVE Clusters
> and
> perform backups to a single datastore on a single PBS I experience a
> lack of namespaces.
>
> Why a single datastore on the PBS for multiple PVE Clusters?
>
> For reasons of efficiency and avoidance of fragmentation I would like
> to
> use a single RAIDZ2 as a target. The problem now arises that both PVE
> clusters see the same "vm/100/{dateTime}".
>
> What about prefixing the backups with the Cluster-Name e.g.
> "pve1/vm/100{dateTime}"?
>
> Is there something I overlooked sofar?
>
> Regards
> ppa. Martin Konold
>
> --
> Martin Konold - Prokurist, CTO
> KONSEC GmbH - make things real
> Amtsgericht Stuttgart, HRB 23690
> Geschäftsführer: Andreas Mack
> Im Köller 3, 70794 Filderstadt, Germany
>
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
next prev parent reply other threads:[~2021-01-11 7:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-09 21:11 Konold, Martin
2021-01-09 22:36 ` Jan Brand
2021-01-11 7:20 ` aderumier [this message]
2021-01-11 7:36 ` Dominic Jäger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=927b14bed1ae378ee740fe7b4eb75cbecaa80811.camel@odiso.com \
--to=aderumier@odiso.com \
--cc=martin.konold@konsec.com \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.