Details
-
Task
-
Resolution: Done
-
Major
-
6.6.0
Description
From our local testing when using S3 compatible object stores it's not always immediately obvious why cbbackupmgr failed. Usually we will end up with a BucketNotExists/Put object failing but this doesn't obviously diagnose to a user why CBM isn't working with their compatible object store. We should add some documentation stating that some compatible object stores don't support the newer style of address and they must use the '--s3-force-path-style' flag.