need guidance of AWS S3 as on-premise NAS backup media

[eek0212]

Hi R&D not sure if its correct to question here or "Fille Share and Object Storgae" but anyway

Firstly, ill explain our VBR environment.

We deployed VBR on on-premise and we backed up our workloads(hosted by vsphere hypervisor) VMs and
NAS to AWS S3(as a offsite backup repository)

So here is the questions

1. Current VBR version support converting backed up NAS data on S3 to EFS natively?
according to your recommended AWS IAM policy on your guide i can assume answer will be 'No'.
So sadly if thats 'No' do you have plan to GA this on feature on future release?
Anyway for now we implented this with following walkround make connectivity between on-premise VBR and pre-configured NAS with VPN.

2. With this sent-up we trying to 'copy' backed up data on S3 to pre-configured EFS but copying speed seems to be extremely low.
we tried with 100gb amount of data and it took more than 14 hours to complete copy job.
If its not normal intended speed is there any best practice to make it much 'optimal' speeds?

This is very important factor because we not just use AWS as off-site backup media but also DR site.

[HannesK]

Hello,
and welcome to the forums.

1) No, NAS restore copies files via SMB / NFS protocol or Veeam internal protocol if the server is a managed Linux / Windows machine. NFS 4.1 might work, but there is no native integration in EFS (also no plan in foreseeable future).

2) It's hard to guess on a forum, but my guess is that there is network traffic going back to on-prem because of gateway server / NAS proxy settings. 100GB in 14h is around 17MBit/s. That sounds too slow.

and pre-configured NAS with VPN.

with a network diagram and how which component is registered to Veeam, one could provide better answers. From a design perspective, you need to ensure that all affected Veeam components are hosted in AWS and network connectivity needs to be inside AWS.

Best regards
Hannes