- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: vgimport with different vgname
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
тАО11-04-2009 03:44 AM
тАО11-04-2009 03:44 AM
I'm little bit confused over one of our current settings. We have two EVA storages and data replication (CA)is enabled between them.There are two hpux servers (2 node cluster) on PRIMARY site and a single server on DR site. There is one shared VG between cluster nodes. For this LUN, a DataReplication group is created in storage and the LUN in DR storage is presented to the hpux server in DR site.
I'm confused about the vgname used in PRI and DR site. In cluster nodes,same vgname is used, but in DR server the VG name is different (with different minor no.).
Suppose I create a vg and export it with a name vg01. On the other system I create a dir with a name /dev/vg02, then create the dev file with different minor no. I import map file using the command.
vgimport -s -v -m /etc/lvmconf/map.vg01 /dev/vg02
Is this work?
Here I would like to make this vg as cluster aware and add to the package control script.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-04-2009 05:03 AM
тАО11-04-2009 05:03 AM
SolutionThen it doesn't matter if it has a different VG name.
Your vgexport/import example would work, UNLESS the 3rd server IS a part of the cluster
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-04-2009 05:09 AM
тАО11-04-2009 05:09 AM
Re: vgimport with different vgname
It would work if vg01 belong to a package and on other node you are importing it as vg02, the only thing to keep in mind is you would be having different scripts on 2 boxes to handle package as your vg name is different.
BR,
Kapil+
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-04-2009 05:24 AM
тАО11-04-2009 05:24 AM
Re: vgimport with different vgname
Yes it will work. if it is a 2 node cluster..
Suraj
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-04-2009 05:55 AM
тАО11-04-2009 05:55 AM
Re: vgimport with different vgname
While it is nice to use the same name for the same volume group on all servers, it's more to keep the admin person sane. HPUX doesn't care.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-04-2009 09:58 AM
тАО11-04-2009 09:58 AM
Re: vgimport with different vgname
It will work for sure. /etc/lvmtab maintains the VG database and it is local to the server. It has nothing to do with the cluster. But having same VG names in cluster makes Sys_Admin job easier to troubleshoot.
A exported VG can be imported with a new name on the server.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-04-2009 10:12 PM
тАО11-04-2009 10:12 PM
Re: vgimport with different vgname
So I can go ahead with adding this vg to the package.Correct me if any mistake in the following steps.
-Add vgname to cluster configuration file(optional) and vg and lv info to pkg control script.
-Copy pkg cntl script to the other node.
#vgchange -c y vgxx
#vgchange -a n vgxx
#cmhaltpkg -v PKG
#cmrunpkg -v PKG
#cmmodpkg -e PKG
I think as I'm not making any changes in package conf file, I dont need to run cmcheckconf and amapplyconf cmds.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-06-2009 03:01 AM
тАО11-06-2009 03:01 AM
Re: vgimport with different vgname
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-06-2009 06:04 AM
тАО11-06-2009 06:04 AM
Re: vgimport with different vgname
If you make the changes before the package is halted, the control script will try to unmount the file systems and deactivate the VG even though this is not necessary.
I doubt it would cause any problems even if it tried except maybe logging a few warnings in the control script log file.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-09-2009 03:38 AM
тАО11-09-2009 03:38 AM