| Deploying Now SMS in a highly available configuration |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through October 19, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| Frank Danielson New member Username: Fdanielson Post Number: 6 Registered: 02-2006 |
We've been running the Now SMS/MMS gateway for a while and have always worried about exposure to risk from having one system providing an important function. When we upgraded to Now2006 and performed the machine specific licensing procedure it made things more difficult because we can not have a hot standby system. Does anyone have any specific reccomendations for running Now in a more robust configuration? I'm open to looking at Windows clustering, running the Now system as a virtual machine under somthing like VMWare, running two Now systems behind a load balancer, or anything else that works in a production environment. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7166 Registered: 10-2002 |
Hi Frank, There are licensing configurations for hot standbys. I try to stay out of the sales side of things ... so I honestly don't know what the policy is. But if you talk to Lisa or Keith, they should be able to help you get that sorted. We've done configurations in the past using Marathon Technologies fault tolerant product. Basically you have 2 systems that are completely mirrored. It's quite impressive ... you pull the plug on one system and the other just keeps running along as if nothing happened. It's overkill for a lot of environments, but it's quite impressive. We've also done MMSC configurations behind load balancers, where you can either configure both systems to point to the same "MMSCDATA" structure on a shared volume ... or each server can have its own with message senders directed randomly by the load balancer, and message retrievers going back to a specific server (the latter is done more frequently when overall server load is a concern). It is also possible to have two or more NowSMS servers use the same outbound message queue directory on a shared volume. However, we do not support shared volumes for inbound messages directed to specific user accounts. So when you talk about load balancing and multiple active servers, it does get a little confusing, as it varies based upon what functions of NowSMS you are using. -bn | |||
