"More Than 65535 Total Parts Uploaded For A Single Object" Error On Image-Based Backup To Wasabi
An image-based backup plan fails with the following error: More than 65535 total parts uploaded for a single object.
The issue is related to recently failed attempts to upload the data to Wasabi storage account. By design, the multipart upload will be only considered finished only if all the parts of it were uploaded and if these parts properly reformed on the storage into a corresponding piece of the data. If for some reason some parts do not arrive, multipart upload cannot be resumed and the portion that was already uploaded, will stay there for 31 days to allow user finishing the operation. Uncompleted multipart upload will count toward your used storage space and upon reaching a limit of concurrent parts for multipart uploads it will also invoke the More than 65535 total parts uploaded for a single object error.
You can use the CloudBerry Explorer, our cloud file manager, to delete the unfinished multipart uploads manually. To do thism proceed as follows:
- Download and install the CloudBerry Explorer for S3: https://www.msp360.com/explorer/windows/amazon-s3.aspx, it comes with a free 15-day trial.
- Select File -> S3 Compatible to add the storage account.
It is recommended to add Wasabi storage accounts using the S3 Compatible option in this article to ensure that you will be able to work with the newest buckets regions that might not yet be supported by the software.
- Fill in all the required fields to finalize adding the storage account. You can refer to this article to find the service point URLs for the Wasabi regions.
In case the storage account will be added successfully you will be able to access it via the “Registered Accounts” application window:
After adding your storage account expand the Tools menu and navigate to the Multipart Uploads option:
Select the S3 Compatible account that you just added and select the bucket you are running the backup plans to, then select multipart upload from the list by clicking on it, then hit the “Delete” button in order to clean up an unfinished upload.
Before deleting the unfinished multipart uploads make sure that you do not have any active ongoing backup plans pointed to your Wasabi bucket, in order to make sure that you would not delete a portion of the current backup. In case you will delete the multipart upload for an ongoing plan it will result in a failure of that plan.
- After the deletion of unfinished multipart uploads start your Image-Based backup plan.
Alternatively, you can refer to this Wasabi documentation that describes how to clean up unfinished multipart uploads via AWS CLI.