Page 1 of 1

BackBlaze uses up Class C Transactions

Posted: 11 Jun 2021, 04:46
by kennethmb
It appears that the BackBlaze client doesn't try to preserve the Class C Transactions. I'm reluctant to let it go unlimited because I have no idea how the code is written.

Could we look at having it do some local tracking of what is on the NAS and what it has pushed to the cloud so we don't blow through the cap every day and make sure we are uploading new or changed files?

Seems like something like this would be a good candidate to open source and let some others share in the work.

Re: BackBlaze uses up Class C Transactions

Posted: 11 Jun 2021, 21:28
by TMS
Your suggestion has been received, and we will evaluate it internally.

Re: BackBlaze uses up Class C Transactions

Posted: 23 Sep 2021, 01:49
by ntrnflxlbs
yes it appears it is using an absurd amount of class c transactions and is running the bill up when i've changed zero files on the NAS in 3 days.
is there a setting we should select in the b2 cloud sync app to resolve this?
I'd like to add that overall the programming quality of this add on app is poor. once you create a connection, I do not have the simple option of going back and editing it.

Re: BackBlaze uses up Class C Transactions

Posted: 23 Sep 2021, 10:54
by TMSupport
{L_BUTTON_AT}ntrnflxlbs

Hi!
In order to achieve timely synchronization of cloud and local files, backblaze will poll to check whether the files of the existing tasks have changed every period of time, so certain bills will be generated.
After the connection is created, you can do simple operations on the connection, such as "Disconnect", "Delete".