- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- HP EVA, LVM, DR Configuration
Disk Enclosures
1753561
Members
5529
Online
108796
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
Discussions
Discussions
Forums
Discussions
back
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
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
09-02-2010 03:02 AM
09-02-2010 03:02 AM
HP EVA, LVM, DR Configuration
Hi,
I am trying to configure DR setup. I am setting up replication using HP EVA 4K. The operating system is AIX 6.1, the disks are configured under LVM. The problem faced is, After the replication is configured, on the DR node I need to run the following 2 commands to ensure LVM metadata is created on the DR node
1) chdev -l -a pv=yes
2)importvg -y -n
Both the commands fails on to update the ODM on the DR node because the disks under replication is not visible.I have tried Destination host access mode = Read only & None. It doesn't work in either case.
Can you please suggest any alternatives to get around this problem.
I am trying to configure DR setup. I am setting up replication using HP EVA 4K. The operating system is AIX 6.1, the disks are configured under LVM. The problem faced is, After the replication is configured, on the DR node I need to run the following 2 commands to ensure LVM metadata is created on the DR node
1) chdev -l
2)importvg -y
Both the commands fails on to update the ODM on the DR node because the disks under replication is not visible.I have tried Destination host access mode = Read only & None. It doesn't work in either case.
Can you please suggest any alternatives to get around this problem.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-02-2010 06:08 PM
09-02-2010 06:08 PM
Re: HP EVA, LVM, DR Configuration
If you have the extra space, I would create a mirrorclone of the replicated disk on the remote side, then fracture and present that mirrorclone to your desired system, after which you can do your LVM commands.
When you are done, unpresent and resynch the mirrorclones and you are ready for your next test. Note that once you resynch, you will have to issue your LVM commands all over again.
The underlying issue here is that the remote volume itself will not be writeable unless you do a failover, at which point you will be functionally replicating in the other direction, which will probably write over or corrupt your LVM info for your production systems and not be usable there once you fail back. I don't think you want that.
When you are done, unpresent and resynch the mirrorclones and you are ready for your next test. Note that once you resynch, you will have to issue your LVM commands all over again.
The underlying issue here is that the remote volume itself will not be writeable unless you do a failover, at which point you will be functionally replicating in the other direction, which will probably write over or corrupt your LVM info for your production systems and not be usable there once you fail back. I don't think you want that.
check out evamgt.wetpaint.com and evamgt google group
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP