application-consistent snapshots will no longer truncate logs by default

[quetschen]

Hello
Nutanix has made changes to the application-consistent snapshot, so the logs from the Exchange are not truncated:

Until Nutanix 6.0, the default VSS snapshot type was Full (VSS_BT_FULL). This resulted in log truncation after each snapshot for workloads like SQL/Exchange, offering limited control in differentiating between a Disaster Recovery Snapshot or a Full backup. To offer better control on backup and RTO/RPO requirements and to overcome limitations with SQL DB restore in case of FULL snapshots, with Nutanix AOS 6.0 the default VSS Backup type has been changed to Copy (VSS_BT_COPY). As a result of this change, protected workloads using application-consistent snapshots will no longer truncate logs by default. For workloads like Microsoft Exchange, this results in higher disk space consumption.

https://portal.nutanix.com/page/documen ... 000LY8oSAG

the KB describes that the backup vendor can influence this via API, reset to VSS_BT_FULL
is this implemented or how can it be controlled via the API?

king regards
Jörg

[ronnmartin61]

Thanks for the heads-up. Yes it definitely appears the behavior is configurable via the v3 API. We'll look into how we may best incorporate this. Question for you - I assume you'd prefer the flexibility of applying this setting at the individual VM level (not cluster/"global" or per backup job) correct?

[asm19]

Hello,

Glad to know I'm not the only one.
I have 2 cases created for this problem, of which a Feature Request has been requested but I have no further news.

Case #06074677
Case #05996930

[ronnmartin61]

@quetschen, @asm19 can either of you (or anyone for that matter) comment on my prior question regarding precisely what sort of setting granularity is preferred?

[asm19]

Thanks for the heads-up. Yes it definitely appears the behavior is configurable via the v3 API. We'll look into how we may best incorporate this. Question for you - I assume you'd prefer the flexibility of applying this setting at the individual VM level (not cluster/"global" or per backup job) correct?

Hello Ron,

Individual VM level, like that we have with Veeam + Vmware.



Thank you

[ronnmartin61]

@asm19 thank you for your feedback! That's what I assumed but wanted to validate.

[ronnmartin61]

@asm19 I wanted to updated this thread to let you all know that we've released a private beta (v6.0) which reverts the default NGT/API interaction to the pre-6.5 operating mode. If you're interested in testing please contact your local Veeam SE who can set up access to the beta bits. Currently this is a global configuration file setting but in the future we'll look toward increased granularity.

[ronnmartin61]

@quetschen, @asm19 just wanted to update this thread now that v6.0 is generally available.

[asm19]

Hi @ronnmartin61,

Is this option applied automatically? I updated to v6 and I don't see the option to "Perform copy only", is it invoked directly from the API by default?

[ronnmartin61]

@asm19 yes the switch to truncate by default is automatic. No UI-level configuration option is presented. We don't yet have the appendix added to our online documentation that describes explicitly setting this but it should be available shortly.