• Skip to main content
  • Skip to secondary menu
  • Skip to primary sidebar
The Blog of Jorge de la Cruz

The Blog of Jorge de la Cruz

Everything about VMware, Veeam, InfluxData, Grafana, Zimbra, etc.

  • Home
  • VMWARE
  • VEEAM
    • Veeam Content Recap 2021
    • Veeam v11a
      • Veeam Backup and Replication v11a
    • Veeam Backup for AWS
      • Veeam Backup for AWS v4
    • Veeam Backup for Azure
      • Veeam Backup for Azure v3
    • VeeamON 2021
      • Veeam Announces Support for Red Hat Enterprise Virtualization (RHEV/KVM)
      • Veeam announces enhancements for new versions of Veeam Backup for AWS v4/Azure v3/GVP v2
      • VBO v6 – Self-Service Portal and Native Integration with Azure Archive and AWS S3 Glacier
  • Grafana
    • Part I (Installing InfluxDB, Telegraf and Grafana on Ubuntu 20.04 LTS)
    • Part VIII (Monitoring Veeam using Veeam Enterprise Manager)
    • Part XII (Native Telegraf Plugin for vSphere)
    • Part XIII – Veeam Backup for Microsoft Office 365 v4
    • Part XIV – Veeam Availability Console
    • Part XV – IPMI Monitoring of our ESXi Hosts
    • Part XVI – Performance and Advanced Security of Veeam Backup for Microsoft Office 365
    • Part XVII – Showing Dashboards on Two Monitors Using Raspberry Pi 4
    • Part XIX (Monitoring Veeam with Enterprise Manager) Shell Script
    • Part XXII (Monitoring Cloudflare, include beautiful Maps)
    • Part XXIII (Monitoring WordPress with Jetpack RESTful API)
    • Part XXIV (Monitoring Veeam Backup for Microsoft Azure)
    • Part XXV (Monitoring Power Consumption)
    • Part XXVI (Monitoring Veeam Backup for Nutanix)
    • Part XXVII (Monitoring ReFS and XFS (block-cloning and reflink)
    • Part XXVIII (Monitoring HPE StoreOnce)
    • Part XXIX (Monitoring Pi-hole)
    • Part XXXI (Monitoring Unifi Protect)
    • Part XXXII (Monitoring Veeam ONE – experimental)
    • Part XXXIII (Monitoring NetApp ONTAP)
    • Part XXXIV (Monitoring Runecast)
  • Nutanix
  • ZIMBRA
  • PRTG
  • LINUX
  • MICROSOFT

Veeam: How to deploy QNAP QuObjects to have an Object Storage on-prem and use it as Capacity Tier

3rd June 2021 - Written in: veeam

Greetings friends, today I bring you a very interesting post, I have commented in several articles all the power of Veeam Capacity Tier, which allows us to leverage Object Storage providers to store large amounts of backups that usually require long retention, months, semesters, or years. In addition, for some time now, Capacity also allows us to have an exact copy of an on-prem repository, and in some cases to have immutability enabled.

Many of you, and in the Community, have wondered if we can use storage that we have in our Datacenters that offer Object Storage services, and the answer is yes, of course, as long as the product publishes the S3 service following modern standards it should work. Veeam has an official list of products and solutions that you can deploy in your Datacenter.

And it is from this list that I have taken one of the products that have caught my attention, due to the company behind it, QNAP, as I have it on good authority that they have a lot of market share, especially in SMBs.

How to deploy QNAP QuObjects, plus configuring it in Veeam to be used as Capacity Tier – in video

I know many of you like step-by-step with detailed explanations, and video commentary, so here is the whole process, some tips, and so on. I hope you find it helpful.

How to deploy QNAP QuObjects, plus configure it in Veeam to be used as Capacity Tier – in images

For the rest of you, I also know that many times doing a quick scroll through the blog and viewing the images saves you many minutes of watching videos, so here are the steps.

Installing, and Configuring QNAP QuObjects

Here we go! From our QNAP, we will go to the AppCenter, and install QuObjects:

It will ask us where we want to install our application, as it is small in terms of space, install it where you have other applications. The application per-se if it consumes more RAM and CPU of the QNAP, take it into account:Once the application is installed, we run it, and we will see a short wizard, quite elegant that surely helps us to understand a little more, what QuObjects is, how it works, etc.

The steps to properly configure QuObjects are very simple, first, we create a user. Which is really reusing local users, or AD users if we have connected the QNAP to our AD, once we have the Users, with the key icon, we create Access Key and Secret Key, in just a few seconds:
The next thing will be to create what QNAP calls Storage Space, we can reuse spaces we already had, but if we have other files, other permissions etc. I prefer to create a new one:
Creating a Storage Space is no big deal, we give it a name (which we will need later), tell it what volume, and associate it with the user(s) who will have access:
Finally, we will create a bucket inside the Storage Space, we can create as many as we need:
If we go to Server Settings, we can copy the URL, and port of our QuObjects, plus we can give it a custom port, and even play with the vhost if we want to use a valid SSL, etc:

We’ve got the QNAP QuObjects part down! Quick, isn’t it?

Add new Object Storage Repository in Veeam Backup and Replication

I wanted to mention to you that Veeam has announced official support for QNAP QuObjects, but you have to look at the hardware that is recommended! 10GbE, or at least 2.5GbE, SSD, etc. Please read the official HCL before opening cases with Veeam due to performance.
Creating an Object Storage repository is always very simple, from the console in Backup Infrastructure – New Object Storage Repository – S3-Compatible, and we already give it the name we want, I like to select concurrent tasks to 2 or a low number to not overflow the QNAP:
In the Service point part, we will enter the IP and port, or FQDN and port, in Region we leave by default us-east-1, and in the credentials, we have to be careful:
Since the Access Key is a combination of the Storage Space and the Access Key, as you see in my case it is QUOBJECTS:YOURACCESSKEY, and the normal Secret Key as given to you by QuObjects:
In the Bucket part, we select the Bucket we created earlier, and we will create a folder inside it, then you can limit the space, or not, it’s up to you.
We are done with everything, we hit Finish:

Create Scale-Out Backup Repository with Capacity Tier to QNAP QuObjects

To make use of our new Object Storage Repo, we have to combine it together with normal Veeam Repositories, so that it extends to this new Capacity Tier, let’s create one, give it a name:We select the Repo, or Repos, that we want to have as an extension of this QNAP QuObjects Object Storage:

In the Capacity Tier part, we will select extend the scale-out Backup repo to the Object Storage, and the options, I like COPY and MOVE, so that everything we have locally we have an exact copy in QNAP QuObjects, and everything that is older than X, is moved to this QNAP QuObjects as well:
That’s it, we hit finish, everything will be done automatically:

We have everything ready, all the backups that are generated in the local repository will be automatically copied to this QNAP QuObjects.

Final details and checks

To conclude, I would like to leave you with some interesting screenshots. For example, this is the screenshot of Veeam doing the offload copy to QNAP QuObjects once the local copy finished, 43MB/s is pretty good to have SATAS on the 7-year-old QNAP:

I like this view a lot too, as in it we can see in detail the data consumption transmitted to QNAP, as well as see the API requests we have made using the S3-Compatible protocol (imagine paying for all those APIs like when we use public Cloud, which well it’s on-prem)
Again, the same image but once the job was finished, copying a few GB, which has generated thousands and thousands of API calls.
Finally, from Filestation, if we explore that folder, we can see the blocks, with their metadata and everything, it’s not important for us since we don’t need to do anything with it, but it’s interesting to see it:That’s all folks, hope you like it and find it helpful.

Filed Under: veeam Tagged With: veeam qnap, veeam qnap quobjects, veeam s3 qnap

Reader Interactions

Comments

  1. Mehmet İstanbullu says

    5th June 2021 at 3:52 pm

    Hello, is immutability supported with Quobjects?

  2. jorgeuk says

    5th June 2021 at 10:32 pm

    Hello, not at the moment I am afraid, Mehmet.

  3. Klaus Elgass says

    21st June 2021 at 1:26 pm

    Hello, it is very interesting for us. We have however a problem with the Certificate of the Qnap.
    We always got the message: “Failed to retrieve certificate from …..” How we can tell Veeam 11 the
    Certificate exception? We only wont to use it within our local LAN. Thanks for your Tips.

    Greetings Klaus

  4. jorgeuk says

    21st June 2021 at 3:07 pm

    Hello Klaus,
    Do you have HTTPS already enabled? And also, are you using the right name convention for the auth?
    https://jorgedelacruz.uk/wp-content/uploads/2021/06/qnap-quobjects-012.jpg

    HTTPS:
    https://www.dropbox.com/s/7z2jc6falqpn096/2021-06-21_15-02-46.jpg?dl=1

    https://www.dropbox.com/s/4jr8mj8y36jyyd1/2021-06-21_15-07-36.jpg?dl=1

    That should work all fine 🙂

  5. fsennj46e7ed4363 says

    11th July 2021 at 3:28 pm

    Hi JOrge, had S3 on Qnap running before with minio in container station – for some unknown reason this wont work anymore for me. GAve it a try with native QuObjects, but after succesfully transferring the files the last failure i see is:

    11.07.2021 16:21:18 :: Processing VM_HDD its-lnx-apc Error: Cannot find repository: {F7179264-F666-4F70-B5FA-DA1D26D799AF}.

    Tried several times with newly createc object stores, monitored FW closely but i first of all it seems as everything is fine and in the end of the job i get the above mentioned failure from Veeam.

    BR
    Franz

  6. jorgeuk says

    14th July 2021 at 2:08 pm

    Hello,
    Strange, as this is supported by Veeam, well at least the technology is but depending of your QNAP model, give it a try to the Support Team if you can, please.

    Best regards

  7. Calvin Ma says

    19th July 2021 at 7:38 am

    Hello!
    1.Is immutability supported with Quobjects?
    => QuObjects will support Veeam immutability plan 2021 ,Q4 . We still study now .
    2. 1.07.2021 16:21:18 :: Processing VM_HDD its-lnx-apc Error: Cannot find repository: {F7179264-F666-4F70-B5FA-DA1D26D799AF}.
    => Please check list website about Veeam Back up notes.
    https://www.qnap.com/en/software/quobjects

    Please note that when using Veeam to back up VMs to QuObjects, there is a capacity limitation for QNAP NAS’s single shared folder. See the recommended configuration as below, and learn more from the Veeam website.

    Thanks!

  8. Franz Senn says

    19th July 2021 at 6:16 pm

    Hi Jorge, can Confirm my failure was Solved by tech support- failure und DB.

    Thank you

  9. jorgeuk says

    20th July 2021 at 2:34 pm

    Awesome, thanks so much!

  10. frscarneiro says

    14th September 2021 at 5:38 pm

    Hello, from the Filestation on QNAP, I can’t see the files. Can you help?

    Thanks!
    BR

  11. Pat says

    1st November 2021 at 10:32 am

    AWS policies don’t work with QuObjects correct?

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Primary Sidebar

  • E-mail
  • GitHub
  • LinkedIn
  • RSS
  • Twitter
  • YouTube

Posts Calendar

June 2021
M T W T F S S
 123456
78910111213
14151617181920
21222324252627
282930  
« May   Jul »

Disclaimer

All opinions expressed on this site are my own and do not represent the opinions of any company I have worked with, am working with, or will be working with.

Copyright © 2025 · The Blog of Jorge de la Cruz