We can’t seem to get reliable transmissions of backups to our BackBlaze B2 bucket. After sending for a while, we get an error "Failed to send request post https://pod-000-1099-09.backblaze.com/b2api/v1/b2_upload_file/…_t0024: HTTPSConnectionPool(host=‘pod-000-1099-09.backblaze.com’, port=443): Max retries exceeded with url: /b2api/v1/b2_upload_file/…_t0024 (Caused by NewConnectionError(’<requests.packages.urllib3.connection.VerifiedHTTPSConnection object at 0x53dd2610>: Failed to establish a new connection: [Errno 111] Connection refused’,))
We’re running on ESXi v5.5, patched to current. Ideas?
Oh, and if I try to restart the backup again with the same command line, it fails with:
2018-01-19 18:41:14.493095 INFO BACKUP_LISTING No previous backup found. Listing existing chunks
Traceback (most recent call last):
File “vertical_main.py”, line 145, in
File “vertical_backup.py”, line 449, in backupCommand
File “vertical_backup.py”, line 473, in backupVM
File “vertical_snapshot.py”, line 356, in createSnapshot
File “vertical_snapshot.py”, line 261, in listChunkFiles
File “vertical_b2storage.py”, line 300, in listFiles
MemoryError
Failed to execute script vertical_main
It looks like the B2 upload server rejected the connection. I don’t know why, but you can increase the number of retries by setting VB_MAX_RETRIES to 16. The default is 8, but if it is a connection error, the number of retries is half of that.
For the memory error, you can run the backup command as:
./vertical backup --no-chunk-listing vmname
With this --no-chunk-listing option, Vertical Backup will not attempt to list all chunks in the storage and construct a chunk cache in memory. The downside of this option is that for each chunk that already exists in the storage, a lookup is needed to determine if the chunk upload can be skipped.
I’m probably doing something wrong here, but I get a “error: unrecognized arguments: --no-chunk-listing” error when I try that option. That option also doesn’t show up for ./vertical backup -h. Am I running the correct version (1.1.5)?
If you download the latest 1.1.5 build from http://acrosync.com/esxi/vertical it should have this option. The sha256 of the latest build is 11a9459a2a93047d16fe5e9399186c33f383e8843ac19b601527cc543eb897bf.
This is what I see when getting the latest version:
/vmfs/volumes/5839ff6b-b37d5a97-9435-6805ca0a89c0/verticalbackup # wget http://verticalbackup.com/esxi/vertical
Connecting to verticalbackup.com (216.239.36.21:80)
vertical 100% |***********************************************************************************| 10472k 0:00:00 ETA
[root@esxi55:/opt/vertical] wget http://acrosync.com/esxi/vertical
Connecting to acrosync.com (198.199.87.9:80)
vertical 100% |****************************************************************************************************************************************************| 10472k 0:00:00 ETA
[root@esxi55:/opt/vertical] sha256sum vertical
11a9459a2a93047d16fe5e9399186c33f383e8843ac19b601527cc543eb897bf vertical
[root@esxi55:/opt/vertical] chmod u+x vertical
[root@esxi55:/opt/vertical] ./vertical backup -h
usage: vertical backup [-h] [-p] [--no-quiesce] [-t TAG] [--threads THREADS]
[-l LIMIT_RATE] [-e EXCLUDES] [--email]
[--subject EMAIL_SUBJECT]
[--failure-subject FAILURE_SUBJECT] [--parallel]
[--exclude-disk EXCLUDED_DISKS] [--no-chunk-listing]
[vmname [vmname ...]]
positional arguments:
vmname the name of the virtual machine to back up
optional arguments:
-h, --help show this help message and exit
-p, --preserve-snapshots
don't remove or create snapshots
--no-quiesce do not quiesce the virtual machine before the backup
-t TAG, --tag TAG specify a backup tag
--threads THREADS number of uploading threads
-l LIMIT_RATE, --limit-rate LIMIT_RATE
limit the upload speed (KiloBytes/sec)
-e EXCLUDES, --exclude EXCLUDES
do not backup the virtual machine with this name
--email email log after backup is done
--subject EMAIL_SUBJECT
the subject of the email to be sent
--failure-subject FAILURE_SUBJECT
the email subject to use when backup fails
--parallel allow multiple backups at the same time
--exclude-disk EXCLUDED_DISKS
do not backup the disk with this name
--no-chunk-listing do not list chunks for initial backup