- Community Home
- >
- Storage
- >
- HPE Nimble Storage
- >
- Array Performance and Data Protection
- >
- Nimble snapshot space usage
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
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
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-16-2020 06:30 AM
06-16-2020 06:30 AM
When a Nimble snapshot starts to consume space, where is the space deducted from? Is it deducted from the Volume or from the underlying Pool? Also, does the snapshot space count against Folder usage?
Thank you.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-16-2020 07:00 AM - edited 06-16-2020 07:01 AM
06-16-2020 07:00 AM - edited 06-16-2020 07:01 AM
Solution@marcusburrows : Hello Marcus,
Nimble Snapshots are ROW ( Redirect on Write) which means the Snapshot would lock the original volume and any modification/deletion of the data protected by the Snapshot would be redirected to a newer block in the Storage Pool.
I work for HPE
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-16-2020 07:42 AM
06-16-2020 07:42 AM
Re: Nimble snapshot space usage
Thank you. Sorry to ask another question, just to be clear. So does the active file system + snapshotted blocks = volume usage capacity? Or is it active file system = volume usage capacity and the snapshotted blocks are deducted from unused Storage Pool space? I hope that makes sense? Thank you again.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-16-2020 08:33 AM - edited 06-16-2020 08:39 AM
06-16-2020 08:33 AM - edited 06-16-2020 08:39 AM
Re: Nimble snapshot space usage
Hi Marcus,
Not sure what you mean by 'active file system'. A volume is created with a virtual size, say, 2 TiB. The 2 TiB is what the host OS sees for the volume size. As the host writes data, it's gathered within the Nimble's memory, deduped and compressed according to the volume's settings, and the result along with other volumes' data is written to the Pool. There are layers of pointers between the volume's logical block and what's written to the physical disks. As data changes and new data comes in, the process repeats and pointers are updated as required.
When a snapshot happens, the volume's pointers would be duplicated for the snapshot. From that point on, as data changes and new data comes in, it's gathered within the Nimble's memory, deduped and compressed according to the volume's settings, and the result along with other volumes' data is written to the Pool. And pointers are updated as required. (Whoa! Deja vu!)
Only what's written by the host OS to the volume is seen by the host. Regardless of the number of snapshots, the host can write the full 2 TiB to the volume. However, considering any deduplication and compression, that does not mean 2 TiB will need to be allocated to hold the volume's 2 TiB.
If you do a command line "vol --list" you will see the volume's (virtual) size, 2 TIB, and how much is currently used.
If you do a "vol --info name --verbose" you will also see the snapshot usage, which is not part of the volume usage.
Note: While I am an HPE Employee, all of my comments (whether noted or not), are my own and are not any official representation of the company
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-16-2020 09:26 AM
06-16-2020 09:26 AM
Re: Nimble snapshot space usage
Although I wasn't clear in my question, you have told me what I needed to know! Many thanks!
This is the bit I meant:
Only what's written by the host OS to the volume is seen by the host. Regardless of the number of snapshots, the host can write the full 2 TiB to the volume.
you will also see the snapshot usage, which is not part of the volume usage.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-28-2020 12:43 AM - edited 07-28-2020 12:46 AM
07-28-2020 12:43 AM - edited 07-28-2020 12:46 AM
Re: Nimble snapshot space usage
I'm an HPE employee.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]