Amazon S3 Sync 0-Byte File Issue

[rodgerwheat]

Hi, I have a problem with AWS S3 sync. If the file was originally synced to the AWS S3 folder with Syncback, the file opens correctly, can be renamed and moved to other folder using the AWS Console. If I upload the file using the AWS Console, the file looks good on the Console, but syncs to the local folder using SyncBack as a 0-byte folder with the same filename. Also, I did not see an answer to this post with a similar issue, "Amazon S3 FTP -- folder names repeated as 0-byte files". I am running SyncBackPro 6.0.3.3. Thanks.

[Dave Wilkins]

S3 storage has no concept of folders, so placeholders for folders have to be used. There is no standard for this, so that using more than one utility to transfer files can result in incompatibilities. That said, there is a fix for one issue ('Fixed (Pro): Was wrongly assuming files uploaded to the cloud via other utilities were folders') in the latest beta (not yet posted elsewhere as a release). This beta also supports Amazon S3 server-side encryption.

http://www.2brightsparks.com/assets/sof ... _Setup.exe

Do not uninstall / reinstall, or you'll lose your profiles & settings. Just install 'over the top'

[merak3d]

I just purchased SyncBackPro V6.0.12.0 and I have the same problem.

My folders at AmazonS3 are converted into zero-length files on my hard-drive (when are run backup in SyncBack)

Even if S3 doesn't support concept of folder, there must be some flag that will tell you "this is something like a folder" - because these "folders" work good for HTTP, so it can't be that different.

[Dave Wilkins]

Um - have you actually tried the beta (see my previous post)?

[Dave Wilkins]

Sorry - just figured out the dates. Try the beta anyway (link now points to a different beta than it did before, with some S3 folder workarounds)

[merak3d]

Thanks.

I will rather wait for official version (don't want to risk beta).