From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>,
Turritopsis Dohrnii Teo En Ming <tdtemccnp@gmail.com>
Cc: ceo@teo-en-ming-corp.com
Subject: Re: [pbs-devel] Does Proxmox Backup Server support immutable backups?
Date: Fri, 23 Jun 2023 17:09:45 +0200 [thread overview]
Message-ID: <87a75af4-3be2-c334-67d7-8fddab1a986e@proxmox.com> (raw)
In-Reply-To: <CAD3upLsi+6Pz1Z3SoPC_5S9Gv__H8T8X1BWrQBbnqDO5BF6TKA@mail.gmail.com>
Hello,
Am 23/06/2023 um 16:49 schrieb Turritopsis Dohrnii Teo En Ming:
> Subject: Does Proxmox Backup Server support immutable backups?
>
> Good day from Singapore,
>
> Does Proxmox Backup Server support immutable backups? We want to make
> our backups fully resistant to ransomware.
Proxmox Backup Server provides this via its permission system.
If you add a user, or API Token, that only has the Datastore.Backup privilege
(via the DatastoreBackup role) on a datastore, then all sites using such a
credential can add new backups but never delete (prune) them.
https://pbs.proxmox.com/docs/user-management.html#privileges
In addition to that you can use LTO tape backup, also in WORM (Write Once Read
Many) mode. This allows you to create secure copies you can physical remove
from the backup server to store in a safe location.
See also the chapter about "Ransomware Protection & Recovery" for more details
about this topic:
https://pbs.proxmox.com/docs/storage.html#ransomware-protection
regards,
Thomas
prev parent reply other threads:[~2023-06-23 15:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 14:49 Turritopsis Dohrnii Teo En Ming
2023-06-23 15:09 ` Thomas Lamprecht [this message]
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=87a75af4-3be2-c334-67d7-8fddab1a986e@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=ceo@teo-en-ming-corp.com \
--cc=pbs-devel@lists.proxmox.com \
--cc=tdtemccnp@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox