Transaction cost estimation

[Tos]

Hi

We have questions about the Transaction cost estimations of Veeam Backup for Azure.
https://helpcenter.veeam.com/docs/vbazu ... tml?ver=20

We have a schedule for backing up to Blobs and taking snapshots once a day.

In this case, if we set the Snapshots to keep value to 1, Transaction cost estimations is "$2.95".
Of we set the Snapshots to keep value to 2 or higher, Transaction cost estimations is "$1.27".

Is it by design that setting the Snapshots to keep value to 1 increases transaction costs ?

Let me know.

[nielsengelen]

Hi Toshihiro,

This is actually by design in the way that storing multiple snapshots can become cheaper.

[Tos]

Hi
Thank you for reply.
"This is actually by design in the way that storing multiple snapshots can become cheaper."
Why is that ? I read the Veeam user guide, but I didn't understand..

[Mildur]

This is something Microsoft is billing you.
You will find your answer in the Microsoft Azure Pages.

If they doing incremental snapshots, then the second snapshot will not have the same size as the first one.
Therefore, not the double amount of storage needs to be paid.

https://azure.microsoft.com/en-us/prici ... ged-disks/

[Tos]

Hi
Unfortunately, I checked the Microsoft Azure Pages, but I wasn't sure about Transaction Cost..
https://azure.microsoft.com/en-us/prici ... ged-disks/

Here is a screenshot of my test environment.
"Snapshots to keep" value is 1;


"Snapshots to keep" value is 2;


Why does changing the "Snapshots to keep" value from 1 to 2 reduce the Transaction cost ?

We understood that Transaction cost is the cost f making API requests to Microsoft Azure during data protection operations.
So I thought changing the "Snapshots to keep" value from 1 to 2 wouldn't change it.

[Vitaliy S.]

Toshihiro, can you please share the scheduling options for backups/snapsots in the right pane (to see what parameters are selected)?

[nielsengelen]

Hi Toshihiro,

Transaction costs are actually related to backups and not to snapshots. U can click on the expected amount to see the details.

The reason why multiple snapshots become cheaper is due to the fact that in the case when we have only 1 snapshot (or 0 for weekly/monthly) we can’t use CBT. As a result, a worker will consume more time for creating a backup as we need to read and parse more data.
Once u configure multiple snapshots (2 or more), we can use CBT for processing this. As a result, the worker doesn't need to run for a longer period and thus the transaction costs go down.

Hope this makes sense.