Backblaze Class C Transactions

Greetings-- I am taking Vertical Backup for a spin using Backblaze.

While attempting my first backup of a VM to Backblaze, I’ve already used more than 2,000 Class C Transactions. Is this normal?

The command I used to initiate this backup is:

vertical backup nameofvm

Is this normal procedure? Thanks!

This is because Vertical Backup still uses b2_list_file_names to check if a chunk exists, which is a Class C transaction.

Duplicacy already uses b2_download_file_by_name, a Class B transaction: https://github.com/gilbertchen/duplicacy/pull/209

I’ll fix it and release a new version in the next week.

This has been fixed by a new version available at http://acrosync.com/esxi/vertical.