VeeamON 2024 - Use Code "COMMUNITY10" for 10% Off!
Hi @MicoolPaul , thanks for getting back to me.It’s not firewall or stange IP, it’s purely the AMI that’s chosen by Veeam for the proxy instance. To test, I set the termination protection on the proxy instance, so Veeam couldn’t tear it down after trying 10 times, and after a few minutes I was actually able to ssh into the instance. So it’s really just that, takes some time for the ssh service to start.In the logs I see:Getting x86x64 images by name: 'ubuntu-bionic-18.04-amd64-server-20180522-dotnetcore-2018.07.11';Getting x86x64 images by name: '*ubuntu-bionic-18.04-amd64-server*';Getting x86x64 images by name: '*ubuntu*';Chosen AMI for AWS proxy: 'ami-00e62671e21dc4aad' The chosen AMI is this one: aws-parallelcluster-3.1.4-ubuntu-2004-lts-hvm-x86_64-202205121006 2022-05-12T10-09-32.380Z, and I wonder why that is. Can that be changed somehow? I tested running the exact same AMI in the same subnet, security group etc and it really takes 5 minutes until I can ssh.Anyway, this AMI seems
Ok, this seems to work better now, no idea why but I’m rarely getting timeouts now. Everything is exactly the same… Maybe was just AWS having a bad day.
I still think the queries to select the ubuntu AMI should be changed, they’re not gonna return anything ever:Getting x86x64 images by name: 'ubuntu-bionic-18.04-amd64-server-20180522-dotnetcore-2018.07.11';Getting x86x64 images by name: '*ubuntu-bionic-18.04-amd64-server*';Getting x86x64 images by name: '*ubuntu*';There’s just nothing for the first 2 queries, so it will always fall back to ANY image with ubuntu in the name.
Hi @Iams3le ,Thanks for the link. I’ve seen that page before, but it seems to be talking about different use cases, and a different product.Anyway, I made sure all mentioned permissions are in place, and I’m still seeing the same error.Thoughts?
Ok, I can shed some light on this now.The way the process works is:- Veeam creates a proxy instance- attaches an EBS volume to the proxy instance- reads backup block data from S3 and writes it to the EBS volume- takes a snapshot of the EBS volume- imports the EBS volume into an AMI, converting from vmdk format.- launch the AMI as new EC2 instance with all the recovered backup data.The problem in my particular case is in the second to last step. That’s done via a call to AWS CLI: import-image, and that fails if the EBS snapshot is encrypted.Unfortunately, in my case that’s a default setting I can’t change, all EBS volumes are encrypted by default in my company. So the error lies actually in AWS, not in Veeam.
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.