This is just a theory; perhaps someone with more understanding of how Active Copy works can chime in.

My theory is that Active Copy is taking lots of bandwidth trying to either a) backup your files or b) figure out if any files need to be backed-up. This theory is based on my evaluation of several backup programs to us in conjunction with my own PP Pro.

First, I rejected Active Copy from the start because it is just a backup. Suppose I accidentally deleted a file and wanted it back? Too late; Active Copy already propagated the delete. Suppose I modified a file and want an older version? Too late; Active Copy already propagated the change. What I needed was something that kept old versions of files.

All the programs I evaluated (except one) would scan the local directories and compare the contents with the PP. The limited amount of time I used Active Copy, it did the same thing. If you make a change in a directory that is being monitored, the program re-scans the entire directory (and subdirectories) to make double-sure it knows what really needs to be backed-up. That scanning process can take some time.

Without knowing much more about your setup, this is my (really rough) theory as to what is happening: you have a couple high-level directories configured with Active Copy (say, "My Documents"). During gameplay (or just while using your computer) you modify something in "My Documents" so Active Copy has to re-scan *everything* in "My Documents" to see what has changed. That requires lots of network traffic with the PP to compare filenames and dates.

"Oh, that is crazy," you say. "Just checking the filename/date takes lots of traffic?" Yes, it can, if you have 10s of thousands of files, which I imagine 800G of data can amount to. Especially if one of your PP is across the internet.

Assuming Active Copy does behave in the way I've described, and this is your problem, then the solution is this: instead of backing-up a few high-level directories, break it down to several lower-level directories instead. In fact, anything that changes a lot should be backed-up separate from everything else.

For example, suppose you have 500G of .mp3 files in a "My Music" directory and another 200M of .doc files for your school/work projects. If you are backing up your "My Documents" directory (which contains "My Music" and "My Projects"), then one change in the school/work directory will cause *all* of your 500G of mp3 files to be scanned. Instead, have two separate backup points, one for music, and one for school/work.

The program I used (I've currently settled on Allway Sync) works well in this scenario. My "My Documents" directory has lots of stuff in it, so I split it out into several smaller backup jobs. That way when something changes in one of the smaller directories, the larger ones (like my music) are *not* re-scanned and backups go very quickly, even over the internet.

Hope this helps.