What Is a Backup Target?

A backup target is the storage system where backup software writes and retains backup data. It is the destination in a backup architecture: the repository that receives data from backup applications such as Veeam, Commvault, or Rubrik and keeps it available for restore. Your choice of backup target determines how fast you can back up, how quickly you can recover, and whether your backups survive a ransomware attack.

Backup targets were once tape libraries, then purpose-built disk appliances. Today, S3-compatible object storage is the preferred backup target for most enterprises because it scales without disruption, supports true immutability through S3 Object Lock, and integrates natively with modern backup software.

Types of Backup Targets

Tape libraries. The original backup target. Tape is inexpensive per terabyte and offline by default, but restores are slow, media must be handled and rotated manually, and recovery at petabyte scale can take days.

Purpose-built disk appliances. Deduplication appliances with fixed controller heads. Ingest is fast at first, but performance per terabyte declines as shelves are added, and growth forces you into multiple independent systems that become management silos.

Public cloud storage. Elastic, offsite by design, and well suited to long-term retention. But large restores are constrained by bandwidth and can carry significant egress fees — a hidden "recovery tax" when you need your data back fastest.

On-premises object storage. Scale-out, S3-compatible clusters built on standard servers. Every node added contributes capacity and performance, restores run at LAN speed, and immutability is enforced in the storage layer. This is now the most common architecture for a primary backup target.

Why Object Storage Has Become the Standard Backup Target

Modern backup software — Veeam, Commvault, Rubrik, Veritas — writes natively to the S3 API, and object storage's flat namespace handles billions of backup objects without the metadata bloat that slows file systems down.

Scale-out performance. In a shared-nothing cluster, every node contributes CPU, memory, and network capacity. Backup software writes in parallel across nodes, so throughput grows near-linearly as the cluster grows and backup windows stay predictable.

Erasure coding durability. Objects are split into fragments and distributed across nodes, so data survives disk and server failures with far less overhead than full replication, and rebuilds run in parallel.

Capacity-aware integration. Protocol extensions such as SOSAPI (Smart Object Storage API) let the storage system advertise capacity and load to the backup server, which routes streams to the least busy nodes — fewer failed jobs, faster backups.

Backup Targets and Ransomware Protection

Ransomware has redefined the backup target's job. Backups are the last line of defense — which is exactly why attackers now target them first, encrypting or deleting repositories before detonating the main attack. A modern backup target defends itself in three layers:

Immutability. S3 Object Lock in Compliance Mode prevents backup objects from being modified or deleted for the retention period — even by storage administrators. Immutability enforced at the storage layer cannot be switched off by a compromised admin account.

Isolation. A logical air gap — a backup repository on a segmented network or in an isolated recovery environment (IRE) — delivers the security benefit of an offline copy without tape's restore latency.

Identity controls. Zero-trust administration, multi-factor authentication, and strict IAM policies shrink the attack surface around the storage itself.

These layers underpin the modern 3-2-1-1 rule: three copies of your data, on two different media, one offsite — and one immutable.

How to Choose a Backup Target

Five criteria separate a backup target that merely stores data from one that gets your business back online:

• Restore speed. RTO is decided at restore time, not backup time. Look for parallel read performance across nodes and test recovery at realistic scale — not with a single VM.
• Non-bypassable immutability. Object Lock in Compliance Mode, enforced at the cluster level, with no administrative override.
• Scaling model. Scale-out clusters grow capacity and performance together, in one namespace. Scale-up appliances fork into silos and end in forklift upgrades.
• Backup software integration. Validated integrations with your backup vendor (such as Veeam Ready qualification) and support for capacity-aware protocols like SOSAPI.
• Total cost of ownership. Standard servers, mixed hardware generations in one cluster, no per-restore egress fees.

ARTESCA as a Backup Target

Scality ARTESCA is S3-compatible object storage designed from the ground up as a secure-by-default backup target. It starts on a single server at around 50 TB and scales out to petabytes — the same architecture from edge site to data center, with no forklift upgrades.

Security is built in rather than bolted on: S3 Object Lock immutability in Compliance Mode, a hardened operating system, multi-factor authentication, and strict identity and access controls by default. That makes ARTESCA a natural fit for the roles where a backup target matters most — primary backup repository, offsite immutable copy, and cyber-recovery vault.

ARTESCA is validated with the leading backup platforms, including Veeam (Veeam Ready with immutability, plus SOSAPI support for capacity-aware load balancing), Commvault, Rubrik, and Veritas.

Backup Target FAQs

Is a backup target the same as a backup repository?

Nearly. "Backup repository" is what backup software like Veeam calls the configured storage destination; the backup target is the underlying storage system that the repository points to.

What makes a backup target immutable?

Immutability must be enforced by the storage system itself — for example, S3 Object Lock in Compliance Mode — so that locked backups cannot be altered or deleted before their retention date, even by an administrator. A delete-protection setting inside the backup software alone is not immutability.

Can I use cloud storage as a backup target?

Yes, and it works well for offsite copies and long-term retention. For the primary backup copy, most organizations keep an on-premises target so large restores run at LAN speed without egress fees, and tier older backups to the cloud.