30.06.2020 · Adding an Amazon S3 object storage repository may fail with the following error: "Failed to load Amazon S3 Compatible configuration: Failed to establish connection to Amazon S3 Compatible endpoin
For an Amazon S3 bucket to be displayed in the Bucket list, it must be created within an AWS account to which the specified IAM role belongs. To learn how to ...
18.03.2021 · In Veeam one of our BCJ buckets has 0 Bytes, but in AWS S3 Console there are still 77 TB. This bucket was not used for offloading for a while so I belief that Veeam is right that there is nothing in the DB.
02.12.2021 · Important. If you have any S3 Lifecycle configuration associated with the selected Amazon S3 bucket, limit the scope of lifecycle rules applied to Amazon S3 objects in the bucket so that no rules are applied to backup files created by Veeam Backup for AWS.Otherwise, the files may be unexpectedly deleted or transitioned to another storage class, and Veeam Backup for …
29.07.2021 · - without fw rule for 151.139.128.14 Veeam is failing to add the bucket VeeamAgent connects to 151.139.128.14 port 80 - with fw rule access rule for 151.139.128.14 Veeam is able to connect to bucket For me it's quite clear that this IP is used somewhere in Veeam and I've no idea why Veeam is not connecting this IP when using AWS S3 buckets.
16.03.2019 · 1) selecting an existing bucket from some eu-* region: failed. 2) MightyNas, create one for me pleease in some eu-* region: failed. 3) played with custom urls: failed multiple times. 4) to confirm my issues, created a new bucket in the us-east-1 region: ReadyNas wins.
09.12.2021 · When adding S3 Object Storage to Veeam Console, Veeam displays the follow error: Failed to list S3 buckets: check if the specified account has required permissions REST API Error: 'S3 Error: The difference between the request time and the current time is too large.