I am attempting to setup a Sync between a local directory and an AWS S3 bucket. The files exist and match identically in both locations, however the S3 objects were uploaded at a later date and therefore have a more recent last modified date.
When setting up a Sync, I correctly received a warning of the collision. If I select the Use details from Left option, SyncBackPro attempts to upload the entire file to S3. I suspect this is because AWS S3 does not support modifying the objects last modified date.
The only thought I have is that AWS S3 supports user defined tags, where the original last modified date could be stored and SyncBackPro could use to compare. What's the best solution in this case, avoiding re-uploading all of the files?
Before posting, and to avoid disappointment, please read the following:
- This forum is not for 2BrightSparks to provide technical support. It's primarily for users to help other users. Do not expect 2BrightSparks to answer any question posted to this forum.
- If you find a bug in any of our software, please submit a support ticket. It does not matter if you are using our freeware, a beta version or you haven't yet purchased the software. We want to know about any and all bugs so we can fix them as soon as possible. We usually need more information and details from you to reproduce bugs and that is better done via a support ticket and not this forum.
- If you are entitled to technical support then please submit a support ticket. Please do not post the same question to the forum and also via a support ticket. Once again, 2BrightSparks does not provide technical support via this forum.
Collision Handling - Syncing with Existing Files on AWS S3
-
priver
- Newbie
- Posts: 1
- Joined: Thu Dec 28, 2023 11:16 pm