GreenLake Administration
- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- Recovering to a snapclone
HPE EVA Storage
1848945
Members
7193
Online
104039
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Forums
Discussions
back
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
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
04-06-2005 08:30 PM
04-06-2005 08:30 PM
Recovering to a snapclone
We are doing some application upgrades and want to take a snapclone before we upgrade, then after the upgrade has completed OK, revert back to the pre-upgrade clone. We have an EVA3000 with HPUX11i. I have created the clones ok and can mount them etc.. however my question is there an easier way to revert to the clone disk than cp -R of the filesystems we want to recover? I can't just rename the mount points as this will change the hardware path and this will mess other things up. Any ideas... I know with the VA business copy you can do armcopy -r to do this but what about EVA?
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-06-2005 09:36 PM
04-06-2005 09:36 PM
Re: Recovering to a snapclone
A finished SnapClone is a new, independent virtual disk which has no relation to the original vdisk. There is no snap-back.
To ease the transition, you can change the LUN WWN of the clone vdisk to that of the original as long as the vdisk is unpresented. This should make sure that you don't get a new device as Secure Path does a persistent binding based on the LUN WWN. Make sure you never have two vdisks with the same LUN WWN.
To ease the transition, you can change the LUN WWN of the clone vdisk to that of the original as long as the vdisk is unpresented. This should make sure that you don't get a new device as Secure Path does a persistent binding based on the LUN WWN. Make sure you never have two vdisks with the same LUN WWN.
.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-06-2005 09:57 PM
04-06-2005 09:57 PM
Re: Recovering to a snapclone
Hi,
I like the WWN chane idea... how would that work then? - Unpresent both LUN's, swap WWN's, re-present LUN's... job done?
Can you change the WWN using the command view interface or via spmgr?
I like the WWN chane idea... how would that work then? - Unpresent both LUN's, swap WWN's, re-present LUN's... job done?
Can you change the WWN using the command view interface or via spmgr?
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2026 Hewlett Packard Enterprise Development LP