Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a requirement for a resilient MSMQ setup on VMWare ESX5. I am aware that we cannot allow the queue storage to be shared as it must be installed on physical disk mount, e.g. it cant be an CIFS or DFS Share. The following constraints apply: We don't use windows clustering We dont't rely on hot standbys

Is there a way I can replicate the queue storage to another platform so that it can assume MSMQ duties on failure of the primary platforms using any method including queue forwarding?

share|improve this question

I've heard of people using block level copying of the disk hosting the MSMQ storage folder to another location.
If you do replicate storage to another location then the destination machine has to have the same computer name to be able to load the messages.
Note that MSMQ can need to update several files for message processing so there is always the scenario where the copy is not completely in synch with the original when failure occurs.
If you don't want to invest in hardware solutions then you could design the application to be resiliant. For example, by sending messages to multiple destinations but processing only one message or intercepting processing of the duplicates.

share|improve this answer
Thanks John, useful to know if not the answer I wanted :-( – Paddy Carroll Nov 27 '12 at 9:39
Sometimes there isn't a powerful-but-free solution :-) – John Breakwell Nov 28 '12 at 0:07

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.