@TechOpsAK , as a best practice, try to avoid using SMB as a Veeam repository. Try to create a LUN on your Synology device and a iSCSI target. The performance and stability is better than using an SMB-share. We are using frequently synology-devices as a repository for our smaller customers.

@TechOpsAK, an extra if you are using an iSCSI LUN : you can use REFS 64K so performance and place-handling will be a lot better in case of synthetic fulls, merging, ...

@TechOpsAK , I see that there is a way of activating ntlmv1 in Synologies newest version 7.0 : Fix Synology DSM 7 SMB Clients Get Disconnected – Marius Hosting

Nico,

Ah, I hadn’t consider iSCSI, I’ll check into that, thanks for the suggestion.

Yeah, I saw that way of activating NTLMv1 but it’s insecure so would rather avoid it.

No problem @TechOpsAK , good luck with using iSCSI. If the answer is sufficient, can you close it by selecting best answer? Thx a lot!

Will do

This is probably the best advice as noted by Nico. Also the ReFS piece too.

I have a Synology DS920+ at home and use both iSCSI and NFS in VMware which works great for Veeam.  Similar with a Windows host too.

Best of luck.

Just agree with @Nico Losschaert and @Chris.Childerhose ! Present a block-device and format with your repo-server. 

BTW: such an constellation is not recommended for Hardened Repository in production, if you think about this.

Got it, thanks all for the confirmations.