BackBlaze B2 (started large file)

Hello, i have successfully upload to BackBlaze 12gb of backup file. But when i go to BackBlaze browser i see the file 2 times. One file with correct 12gb of size and another one same name with 0 byte of size and renamed at the end (started large file).

The command i use is:

rclone copy -P -vv --transfers 3 d:/shared/Veeam_SqlServer BackBlazeCloud:BetAthens

result:

C:\Users\Administrator\Documents\rclone>rclone copy -P -vv --transfers 3 d:/shared/Veeam_SqlServer BackBlazeCloud:Bet
Athens
2019/04/29 02:23:19 DEBUG : rclone: Version “v1.47.0” starting with parameters [“rclone” “copy” “-P” “-vv” “–transfe
rs” “3” “d:/shared/Veeam_SqlServer” “BackBlazeCloud:BetAthens”]
2019/04/29 02:23:19 DEBUG : Using config file from “C:\Users\Administrator\.config\rclone\rclone.conf”
2019-04-29 02:23:21 INFO : B2 bucket BetAthens: Waiting for checks to finish
2019-04-29 02:23:21 DEBUG : Veeam_SqlServer.vbm: Size and modification time the same (differ by -645.4.s, within tole
rance 1ms)
2019-04-29 02:23:21 DEBUG : Veeam_SqlServer.vbm: Unchanged skipping
2019-04-29 02:23:21 INFO : B2 bucket BetAthens: Waiting for transfers to finish
2019-04-29 02:25:35 DEBUG : Veeam_SqlServer2019-04-27T210008.vbk: Starting upload of large file in 12 chunks (id “4_z
652c63c7ad892d356aa30014_f20674d61fab52d20_d20190428_m232521_c002_v0001110_t0031”)
2019-04-29 02:25:43 DEBUG : Veeam_SqlServer2019-04-27T210008.vbk: Sending chunk 1 length 1073741824
2019-04-29 02:25:52 DEBUG : Veeam_SqlServer2019-04-27T210008.vbk: Sending chunk 2 length 1073741824
2019-04-29 02:26:00 DEBUG : Veeam_SqlServer2019-04-27T210008.vbk: Sending chunk 3 length 1073741824
2019-04-29 02:48:14 INFO : Veeam_SqlServer2019-04-28T210012.vib: Copied (new)
2019-04-29 03:49:54 DEBUG : Veeam_SqlServer2019-04-27T210008.vbk: Done sending chunk 1
2019-04-29 03:50:00 DEBUG : Veeam_SqlServer2019-04-27T210008.vbk: Sending chunk 4 length 1073741824
2019-04-29 04:00:55 DEBUG : Veeam_SqlServer2019-04-27T210008.vbk: Done sending chunk 2
2019-04-29 04:01:02 DEBUG : Veeam_SqlServer2019-04-27T210008.vbk: Sending chunk 5 length 1073741824
2019-04-29 04:48:07 DEBUG : Veeam_SqlServer2019-04-27T210008.vbk: Done sending chunk 3
2019-04-29 04:48:14 DEBUG : Veeam_SqlServer2019-04-27T210008.vbk: Sending chunk 6 length 1073741824
2019-04-29 05:03:21 DEBUG : Veeam_SqlServer2019-04-27T210008.vbk: Done sending chunk 4
2019-04-29 05:03:28 DEBUG : Veeam_SqlServer2019-04-27T210008.vbk: Sending chunk 7 length 1073741824
2019-04-29 06:03:20 DEBUG : Veeam_SqlServer2019-04-27T210008.vbk: Done sending chunk 5
2019-04-29 06:03:27 DEBUG : Veeam_SqlServer2019-04-27T210008.vbk: Sending chunk 8 length 1073741824
2019-04-29 06:18:50 DEBUG : Veeam_SqlServer2019-04-27T210008.vbk: Done sending chunk 7
2019-04-29 06:18:58 DEBUG : Veeam_SqlServer2019-04-27T210008.vbk: Sending chunk 9 length 1073741824
2019-04-29 06:23:05 DEBUG : Veeam_SqlServer2019-04-27T210008.vbk: Done sending chunk 6
2019-04-29 06:23:13 DEBUG : Veeam_SqlServer2019-04-27T210008.vbk: Sending chunk 10 length 1073741824
2019-04-29 07:35:32 DEBUG : Veeam_SqlServer2019-04-27T210008.vbk: Done sending chunk 8
2019-04-29 07:35:39 DEBUG : Veeam_SqlServer2019-04-27T210008.vbk: Sending chunk 11 length 1073741824
2019-04-29 07:46:37 DEBUG : Veeam_SqlServer2019-04-27T210008.vbk: Done sending chunk 9
2019-04-29 07:46:40 DEBUG : Veeam_SqlServer2019-04-27T210008.vbk: Sending chunk 12 length 480628736
2019-04-29 08:20:17 DEBUG : Veeam_SqlServer2019-04-27T210008.vbk: Done sending chunk 10
2019-04-29 08:23:41 DEBUG : Veeam_SqlServer2019-04-27T210008.vbk: Done sending chunk 12
2019-04-29 08:41:30 DEBUG : Veeam_SqlServer2019-04-27T210008.vbk: Done sending chunk 11
2019-04-29 08:41:30 DEBUG : Veeam_SqlServer2019-04-27T210008.vbk: Finishing large file upload with 12 parts
2019-04-29 08:41:31 INFO : Veeam_SqlServer2019-04-27T210008.vbk: Copied (new)
Transferred: 11.669G / 11.669 GBytes, 100%, 539.225 kBytes/s, ETA 0s
Errors: 0
Checks: 1 / 1, 100%
Transferred: 2 / 2, 100%
Elapsed time: 6h18m11.8s
2019/04/29 08:41:31 INFO :
Transferred: 11.669G / 11.669 GBytes, 100%, 539.225 kBytes/s, ETA 0s
Errors: 0
Checks: 1 / 1, 100%
Transferred: 2 / 2, 100%
Elapsed time: 6h18m11.8s

2019/04/29 08:41:31 DEBUG : 6 go routines active
2019/04/29 08:41:31 DEBUG : rclone: Version “v1.47.0” finishing with parameters [“rclone” “copy” “-P” “-vv” “–transf
ers” “3” “d:/shared/Veeam_SqlServer” “BackBlazeCloud:BetAthens”]

and config:

[BackBlazeCloud]
type = b2
account = 002xxxxxxxxxxxxx
key = K00xxxxxxxxxxxxxxxxxx
hard_delete = false
upload_cutoff = 4G
chunk_size = 1G

BackBlaze Browser:

Veeam_SqlServer2019-04-27T210008.vbk 12.3 GB 04/29/2019 02:25
Veeam_SqlServer2019-04-27T210008.vbk (started large file)0 bytes 0 4/29/2019 01:50

My question is should i put something extra to my command to delete the 0 byte file?

Should i run an extra command to do it?

Or should i delete it manually?

Thank you.

That is a large file upload that was started but not completed. I guess you tried the upload once then interrupted it?

In 1.47 we made rclone cleanup b2:bucket clean up pending large file uploads as well as old revisions so you can use that.

I think it will expire anyway after some time (not sure how long)

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.