- Community Home
- >
- Storage
- >
- HPE Nimble Storage
- >
- Array Performance and Data Protection
- >
- Re: Can you refresh a clone on the fly?
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-09-2015 04:44 PM
тАО02-09-2015 04:44 PM
This is sort of a newbie Nimble question, but here goesтАж
Our DBAs have a use case (for testing, say) where they make a snapshot of a DB volume, then make a clone of it, write some stuff to it, and then maybe their test is bad.
At that point they would like to be able (leaving everything mounted, connected, etc.) to tell the clone to revert back to the fresh state as if it were just made (abandon all changes) and then do the test again.
They donтАЩt do this all the time, but they do it.
As it is now, we have learned to make the clone, mount the clone, use the clone. But right now to refresh it, we have to unmount the clone, destroy the clone, make a new clone, mount the new clone, etc.
This would be something like the NetApp "volume restore snapshot" command, which they are used to using.
https://library.netapp.com/ecmdocs/ECMP1196817/html/volume/snapshot/restore.html
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-09-2015 09:37 PM
тАО02-09-2015 09:37 PM
SolutionGreg - I have only tried this in my lab but once you create the clone the first time the clone shows up as a volume. At that point you can make snapshots on the new clone volume, create a baseline snapshot before you do anything. If the DBA's want to "restore" back to baseline you have the snapshot.
Let me know if this works.
Happy Hunting!!! ;^)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-13-2015 08:48 AM
тАО02-13-2015 08:48 AM
Re: Can you refresh a clone on the fly?
Hi Greg,
I think there's a small mismatch in what you're trying to do on Nimble vs Netapp. The answer that Jason has provided is perfect, but will require a dismount and remount. I'm kind of assuming you were using the Netapp as a fileserver (NFS). If that's the case it's really easy from a storage point of view to do a snapshot restore. You just present the old pointers to your host. In a block-based storage device you have a virtual disk drive and we cannot change the contents of the drive without a remount.
The good news is that this process can be easily scripted. I'm sure your Nimble SE can help you with this should you require some pointers.
Thanks,
Arne