GreenLake Administration
- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- Linux LVM and snapclones (EVA8000)
HPE EVA Storage
1849379
Members
5970
Online
104044
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
02-19-2007 12:08 PM
02-19-2007 12:08 PM
Linux LVM and snapclones (EVA8000)
Hi all,
I have a setup with 2 EVA8000, using Continuous Access to replicate the data and I'm taking snapclones in the second storage.
My main problem comes when presenting those clones to a recovery machine, since the metadata is sometimes inconsistent. If I run fsck on the volumes all works ok, but I can't automate that.
I'm using SSSU and the ADD MULTISNAP command to trigger all snapclones belonging to a single volumegroup at once. Even with that sometimes this metadata problem arises.
I'm now considering in suspending C.A., take the snapclones and then activate the replication again, but I'm not sure if that'll make any difference.
Any experience with a similar setup or any hints?
TIA and best regards.
Rob.
I have a setup with 2 EVA8000, using Continuous Access to replicate the data and I'm taking snapclones in the second storage.
My main problem comes when presenting those clones to a recovery machine, since the metadata is sometimes inconsistent. If I run fsck on the volumes all works ok, but I can't automate that.
I'm using SSSU and the ADD MULTISNAP command to trigger all snapclones belonging to a single volumegroup at once. Even with that sometimes this metadata problem arises.
I'm now considering in suspending C.A., take the snapclones and then activate the replication again, but I'm not sure if that'll make any difference.
Any experience with a similar setup or any hints?
TIA and best regards.
Rob.
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