Skip to main content
Solved

AWS Tape Backup Restore to AWS ec2

  • March 23, 2022
  • 8 comments
  • 206 views
chandrasinghe

Hi, 

I am new to Veeam, I am trying to restore my already backedup  VM to AWS ec2. I did following test run

 

TestVM  backup >  Tape BackupAWS tape Gateway > Sucesss 

 

Restore from backup > VM Restore > Restore to EC2 > Failed

Restore job failed Error: File does not exist. File: []. Failed to open storage for read access. Storage: []. Cannot open a local backup for the file level restore. Storages: [AWS-TEST-RUND2022-03-23T101007_BE57.vbk]. Agent failed to process method {Mount.QueryOsInfo}.

Best answer by JMeixner

I assume this is a virtual tape library. You have to copy the files from the tape repository to a disk repository in Veeam before restoring the data.

This is a restriction with Veeam. But for file-level-restore the VBK file has to be mounted and examined, this is not possible from a tape repo.

8 comments

MicoolPaul
Forum|alt.badge.img+23
  • MicoolPaul
  • 2425 comments
  • March 23, 2022

Hi @chandrasinghe, based on the detail provided is this an AWS VTL you’re trying to recover from, to AWS EC2?

Michael Paul - Opinions are my own and do not necessarily reflect the opinion of Veeam | https://micoolpaul.com | Mastodon: @micoolpaul@masto.nu | Bluesky: @micoolpaul.com
JMeixner
Forum|alt.badge.img+16
  • JMeixner
  • On the path to Greatness
  • 2687 comments
  • Answer
  • March 23, 2022

I assume this is a virtual tape library. You have to copy the files from the tape repository to a disk repository in Veeam before restoring the data.

This is a restriction with Veeam. But for file-level-restore the VBK file has to be mounted and examined, this is not possible from a tape repo.

Jochen (Joe) Meixner | Veeam Vanguard 2024 | Veeam Legend 2021 - 2024 | Veeam Certified Architect (VMCA) | X: @JoMeix | BlueSky: @jmeixner.bsky.social
MicoolPaul
Forum|alt.badge.img+23
  • MicoolPaul
  • 2425 comments
  • March 23, 2022

@JMeixner is right here, my question around the VTL was focused on giving you a better way forward if you’re using this, you could move to object storage to overcome tape limitations.

Michael Paul - Opinions are my own and do not necessarily reflect the opinion of Veeam | https://micoolpaul.com | Mastodon: @micoolpaul@masto.nu | Bluesky: @micoolpaul.com
JMeixner
Forum|alt.badge.img+16
  • JMeixner
  • On the path to Greatness
  • 2687 comments
  • March 23, 2022

@JMeixner is right here, my question around the VTL was focused on giving you a better way forward if you’re using this, you could move to object storage to overcome tape limitations.

I am a fan of physical tape, but in this case when using AWS I would use object storage, too.

Jochen (Joe) Meixner | Veeam Vanguard 2024 | Veeam Legend 2021 - 2024 | Veeam Certified Architect (VMCA) | X: @JoMeix | BlueSky: @jmeixner.bsky.social
chandrasinghe
  • chandrasinghe
  • Author
  • Comes here often
  • 7 comments
  • March 24, 2022

Sorry for late response

Seems Tape backup wont help immeadiate disaster recovery

Veeam offer D1(VM virtual disk) to D2 (Veeam local backup) to T (AWS Virtual Tape)

If I need recover  I shoud reverse  it. ok 👌 

AWS Tape to D1 to D2

Can I use this D1 as AWS S3 or EBS via Veeam.

 

JMeixner
Forum|alt.badge.img+16
  • JMeixner
  • On the path to Greatness
  • 2687 comments
  • March 24, 2022

I would use a scale-out repository with object storage as capacity tier….

Jochen (Joe) Meixner | Veeam Vanguard 2024 | Veeam Legend 2021 - 2024 | Veeam Certified Architect (VMCA) | X: @JoMeix | BlueSky: @jmeixner.bsky.social
chandrasinghe
  • chandrasinghe
  • Author
  • Comes here often
  • 7 comments
  • March 25, 2022

Can we copy backup jobs to AWS S3 bucket on by One. Could some one help me to find proper documentation

chandrasinghe
  • chandrasinghe
  • Author
  • Comes here often
  • 7 comments
  • March 26, 2022

Hi Community,

Thank you all for guide me.  😀 I have tested backup offload to AWS S3 and Restore to Ec2. Then I got this error while restoring Ubuntu VM.

 


Terms & ConditionsAccessibility statement