Yes that should be possible too. Simply have mostly the same configuration on two Mango instances on the same network, with one asymmetry being one is publishing its heartbeat to the other (publish system uptime or a random number, whatever) and have a no-update detector on the received point, which has a script to start all the data sources, and then stop them once the first machine is updating that point again. As far as merging after the fact, the easiest way would be to do a NoSQL "Migrate Mango NoSQL Data into Mango" on the second Mango/databases/mangoTSDB and Mango/databases/mah2 after any outage. There may be some issue with the changeover, but that's likely to do with the specifics of your system (i.e. some other host on the network refused the first connection, etc).
Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.
