AHV backups and Nutanix files with Hardened Repository

[cdekermadec]

in an AHV and Nutanix Files situation, is there any limitation with the immutability feature associated with the Linux Hardened Repository ?

[HannesK]

Hello,
and welcome to the forums.

I split the question away from the other topic, as it was about something else.

https://helpcenter.veeam.com/docs/backu ... ml?ver=110

I assume that you ask for AHV backups: works same as other workloads.

Nutanix Files: I assume that you use NAS backup for that... NAS backup / file backup jobs can store data on Hardened Repository, but the data stays mutable

Best regards,
Hannes

[cdekermadec]

Thank you Hannes. In order to get the immutability feature for Nutanix Files, can I map the UNC path of the share as a drive that needs to be backed up? If so, what would be the risks?
Best regards,
Claude

[HannesK]

Hello,
I don't understand the question (it just makes no sense to me), but there is zero risk using Hardened Repository

Additionally to the user guide above, I recommend the FAQ: post402811.html#p402811

Best regards,
Hannes

[PTide]

Hi @cdekermadec,

Yes, there are some limitations:

If you want to store AHV VM backups on immutable Linux repositories, make sure that you enable periodic creation of active full backups in the backup job settings and make sure that the backup job retention period is longer than the immutability period of the repository. Otherwise, the backup chain transformation will fail because merging of incremental backups into a full backup is not possible in immutable repositories.

Thanks!

[HannesK]

I don't consider that as a limitation for AHV, as we require non-merging backup modes for every kind of backup.

That's why I still try to understand what the question is really about with Nutanix Files. Because that's not AHV VM backup as far as I understand the question.

[cdekermadec]

The goal is to protect the backup of Nutanix files by making it immutable, at the production site, AND in the Cloud. I
nderstand that this is not possible with the Hardened Repository.
What other alternatives? For al ocal copy: a dedup appliance such as HPE Storeonce?
For the copy in the cloud: AWS s3?
Thanks.

[Mildur]

At the moment, a immutability feature for NAS Backups do not exist.
I thinking, if it‘s possible to define a VM as a Backup Repo for the NAS Backups (Nutanix Files).
You can do a VmImage Backup Job of this vm when no NAS backups jobs are running.

The Backup of the vm can be stored on a local repo and then offloaded to the cloud.
And the 3-2-1 rule will be followed.

Direct Restore from the copy would not be possible of the NAS Files, but the backup Repo Data would be safe on a second location

[HannesK]

Hello,
in general: the backup environment should be protected against external access. Relying on immutable backups is a bad practice. I should just be a "last line of defense".

Dedupe appliances also do not really help. In most cases they are just a waste of money. See Forum FAQ on that topic.

For cloud copy to object storage (S3): for NAS backup, we are still working on that.

So as for now, there is only "workarounds" for what you are asking for.

Best regards,
Hannes

PS: I moved the topic to the "file shares" forum