Horizon Administrator has four options to recover instant clones: Restart Desktop, Reset Virtual Machine, Recover, and Remove. This made sense to me since the cp-replica and cp-parent objects are associated with a host, and because I used local datastores for this instant clone desktop pool, the instant clone objects that were hosted on it became orphaned as a result when the host went down. I was not surprised to see, upon closer inspection, that the orphaned objects were associated with the host that went down. VSphere Client also showed the desktop, as well as some of the cp-parent and cp-replicate objects, in an orphaned state. Moreover, Horizon Administrator showed error messages for many instant clone desktops. When the host came back up, ControlUp Console showed that many instant clone desktops were disconnected.
I’m a big fan of instant clones and use them on a regular basis, but they do drive me crazy on occasion.Īs a prime example, just the other day, I had one node of a two-host cluster-which was running a small instant clone environment-go down.
0 kommentar(er)
