Let's say we have two domains, production (PROD) and disaster recovery (DR). That means four servers, one App and one DB for each domain.
My summarized plan to set up in case there is a disaster
When Disaster happens
After Disaster is over
Does this sound right? Am I missing anything? I read the documentation which was talking about log files, but it wasn't clear, and I don't know why I'd need log files. (Installation and Deployment, Physical backup). It also said "By default folder of each HOPEX Environment", which I have no clue what that means, maybe the repository folder I have above?
For a truly tailored disaster recovery plan I would recommend working with a member of our Professional Services team but, after reviewing your steps from this post, I can say you have the general idea. Generically speaking, have a deployment that mirrors your current production in an alternate server farm (same Hopex version/ Same Megasite.ini settings/same customer jar/same custom "Mega_Usr" icons and objects pointing to an available license file) then be in the habit of performing nightly backups of your environment folder and associated Sql databases. If disaster strikes, you point users over to the DR server set after you've restored the latest copy of the Environment folder and Sql bakups (Updating the SystemDb and Data Repository/Repositories' "Sql Conneciton instance/user/password" to point to the DR Database server via Administration.exe) and you should be back up and running with minimal data loss (assuming you perform nightly backups, a maximum of 24 hours worth of work would be lost).
If you perform it in that way, you'll capture all the environment and installation specific data/settings. Any interface specific user settings (tab layouts and personalized settings) would have been stored in the Production Server's "%ProgramData%\MEGA\HOPEX V2R1\ClusterRoot\UserSettings" folder, so backing those up as well would allow you to restore them on the DR server too.
Hope That Helps!