> For the complete documentation index, see [llms.txt](https://docs.zmanda.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zmanda.com/zmanda-classic/installation-and-configuration/step-4-run-a-backup.md).

# Step 4: Run a Backup

Backup sets allow you to group multiple sources based on backup properties such as storage location, frequency, and type of backup (incremental or full). We will guide you through the process of configuring a backup set and executing your first backup.

{% embed url="<https://www.youtube.com/watch?index=6&list=PLL4MMZpK0mYvsIPukigRR9ZCBo0JXuPLS&v=JEJfu-fa2D4?rel=0>" %}

After configuring storage, initializing a backup set, and adding sources, you are now ready to run your first backup and begin protecting your data!

Another optional step before running your first backup is to create a schedule. For steps to create Intelligent Schedules, please visit [this article](https://docs.zmanda.com/customization/how-to-customize-your-zmanda-deployment/creating-schedules).

## General Steps

1. In the left navigation bar of the ZMC, click **Backup Sets**

![](/files/eahJv9a8AVIia3hgn6Ag)

2. Click on the ![](/files/eaHnRMxZ09eey62rkC4I) **icon** next to the Backup Set that you wish to perform a backup for

<figure><img src="/files/O4KPdODeReCvkXZZ4iME" alt=""><figcaption></figcaption></figure>

In the screen that appears, you will see a workflow consisting of the following steps: **Backup What -> Backup Where -> Backup Staging -> Backup How -> Backup When -> Backup Now**.

You will also see a 7th page called **Backup Media.** This contains a table of all backups that have been performed for this backup set. We will cover this further on the [**Run a Restore**](https://docs.zmanda.com/installation-and-configuration/step-5-run-a-restore) page.

<figure><img src="/files/5IJ0aCJt2rqnIpfjO2m4" alt=""><figcaption></figcaption></figure>

You may navigate through each step by clicking on its name in the above bar, which acts as a navigation bar.

In each step, you will see some advanced configuration options. For a full guide on what each of the options does, click [here](https://docs.zmanda.com/backup-and-restore-information/backup-overview/backup-sets). We will only be covering the essentials in this article.

3. Let's go through the backup workflow:

### **Backup What**

Here, you will see all of the Sources that you linked to this specific Backup Set. Check the boxes next to the sources that you wish to back up. If you do not check any boxes, then *all* of the entries will be backed up.

<figure><img src="/files/BATvhboi5MJyealA6qAN" alt=""><figcaption></figcaption></figure>

### **Backup Where**

Most of the fields in this step are informational, and the Taperscan drop-down is only applicable for tape backups.

The exception to this is if you are using AWS S3 as a storage option, in which case you should see the **Special Steps for AWS S3** section found at the bottom of this page.

When you are ready, click **UPDATE CONFIGURATION**.

<figure><img src="/files/FW9zdm5hYQGqMjAfjTMI" alt=""><figcaption></figcaption></figure>

### **Backup Staging**

Staging is used primarily for backups to tape, but you may also use them for other storage media. We recommend disabling staging unless you are using tape. [See here for more details](https://docs.zmanda.com/installation-and-configuration/step-4-run-a-backup#backup-staging-1).&#x20;

<figure><img src="/files/u5j7OI95JCgfOMcwnQ3u" alt=""><figcaption></figcaption></figure>

### **Backup How**

This page contains Performance Parameters and Time Out settings that you are free to configure as needed. The default settings are acceptable for most environments.&#x20;

You can also enable email notifications on this page. You must first configure your server to use SMTP. See [this article](https://docs.zmanda.com/customization/how-to-customize-your-zmanda-deployment/enabling-email-notifications) for more details. You may enter multiple emails using a comma-separated format.&#x20;

Click **UPDATE** and continue to the **Backup When** page.

<figure><img src="/files/dV9KPF61KJkbWBZqjbGz" alt=""><figcaption></figcaption></figure>

### **Backup When**

This is where you may add or replace the schedule linked to this backup set. Simply click on the drop-down, select the schedule you wish to apply, and click UPDATE SCHEDULE. If you have not configured any schedules yet, you may leave this as **None** as shown below.

<figure><img src="/files/4UomwZG6TdS8oxHEZ7MN" alt=""><figcaption></figcaption></figure>

### **Backup Now**

As the name suggests, you may start your backups from this page. If you opted to add a schedule in the previous step, you can click on the **red play button** to activate the backup set and it will begin to backup according to the schedule that you have specified.

If you wish to run a backup immediately, you may select the backup level and click either the **green play button** or **START BACKUP NOW**. You will then be taken to the **Monitor** page where you can monitor the progress of your backups.

<figure><img src="/files/QEe5fQS96go4qkEr83Vs" alt=""><figcaption></figcaption></figure>

### Backup Media

The **Backup Media** page is not a required step in the backup workflow. It is where you may configure the retention period for a given backup set as well as the backup cycle. You may also see and manage backup media on this page.

<figure><img src="/files/Qb2EdIF3QYMofG5JOR6Q" alt=""><figcaption></figcaption></figure>

As shown in the movie above, you may adjust the backup cycle and retention policy as desired. Upon changing the retention period, you will see if there are any expired backups (media). If you click on the ![](/files/sT0EhJBbqmSl7C7PTiph) button, this will prune/remove all expired backups.&#x20;

For a detailed description of what a backup cycle is, please see [this article](https://www.zmanda.com/knowledge-base/how-backup-scheduling-works-in-amanda-enterprise/).

Clicking the ![](/files/v3gYvU19u26jbQ6h5eeE)button will verify the data integrity for the given backup media.

Clicking the![](/files/BjHNxakZY4iOXeTjHVbT)button will take you to the [Restore](https://docs.zmanda.com/installation-and-configuration/step-5-run-a-restore) workflow for the given backup media.&#x20;

## Special Steps for AWS S3

If AWS S3 is the storage target for your backup set, you will have some additional essential options to configure - specifically on the **Backup Where** page.

The first feature to note is the **Archive to Glacier** checkbox. When you select this option, you will then be able to choose after how many days the backed-up data will be transitioned from the S3 standard tier to S3 Glacier Flexible Retrieval.

<figure><img src="/files/qttUineN7HY4Xkixm9Qz" alt=""><figcaption></figcaption></figure>

The next feature to note is the **Immutable Backup** slider. The slider will only be active the first time you visit the Backup Where page, and inactive after you click **Add Configuration** for the first time. Activating this option will allow you to choose between the [AWS-defined](https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lock-overview.html) Governance and Compliance Immutability modes, as well as select the retention period in days.

<figure><img src="/files/fwsi5KNU0tBMmC2xIHwy" alt=""><figcaption></figcaption></figure>

Another feature unique to AWS is the ability to select the availability zone as shown below. This feature is also unconfigurable after the first time you click **Add Configuration**.

<figure><img src="/files/tcuiy5AYUkHVds5X7zWZ" alt=""><figcaption></figcaption></figure>

The final feature that you may configure is found in the **Advanced Options** menu. Here we recommend changing the **Max Upload Speed** and **Max Download Speed** fields to match your specific environment's capabilities. For example, if you normally expect upload speeds of 10MiB/s, put *10000* in the **Max Upload Speed** field. You may also choose how many threads to use per Upload/Download.

<figure><img src="/files/kDcYCLYfpgeSBEN51MtM" alt=""><figcaption></figcaption></figure>

After configuring these settings, you may click **ADD CONFIGURATION** and continue using the **General Steps** to perform the backup.

## Special Steps for Tape Backups

Similar to AWS S3, Tape Backups also have special steps during the backup workflow, specifically on the **Backup Where, Backup Staging, and Backup Media** pages.&#x20;

#### Backup Where

This page appears as follows:

<figure><img src="/files/uXiCF2py8kS989odWOuq" alt=""><figcaption></figcaption></figure>

1. Ensure that the **Slot Range** is configured per your requirements. By default, a Backup Set will use all slots

A "Slot" is equivalent to a Storage Element. You can see a list of the Storage Elements by clicking **MTX / LSSCSI -> MT/MTX**

<figure><img src="/files/wq720DFxZi5bjjzMfdZC" alt=""><figcaption></figcaption></figure>

2. Next, select the correct **Tape Drive Device.** A **"**&#x54;ape Drive Device" or "Drive Slot" is equivalent to a Data Transfer Element (DTE). Please follow the below substeps if you have more than one DTE:

2A. Check the status of both data transfer elements. You can do this by running the following commands

<pre><code><strong>// Go to the appropriate directory
</strong><strong>cd /dev/tape/by-id
</strong>
// View the devices and soft links
ls -la

// Check the status of the DTEs.
//Make sure the nst# matches the output of the ls command
mt -f /dev/nst0 status
mt -f /dev/nst1 status

//Sample Output of mt command
SCSI 2 tape drive:
File number=-1, block number=-1, partition=0.
Tape block size 0 bytes. Density code 0x0 (default).
Soft error count since last status=0
General status bits on (50000):
DR_OPEN IM_REP_EN
</code></pre>

2B. If the last line of the output says **DR\_OPEN** for each DTE, run the following commands to load a tape into the DTE. **If one of the outputs says BOT ONLINE, proceed to step 2C.**&#x20;

```
//double-check the sg#. 
mtx -f /dev/sg6 status

//load a tape from one of the full elements into the DTE
//In the below example, 5 is the Storage element number,
//and 1 is the DTE number
mtx -f /dev/sg6 load 5 1
```

2C. Repeat the mt commands from Step 2A to check if one of the DTEs has a tape loaded. In our case, nst0 is loaded, so take note of which device this corresponds to based on the ls -la command from Step 2A.

<figure><img src="/files/caLmTGFqMR7q5oIOOkNN" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
The nst number and the DTE Number do not always match. For example, DTE 0 could correspond to nst1
{% endhint %}

2D. Find the corresponding device in the **Backup Where** page under the **Tape Drive Device** section. Leave the checkbox next to that drive unselected, and select **Skip** for the other devices.&#x20;

<figure><img src="/files/LxA0o0To12gTzEbI17aR" alt=""><figcaption></figcaption></figure>

2E. Make sure the **Drive Slot** number corresponds with the Data Transfer Element number from the mtx command and click **NEXT**

<figure><img src="/files/ux8cABnTPvBIgyXih0u8" alt=""><figcaption></figcaption></figure>

2F. Click **Confirm** on the **Update and Verify** pop-up. If you are taken to the next page, go back to the Backup Where page and ensure that you see a green check beside the Tape Drive Device name. If you do not, click **NEXT** again to Update and Verify.&#x20;

#### Backup Staging

On the **Backup Staging** page, you may configure how big of a staging area you would like for your backups.  Staging is beneficial as it allows you to utilize tape space more efficiently. We recommend initially setting your staging area size to be *slightly less than your native tape size* which will allow you to maximize your tape capacity. As you run more full and incremental backups, you may adjust the size of the staging area to correspond with the average size of said backups to compensate for factors such as compression.&#x20;

You may also configure where backups will be staged on the backup server, as well as how much of the partition space to reserve for root using the **Reserved for root %** field.

To calculate, look in the **Live Statistics** section and calculate the correct percentage based on the **Partition total space**.&#x20;

<figure><img src="/files/MvjkNwqHfQW1AlcKJnIh" alt=""><figcaption></figcaption></figure>

#### Backup Media

This is where you will label tapes for use with the backup set.&#x20;

{% hint style="info" %}
Each Backup Set will use *only the tapes that are labeled for it*, and each backup job will take up one tape unless you enable staging.&#x20;

In other words, **ensure you assign enough tapes to each backup set to account for the maximum expected data size of your backup**. You will <mark style="background-color:red;">not</mark> be able to label tapes mid-backup if you underestimate the backup size. You can always relabel unused tapes for use with other backup sets in the future.&#x20;

In addition, if you run a backup job with a native size of 100 GB, but your tape has a native capacity of 1 TB, there will be at least 900 GB of unused space on that particular tape that you will not be fully utilizing. To account for this (and using the same example), you can set the staging area to be 1 TB in size. This will allow you to fully utilize the space on each tape.&#x20;
{% endhint %}

Labeling tapes is a simple process. When you scroll to the bottom of the Backup Media page, you will see a table like this:

<figure><img src="/files/w7rj6XPgcXpstAf8pzHx" alt=""><figcaption></figcaption></figure>

1. Select the **Overwrite Media** check box.
2. You will then be able to select the boxes next to the **Slots** of the tapes that you wish to relabel.&#x20;
3. Click the ![](/files/3xoonIkaUtCO15sfvS8M)icon. The tapes will be re-labeled and therefore assigned to the Backup Set that you are currently configuring.

<figure><img src="/files/N52hAdmnzDkfZkGfteUq" alt=""><figcaption></figcaption></figure>

4. **The re-labeling process will erase the data currently stored on the tapes you selected** and will relabel the tapes. Once this is complete, you should see green check marks next to each tape you selected.&#x20;

<figure><img src="/files/lrwUiwP9c3Gxcu5tO3IB" alt=""><figcaption></figcaption></figure>

After labeling the tapes, you can go back to the **Backup Now** page and run a backup, or to the **Backup When** page and activate the backup schedule.&#x20;


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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/installation-and-configuration/step-4-run-a-backup.md?ask=<question>
```

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.