A little context, just in case it helps. VM1 is a Veeam Backup and Replication server that's responsible for backing up all the VMs in my environment. The disk target for the backup files is a Synology DS1511+. The Synology has two volumes of 10 TB each and both are presented as iSCSI targets to HOST4 (where VM1 lives). VBR runs on VM1 and is able to write to the Synology.
I have a requirement to go to tape, so I have a physical server running Backup Exec 2010R3. This is a physical Windows Server 2008 R2 that uses the iSCSI Initiator to access the data on the Synology so that it can write the backup files to tape once a month (this is read-only access since it never should change the source files).
I replicate the VBR backup files to a matching Synology at our DR site via rsync. The problem is that when I run my full backups, the VBR jobs and the rsync replication end up running at the same time and crush my VBR server (VM1). My goal was to move the replication load to a second VM (VM2) so that VM1 would handle the backups and VM2 would handle the replication.
Because there's a physical server in this equation, I don't think I can do what Mark suggested, but please correct me if I'm wrong.