Large Fileserver Backup Issues

[jdoster]

We have migrated our old File server (Physical) to a new WS 2008R2 (Virtual) and moved everything over. It's a really large server with 5.8TB of storage space. What I am having an issue with is getting the initial back up to finish in a decent time frame. Any Suggestion on how to handle a large VM To backup across WAN to DR site? I have the rest of my environment working on Veeam for the past 8 months.

Job Details
Incremental with Synthetic Fulls on Saturdays.
Enable inline data Deduplication-Checked
Compression- Optimal
Storage Optimize for- WAN
Enable VMware Tools Quiescence- UNCHECKED
Change block tracking- Both Checked


File server
VM Size- 5.7 TB (3.4 TB Used)
Seperate VMDK
LUNS are stored on a EqualLogic isci SAN

Environment
Main Site
5 Host ESXi 5.0
Vcenter 5.0
100 MB pipe to the DR Site
Combination of Fiber SAN (Compellent), EqualLogic iSCSI SAN, and HP SAN
2 VEEAM Proxy Servers (Virtual)

DR Site
1 ESXi Host 5.0
Compellent Fiber Channel SAN that all Veeam Repositories Reside
Veeam B&R Console (Virtual)
4 Backup Proxy that Repositories are spread across. (Virtual)

Thanks!

[foggy]

Hello, Jeremiah!

Have you considered using initial seeding for this file server? You can backup locally first, then move the backup files to the DR site and edit the job to map it to the existing backup. In that case, only incremental changes will be transferred during the next job run over the slow link. You can find step-by-step instructions here.

[jdoster]

Trying that now, it's still only processing at 4 MB/s. Showing bottleneck as target.

[foggy]

What are the full bottleneck stats numbers for this job? What repository type do you use? What about other VMs being backed up to the same storage - are they experiencing the same issue?