I am not sure if I understand what you would like to do. It sounds like you want to have Unity go to the failover server and then reboot the primary server? If this is the case if you schedule a reboot of the primary then once the primary goes down your failover will kick in. Is this not what you want to have happen?
You just have to figure out an event that you can casue to happen at 5:00 AM that causes a failover to occur. You can also schedule a fallback to occur shortly after the failover of after a scheduled Unity restart on the primary server.
I have to put a disclaimer on this solution. I have never tried it myself but in looking through the documentation it seems like it will work but you might want to wait on the Unity Dev team or some Unity gurus to chime in before you put a lot of work into trying this out.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.