The Basics: Snapshots

In my IT career at work I have never had shared storage that didn’t have snapshots integrated. They were considered fundamental to me if I was going to put all my eggs into one basket. Performance, ease of use and reliability were all deciding factors on selecting a solution. There are lots of different solutions on the market today and some are really good but it’s hard to get all three deciding factors to line up if snapshots were not integrated from the ground up.


It’s great to have a feature but if the performance impacts of using it are such that it impacts the environment then what’s the point? Snapshots are used for a point in time copy of data so that you can roll back incase of corruption, file recovery or part of a larger business continuity plan that makes use of replication.

Snapshots should be able to be used on running applications without causing any performance impacts. Nutanix being per VM defiantly helps in this regard. If you have a LUN with 100 server workloads and take a hardware-based snapshot then you are taking a snapshot of every one of those workloads. Cache and metadata resources are wasted, as all the workloads now have to be tracked and maintained due to the snapshot process.

More and snapshots under stress video here.

Nutanix will be releasing a Tech Note on Snapshots as well in the next week or two.

Speak Your Mind