Biztalk - how do I set up MSMQ load balancing and high availability? -
from understand, in order achieve msmq load-balancing, 1 must use technology such nlb.
and in order achieve msmq high-availability, 1 must cluster related biztalk host (and hence underlying servers have in cluster themselves).
yet, according microsoft documentation, nlb , failover clustering technologies not compatible. see link reference: http://support.microsoft.com/kb/235305
can please explain me how msmq load-balancing , high-availability can achieved?
thank in advance,
m
i've edited original answer because on reflection, think talking nonsense.
i don't believe possible achieve both load balancing , high availability in biztalk transactional scenario. have @ section "migration considerations moving msmq/t msmq adapter in biztalk 2006" on following site http://blogs.msdn.com/eldarm/
to summarise post, there couple of scenarios:
high availability (non-transactional)
you have msmq on more 1 biztalk server behind nlb
high availability (transactional)
for need have clustered msmq host, means can't sort of load balancing upon single queue.
one possible halfway solution create 2 msmq adapters, on different clustered hosts, each handling different queues. doesn't sound nice me though.
a key point understanding reasons why want transactional, clustered behaviour - need ordered delivery , ensure no duplicates.
in general wouldn't go trouble of load balancing msmq - biztalk load balanced once messages have reached messagebox database. while true see asymmetric load due queue processing happening on 1 machine, in overall context of biztalk environment should not significant.
again, worth remembering clustering msmq reasons beyond simple high availability:
msmq adapter receive handler - msmq not support remote transactional reads; local transactional reads supported. msmq adapter receive handler must run in host instance local clustered msmq service in order complete local transactional reads msmq adapter.
that following msdn page.
i hope edited answer helps - don't think after, maybe i'm wrong , you'll find workable solution nlb , transactional msmq, more think more seems 2 scenarios not compatible.
a final thought try posting similar question on server fault - few biztalk devs on stack overflow, including @ least 2 mvps, @ least work sort of question i'd passing on networking team.
Comments
Post a Comment