Syncovery Support Forum

Thanks
I will try with 1 file and turn-on the logging as you suggested

Hi Tobais

Thanks for your fast response
I don't have "Files" -> "Files" -> "Verify copied files" checked but I have that other "Files" -> "More" -> "Check destination file (again)" checked
The seems to be default, I didn't changed any of those

What I find strange is that each file is large and ...

Hello

I'm trying to use Syncovery 10.15.10 in a docker with Ubuntu 24.04, on a Core i5, 4 CPU, 8GB, HDD (non SAT) to upload files from external, USB3 connected SSD drives to Amazon S3
For now I have 2 SSD connected on 2 different USB ports
2 jobs running, transferring 2 files per SSD each, so a ...

Hi Tobias

Thanks for jumping in quickly
- Files are from 3GB up to 89GB
- Version 10.11.9
- Running as a docker container in AWS fargate: 4 vCPU, 8 GB RAM and 200GB local storage

We have another profile running fine with files of similar size but from a Google Storage bucket to S3
This one is S3 ...

hello,

I'm trying to get 112 files copied from an AWS S3 bucket to another S3 bucket
All files fails with the below status:
Failing after exception: File too big for renaming, Retry Number: 0
Exception File too big for renaming at 000000000112C164.
Filename: S3://redacted-source-bucket-name ...

Hello

We have problems moving files from a FTPS server to our S3 bucket
Looks like the connection get closed after 10 minutes with the above error code

From the session log below, could you please confirm that the problem is on the FTPS server and not in our Syncovery configuration or access to ...

Hi Tobias

Sorry for the late feedback
Just to update you, we just have purchases a Professional license to complete our month of intensive testing and we are currently in production copying roughly 10TB a day from our customer's Google bucket to our AWS bucket.
We are running Syncovery on a FARGATE ...

Hello

We are evaluating running Syncovery running in AWS cloud. Currently we have a docker instance running in a 4vCPU / 4GB FARGATE for testing

Last night I started a test between a AWS S3 bucket and a GCS bucket with 220 files with a total of 4TB
The job is running 5 files in parallel
The ...

Thanks a lot Tobias

We will live with key credentials for now


Indeed when using the AWS SDK from inside an AWS infrastructure such as a Lambda, a docker task etc ... you assign a role to that instance which can have well defined access rights to the AWS services. In that case, you don't need to ...

Hello,

We have started evaluating running Syncovery as a Docker in AWS Elastic Container Service
On the AWS ECS task we have configured the role to have access to our buckets in order to avoid using AccessKey+SecretKey

So you know if this is supposed to work ?
Anyone had it to work ?

Thanks