> 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-restore-an-object-storage-backup-to-qnap.md).

# How to Restore from an Object Storage Backup to QNAP

If you store your backups in Object Storage, you can restore them on a QNAP NAS with **HBS 3 (Hybrid Backup Sync)**.

The entire process is done from HBS 3 on the QNAP itself; Plenit acts only as the data source. This guide walks through the recovery from start to finish.

> #### 👍 What you get
>
> A backup stored in Object Storage restored to the QNAP path of your choice, with HBS 3.

### Before you begin

* Have a subscription of **Object Storage** with the backup you are going to restore. If you need to create it, start from the [Object Storage Quick Start.](https://docs.plenit.com/docs-en/productos/object-storage/quickstart.md)
* Having the **QNAP** up and running, with Internet access and administrator permissions.
* Have Plenit configured as a destination in HBS 3 (you get the S3 access keys from your Object Storage subscription).

> #### 📘 About the model and version
>
> This procedure was carried out with a QNAP TS-x73A and is valid for both **QTS** and **QuTS hero**. Depending on the model and version, some menus may vary slightly.

### Step 1. Open HBS 3 and start the restore

Open **HBS 3 Hybrid Backup Sync** from the QNAP desktop. Go to **Backup and Restore**, expand the selector and choose **Restore**.

{/\* 📸 CAPTURE 1 · HBS 3 · Backup and Restore › Restore \*/}

![Starting the restore in HBS 3](https://reemplaza-url/almacenamiento-objetos-qnap-01.png)

### Step 2. Choose Plenit, the storage space, and the source bucket

In **Create a restore job**, select **Plenit** as the source and choose the **storage space** from which you are going to restore. Then open **Bucket name**, select the bucket that contains the backup and click **Select**.

{/\* 📸 CAPTURE 2 · Create a restore job · Plenit as source and bucket selection \*/}

![Selection of Plenit and the source bucket](https://reemplaza-url/almacenamiento-objetos-qnap-02.png)

### Step 3. Select the backup and the content to recover

Assign a **name** to the task (and a description if it helps you identify it). If you want to exclude files deleted in the latest backup versions, check **Skip deleted data**.

In the list of available backups, choose the one you are going to restore. In the right pane, decide whether you are restoring the entire structure, a specific folder, or a file, and click **Ok**.

{/\* 📸 CAPTURE 3 · backup and content selection (all / folder / file) \*/}

![Selection of the backup and the content to recover](https://reemplaza-url/almacenamiento-objetos-qnap-03.png)

### Step 4. Choose the destination path on the QNAP

Open the **destination path** selector and choose the folder where the restored data will be saved. If needed, create a new folder. Check that the source and destination paths are correct and click **Next**.

{/\* 📸 CAPTURE 4 · QNAP destination folder selector \*/}

![Selection of the destination path on the QNAP](https://reemplaza-url/almacenamiento-objetos-qnap-04.png)

> #### 🚧 Be careful when restoring over an existing path
>
> If you restore over a folder that already contains data, review what is there first so you don't mix old files with the restored ones. If possible, restore to a new folder and move the data afterward.

### Step 5. Decide when it runs

For a one-time recovery, select **Restore Now** and click **Next**. Scheduling options are available, but in a manual restore they usually add no value.

### Step 6. Adjust the transfer rules

In **Rules** you can enable:

* **Use rate limits**: limits the transfer speed so you don't saturate the connection. Useful if the restore shares connectivity with other critical services.
* **Integrate with QuWAN**: lets QuWAN manage the traffic.
* **Replicate ACL and extended attributes**: replicates permissions and attributes from the source to the destination.

Click **Next**.

> #### 🚧 Replicating ACL and extended attributes changes permissions
>
> This option can modify the permissions and attributes of the destination to match the source. Enable it only if you need to preserve that behavior exactly; otherwise, leave it unchecked so you don't alter the permissions of the destination folder.

### Step 7. Review the summary and launch the recovery

Check the summary window. From there, click **Back** if you want to change anything or **Restore** to launch the recovery. During execution, HBS 3 shows progress.

{/\* 📸 CAPTURE 5 · task summary · Restore button \*/}

![Recovery summary before launching it](https://reemplaza-url/almacenamiento-objetos-qnap-05.png)

> #### 📘 If startup seems slow
>
> It is normal for the task to take a while to start moving data: HBS 3 first validates the connection to the source and prepares the transfer before copying. Do not interpret this as a failure.

### Step 8. Validate the result

When it finishes, HBS 3 displays a message that the recovery has been completed. To review this task or relaunch it later, go to **Jobs**, locate the job and use its options: relaunch the task, view its information (copied files, times), or edit it to fit another need.

{/\* 📸 CAPTURE 6 · Jobs · completed recovery task \*/}

![Recovery task in Jobs](https://reemplaza-url/almacenamiento-objetos-qnap-06.png)

> #### 👍 How to know it went well
>
> HBS 3 shows the success message, the restored files appear in the chosen destination path, and the task appears in **Jobs** with the expected result.

### Conclusion

Restoring to a QNAP from Object Storage is a guided workflow within HBS 3: you choose Plenit and the source bucket, the backup and the content, the destination path, and launch it.

The two points where it is worth being careful are restoring over folders with content and the option to replicate ACLs, because both can alter what is already in the destination.

With that under control, the process is straightforward and is recorded in Jobs in case you need to repeat it.

### Next steps

* Review how the service and buckets work in [Object Storage Concepts.](https://docs.plenit.com/docs-en/productos/object-storage/concepts/what-it-is.md)
* Check the S3 connection details for your subscription in [S3 Access and compatibility.](https://docs.plenit.com/docs-en/productos/file-storage/concepts/access-and-sharing.md)
* Review the organization of your buckets in [Structure and buckets.](https://docs.plenit.com/docs-en/productos/file-storage/concepts/folder-structure.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.plenit.com/docs-en/productos/object-storage/how-to/how-to-restore-an-object-storage-backup-to-qnap.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
