Luminis IV Parallel Deployment Questions

We are in the process of designing a parrallel deployment for our luminis iv production system. Currently we are using a 3 server architecture with email hosted externally. At the moment we are live with with Luminis IV, and are looking at leveraging our Big IP load balancer. What considerations and or design decisions have other institutions looked at? Any info is appreciated.

Cheers!

0
No votes yet

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

PD suggestions

Either there are not a big list of gotchas, or we haven't been running PD long enough to develop a big list of design concerns, but I do have two to share:

1. Make sure that your load balancer works with PD before buying any new hardware. Our ended up not working with Luminis, but it did load balance self service just fine. We had to buy a new load balancer, and by the time that was accomplished, we could have gotten better production servers:)

2. Try to make all your luminis servers identical as much as possible. Same directory structures, same config locations, same variable names, etc.. for two reasons: 1) I've noticed some annoying problems with patches complaining about say, /mnt/calendar being different than /mnt/web (CP_ROOT) conflicts. Also, it makes scripting changes to servers easier. Like right now, I'm playing with subversion as a means of pushing a change done on a single development server to multiple production front-end web servers. It is easier if all the file paths are the same.