Immutability with NAS

[NorthGuard]

My current implementation for onsite immutability is having a linux server with storage, but I would like to simply that a bit more.

I was reviewing the Veeam Ready list and it appears that currently, only QNap with QuObjects are the only Veeam-verified devices. Is that correct?

Assuming it is, I just want to verify that I understand the architecture:

I would only have a B&R server and a QNAP NAS.
The QNAP would be repository configured for immutability.

I know I am over simplifying, but is that essentially the picture?

[Mildur]

Hi North Guard

Immutability and direct to object storage for NAS backups are V12 features. Earlier versions will not be able to use it.

I was reviewing the Veeam Ready list and it appears that currently, only QNap with QuObjects are the only Veeam-verified devices. Is that correct?

Yes, if it's in the Veeam Ready list. It will be updated if other devices are receiving the Veeam ready status.
I also recommend checking out other solutions.

Thanks
Fabian

[NorthGuard]

It wouldn't be setup or present itself in the same manner that something like Wasabi does?

[Mildur]

It wouldn't be setup or present itself in the same manner that something like Wasabi does?

QNap with QuObjects is an S3 compatible object storage.
You will create a bucket on the QNAP and then add it as an object storage in Veeam Backup & Replication.
The configuration in Veeam will be the same as for Wasabi today.

- V11 can only offload deleted files or older file versions to object storage. And it cannot be immutable.
- V12 is able in addition to backup all files and their versions to object storage directly and set them immutable.

Thanks
Fabian

[NorthGuard]

I am currently doing immutable with Wasabi for a couple of clients and it offloads the immediate backup....

For the 2nd part, is the difference in who actually handles the immutability? With V11 the vendor ( Wasabi, QNAP, etc ) is handling it?

I think I am getting a bit confused

[Mildur]

Is the question about NAS backup Jobs or VM backup Jobs?

[NorthGuard]

NAS would be the storage to hold the backups....

[Mildur]

Ok, then I was confused by the title
Moved again to object storage.
For VM and Agent Jobs, it behaves the same as Wasabi or any other object storage with object lock support.

1) You create a bucket on the "QNap with QuObjects".
2) You connect the bucket to VBR.
3) You add the bucket as a capacity tier to a SOBR.

Thanks
Fabian

[NorthGuard]

One more hopefully easy question:

Would I still need a "local" backup to Veeam ( ie., the SOBR would need a local + a capacity tier )?

[Mildur]

Yes, in V11 you need a SOBR with "local" storage (performance tier).

V12 will allow you to back up a VM, Agent and almost any other workload directly to object storage without a SOBR.

[SinDmit]

QNAP TS-1886XU-RP
QuTS hero h5.0.1.2277
QuObjects 2.4.1446

Veeam B&R 12.0.0.1420 P20230223

Immutability does not work.

[Andreas Neufert]

Please contact QNAP if you can not enable it on the Veeam side.
Edited: Qulogic=>QNAP

[SinDmit]

why Qulogic? QuObjects from Qnap.

Oder Qulogic.de?

[jorgedlcruz]

Hello,
Have you followed all the needed steps to configure QuObjects, and create a bucket with object-lock, plus add it to Veeam properly? I have the same build and all works as expected, more info here with the step by step: https://www.youtube.com/watch?v=EbTQLihEiII

If you encounter issues, after following that video, I would recommend to open a QNAP ticket. As Veeam will use the bucket as QNAP has it configured.

Thanks!

[SinDmit]

i have QuObjects 2.4.1466
in Window StorageSpace i have Settings "Worm"
in Window Backet: Object lock is not supported. Word is disabled on the storage space.