Best Practice for Veeam 9.5 and Synology Synology RS3617xs+

[m.humphreys]

We have a customer running B&R 9.5
VM backup All VMs are processed in one job
VMs 50
Restore points 24 (includes 5 weekday incrementals and 1 weekend active full per week)
Incremental backups Approx 200GB each
Weekly full backup Approx 4 to 4.5TB each
Backup repository Synology "backup-nas" iSCSI LUN


Physical backup 5 physical servers each have their own backup job
Servers 5
Restore points 24 each (includes 5 weekday incrementals and 1 weekend active full per week)
Incremental backups The largest of the 5 is approx 100GB
Weekly full backup The largest of the 5 is approx 1.3TB
Backup repository Synology "backup-nas" iSCSI LUN

Backup Copy Jobs
VM backup copy All VMs are processed in one job
Restore points to keep 2
Weekly 4 (approx currently 4.5TB)
Monthly 12 (increasing from 2.6TB in Nov '18 to 4.4TB in Nov '19)
Backup repository Synology "backup2-nas" CIFS share

Physical backup copy All physical servers are processed in one job
Restore points to keep 2
Weekly 4 (approx 1.7TB each)
Monthly 12 (steadily decreasing in size as physical servers retired)
Backup repository Synology "backup2-nas" CIFS share

They are running out of space and need a solution to be able to migrate the current data to an unused Synology whilst the existing are upgraded with extra disks. the upgraded boxes will then be configured to run new backups.

I need to design a solution using best practices for Veeam and Synology
Would CIFS or iSCSI be best and also how should the storage be setup. the plan is to split the existing jobs into two separate backup/copy jobs
Thanks,
Mark

[Gostev]

CIFS is definitely not recommended in this case (you can see this warning directly in Veeam UI, when trying to register a CIFS repository).