> For the complete documentation index, see [llms.txt](https://docs.plenit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plenit.com/docs-en/productos/object-storage/how-to/how-to-configure-a-manual-qnap-backup.md).

# How to Manually Set Up a Backup from Your QNAP to Object Storage

A QNAP unit on its own is not a complete continuity plan: if it is in the same location as your servers, a physical incident takes both out.

Backing up the QNAP to an Object Storage bucket gives you that off-site, reliable, low-cost copy.

This guide sets up a manual backup with **HBS 3**, using an **S3 Compatible**.

> #### 👍 What you get
>
> A backup of the folders you choose from your QNAP stored in an Object Storage bucket, launched on demand from HBS 3.

### Before you begin

* Access the administration panel at [admin.plenit.com](https://admin.plenit.com) with permissions on the service.
* Have an **Object Storage**. If you don't have one yet, set it up with the [Object Storage Quick Start](https://gitlab.com/plenit-group/plenit-docs-es-es/-/blob/v1.0/docs/Productos/servicios-cloud-almacenamiento-de-objetos/servicios-cloud-almacenamiento-de-objetos-how-to/servicios-cloud-almacenamiento-de-objetos-desplegar-almacenamiento-objetos/README.md).
* Have the **QNAP** unit up and running, with Internet access and administrator permissions.
* Have your Object Storage connection details handy: the access keys (in **Users → user → menu (…) → Keys**) and the bucket name (in the **Bucket**tab, field **My bucket**).

> #### 📘 About the model, version, and mapping
>
> This procedure was done with a QNAP TS-x73A and is valid for **QTS** and **QuTS hero**; depending on the model and version, some menus may vary. Here we map the destination on the fly; if you'd rather prepare it ahead of time to reuse it in several tasks, you can map it first and then select it.

### Step 1. Open HBS 3 and create a new backup job

On the QNAP, open **HBS 3 Hybrid Backup Sync** (the built-in backup app on the unit, so you avoid installing extra software). Click **Back up now** and, in the menu, choose **New backup job**.

{/\* 📸 SCREENSHOT 1 · HBS 3 · New backup job \*/}

![New backup job in HBS 3](https://REEMPLAZA-URL/almacenamiento-objetos-backup-01.png)

### Step 2. Choose the source folder

Select the QNAP folder you want to back up. Tick its **checkbox** (it is not enough to highlight it; without the check you cannot continue) and click **Next**.

{/\* 📸 SCREENSHOT 2 · source folder selection with the checkbox checked \*/}

![Source folder selection](https://REEMPLAZA-URL/almacenamiento-objetos-backup-02.png)

### Step 3. Create the S3 Compatible destination account

As the destination, select **Amazon S3 and S3 Compatible** and click **Add new account**. Fill in the connection details with those of your Object Storage:

* **Name**: the name of the connection (auto-completes).
* **Service provider**: S3 Compatible.
* **Server address**: `s3.plenit.com` (the address shown by the service, without the `https://` at the beginning).
* **Access key**: your Object Storage Access Key.
* **Secret key**: your Object Storage Secret Key.
* **Signature version**: V2 (the default).
* **Enable secure connections (SSL)**: enabled.
* **Validate SSL certificate**: enabled.

Click **Create**.

{/\* 📸 SCREENSHOT 3 · S3 Compatible account settings (endpoint, keys, V2, SSL) \*/}

![S3 Compatible account setup](https://REEMPLAZA-URL/almacenamiento-objetos-backup-03.png)

> #### 📘 Why S3 Compatible
>
> Object Storage is compatible with the S3 protocol, so HBS 3 connects to it using its S3 Compatible account option.&#x20;
>
> That is why the data you enter are the endpoint, the keys, and the standard S3 signature.

### Step 4. Select the bucket and destination path

Check that the resource you just created is selected. In the bucket field, the **bucket name** (if it does not appear, expand and choose it). The **part size** you can leave it at **128 MB**, the default value. Click **Select**. Then choose the **destination folder** inside the bucket according to how you want to organize the backup.

{/\* 📸 SCREENSHOT 4 · selection of the bucket, part size, and destination folder \*/}

![Selection of the bucket and destination path](https://REEMPLAZA-URL/almacenamiento-objetos-backup-04.png)

### Step 5. Name the job and choose when it runs

Give it a **job name** that is descriptive and, preferably, a **description**: over time and with several tasks, you'll appreciate knowing what each one is for. For a one-time backup, check **No schedule** and then **Back up now**, and click **Next**.

{/\* 📸 SCREENSHOT 5 · job name and Back up now option \*/}

![Job name and immediate execution](https://REEMPLAZA-URL/almacenamiento-objetos-backup-05.png)

<br>

### Step 6. Adjust the methods, review, and create

In the methods section, uncheck the options that are enabled by default if you don't need them, and click **Next**Next **summary** and, if everything is correct, click **Create**.

HBS 3 shows the backup progress (duration depends on the size and the connection). When it finishes, you'll see a **Success** message with the completion time and backup details. Close with **Close**.

{/\* 📸 SCREENSHOT 6 · summary, creation, and backup progress \*/}

![Summary and backup progress](https://REEMPLAZA-URL/almacenamiento-objetos-backup-06.png)

### Step 7. Verify that the data are in the bucket

To confirm it, go into the **structure of your Object Storage** and check that the data copied from the QNAP appear.

> #### 👍 How to tell it went well
>
> HBS 3 shows the successful backup message, and in the bucket structure the files you backed up from the QNAP appear.

### Conclusion

The first time takes some work — creating the S3 Compatible account with the endpoint and keys, choosing the bucket and folder — but it opens the way: from then on, launching new backups is immediate.

The important thing is to enter the connection details correctly (endpoint `s3.plenit.com` without `https://`, correct keys, V2, and SSL enabled) and give the tasks descriptive names so you don't get lost when you have several.

With the copy in the bucket, you have the off-site backup that a good continuity plan needs.

### Next steps

* If you prefer a copy that stays up to date by itself, set up a [One-way Sync](/docs-en/productos/object-storage/how-to/how-to-sync-qnap-to-object-storage.md).
* To restore what you've backed up back to the QNAP, follow [How to restore a backup from Object Storage to a QNAP.](/docs-en/productos/object-storage/how-to/how-to-restore-an-object-storage-backup-to-qnap.md)
* Check the S3 connection details and compatibility at [S3 Access and compatibility.](/docs-en/productos/file-storage/concepts/access-and-sharing.md)


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.plenit.com/docs-en/productos/object-storage/how-to/how-to-configure-a-manual-qnap-backup.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
