Guild icon
S3Drive
Community / support / Bug? Automatic Upload to ALL Buckets/Storage Backends
Avatar
Hi 😉 When i set automatic media (Foto) backup in Android s3drive app, it will upload and show the folder in ALL my configured storage buckets. This is not intentionally 😄 Is there a fix for this?
Avatar
Hi @Floh, Do you mean that your Media Backup stores files not only in the bucket that you've initially configured, but instead your all configured buckets? In such case are files duplicated in each bucket or spread, like some files in bucket A, some files in bucket B etc.?
Avatar
Hi @Tom, my observations: As tested with only 3 files now: If i wait until the backup is finished and within this time stay only actively in the one selected bucket, in which i also want the media backup to go to, then everything works as intended. The files only go to the one bucket. But it seems like, if i switch between configured buckets while the upload is still going, it will start the backup als in the other buckets and ---> yes split up the files into the several buckets, depending on how long i stay actively in these buckets ;D Also: the backup is "Unstoppable" then 😄 meaning, i can a) cancel, b) do several actions that should stop it like disabling or turn on "only backup with wifi and/or when charged" --> it will continue unstoppably in every bucket, nomatter how many "disables" in configure 😄 For my current observation also: the "sync/copy/bi-sync..." feature works perfectly fine 😉 i will be using this for now 🙂 (edited)
2:08 PM
I use the default path btw.: /automatic upload/devicename Or should i configure something like bucketname:/path?
Avatar
Avatar
Floh
Hi @Tom, my observations: As tested with only 3 files now: If i wait until the backup is finished and within this time stay only actively in the one selected bucket, in which i also want the media backup to go to, then everything works as intended. The files only go to the one bucket. But it seems like, if i switch between configured buckets while the upload is still going, it will start the backup als in the other buckets and ---> yes split up the files into the several buckets, depending on how long i stay actively in these buckets ;D Also: the backup is "Unstoppable" then 😄 meaning, i can a) cancel, b) do several actions that should stop it like disabling or turn on "only backup with wifi and/or when charged" --> it will continue unstoppably in every bucket, nomatter how many "disables" in configure 😄 For my current observation also: the "sync/copy/bi-sync..." feature works perfectly fine 😉 i will be using this for now 🙂 (edited)
But it seems like, if i switch between configured buckets while the upload is still going, it will start the backup als in the other buckets and ---> yes split up the files into the several buckets
Oh dear, that's a bug indeed, thanks for spotting that. We'll be expediting fix, however given a current break we'll likely include it in release early January 2026.
Also: the backup is "Unstoppable" then 😄 meaning, i can a) cancel, b) do several actions that should stop it like disabling or turn on "only backup with wifi and/or when charged" --> it will continue unstoppably in every bucket, nomatter how many "disables" in configure 😄
We will check that one as well. Is backup "Stoppable" if you don't switch between buckets?
For my current observation also: the "sync/copy/bi-sync..." feature works perfectly fine i will be using this for now
It's using different logic, glad to hear it's working fine.
I use the default path btw.: /automatic upload/devicename Or should i configure something like bucketname:/path?
Bucket shouldn't be set. We probably need to rework Media Backup funcionality and actually allow cross-bucket configuration. User may want to split data intentionally or conversely they may want to have some redundancy and backup whole set across different destinations. We'll be adding this straight after providing a fix.
Avatar
Thanks guys, for your amazing work nonetheless! Have a great Christmas and take your time off 🙂
🎄 1
2:49 PM
Yes: when only in single bucket(ill call it "bug not activated" :D) then "cancel" immedtiatly stops transfers. Works! 🙂
Exported 7 message(s)
Timezone: UTC+0