S3 Destinations: Disable/Enable object integrity

michael shared this idea 15 months ago
Under Consideration

Hi!

Currently JetBackup is forcing object integrity on S3 destinations which results in files failing to be backed up if they are currently written to while backup is running.

I'd like an option to be able to enable/disable this object integrity (sending filehash in S3 header), so you do not get warnings/errors when backing up open files. (Same way as rsync destinations)

Replies (1)

photo
1

Hello Michael,

We appreciate your feedback and the feature request you submitted. Our team will review your request and keep you informed of any updates. Please do note, however, that sending a file hash is part of the S3 upload process. Essentially, the way this process works is that, prior to uploading the file, the file is first hashed and then sent to the S3 destination. Then, the file is uploaded and, using the same hashing algorithm is hashed once again on the S3 storage destination. The two hashes are compared and if they do not match then the S3 destination rejects the file. This is a required part of the S3 upload process and is not something that JetBackup has control over. The same process occurs whenever a file is uploaded to S3, whether using JetBackup or even just a manual file upload.

Best Regards,

The JetApps Team

Leave a Comment
 
Attach a file