Immutability with Wasabi

[MetisPT]

Hi all.

I am trialling NAKIVO and started with the backup of a Windows Server to a Wasabi bucket.

I created the Wasabi bucket without versioning or locking (compliance-mode) and proceeded to create the corresponding repository in NAKIVO. In the settings the immutable backup option was disabled.

Back in Wasabi I enabled file versioning and compliance mode.

IN NAKIVO I refreshed the repository and tried to create the backup job again, but there is no way to enable the immutable option.

What am I missing?

 

 

[MetisPT]

Answering my own question.

The Object Locking has to be enabled when creating the bucket in Wasabi. And then let NAKIVO set the immutability period.

[The Official Moderator]

On 1/24/2025 at 7:48 PM, MetisPT said:

Hi all.

I am trialling NAKIVO and started with the backup of a Windows Server to a Wasabi bucket.

I created the Wasabi bucket without versioning or locking (compliance-mode) and proceeded to create the corresponding repository in NAKIVO. In the settings the immutable backup option was disabled.

Back in Wasabi I enabled file versioning and compliance mode.

IN NAKIVO I refreshed the repository and tried to create the backup job again, but there is no way to enable the immutable option.

What am I missing?

 

 

Hi @MetisPT,

You can check our system requirements regarding the immutability:

https://helpcenter.nakivo.com/User-Guide/Content/Deployment/System-Requirements/Feature-Requirements.htm#Immutability

If you think that all settings were applied correctly and it should work, pleaes send us the support bundle with the main database included along with screenshots of the Wasabi bucket settings (versioning, Object Lock) to support@nakivo.com 

For instructions on how to create and send a support bundle, refer to this article: https://helpcenter.nakivo.com/User-Guide/Content/Settings/Support-Bundles.htm?Highlight=support%20bundle

We look forward to hearing from you soon.

[Emanuele.digiammarino]

Hello to everyone;
 

 

11.0.2 (build 91392 from 12 Mar 2025) here, trial

I did as the Initial user:

I created the bucket  in wasabi  with version enabled and object lock enabled, I didn't enable the retention though.
Excecuted Wasaby inventory
Created The wasabi Repo

Created a Hyper-v VM test Job,  set on the schedule part the immutability 4 days.

Started the job
Checked  wasabi side the obijects properties and weren't marked as  compliance mode.
I got in wasabi with a IAM account  that has  power to  manage / cancel buckets ..... 

I cancelled everything smoothly! what a NAKIVO CRAP!

If I had enabled the Compliance mode  Wasabi side, THERE WAS NO WAY the inventory could succede,  it fails  at any attempt so, where the hell is this so called immutability?

So disappointed.

[The Official Moderator]

On 4/12/2025 at 6:17 PM, Emanuele.digiammarino said:

Hello to everyone;
 

 

11.0.2 (build 91392 from 12 Mar 2025) here, trial

I did as the Initial user:

I created the bucket  in wasabi  with version enabled and object lock enabled, I didn't enable the retention though.
Excecuted Wasaby inventory
Created The wasabi Repo

Created a Hyper-v VM test Job,  set on the schedule part the immutability 4 days.

Started the job
Checked  wasabi side the obijects properties and weren't marked as  compliance mode.
I got in wasabi with a IAM account  that has  power to  manage / cancel buckets ..... 

I cancelled everything smoothly! what a NAKIVO CRAP!

If I had enabled the Compliance mode  Wasabi side, THERE WAS NO WAY the inventory could succede,  it fails  at any attempt so, where the hell is this so called immutability?

So disappointed.

Hello Emanuele,

The NAKIVO solution uses its own immutability and retention policy algorithms.

Compliance mode and policies should be disabled on the Wasabi side.

 

To enable NAKIVO immutability, only Object Lock and Versioning must be enabled.