BE 20.5 - Cloud Storage unavailable after update
Hello, Recently we have updated Backup Exec to 20.5 due to a requirement to update .net framework to 4.8. However since the update our S3-Compatible cloud storage device has been 'Offline'. At first we removed the cloud storage device and then re configured it, this was still showing as offline after all services were restarted. The server was rebooted, but still unavailable. We have confirmed the CloudInstance is available by running a Test-NetConnection on port 443 to the cloud storage server. The cloud storage instance SSL Mode is set to full so no backup data should be shipped on port 80. We are also able to access the buckets from the backup server via an S3 Client. For good measure we have removed and re-added the cloud instance, but still the same issue. When configuring the cloud storage device in backup exec it see's all the buckets available in the S3-compatible storage. Windows EventVwr confirms that the cloud storage first became unavailable during the update for 20.5 as show in the attached images. Has anyone else experienced this issue or can provide any advice? I'm rather hesitant to reinstall BE and the evidence is clear this is not a network related issue. Thanks All.Backup Exec 16.2 S3 Compatible Configuration
Hi all, i'm trying to configure Backup Exec 16.2 with the S3 Compatible IBM Cloud OBject Storage (https://ibm-public-cos.github.io/crs-docs/api-reference) and it authenticates, but it shows an error of no Storage found. My gues is that this is related toLocationConstraint which differs from AWS S3 implementation. Was anyone able to successfuly connect Backup Exect 16.2 with any S3 Compatible Cloud Object Storage? Thanks