LogoLogo
EBR DocsHelp
Zmanda Classic
Zmanda Classic
  • Welcome to Zmanda Documentation
    • Zmanda Video Walkthrough
    • Zmanda 5.1 Release Notes
      • Zmanda 5.1.1 Release Notes
      • Zmanda 5.1.2 Release Notes
      • Zmanda 5.1.3 Release Notes
      • Zmanda 5.1.4 Release Notes
      • Zmanda 5.1.5 release notes
    • Zmanda 5.0 Release Notes
      • Zmanda Patch 5.0.0.7 Release Notes
      • Zmanda Patch 5.0.1.0 Release Notes
    • Zmanda 4.3 Release Notes
    • Zmanda 4.2 Release Notes
    • Zmanda 4.1 Release Notes
  • Getting Started With Zmanda
    • Terms, Concepts, and Best Practices
    • Cloud-Based Trial Environment
  • Installation & Configuration
    • Step 1: Install Zmanda Server
      • Dependencies & System Requirements
      • Zmanda Backup Appliance Installation
      • Oracle Cloud Marketplace Installation
      • AWS Marketplace Installation
      • Azure Marketplace Installation
      • Linux Binary Installation
      • Client-side Deduplication Documentation
      • Add Backup Servers in the ZMC
    • Step 2: Add Storage
      • Zmanda Cloud Storage
      • Simple Disk
      • NAS & SAN
      • Tape
      • Cloud Storage
    • Step 3: Add Sources
      • Prerequisite: Initialize a Backup Set
      • Windows
        • Installation
          • ZWC Silent Installation Guide
        • Configuration
      • Linux
        • Installation
        • Configuration
      • VMware and Hyper-V
      • File Shares
      • Databases and Applications
        • Oracle DB's - Linux
        • Oracle DB's - Windows
        • PostgreSQL Server - Linux
        • Microsoft SQL Server
        • Microsoft Exchange
        • Microsoft SharePoint
      • Mac OS
    • Step 4: Run a Backup
    • Step 5: Run a Restore
      • VMs Restore Process
      • PostgreSQL Restore Process
    • Step X: Intelligent Scheduling
    • Troubleshooting
  • Information
    • Backup Overview
      • Storage
      • Backup Sets
      • Sources
        • Large and complex data sources
      • Schedule Plan
    • Restore Overview
    • Disaster Recovery
      • Disaster Recovery with Zmanda: A Comprehensive Guide
    • Reports
    • Data Integrity
    • Custom Reports
    • Audit
    • License Info
    • Comprehensive Guide to Downloading Zmanda EBR 5.1 License
  • CUSTOMIZATION
    • How to Customize Your Zmanda Deployment
      • Vaulting
      • User Management
        • Single Sign-On Integration
        • LDAP Integration in Zmanda
        • Custom Roles and Policies
      • Enabling Email Notifications
      • Bulk Deployment of Zmanda Linux Clients
      • Bulk Deployment of Zmanda Windows Clients
      • Bulk Automation Guide
      • Immutable Backups
      • Global Exclusion Policy for Linux and Windows Clients
      • Client Triggered Oracle Backups
      • Archive to AWS Glacier Tiers
      • Comprehensive Guide to Setting Up Zmanda in AWS
      • Comprehensive Guide to Setting Up Zmanda in Azure
  • Product Lifecycle
    • Explore product lifecycle
Powered by GitBook
LogoLogo

Quick Links

  • Amanda Community Wiki
  • Amanda Community Downloads
  • Share Feedback

About

  • About Us
  • Customer Testimonials

Terms

  • Terms of Use
  • Privacy Policy

Contact Info

  • Denver, CO, USA
  • 888-496-2632 (US)
  • 408-732-3208 (INT)

2025 © Zmanda, A BETSOL Company

On this page
  • Backup Scenario
  • Building a Backup Set

Was this helpful?

Export as PDF
  1. Information

Backup Overview

Save your data by creating backup sets. Backup sets offer more scaffolding by creating an isolated data boundary that groups sources, storage, and timing templates together.

PreviousTroubleshootingNextStorage

Last updated 1 year ago

Was this helpful?

This article introduces you to all the moving elements needed to backup your source. Right now, we assume you have the backup server running and the backup agent installed on the source to backup. If you need help understanding Zmanda from a bird's eye view, please refer to the Zmanda Overview guide.

Zmanda groups sources by a virtual entity called backup sets. Backup sets offer more scaffolding by creating an isolated data boundary that groups sources, storage, and timing templates together. Thus, even to back up an individual source, you must create a backup set. This framework simplifies backups of 100's of endpoints, where different groups have different backup requirements. For example, on a network that includes servers with a high rate of data change and desktop systems that change data more slowly, you would probably want to create one backup set for the servers and another backup set for the desktops.

To build a backup set, you must create three components: sources, a storage container, and a schedule plan. Note that a backup set is bound to a single storage container, ensuring that multiple backup sets do not override each other's data. However, a backup set can have numerous sources linked to it and vice versa, forming an n-n relationship. This relationship enables the backup set to group sources based on a shared pattern, like APAC_Production_Servers. It also allows the source to be a part of multiple backup sets.

Backup Scenario

To backup data from 5 production servers to disk and cloud, you must create two backup sets, each with all five sources. While configuring the first backup set, configure its storage endpoint to disk, and while configuring the second backup set, configure its storage endpoint to the cloud.

Building a Backup Set

Over the following guides, we walk through the steps to create a backup set. Before we jump in, below is an overview.

  • Step 1: Sources: It helps you define workloads, directories, or applications you want to back up.

  • Step 2: Storage: This lets you configure the storage container that a backup set will use. Each storage container can be used by only one backup set.

  • Step 3: Schedule Plan: Enables you to modify your backup windows centrally. Scheduled plans can be shared across backup sets.

  • Step 4: Backup Set: Connect sources, storage containers, and schedule plans to run your first backup run.

In the next sections, we will see how to configure the steps to run your first backup.

Pictorial representation of how Backup Sets help create virtual boundaries.
Demonstrates the relationship between a storage set, sources, and backup sets. Also shows how a source can be simultaneously backed up to two different storage endpoints.