- Community Home
- >
- Storage
- >
- Around the Storage Block
- >
- Advantages of VVol Storage Snapshots, and a word o...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Receive email notifications
- Printer Friendly Page
- Report Inappropriate Content
Advantages of VVol Storage Snapshots, and a word of caution about Memory Snapshots
One of the many benefits of VVols is that snapshots of a VVol VM are offloaded to the storage array. With HPE Nimble Storage arrays, you can create a large number of space-efficient snapshots and retain them for longer.
Unlike VM Snapshots on a VMFS datastore, VVol snapshots on Nimble do not have any impact on disk IO performance. No penalty on reads for a VM with any number of snapshots. And most importantly, no penalty for deleting the VM snapshots. The deletions are instantaneous. There is no snapshot consolidation process that needs to read the data from redo logs and write them to base disks!
You can also snapshot a VVol VM with the option "Snapshot the virtual machine's memory" selected. Such VMs can be restored to the powered on state it was in when the snapshot was taken. Without this option, the VMs would be restored to a powered off state.
This is great, but โฆ
"Snapshot the virtual machine's memoryโ does not use storage array snapshots. It uses a new VVol disk, and counts against the total number of VVol volumes supported by the storage array!
Letโs break this down a little more:
- When you create a VVol VM, a Nimble volume is created for every VMDK (Data VVol). And one Nimble volume is created to hold the configuration of VM (Config VVol). When the VM is powered on, a Swap VVol is also created.
- When you create a snapshot of a VVol VM, a Nimble volume snapshot is created for every data VVol.
- And if you chose to snapshot the VM memory?
- A new Nimble volume is created to hold the VM memory contents.
- The size of this volume is the size of the VMโs Memory. So, a VM with 16 GB RAM would result in a 16 GB Nimble volume to be created.
The VVol volumes are shown in the Nimble management UI, with the volume created for memory snapshots highlighted.
The Nimble volume created for holding the memory contents is Thick Provisioned, and typically all of the data in a RAM is in use, so entire contents are written to the storage volume.
Storage compression reduces the actual storage capacity used to a good extent, but YMMV. Average compression observed from InfoSight for VM memory VVols is around 4X. If multiple such VM snapshots are created, a new volume is created for each memory snapshot.In conclusion, for VVol VM deployments:
- Each VM snapshot with memory results in a Nimble volume, thereby reducing the number of VVol VMs you can create on the storage array
- The volume size is the same as the VM RAM, the volume is thick provisioned and typically uses quite a bit of storage space even after compression
- Snapshots take quite a bit of time to be created, although this is not specific to VVols
It is advisable not to select "Snapshot the virtual machine's memoryโ as a default option for all VM snapshots. Use them sparingly when absolutely necessary.
- Back to Blog
- Newer Article
- Older Article
- haniff on: High-performance, low-latency networks for edge an...
- StorageExperts on: Configure vSphere Metro Storage Cluster with HPE N...
- haniff on: Need for speed and efficiency from high performanc...
- haniff on: Efficient networking for HPEโs Alletra cloud-nativ...
- CalvinZito on: Whatโs new in HPE SimpliVity 4.1.0
- MichaelMattsson on: HPE CSI Driver for Kubernetes v1.4.0 with expanded...
- StorageExperts on: HPE Nimble Storage dHCI Intelligent 1-Click Update...
- ORielly on: Power Loss at the Edge? Protect Your Data with New...
- viraj h on: HPE Primera Storage celebrates one year!
- Ron Dharma on: Introducing Language Bindings for HPE SimpliVity R...