From: Laurent GUERBY <laurent@guerby.net>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>,
Thomas Lamprecht <t.lamprecht@proxmox.com>
Subject: Re: [pbs-devel] [PATCH] tape: forbid operations on a s3 datastore
Date: Sat, 26 Jul 2025 23:19:17 +0200 [thread overview]
Message-ID: <ad4d893fad70444ed36ebcd1cefbf58081d905e5.camel@guerby.net> (raw)
In-Reply-To: <fb24d883-28cd-47b2-abde-33ee98cf0d78@proxmox.com>
On Thu, 2025-07-24 at 08:50 +0200, Dominik Csapak wrote:
> Hi
>
> On 7/23/25 21:51, Thomas Lamprecht wrote:
> > This was fine and I applied it but still have some comments on one
> > of the arguments that would indicate that this never makes sense to
> > have, as IMO it can.
> >
> > Am 23.07.25 um 16:31 schrieb Dominik Csapak:
> > > namely:
> > > * backup to tape from s3 (including a configuring such a job)
> > > * restore to s3 from tape
> > >
> > > It does not work currently, but it probably does not make sense to allow
> > > that at all for several reasons:
> > > * both are designed to be 'off-site', so copying data from one off-site
> > > location to another directly does not make sense most of the time
Hi,
With my CISO hat on I see tapes physically removed from the tape
library as an essential security tool providing the "offline" property
to one copy of the backups, this is orthogonal to "off-site" being
discussed here.
S3 is typically online, even if some providers offer S3 to
tape/offline.
Bandwith/delay constraints especially for full restore after a
successful deep cyberattack might favor an "on-site "offline" tape
backup for many organization.
Backup solutions like Veeam already provide "object to tape".
I think it would be nice to have this feature in the PBS roadmap if
there's no technical roadblock to having the same feature set for S3
and directory datastore, including tape.
Sincerely,
Laurent GUERBY
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
next prev parent reply other threads:[~2025-07-26 22:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 14:31 Dominik Csapak
2025-07-23 18:37 ` [pbs-devel] applied: " Thomas Lamprecht
2025-07-23 19:51 ` [pbs-devel] " Thomas Lamprecht
2025-07-24 6:50 ` Dominik Csapak
2025-07-26 21:19 ` Laurent GUERBY [this message]
2025-07-28 7:25 ` Christian Ebner
2025-07-28 18:08 ` Laurent GUERBY
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=ad4d893fad70444ed36ebcd1cefbf58081d905e5.camel@guerby.net \
--to=laurent@guerby.net \
--cc=pbs-devel@lists.proxmox.com \
--cc=t.lamprecht@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.