# Backup Overview This article introduces you to all the moving elements needed to backup your [source](https://docs.zmanda.com/backup-and-restore/step-1-sources). Right now, we assume you have the [backup server](https://docs.zmanda.com/installation/backup-server-installation) running and the [backup agent](https://docs.zmanda.com/installation/backup-agent-installation) 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](https://docs.zmanda.com/). Zmanda groups sources by a virtual entity called [backup sets](https://docs.zmanda.com/backup-and-restore/step-4-backup-sets). Backup sets offer more scaffolding by creating an isolated data boundary that groups [sources](https://docs.zmanda.com/backup-and-restore/step-1-sources), [storage](https://docs.zmanda.com/backup-and-restore/step-2-storage), and [timing templates](https://docs.zmanda.com/backup-and-restore/step-3-schedule-plan) 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.

Pictorial representation of how Backup Sets help create virtual boundaries.

To build a backup set, you must create three components: [sources](/zmanda-classic/information/backup-overview/sources.md), a [storage container](/zmanda-classic/information/backup-overview/storage.md), and a [schedule plan](/zmanda-classic/information/backup-overview/schedule-plan.md). 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.

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.

## 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**](https://docs.zmanda.com/backup-and-restore/step-1-sources)**:** It helps you define workloads, directories, or applications you want to back up. * **Step 2:** [**Storage**](https://docs.zmanda.com/backup-and-restore/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**](https://docs.zmanda.com/backup-and-restore/step-3-schedule-plan)**:** Enables you to modify your backup windows centrally. Scheduled plans can be shared across backup sets. * **Step 4:** [**Backup Set**](https://docs.zmanda.com/backup-and-restore/step-4-backup-sets)**:** 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. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.zmanda.com/zmanda-classic/information/backup-overview.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.