Secure Deployment Advice for Hyper-V with Synology NAS as a Veeam Repository

[hthonza]

Hi everyone,

I’d like to get some advice on how to securely deploy Veeam Backup in my Hyper-V setup. I have a single Hyper-V host with four NICs and a Synology NAS that I plan to use as the backup repository (i know its not ideal, but I have to work with what i got). My main goal is to design the environment in a way that’s secure, resilient, and still reasonably easy to manage.

I’m interested in best practices around:

Network isolation for backup traffic vs. management

Hardening both Hyper-V and the Synology NAS

Whether it’s better to use iSCSI or SMB for the repository in terms of security and reliability

Protecting backup data (e.g., immutability/WORM options on Synology, recommended Veeam settings, etc.)

If anyone has experience with similar setups, I’d appreciate any guidance or tips on how to build this in a secure and future-proof way.

Thanks!

[edh]

Hi,

In Small Company, Synology is ok. But i dont recomend in a real world. Dont kill me Synology FanBoys.

Anyway, you can use iSCSI volume to Veeam Server and the format to XFS with inmutability/deduplicacion or in Windows with REFS with Deduplication.

Is not a real inmutability due the layer of Synology that normally are not updated by customer and got bugs ..., and someone can connect to Synology and format, dump luns etc...

Dont create multiple iSCSI disk , you can do a big one 10TB / 20 TB Lun and will work better than small luns.

Dont use SMB , if you dont wanna get angry with your NAS. iSCSI performance is much better, also you can enable Jumbo Frames between your server and NAS ( Test it hard before production and check switches discard on ports).

Regards,
Manuel