HYPER-V Production checkpoints

I already assume you’re aware and having Hyper-V experience knows the convenience / advantages of being able to take snapshots of VMs state before implementing a potentially disruptive change. But you also know the dangers of snapshotting for workloads such as domain controllers (DCs), Exchange Servers and SQL Servers: If you apply a checkpoint to a VM that’s replicating with others, it’s effectively sent back in time. That can cause AD corruption, password mismatches, missing group memberships and other data loss. But if you’re a developer then snapshot is a blessing for you to re-produce bugs…etc

With Server 10 (aka Server vNext) Microsoft is introducing new types of snapshots, called “Production Checkpoints”

Production_checkpoint

It uses the Volume Snapshot Service (VSS) from within the VM, because the VM is aware that it happened (it’s more like a backup operation), applying a checkpoint won’t disrupt workloads. Basically machine will boot in normal boot process be restoring the previous snapshot data. Enterprise level applications (SQL, Exchange) will be aware about this restore process. This is an option you can enable and if you still prefer previous snapshot method in your demo environment you can switch back. With production checkpoint enabled Microsoft has taken HYPER-V customers to whole new level.

Production_checkpoint_enable

You can find entire list of Server vNext improvements in here

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s