I am no specialist on AWS... but why are you using iSCSI on AWS? I consider iSCSI ultra-fragile and using the internet to reach it (VPN or not) is something that would never cross my mind.
Yes, the configuration with ISCSI looks somewhat strange, the recommended approach is to add AWS S3 as an object storage repository and subsequently use it as a backup target. Thanks!
Seve CH wrote: ↑Apr 14, 2025 7:19 am
I am no specialist on AWS... but why are you using iSCSI on AWS? I consider iSCSI ultra-fragile and using the internet to reach it (VPN or not) is something that would never cross my mind.
A decade ago we wanted to get away from a traditional NAS hardware. So AWS offers storage via iSCSI with NTFS/share permissions. Eventually we got a new hardware NAS and left the AWS as a backup feature.
Hi Trackstar
I would use S3 for the backup copy jobs instead of iSCSI. I suspect it will be cheaper, you may require less storage, and it will be more performant than iSCSI (very latency sensitive). You can also implement hardened repos to protect your data against ransomware.
Having a fully provisioned Veeam Server on the cloud instead of deploying it only on demand can be onerous, but it depends on your RTO requirements, etc.
Best regards.