- Community Home
- >
- Storage
- >
- HPE Nimble Storage
- >
- Array Performance and Data Protection
- >
- Snapshot Writability and Zero-copy Clones
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 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
тАО02-06-2014 11:32 AM
тАО02-06-2014 11:32 AM
Maybe I missed the documentation somewhere but I need help understanding Snapshot Writability. So there are two modes, Writable and Non-writable.
I would assume a Writable snapshot would allow future writes to be store in the snapshot. Where as a non-writable snapshot is more of a point in time restore.
Assuming that, Zero-copy Clones would require a non-writable snapshot correct?
Could someone also clarify online, vs offline? That is just whether the host can see it when the volume is scanned correct?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-07-2014 01:47 AM
тАО02-07-2014 01:47 AM
SolutionHi Jesse,
Any Nimble snapshot that taken as part of a schedule is by design non-writable. This is because your schedule is part of your backup strategy with RPO/RTO assigned. If the snapshot was writable then it may be possible to change (or even delete) data thats in your backup - thus invalidating your RPO/RTO.
The only way to write to this snapshot is to clone the snap into a writeable child volume, meaning any delta changes made to that data will not ruin your backup RPO/RTO.
A manual snapshot (ie a snapshot manually initiated) CAN be writable, as that is a user-requested item and not part of a backup policy.
Note: a non-writable snapshot will cause problems if attempted to be mounted by Windows or VMware - so the best practice here is to always clone to a new volume should a snapshot need to be accessed.
When a snapshot is offline it means it is not visible and cannot be accessed by a host. When it's online it means it's visible and can be mounted by it's associated hosts as referenced in it's ACL.
Hope that's cleared it up, please let me know if you have any further questions.
twitter: @nick_dyer_
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-07-2014 07:38 AM
тАО02-07-2014 07:38 AM
Re: Snapshot Writability and Zero-copy Clones
Thank you, that validated my assumptions!