Cloudback Docs
HomePricingBlogContactSign In
  • Getting Started
    • What is Cloudback?
    • Installation Guide
    • First Backup Walkthrough
  • Managing Backups
    • Automated Daily Backups
    • Metadata Backups
    • One-Click Manual Backups
    • Setting Backup Schedules
    • Manage Backup Storage
    • Backup Retention Policy
    • Password-Protected Backups
    • Account Settings
    • Bulk Operations
    • Data Deduplication
    • Email Notifications
    • Instant Notifications
    • Archive Name Pattern
  • Data Restoration
    • Download Backups
    • Restore to GitHub
  • Automation
    • Terraform Provider
    • Operations API
  • Dashboard
    • Dashboard Overview
    • Card view
    • Table view
    • Repository Details
    • Backup Details and Metadata
    • Backup Status Badge
  • Storage Configuration
    • Cloudback Managed Storages
    • Customer Managed Storages
    • Replicating Backups
  • Supported Storages
    • Alibaba Cloud Object Storage Service
    • Amazon S3 Bucket via Access Key
    • Amazon S3 Bucket via Access Point
    • Amazon S3 Glacier
    • Amazon S3 Object Tagging
    • Google Cloud Storage Bucket
    • Microsoft Azure Blob Container
    • Microsoft OneDrive Business
    • Microsoft OneDrive Personal
    • OpenStack Swift
    • Wasabi Customer Managed Storage
  • Account and Billing Management
    • Payment Methods
    • GitHub Organizations
    • Invoiced Customers
  • Troubleshooting and Support
    • Known Issues
    • Contact us
  • Security Features
    • Access Review: Vanta Integration
    • Immutability: Amazon S3 Object Lock
    • Encryption: Password-Protected Archives
    • Traceability: Audit Log
  • Legal
    • Terms of Service
    • Privacy Policy
Powered by GitBook
LogoLogo

Learn more

  • Integrations
  • Blog

Explore

  • Roadmap
  • Changelog

Support

  • Contact Us
  • Status

Legal

  • Terms of Service
  • Privacy Policy

© 2025 Cloudback

On this page
  • What is a Composite Storage?
  • Benefits of Replicating Backups
  • Setting Up Replicated Backups
  • How it works
  • Conclusion
  • Learn more

Was this helpful?

  1. Storage Configuration

Replicating Backups

PreviousCustomer Managed StoragesNextSupported Storages

Last updated 5 months ago

Was this helpful?

Cloudback allows you to leverage the power of composite storage to replicate your backups across multiple destinations, enhancing your data redundancy and disaster recovery capabilities. This article guides you through the process of setting up and managing replicated backups with Cloudback.

What is a Composite Storage?

Composite storage combines two storages: primary and secondary. Think of primary storage as the main location for your data, while secondary storage acts as a backup copy. In simpler terms, Cloudback duplicates your backup archive and stores it in both locations. This strategy distributes your data across different sites, effectively increasing data redundancy and helping you meet compliance regulations.

Benefits of Replicating Backups

Replicating backups offers several advantages:

  • Eliminate single points of failure: Storing backups across diverse locations ensures data remains accessible even if a single storage provider encounters issues.

  • Rapid disaster recovery: Replicated backups allow for swift restoration from an unaffected location, minimizing downtime and ensuring business continuity.

  • Compliance Adherence: It supports compliance with laws requiring multiple backup copies, ensuring legal and regulatory standards are met.

Setting Up Replicated Backups

There are only three steps:

  1. Create a for a primary and secondary destination.

  2. Create a composite storage and set primary and secondary targets.

  3. Configure repositories to use a newly created composite storage via the menu.

How it works

  • Automatic Replication: During a backup process, Cloudback automatically copies an archive to both a primary and secondary destination.

  • All or None: If any of the underlying storages fails during a backup process - the entire backup is marked to be failed and appropriate notification is sent.

  • Restore takes first available: During a restore process, Cloudback probes storages from primary to secondary and picks the first available.

  • Composite storage settings win: The "Deduplication type" and "Archive type" settings configured for the individual underlying storage will be disregarded when using a composite storage. Instead, the deduplication and archive behavior will be determined by the settings applied to the composite storage itself.

  • Nesting capability: It is possible to embed one composite storage within another, enabling you to create a desired number of copies of a backup.

Conclusion

Replicating backups with composite storage is a flexible way to ensure data redundancy. Its straightforward setup process provides an accessible option for IT professionals at any skill level, making it a cost-effective choice. The system's adaptability allows for configuring an unlimited number of backup storages, either per repository or for the entire account, ensuring comprehensive data protection.

Learn more

Customer Managed Storages
Cloudback Managed Storages
customer managed storages
Bulk Operations
Composite storage