Object storage has moved from a specialist storage model into a mainstream component of modern backup infrastructure. The reason is practical rather than fashionable. UK organisations are storing more data, keeping backup copies for longer and expecting backup repositories to support larger, more varied estates without constant redesign. At the same time, backup software vendors have increasingly built object storage into their architectures, especially through S3-compatible repositories and immutable storage features.

The shift is particularly relevant for backup because backup data behaves differently from production data. It is usually written, retained and read back only when required, rather than updated continuously like a transactional database. That makes object storage well suited to many backup and archive use cases, where scale, durability, retention and software compatibility matter more than low-latency block performance. It also explains why object storage is becoming more visible in discussions around Veeam repositories, capacity tiers, cloud archive targets and managed backup platforms.

For UK businesses, the topic matters because backup infrastructure is no longer a minor operational detail. The UK Government’s Cyber Security Breaches Survey 2025/2026 reported that 43% of businesses identified a cyber breach or attack in the previous 12 months, rising to 65% of medium businesses and 69% of large businesses. Ransomware was reported by 1% of businesses, down from 3% in the previous two years, but destructive attacks remain a design concern because backup repositories are often part of the recovery target. Object storage is not a complete answer to those risks, but it is increasingly being adopted because it fits several backup requirements at once: scale, retention, immutability, software support and flexible deployment.

Current Situation

The wider storage context is clear. IDC’s Data Age 2025 research, sponsored by Seagate, projected that the global datasphere grew from 45 zettabytes in 2019 to 175 zettabytes by 2025. It helps explain why backup storage requirements have become more difficult to manage. As production data grows, backup repositories often grow faster because they retain multiple copies, historical versions and long-term archive sets.

The backup software market has adjusted to this reality. Veeam supports S3-compatible object storage repositories and includes immutability options for object storage repositories. Commvault lists Amazon S3 storage classes among supported cloud storage products and also documents storage lock behaviour for immutable retention, including the warning that immutability can increase storage consumption and costs. Cohesity documentation and guidance also reference immutable backup designs and the move from traditional 3-2-1 backup thinking towards models that include an immutable copy. These are important signals because object storage adoption is not being driven only by storage vendors; it is now embedded in the way major backup platforms are designed.

Cloud storage economics are also shaping the discussion. Wasabi’s 2025 Global Cloud Storage Index reported that 62% of surveyed organisations exceeded their cloud storage budgets in 2024, and that 49% of cloud storage billing was allocated to data and usage fees rather than stored capacity. Backblaze and Dimensional Research reported in 2025 that 95% of surveyed organisations experienced unexpected cloud storage charges. Both sources are from storage providers or commissioned by storage providers, so they should be read with that context. Even so, they reflect a real infrastructure issue: backup storage costs are not limited to the amount of data stored.

There are also credible cautionary views. AWS explains that object storage generally involves more latency than block storage and is better suited to large volumes of unstructured data than low-latency workloads. Google Cloud similarly notes that object storage is not ideal for transactional data because writes can be slower than file or block storage and objects usually need to be recreated when changed. These limitations do not weaken the case for object storage in backup. They clarify where object storage fits: as a repository, archive tier, capacity tier or secondary storage layer, not as a universal replacement for every storage model.

Reason 1: Backup Data Volumes Continue to Grow

The first reason UK businesses are embracing object storage is the simple growth of backup data. A production environment may hold one active dataset, but backup infrastructure may hold daily, weekly, monthly and annual recovery points. It may also hold archive copies, backup copies for different systems, retained data for contractual reasons and older recovery points that are rarely accessed but still need to be preserved. This means backup storage can grow disproportionately compared with the systems it protects.

Traditional backup repositories can support large environments, but they often require more active capacity planning as data volumes expand. Organisations may add storage arrays, extend file repositories or move older backup sets into separate archive locations. Over time, this can create a fragmented estate in which backup data is spread across different systems, hardware generations and management processes. The result is not always failure, but it can become administratively heavy.

Object storage addresses this problem by providing a scale-out model for large volumes of unstructured data. Objects are stored with metadata and unique identifiers rather than in traditional file hierarchies. This model is particularly suitable for backup sets, archive data and retained recovery points because these datasets are usually written once and accessed only when needed. For infrastructure teams, the value is the ability to treat backup storage as a scalable platform rather than a series of separate repository projects.

The benefit is not only technical scale. It is also planning clarity. When backup growth is expected to continue, infrastructure leaders need storage models that can expand without forcing repeated redesign. Object storage does not remove the need for capacity management, but it can make growth easier to plan and easier to standardise across different backup workloads.

Reason 2: Object Storage Scales More Easily Than Traditional Backup Repositories

The second reason is operational scalability. Backup storage is not only a capacity issue; it is also a management issue. Large backup estates require monitoring, lifecycle policies, access control, retention management and predictable expansion. The more separate repositories an organisation operates, the harder it becomes to maintain a consistent view of capacity, ageing data and restore readiness.

Object storage is attractive because it allows storage pools to scale horizontally. Instead of relying only on larger individual systems, additional capacity can be added to the storage platform. This does not make object storage effortless to run, and it does not remove the need for skilled administration. However, it gives infrastructure teams a more suitable model for repositories that are expected to grow steadily over several years.

This is particularly relevant for organisations with distributed infrastructure, multiple backup workloads or a mix of on-premises and hosted systems. In those environments, a unified object storage target can reduce the number of separate storage designs needed for backup data. It can also make it easier to apply consistent retention and access policies across backup repositories, provided the backup software and storage platform are configured properly.

The main caution is that scale should not be confused with simplicity. Object storage still needs proper design, especially around bucket structure, access keys, lifecycle policies, immutability settings and monitoring. It can reduce some forms of storage complexity, but it introduces its own operational considerations. For that reason, object storage adoption should be treated as an infrastructure architecture decision rather than a simple storage purchase.

Reason 3: Modern Backup Platforms Are Built Around Object Storage

The third reason is software ecosystem support. Object storage has become easier to adopt because major backup platforms increasingly support it as a repository, capacity tier, archive target or immutable storage layer. Veeam’s documentation for S3-compatible object storage shows that such storage can be added as an object storage repository, with specific prerequisites when immutability is required. Veeam also states that its immutability feature can prohibit deletion of data from an object storage repository for a defined period.

Commvault’s documentation lists multiple Amazon S3 storage classes as supported for cloud storage libraries, including S3 Standard, S3 Intelligent-Tiering, S3 Standard-Infrequent Access and Glacier-related classes. Commvault also documents storage lock behaviour for immutable retention, while warning that storage consumption may increase because data is retained until retention rules are met. These details matter because they show both the support for object storage and the need to understand its operational consequences.

The importance of S3 compatibility is difficult to overstate. S3 has become a widely supported interface across the storage and backup market, giving organisations more choice over where backup data is held. A business can use a hyperscale cloud service, a specialist object storage provider, a private object storage platform or a UK-hosted S3-compatible service, depending on its priorities. This choice matters for organisations that want compatibility with backup software without being tied to one storage deployment model.

The opposing view is that compatibility is not the same as identical behaviour. Different object storage platforms may vary in performance, immutability implementation, billing model, support process and behaviour under heavy restore activity. Infrastructure teams should therefore test object storage targets with their actual backup software, restore patterns and retention settings. The fact that a platform is S3-compatible is a starting point, not a full validation exercise.

Reason 4: Storage Economics Are Becoming More Important

The fourth reason is cost discipline. Backup storage has historically been treated as a necessary infrastructure cost, but that view becomes harder to sustain when backup repositories grow year after year. Long retention periods, archive copies, compliance-driven retention and multiple recovery points all increase storage consumption. The commercial issue is not whether backup is important; it is whether the storage model remains sustainable as data volumes rise.

Object storage can be economically attractive because it aligns with the access pattern of many backup workloads. Much backup data is retained rather than actively used. Recent backups may need faster restore performance, while older backups may be accessed rarely. Object storage platforms and cloud storage services can support different storage classes or lifecycle policies, allowing older data to be held in a lower-cost tier where appropriate. This can be useful where retention requirements are long but restore frequency is low.

However, storage economics are also one of the strongest areas of criticism. Wasabi’s 2025 Global Cloud Storage Index reported that 49% of cloud storage billing went to data and usage fees rather than stored capacity. Backblaze and Dimensional Research reported that 95% of surveyed organisations experienced unexpected cloud storage charges. These findings support a common concern among infrastructure leaders: cloud storage can appear inexpensive when judged by capacity price alone, but restore, retrieval, API and data transfer activity may change the real cost.

The sensible position is balanced. Object storage can improve backup economics, especially for long-term retention and archive workloads, but only when the full cost model is understood. UK businesses should model recovery scenarios, not only steady-state storage. If a major restore would trigger significant egress or retrieval charges, that cost should be known before the organisation depends on the platform. Object storage economics are strongest when pricing is transparent and aligned with the organisation’s actual backup and restore behaviour.

Reason 5: Immutability Has Increased Interest in Object Storage

The fifth reason is immutable backup design. AWS states that S3 Object Lock can help prevent objects from being deleted or overwritten for a fixed period or indefinitely, using a write-once-read-many model. Veeam similarly states that immutability for object storage repositories can prohibit deletion of backup data and help protect against malware activity by maintaining versions of a backup. This has made object storage more attractive as organisations look for additional protection against accidental deletion, administrator error and malicious activity.

The appeal is easy to understand. If backup data can be changed or deleted by a compromised account, then the backup repository itself becomes part of the attack surface. Immutability creates a barrier by preventing deletion or alteration before the retention period expires. For backup teams, this can provide a stronger repository layer than storage that allows immediate deletion by any sufficiently privileged account.

The cautionary view is equally important. NCSC guidance on ransomware-resistant backups focuses on mitigating destructive ransomware attacks and stresses that backup systems should be protected from unauthorised access because they may hold sensitive and critical data. NCSC’s cloud backup principles also state that backups should be resilient to destructive actions and configured so that it is not possible to deny all customer access. In earlier guidance, NCSC also noted the importance of offline backups and secure identity protection for cloud backups.

This means immutable object storage should not be presented as a replacement for every other backup control. It is a valuable layer, but it does not remove the need for identity security, administrative separation, tested restores and independent backup copies where appropriate. The strongest adoption case is therefore not “object storage solves ransomware”. It is that object storage can support immutable repositories within a broader backup design.

Reason 6: UK Organisations Are Paying More Attention to Where Backup Data Resides

The sixth reason is data location. Backup data often contains the same information as production systems, including personal data, customer records, operational data and sensitive business information. As a result, organisations are increasingly asking where backup data is stored, who operates the platform and whether access could involve parties outside the UK.

The ICO’s international transfers guidance, updated in January 2026, explains how organisations should identify and assess restricted transfers under UK GDPR. The ICO also states that UK GDPR rules apply to transfers of personal information to separate organisations outside the UK where those transfers meet the definition of a restricted transfer. These rules do not require every UK organisation to use UK-only storage. They do mean that backup storage location and provider arrangements should be understood rather than assumed.

Object storage is relevant because it can be delivered in different models. A business may choose hyperscale object storage in a UK region, a UK-hosted S3-compatible service, a private object storage deployment or a managed backup repository operated by a UK provider. This flexibility allows organisations to match backup storage decisions to their own operational, regulatory and commercial priorities.

A UK infrastructure provider offering sovereign cloud, backup, hosting and object storage services sits within the decision space where organisations are assessing location, access, backup software compatibility and long-term retention. The value is not that every organisation must choose a sovereign model. The value is that UK-hosted object storage gives infrastructure leaders another credible option when backup data location matters.

Reason 7: MSPs Are Increasingly Moving to Object Storage Delivery Models

The seventh reason is managed service delivery. Many UK organisations rely on MSPs, cloud providers or backup specialists to operate backup infrastructure. For those providers, object storage is attractive because it can support scalable repositories, customer separation, S3-compatible integration and repeatable service design. This is important because a managed backup service must be efficient to operate across many customers, not only technically sound for one environment.

Object storage fits this model because it can provide a consistent repository layer behind multiple backup services. Capacity can be allocated across customers, retention policies can be standardised and storage growth can be managed within a shared operational framework. This does not remove the need for customer-specific policies, but it can reduce the number of bespoke storage designs a provider needs to maintain.

For customers, this trend matters even when the storage platform is not visible day to day. A managed backup service built on object storage may offer better scalability, clearer immutability options and more predictable repository expansion than one built only on traditional storage appliances. However, customers should still ask practical questions: where is the data stored, how is immutability configured, how are restores tested and what happens if a large restore is needed?

The UK data centre context adds further relevance. The UK Government designated UK data infrastructure as Critical National Infrastructure in September 2024, stating that the security and resilience of the UK’s data and digital infrastructure are central to strategic objectives. This does not prescribe a particular backup architecture, but it reflects the growing importance of the infrastructure layer behind digital services. Object storage adoption by MSPs and infrastructure providers is part of that wider shift towards more scalable and standardised data infrastructure.

Conclusion

UK businesses are embracing object storage in backup infrastructure because it fits the way modern backup data behaves. Backup repositories are growing, retention periods are extending and backup software platforms increasingly support S3-compatible storage. Object storage provides a scalable model for large volumes of backup and archive data, while immutability features have increased its relevance for protected repositories.

The case is not one-sided. Object storage is not suitable for every workload, and cloud object storage pricing can be difficult to assess if organisations focus only on capacity charges. Immutability is valuable, but it is not a substitute for secure identity, backup isolation and tested restore processes. These limitations are important because they prevent object storage from being treated as a generic answer to every storage problem.

For UK infrastructure leaders, the practical question is where object storage fits within the backup estate. It is increasingly appropriate for backup repositories, archive tiers, capacity extensions, immutable backup copies and managed backup platforms. It is less appropriate where applications require low-latency transactional storage or frequent in-place modification. That distinction is what makes the adoption trend credible: object storage is growing because it is being used for the workloads where its design makes sense.

Object storage sits naturally alongside backup, disaster recovery, hosting and sovereign infrastructure discussions because it affects where retained data lives, how it is protected and how economically it can be stored over time. The organisations that benefit most will be those that assess object storage as part of a practical backup architecture, not as a storage fashion or a single-vendor preference.