Hope you're all doing well these days.
I work for a company in Spain and I would like to ask you about an issue I’m facing with archive offload to AWS S3 storage.
We are currently performing backups on a capacity tier (AWS S3) without issues but archive tier offload is failing. Here is what the proxy appliance log says:
02.12.2021 15:02:46] <43> Info [Ssh] Granados '617c81c8-8c61-404a-86c0-1f00ecf6ee18' connected to . Session: [SSH Session; Local: ; Remote: ]
[02.12.2021 15:02:46] <43> Info [Ssh] Connected to x.x.x.x while other addresses () are unavailable.
[02.12.2021 15:03:07] <43> Error Failed to connect by SSH. RetryCount: '0'. MaxRetryCount: '10'.
[02.12.2021 15:03:07] <43> Error Failed to login to host: 'x.x.x.x', port: 2500, elevation to root: 'no', autoSudo: no, use su if sudo fails: no, host name: , IPs: [x.x.x.x], AuthenticationData: [UserName: ubuntu, AuthTypes: [PublicKey]]. The destination would not be a correct SSH server. (System.Exception)
x.x.x.x is our Veeam B&R server located in our internal network.
- We currently have that Veeam B&R internal server selected as a gateway server in the S3 Glacier repository.
- I have already configured both TCP 22 and TCP 443 ports in the security group configured under "Proxy Appliance" on the S3 Glacier Veeam side.
- I’ve been able to verify that EC2 appliances are being created on AWS side.
- I have already configured a firewall rule to reach AWS.
What am I missing?
I've already opened a case with Veeam support. I'm waiting for their answer.
Thank you very much for your time.