Immutable backup storage for Veeam and other backup software

Ransomware goes after the backups first. We run S3-compatible object storage with S3 Object Lock in Ashburn, Chicago and Los Angeles, so the copies your backup software writes can't be changed or deleted until their retention date. Point Veeam, Commvault, NAKIVO or any backup tool that supports Object Lock at it.

WORM Write once, read many with Object Lock
3 regions Ashburn, Chicago and Los Angeles
SOC 2 Type II certified
24/7 People answer tickets and calls

What makes a backup immutable here

Object Lock is enforced by the storage, so the protection doesn't depend on your backup server staying clean.

S3 Object Lock

Each backup object gets a retain-until date, and until then it can't be overwritten or deleted. Versioning stays on, so anything that writes over a file only adds a new version.

Built for Veeam's object storage repository

Veeam Backup & Replication can back up straight to S3-compatible storage with immutability, copy backups to it with a backup copy job, or use it as the performance or capacity tier of a scale-out backup repository.

Offsite by default

Your backups sit in our data center, away from the servers and network they protect. Pick Ashburn, Chicago or Los Angeles, and a different region from production if you want the distance.

Restores without a per-GB bill

A restore is when you need your data back fast. Reads inside your plan cost nothing extra, and past a metered allowance it's $0.02 per GB.

Works with more than Veeam

Commvault, NAKIVO, MSP360, Kopia and rclone all document Object Lock support on S3-compatible storage. Your backup software sets the lock, and the storage enforces it.

Set up with you

Object Lock has to be on when a bucket is created. Tell us on the quote form and we'll create the bucket with Object Lock and versioning turned on.

With Veeam

Setting it up in Veeam Backup & Replication

The short version, from Veeam’s v13 user guide (checked October 16, 2026):

  1. Bucket: Object Lock and versioning on, no default retention and no lifecycle rules. Most S3 platforms only let you turn Object Lock on when the bucket is created, and Veeam says not to change either setting after you add the bucket.
  2. Repository: add an S3-compatible object storage repository with our endpoint and your access keys, and turn on immutability in the wizard.
  3. Immutability period: 1 to 999 days. Veeam adds a block generation period on top, 10 days for S3-compatible storage, so a 30-day setting can keep backups locked for up to 40 days.
  4. Jobs: point a backup job or backup copy job at it, or add it to a scale-out backup repository as the performance or capacity tier.

Plan capacity for the lock, not only the retention. Locked versions can’t be removed early, so the space you use follows your immutability period plus the block generation days.

Your options

Three ways to keep a copy attackers can't delete

  • Immutable object storage (this page): your backup software writes to our S3 storage with Object Lock. You run the backups; we run the storage.
  • A hardened Linux repository: Veeam’s Hardened Repository marks backup files immutable on a Linux server you control. Rent a storage server with big drives for it.
  • Managed offsite backups: we run the offsite side with Veeam Cloud Connect, from $35 per TB a month on a 2 to 3 year term or $60 per TB month to month. See Veeam backups.

CISA’s ransomware guide tells organizations to keep offline, encrypted backups and to test them regularly. Object Lock gives you a copy that can’t be deleted early. Testing the restore is still your job, and it’s the step people skip.

Get an immutable backup storage quote

Tell us how much you back up, how long backups must stay locked, which backup software you use and which region you want. It goes straight to our sales team, and we'll reply within 1 business day with a configuration and a monthly price.

Prefer to talk first?

    1About you

    2Your storage

    Which setup? *

    3Anything else

    By submitting this form, you agree to GigeNET's Privacy Policy. We'll use your information to respond to your quote request.

    Immutable backup storage FAQs

    Related: S3-compatible object storage · Veeam backups · Storage servers · AI data storage

    What is immutable backup storage?

    Storage where a backup, once written, can’t be changed or deleted until a set date. Ours uses S3 Object Lock: each object version carries a retain-until date, and the storage refuses overwrites and deletes before it.

    Does it work with Veeam?

    Veeam Backup & Replication supports S3-compatible object storage with immutability as a backup target, a backup copy target, and a performance or capacity tier. The bucket needs Object Lock and versioning on from the start, and we set both when we create it.

    How long can backups stay locked?

    Your backup software sets it. In Veeam it’s 1 to 999 days, plus 10 days of block generation on S3-compatible storage. Locked versions count toward the storage you use until they expire.

    Can anyone delete a locked backup early?

    When your backup software locks a version, the storage refuses deletes and overwrites until its retain-until date, so a stolen backup password or a bad script can’t wipe it. S3 has two lock modes: governance mode lets specially permitted accounts remove a lock, and compliance mode doesn’t let anyone.

    How much does it cost?

    Shared storage starts at 10 TB, and it’s quoted per deployment, because the price depends on how much you store, how long it stays locked, the region and how much you restore. Fill in the quote form and we’ll price it.

    Do restores cost extra?

    Reads inside your plan cost nothing extra. Bandwidth works like our dedicated servers: each plan includes a monthly allowance, or you can choose an unmetered port. Past a metered allowance it’s $0.02 per GB.

    Where are the backups stored?

    In the region you pick: Ashburn, Virginia (Equinix DC3), Chicago (our Arlington Heights facility) or Los Angeles (Digital Realty LAX10). Choose a different region from your production servers if you want them farther apart.