2 chunks folders with < 500KB data after 4 hours. Is this normal?

#1

So I am backing up a relativiely small VM of about 8GB. However its past 5 hours or os and yet the wasabi bucket still shows only 2 chunks folders with hardly any data. Is it because it wont propagate until complete?

Reason I ask is because Duplicati through wasabi buckets shows me fairly quickly what files have been uploaded as part of its segmentation of a VeeamZip. In the same time span I see about 10GB of data with Duplicati.

I should mention my first backup failed and when I decided to try a different VM, the 8GB one, is when I noticed this. It’s still going too. And I dont see any progress indicator. Here is the ouput in console so far:

[root@XXXX:/vmfs/volumes/5d749fae-5976ff06-7bbb-7085c2bdc091/verticalbackup] ./v
ertical backup Office --no-chunk-listing
Vertical Backup 1.3.2
Trial license expires on 2019-10-16
Enter the S3 access id:
Enter the S3 secret key:
Storage set to wasabi://XXXXX
Listing all virtual machines
Backing up Office, id: 6, vmx path: /vmfs/volumes/VM/Office/Office.vmx, guest os: windows9_64Guest
No previous backup found
Virtual machine Office is powered on
Removing all snapshots of Office
Creating a new virtual machine snapshot for Office
Create Snapshot:
Create snapshot failed
Command '/bin/vim-cmd vmsvc/snapshot.create 6 2019-09-16-21-11-30 'Created by Vertical Backup 1.3.2' 0 1' returned 1
Removing all snapshots of Office
[root@XXXX:/vmfs/volumes/5d749fae-5976ff06-7bbb-7085c2bdc091/verticalbackup] ./v
ertical backup HASS --no-chunk-listing
Vertical Backup 1.3.2
Trial license expires on 2019-10-16
Enter the S3 access id:
Enter the S3 secret key:
Storage set to wasabi://XXXX
Listing all virtual machines
Backing up HASS, id: 2, vmx path: /vmfs/volumes/VM/HASS/HASS.vmx, guest os: centos7_64Guest
No previous backup found
Virtual machine HASS is powered on
Removing all snapshots of HASS
Creating a new virtual machine snapshot for HASS
Uploaded file /vmfs/volumes/VM/HASS/hassos_ova-2.12_new.vmdk
Uploading file hassos_ova-2.12_new-flat.vmdk
Uploading ----------------------------------------------- 539KB/s 03:14:38 0.0%
Failed to upload file chunks/7e/779ea6123c9bce757356c8ed030fe2ce25ba9bbcc44eb5d583299f48266a11: error(32, 'Broken pipe')
[root@XXXX:/vmfs/volumes/5d749fae-5976ff06-7bbb-7085c2bdc091/verticalbackup]
[root@XXXX:/vmfs/volumes/5d749fae-5976ff06-7bbb-7085c2bdc091/verticalbackup] ./v
ertical backup HASS --no-chunk-listing
Vertical Backup 1.3.2
Trial license expires on 2019-10-16
Another backup job is in progress
[root@XXXX:/vmfs/volumes/5d749fae-5976ff06-7bbb-7085c2bdc091/verticalbackup] lis
t
-sh: list: not found
[root@gong:/vmfs/volumes/5d749fae-5976ff06-7bbb-7085c2bdc091/verticalbackup] ./v
ertical list backups
Vertical Backup 1.3.2
Enter the S3 access id:[root@XXXX:/vmfs/volumes/5d749fae-5976ff06-7bbb-7085c2bdc[root@XXXX:/vmfs/volumes/5d749fae-5976ff06-7bbb-7085c2bdc091/verticalbackup] ./v
ertical backup HASS --no-chunk-listing
Vertical Backup 1.3.2
Trial license expires on 2019-10-16
Another backup job is in progress
[root@XXXX:/vmfs/volumes/5d749fae-5976ff06-7bbb-7085c2bdc091/verticalbackup]
#2

Welp, there is no pending uploads anymore. But backup list says no vms in wasabi. Nice.

#3

Try uploading with 4 threads:

./vertical backup Office --threads 4

‘Broken pipe’ could be a temporary network error. If you keep getting the Another backup job is in progress error, run pkill vertical and delete the file .verticalbackup/plock.

#4

I can confirm now that this was caused by the bucket being in the us-west-1 region. You can switch the s3 url to access such a bucket:

./vertical init hostid s3://s3.us-west-1.wasabisys.com/bucket

BTW, can you change your screen name on this forum so it won’t cause confusion.

#5

Ah ok, I was following Wasabi’s guide and must have misinterpreted the directions or they need to update them. Also, name changed. I use my own email domain so the user is based per website, thats why you saw that.

#6

Actually looks like youll need to do that. System wont let me.