It failed with the same message but different IP address: I’ve tried to uncheck the gateway box to see what happened. If this comment helps in resolving your issue, please let us know! As you can see from the log, the destination server is not a correct SSH server.Is your x.x.x.x (Veeam B&R) a Windows Server or Linux machine? If you are able to answer this correctly, you should be able to resolve this issue. You can see the errors in the log you appended are failed logins. You may have configured the SGs and external facing FW. I've already opened a case with Veeam support. I have already configured a firewall rule to reach AWS.I’ve been able to verify that EC2 appliances are being created on AWS side.
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.We currently have that Veeam B&R internal server selected as a gateway server in the S3 Glacier repository.X.x.x.x is our Veeam B&R server located in our internal network. The destination would not be a correct SSH server.
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:, AuthenticationData: ]. Info Connected to x.x.x.x while other addresses () are unavailable. Here is what the proxy appliance log says:
#Ssh proxy error archive
We are currently performing backups on a capacity tier (AWS S3) without issues but archive tier offload is failing. 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.
0 kommentar(er)
