DISK SPACE FULL ERROR???

Replistor is referring to the volume where the Replistor data files are located, not to the actual specification. Check in the configuration where your data directory is configured to reside and move it to another location.

The REAL problem here is that your data directory shouldn't be filling up in the first place. This means that your 2Mb link isn't fast enough which is common if you are doing an initial sync. Is this the first initial sync of these specs that you are dealing with?

27 GB over 2Mb link should take 30-40 hours if the link is dedicated to just Replistor. However, if you are mirroring at the same time Replistor will also be keeping track of the changes and keeping them in the DataDir to send over when the sync is completed. Here are some things to look at:

First of all, the DataDirectory should be moved off of C unless C is the only place it can go. Moving the datadir requires a reboot.

Second, make sure you look at your process excludes. You can read up on it in the admin guide but when a backup or AntiVirus application is scanning or backing up files it will change the attributes when it accesses the file. It then changes the attributes back once it is done with the file.

Replistor will see that the file has changed and start the process of doing a CRC check against that file and the one on the other side, if it exists. This is something that can fill up the datadirectory in a hurry. With Replistor 6x these process excludes are supposed to be created automatically upon installation but they hardly ever are. Make sure you go into options on the process tab and add any backup, or antivirus type software processes in there. When that is done, Replistor will ignore i/o changes to the files from those specific processes.

Third, keep an eye on your kernel cache and kernel log count. When you attach to a server and have the site highlighted you will see the kernel cache and kernel log count over to the right. As soon as kernel cache fills up the log count will start to go up. The kernel log count is the number of transaction log files that are backed up in the DataDirectory and after 6.2 these files are 100 MB each. If you did an upgrade from an older version these files will be 1 MB and not 100 MB. While doing the first initial sync, you will want to keep a close eye on this and if it gets to the point where it starts to fill up then just disable the specs. After you disable the specs the log files will still continue to transfer over and Replistor should get caught up. Once the files are back down to 0 you can enable and sync the spec again. Then follow this procedure until the sync can complete. It will probably take several days.

If you have your process excludes in there and have finished an initial sync and the kernel log files are still going up, that probably means that there is a problem with your link or that it just isn't fast enough to keep up with the changes on your server.

Another option for the initial sync is to backup the data and ship a tape or external drive over then put it on the target server. This will save time with large files that don't change much. But if you are doing Exchange data or SQL or something that changes on a regular basis, this option won't help much.

Let me know if this helps.

Another option that I have had clients do in the past is they are able to talk their Provider into loaning them extra bandwidth just for the initial sync. Some have had to pay for it some haven't. Might be worth a try.

I've been lucky enough that most of my implementations over the past several years the link was at least 45 Mbs and often 100 Mbs.