For your first question: you can build a scale-out repository with a capacity tier on AWS S3 storage. Then your backups can be moved or copied to the S3 storage.

https://helpcenter.veeam.com/docs/backup/vsphere/backup_repository_sobr.html?ver=110

Please keep in mind, you need a Universal License or a socket licebse in level enterprise or enterprise plus for this.

For your second question: you want to restore your on-premise VMs to AWS? Could you please explain your usecase in a little bit more detail?

here is second qus-

i want to restore my data s3 to ec2.

first i take my on-prem backup to s3 and restore to s3 to ec2

I don’t think that this is working…

But you can restore your on-premise backups to AWS directly.

Hi, @JMeixner 

Aws s3 to ec2 its working or not?

I don’t think it is working in the way you said. But you can - as said above - restore your VMS with your on-premise VBR Server to AWS ES2.

https://helpcenter.veeam.com/docs/backup/vsphere/restore_amazon.html?ver=110

This is correct as noted by Joe. Just follow the link above about restoring directly to EC2.

Yep, just also remember, it’s easy to restore the VMs to the cloud, the security & connectivity (both internally and external) is where you need to pre-plan for your recovery to ensure it works as you expect moving forwards.

For example, I can spin up a domain controller VM in AWS nice and easy, but without any connectivity between my offices and that AWS VM via any dedicated link or VPN, it doesn’t benefit me as I can’t auth via it.

hey when i restore s3 to ec2-

all steps done but they will not complte the job-

hey when i restore s3 to ec2-

 

all steps done but they will not complte the job-

 

 

Hi, can see Importing VM was only 27% done when it failed unexpectedly (don’t know why it ticked that stage). You’ll need to jump into the logs to find out what happened. Interestingly the disk uploaded in about 3.5mins but it took over 15 hours to import the VM. That’s clearly not right and makes me believe there was either a communication problem between VBR & AWS or a permissions issue. The logs will tell us more however.

I hope all the answers have helped you.

The logfiles are always a good to start looking for the root cause of a problem.

@JMeixner @MicoolPaul thanks 

i think we getting the better ans from you

Hi ,@MicoolPaul 

please help to get where is problem to restore to ec2.

@please find the log file-

Hi @Gopal Singh,

The error isn’t in that screenshot of the logs, that’s just info messages, search for “Warning” or “Error” within the logs and see what appears.