[pbs-devel] [PATCH] tape: forbid operations on a s3 datastore

Laurent GUERBY laurent at guerby.net
Sat Jul 26 23:19:17 CEST 2025


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




More information about the pbs-devel mailing list