I am not familiar with the topic, but from what I've read here and there, doesn't the second part of the request sound like load balancing to some degree?
Other than that, keeping a staging and a live site in sync seems a bit complicated in some parts. On this topic we 've discussed a few of the challenges. The way I see it, the staging site cannot always be an exact replica of the live one. For example, you will probably need to turn caching off, remove a few plugins or add some others etc.
It seems to me that there are two different requests here. One is a mechanism where you keep your backup site in complete sync with the live and use it as a failover.
The other is an easy way to manually update the staging site with the content of the live whenever you need to.
In any case, the ability to run certain Webinoly commands like -clone across different servers would be really interesting.
In fact, there is one thought that kept buzzing me for some time but I thought that it would be too far-fetched and hyper-ambitious. What if we could use one server as the Control Panel of many other servers? I mean, being able to run all Webinoly commands from one server, or even from our local installation, and execute them on another Webinoly server. Some of the commands could even be run in a batch across different servers. For example, site -list -global would list all sites across all our connected servers. It would be like a command-line version of popular control panels like GridPane.