I have the same question, but have run some experiments. If I copy the entire data/cache directory from host A to B, and the ESB installation path differs between A and B, then when I start SMX on B, an exception is thrown about the logging directory not existing, but SMX otherwise starts up. I have not fully tested everything on B to make sure SMX still works. What needs to be done to make this work seamlessly? Is there a compelling reason not to be moving the data cache around?
This is a topic where some "best practices" advice would be useful. For instance, is it better to set up a maven mirror on host B so that SMX can retrieve its artifacts there and build its own cache? In my case, there is Internet access from host A, but not host B. It seems possible to set up a local m2 repository on host B and mirror it from host A, but I expect that will take hours (days?) of "reading of the maven instructions" - followed by despair - followed by "reading the maven instructions again" to get this to work correctly. Alternately, is it better to simply check host A's m2 repo into version control and check it out on host B? What bear traps await the intrepid explorer of this idea?
In general, a FUSE/ServiceMix operational cookbook would be most welcome to those of us working to set the ESB up in a multi-environment, relatively locked-down universe.