Backup archive larger than 5GB cannot be uploaded to S3 service
-
When BackWPup is updated to version 3.6. 10, forwarding to S3 services will fail.
The log when the job failed is as follows:
[16-Jul-2019 09:17:17] Backup archive created.
[16-Jul-2019 09:17:17] Archive size is 5.63 GB.
[16-Jul-2019 09:17:17] 79639 Files with 5.96 GB in Archive.
[16-Jul-2019 09:17:18] 1. Trying to send backup file to S3 Service…
[16-Jul-2019 09:17:19] Connected to S3 Bucket “xxxxxxxxx” in ap-northeast-1
[16-Jul-2019 09:17:19] Checking for not aborted multipart Uploads…
[16-Jul-2019 09:17:19] Starting upload to S3 Service…
[16-Jul-2019 09:22:02] ERROR: Cannot transfer backup to S3! (0)
[16-Jul-2019 09:22:03] One old log deleted
[16-Jul-2019 09:22:03] ERROR: Job has ended with errors in 3076 seconds. You must resolve the errors for correct execution.The environment running BackWPup plugin is as follows:
- WordPress version: 5.2.2
- BackWPup version: 3.6.10
- PHP version: 7.1.29 (64bit)
- MySQL version: 10.1.23-MariaDB
Looking at the BackWPup source code, it appears that there seems to be a problem with the MultipartUpload argument of the completeMultipartUpload method.
The argument uses the results of the listParts method, which can only get 1,000 parts at a time.Multipart Upload Listings
You can list the parts of a specific multipart upload or all in-progress multipart uploads. The list parts operation returns the parts information that you have uploaded for a specific multipart upload. For each list parts request, Amazon S3 returns the parts information for the specified multipart upload, up to a maximum of 1,000 parts. If there are more than 1,000 parts in the multipart upload, you must send a series of list part requests to retrieve all the parts.
The size of each part seems to be 5 MB, so multipart uploads can only upload 5 MB * 1000 = 5 GB.
- The topic ‘Backup archive larger than 5GB cannot be uploaded to S3 service’ is closed to new replies.