I logged into the environment and was checking some things out and we just recently broke a rather important milestone.

In our production environment one of our oldest clusters just broke 100,000 vMotions (or more accurately since they aren't at ESXi 4.1U1 yet, VMotions).

100k vMotion Summary This cluster has weathered the ups and downs of a functional vSphere cluster with hosts going into an out of Maintenance Mode, Hardware failures and general maintenance. This cluster we had over allocated on CPU for a couple months per our standard policy, though we got no real complaints about performance there. We have since updated that policy and I'm sure the number of vMotions has slowed down somewhat.

Just proof that vMotions/DRS & the entire vSphere solution is valid and solid. Here's to another 100k vMotions.