HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- SAN Migration
Operating System - Linux
1827487
Members
2194
Online
109965
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
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
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
10-23-2009 02:35 PM
10-23-2009 02:35 PM
SAN Migration
One of our client is migrating from DMX 850 to DMX 950. EMC is taking care of SAN migration. The SAN is presenting 10 LUNS namely emcpowera to emcpowerj and all of them are part of the same Volume Group namely VG01. We are using EMC power path. The OS versions is RHEL 3.6 and PowerPath version is 4.3.5 (build 2). Now EMC is saying when they migrate LUNS, it will change the Logical Device ID and probably the emc pseudo device name.
We will be doing vgexport before this migration start and then vgimport after the migration is complete.
I have a question here. Since the powerpath device names of the luns is changing, does that mess up the data integrity of the volume groups?
We will be doing vgexport before this migration start and then vgimport after the migration is complete.
I have a question here. Since the powerpath device names of the luns is changing, does that mess up the data integrity of the volume groups?
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-23-2009 04:15 PM
10-23-2009 04:15 PM
Re: SAN Migration
> Since the powerpath device names of the luns is changing, does that mess up the data integrity of the volume groups?
No. Linux LVM does not care about device names at all. When you run "vgscan" (or the system startup script runs it when the system is booting up), LVM checks every partition on every disk to find LVM PV signatures. This is how it finds the PVs. Then it looks at the VGIDs stored on each PV that is a member of a VG. If all the PVs making up a VG are available, the VG can be activated and used.
In a SAN migration situation, vgexport and vgimport are very important in HP-UX LVM, but Linux is different. (On HP-UX, vgexport produces a map file for the exported VG. On Linux, VG map files don't exist.)
On Linux, you should still unmount the filesystems and deactivate the VGs for the migration... but after the system can see the new LUNs (i.e. the new emcpower* devices) and the old ones are gone, just run "vgscan" and then activate the VG again.
Doing a vgexport/vgimport on Linux should not be harmful, but it isn't necessary either.
Note: the FC drivers and the associated infrastructure was somewhat immature in RHEL 3. It has been my experience that hot-adding new LUNs without booting the OS will not always be fully successful on RHEL 3.x. Sometimes new devices don't show up at all; sometimes only some of them do.
Rebooting the system or simply unloading & reloading the HBA driver has helped even the most stubborn driver to detect all FC configuration changes.
RedHat says only RHEL 5 and above will fully support hot-adding FC LUNs. I assume this means "with drivers included in the distribution": updated FC drivers from the HBA manufacturers might perform better.
http://kbase.redhat.com/faq/docs/DOC-3942
MK
No. Linux LVM does not care about device names at all. When you run "vgscan" (or the system startup script runs it when the system is booting up), LVM checks every partition on every disk to find LVM PV signatures. This is how it finds the PVs. Then it looks at the VGIDs stored on each PV that is a member of a VG. If all the PVs making up a VG are available, the VG can be activated and used.
In a SAN migration situation, vgexport and vgimport are very important in HP-UX LVM, but Linux is different. (On HP-UX, vgexport produces a map file for the exported VG. On Linux, VG map files don't exist.)
On Linux, you should still unmount the filesystems and deactivate the VGs for the migration... but after the system can see the new LUNs (i.e. the new emcpower* devices) and the old ones are gone, just run "vgscan" and then activate the VG again.
Doing a vgexport/vgimport on Linux should not be harmful, but it isn't necessary either.
Note: the FC drivers and the associated infrastructure was somewhat immature in RHEL 3. It has been my experience that hot-adding new LUNs without booting the OS will not always be fully successful on RHEL 3.x. Sometimes new devices don't show up at all; sometimes only some of them do.
Rebooting the system or simply unloading & reloading the HBA driver has helped even the most stubborn driver to detect all FC configuration changes.
RedHat says only RHEL 5 and above will fully support hot-adding FC LUNs. I assume this means "with drivers included in the distribution": updated FC drivers from the HBA manufacturers might perform better.
http://kbase.redhat.com/faq/docs/DOC-3942
MK
MK
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
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP