Thanks!
HKStrongside
-Bill
--Jonathan
If you have multiple web servers and are using a load balancer, I
generally recommend that you set the CMS server up to publish to a
staging machine (an older, phased peice of hardware that is just
sitting around since so many company's seem to have them lately, and
then do exactly what everyone else has said and use something that
will monitor the folder and push the staging publish out to the web
servers, Cute FTP pro works really well for this and is only $69.00
(usd)
This actually serves two purposes. First, it cuts the publication time
down so that only one publishing job is involved and secondly, it
ensures uniformity throughout your live web servers.
I am currently running some benchmark tests relative to publishing and
should have that information in the next week or so.
Andrew Salik, Project Manager
RedDot Solutions, NA
On May 17, 6:02 am, "Rakefet Shohat, RepliWeb" <rake...@repliweb.com>
wrote:
I'm curious to hear about your benchmarks Andrew as mine also seem to
indicate that as projects get larger, UNC loses what speed advantage
it has over FTP due to the diff process performed when using FTP
publishing.
In the realm of free replication options you might look at robocopy
(part of Windows Resource Kit) or rsync as Bill mentioned (which can
be installed on Windows from what I hear).
Nick
> > replication. Works also extremely well on wide area networks.- Hide quoted text -
>
> - Show quoted text -