S3 backup error: Bucket name is not available (not empty)

[mattgroves]

I noticed last night that my scheduled backup to S3 hadn't run for several months, no explanation in the logging, so I simply started it manually and it completed successfully this morning.

I then opened the config settings for the job and altered the schedule from monthly to weekly (so see if it started as scheduled without having to wait 3 weeks) and updated the 'concurrent processing files' to 10 (from 5) as I now have more upstream bandwidth from my ISP.

The job now errors with:

[S3Plus] Backup job [%jobname%] failed because the bucket name is not available (not empty). Please select another one.

I haven't altered the cloud account or bucket/folder settings - so it ought to do an incremental backup to the same destination. I don't understand why I am getting error only a day after a successful backup with only minor settings changes...


Any ideas?


System info:

S3 Plus app version: 1.2.420 (2017/07/07)
TS412 running 4.3.3.0378 Build 20171117 (4 x WD 3TB in RAID5)

[critchlg]

Seems like the S3 app thinks this is a new job. What happens when you put the concurrent jobs back to 5?


Sent from my iPad using Tapatalk