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.
Disaster Recovery on Mango ES
-
Hi there, I am trying to do so documentation on how to do a complete disaster recovery on a Mango ES. To be honest I got kind of stuck. So i'm just looking for some clarity and what exactly needs to be restored.
I did a experiment to see how quickly I could replace a current mango ES. I took a mango ES V3 out the box then dropped the configuration backups from the running system into the configuration upload page. that went smoothly. As soon as I tried to go the the data source page. I get routed to the server error page. I thought I would stop there and just get more clarity. On a few things.
- I try to keep my MangoESs are running the latest version. Will I need to make sure the out of the box ES is on the same version before I start restoring?
- Could you maybe just explain what is the best sequence of events. eg. update->upload SQL back ups->configuration backups-> file store upload - > network settings.
-
Hi CraigWeb,
As always, providing the error from your log file would be useful.
I suspect your intuition from (1) is correct. It sounds like you may be restoring from a backup created in a previous version in an up to date Mango. This sometimes will not work, as the database schema may have changed in that time. This can still be resolved though, since really all the restore tool is doing is running the SQL in the database backup into the running database.
To avoid the issue of restoring to an old database version, you should be able to run the restore on the command line to get the appropriate mah2.h2.db file, which can then be placed at Mango/databases/ and Mango can be started to upgrade that database appropriately to the version of Mango running.
To run a restore on the command line, I provided instructions in this thread: https://forum.infiniteautomation.com/topic/2748/how-to-restore-a-database-backup
If you had moved the entire Mango/databases/ directory from the old Mango into the new Mango/ directory, then you wouldn't have had to do a database or NoSQL restore.
Could you maybe just explain what is the best sequence of events. eg. update->upload SQL back ups->configuration backups-> file store upload - > network settings.
Restoring the database from the command line would give a newer version of Mango the chance to upgrade it. That's really the only critical sequencing (and that only applies if you're restoring a backup from an older Mango version). Not sure what else to be consider in answering that. Like, overrides, properties and whatnot.
-
Sorry about not providing the log file, I was more concerned about what needs to be done to restore a system from backup files than the error I was getting as it was a spare MangoES. Updating the MangoES Sorted it out. Any way I have come right and know what to do now. If you are interested in the log let me know and ill boot it up again and download it.
-
Seems like the issue I was having was not related to me doing the restore, but the problem that I reported on email.
