Ok here is our current setup - (note this is for 1 site)
1 development server backed by 1 database (different database than our prod database)
2 production servers backed by 1 database (I will explain this further below)


Production Server setup - Our internet web servers are located behind a F5 (load balancer). In the sitemanager I have 1 site setup with the default url being fdle.state.fl.us and with 2 default aliases (the urls to access our inet website from within - this is for the content staging purposes).

Since both servers use the same site, I only have 1 server enabled in the content staging area (our iweb1 box).

THE PROBLEM: When I run a task to sync a page to production it will appear on our iweb1 box, however, sometimes it will not appear on our second iweb box (iweb2). Is this normal? I am assuming that our second install is keeping a cached version, and that when I sync the data to our iweb1 box it refreshes the content for that install because it knows that data has changed.

POSSIBLE SOLUTION: Is it a good idea to have both iweb boxes in our content staging server list even though they are both tied to the same site in the same database?

If this is unclear let me know.

Thanks,
Jonathan Chauncey
Webmaster
Florida Department of Law Enforcement