Engineering capabilities
- Offsite repository for Veeam, NAKIVO, Acronis and Commvault
- Bucket, lifecycle and retention layout
- Object-lock immutability configuration
- Restore throughput testing from the cloud tier
Backup & Email
Wasabi
S3-compatible hot cloud object storage used as an offsite backup target where predictable per-terabyte pricing and no egress or API fees decide the design.
Security & hardening
- Object lock in compliance or governance mode
- Scoped access keys separate from production credentials
- Encryption in transit and at rest
Offsite object storage tier
S3-compatible hot storage used as the offsite copy in a 3-2-1 design, with object lock making the copy resistant to deletion.
-
01
Backup platform
The existing backup product writes directly to the object tier as a copy job.
-
02
Bucket design
- Per-workload buckets
- Lifecycle policy
- Versioning
Layout is planned so retention and cost are predictable per workload.
-
03
Immutability
- Object lock
- Compliance / governance mode
- Retention period
Locked objects cannot be deleted by a compromised backup account.
-
04
Recovery
- Restore throughput test
- Partial restore
- Full site recovery
Restore speed from the cloud tier is measured so recovery plans use real numbers.
Frequently asked questions
Why use Wasabi instead of the hyperscalers?
Predictable per-terabyte pricing with no egress or API charges makes the cost of an actual restore knowable in advance, which is often the deciding factor for backup storage.
Is cloud storage a complete backup strategy?
No. It is the offsite copy. A local copy for fast restores plus immutability on the cloud tier is what makes the design work.
How long does a full restore take?
It depends on your internet bandwidth far more than the provider. That figure is measured during commissioning and written into the recovery plan.
Scope the work before you commit budget
Send the environment details and get an engineered proposal with assumptions, risks and a rollback path.