Hello,   There is no manual sync rep.   I would start by thin provisioning the volume to provide more space for snapshot reserve.  I would also try to do that for other volumes to provide additional free space as well.   You have the initial 4+TB to sync, plus new writes coming in so additional snapshot reserve is needed.   What's the interconnect between the source and alternate pool?   Are they on the same switches?   If  that still fails I would suggest opening a support case.  Regards, 
We've decided to change our setup a bit. Previously we had 2 identical virtual hosting rigs in 2 different server rooms on campus. Both consisted of a PS4100 and 3 Dell servers in a failover cluster with a CSV stored on each SAN. Our main rig replicated VM's to the backup rig via Hyper-V replication. Because our needs have expanded, the resources on 3 host servers can no longer hold the load and have enough to spare for failover. So we have moved the 3 backup hosts to the main server room and will be adding them into the existing cluster, then replicating the SANs, hopefully using SyncRep. I have added the backup SAN into the group with the main SAN and created a separate storage pool, but when I try to enable SyncRep, we discovered our problem. The volume we have set up for the CSV is 6.5 TB and we only have enough extra space to set up a 6% snapshot reserve. I figured this would be ok since the minimum requirement for SyncRep is 5%, but when initial synchronization kicks off, it fills up the snapshot reserve and then throws an error saying the snapshot reserve is exhausted and starts the process over again. I'm not sure where to go from here, is it possible to do a manual initial synchronization, similar to traditional replication with the manual transfer utility? Here is a snip of what I'm seeing: [IMAGE]    Thanks in advance for any advice you might have for us. 
Setting Up SyncRep