yes agree. i will contact their support team. it's weird how it works in dry run and even lsd work but then copy tries to hit aws again. thanks for your help today.
wasabi tech support is very good.
please update this post when you get a reply from them.
ok as i was composing a note to them i checked permissions for the new user i was using as i had made it both read-only and write only, but changing it to full access allowed me to write. i guess that was just my misunderstanding of how the access levels worked. what are you using for your user
i have a local backup server.
i use wasabi to keep a copy of recent veeam and other backups.
on daily basis
- i upload latest backups of veeam and some other stuff.
- move stuff one month old to aws s3 deep glacier
- prune the corresponding stuff in wasabi.
for that i use rclone copy --immutable from local to wasabi
ListBucket
GetObject
PutObject
PutObjectACL
ListAllMyBuckets
and i manually prune using cloudberry explorer and/or s3browser
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.