Menu

Post image 1
Post image 2
1 / 2
0

How to Configure Immutable Backups on a Dedicated Server to Prevent Ransomware

DEV Community·Felicia Grace·about 1 month ago
#9terDKuH
#devops#security#linux#backup#server#backups
Reading 0:00
15s threshold

Ransomware operators have evolved. They no longer just encrypt your active databases; their primary target is your backup repository. If your server backups are compromised, encrypted, or deleted, you lose your only leverage. The absolute best defense against this is configuring immutable backups using a WORM (Write Once, Read Many) architecture. An immutable backup ensures that once your data is written, it cannot be modified or deleted by anyone—not even the system administrator—until a strict time limit expires. The Architectural Choice: Cloud Storage vs. Dedicated Server When setting up immutable backups (S3 Object Lock), system administrators typically face two choices: Public Cloud Storage (AWS S3, Wasabi): Sending backups to a public cloud is easy, but you are charged per gigabyte and face unpredictable, massive "egress fees" when you need to download your data for a restoration.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.

Read More