- eWEEK Labs Walk-Through: EverRun HA
- eWEEK Labs Walk-Through: EverRun HA – All Systems Go
- eWEEK Labs Walk-Through: EverRun HA – Unplugged
- eWEEK Labs Walk-Through: EverRun HA – Unplugged Two
- eWEEK Labs Walk-Through: EverRun HA – Unplugged Three
- eWEEK Labs Walk-Through: EverRun HA – Unplugged Four
- eWEEK Labs Walk-Through: EverRun HA – Unplugged Five
- eWEEK Labs Walk-Through: EverRun HA – Unplugged Six
eWEEK Labs Walk-Through: EverRun HA

We accessed and controlled our EverRun HA virtual server using Windows Remote Desktop.
eWEEK Labs Walk-Through: EverRun HA – All Systems Go

EverRun HAs management console shows all green–our CoServer pair is up and running normally.
eWEEK Labs Walk-Through: EverRun HA – Unplugged

When we pulled the plug on our primary CoServer, the management console registered the failure right away, both in the main dialog and in the task bar.
eWEEK Labs Walk-Through: EverRun HA – Unplugged Two

Our downed primary CoServer shows up in the management console as dead, and the hosting of the virtual server has shifted to the secondary CoServer.
eWEEK Labs Walk-Through: EverRun HA – Unplugged Three

After powering our primary CoServer back on, we brought it online again from the management console.
eWEEK Labs Walk-Through: EverRun HA – Unplugged Four

Bringing our primary CoServer back online triggered a disk syncing operation from the secondary CoServer back to the primary.
eWEEK Labs Walk-Through: EverRun HA – Unplugged Five

We watched the progress of the disk sync through the EverRun HA management console.
eWEEK Labs Walk-Through: EverRun HA – Unplugged Six

With the disk sync complete, we were back in the green, with the primary CoServer again hosting our virtual server.


