Checkshots or Snappoints?

Stop me if you’ve heard this one:

What’s the difference between a checkpoint and a snapshot?

Two Microsoft development groups.

Don’t get it?  Let me explain…

Hypervisors offer a means of saving the current state of a virtual machine and later returning to the saved state, if desired.  This is extremely useful when performing repetitive testing procedures, and also as a contingency plan in case an application upgrade fails.

VMware products use the term “snapshot” for this technology, and so does Hyper-V.  Surprisingly, even though SCVMM manages Hyper-V and ESX, it uses a different term for the exact same feature.  SCVMM calls them “checkpoints” and evidently this is confusing enough for Microsoft users that they have even called Microsoft support to ask about the differences.

Microsoft has two completely separate interfaces, with different capabilities and terminology, for just their hypervisor.  Can you seriously believe the rhetoric about Microsoft’s single pane of glass to manage your entire environment?

Administrators use the same exact VI Client whether they are connecting to an individual VMware ESX host or centrally managing many hosts with VirtualCenter.  No need for multiple terminology or interfaces.

(Visited 155 times, 1 visits today)
This entry was posted in Virtualizationism and tagged , , . Bookmark the permalink.

1 Response to Checkshots or Snappoints?

  1. Pingback: VCritical · Snapshots that shoot back

Comments are closed.