- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Cluster Lock after vgexport
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
тАО07-29-2006 12:30 AM
тАО07-29-2006 12:30 AM
Now we need to do the vgexport on primary node & vgimport on secondary node (after doing vgexport) using map file in a two node cluster.
Since on secondary we r doing vgexport & vgimport,is it create any problem for Cluster Lock since same vg we r using as cluster lock vg or it will keep safe that Cluster Lock information?
thanks in advance.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-29-2006 12:03 PM
тАО07-29-2006 12:03 PM
Re: Cluster Lock after vgexport
is the first problem device changes?
If that is ur problem, you need change cluster ascii file at /etc/cmcluster
check about vg
FIRST_CLUSTER_LOCK_VG /dev/vg01
FIRST_CLUSTER_LOCK_PV /dev/dsk/c4t0d0
after that complie the cluster ascii file.
thanks
freddy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-29-2006 12:29 PM
тАО07-29-2006 12:29 PM
Solutionthere is no problem, it is normal steps that you are doing.
Cluster Lock information is already written on the specific disk.
You just wrer importing the primary Vg information to the sec system.
you know cluster lock information couldn't access with lvm mechanism.
Don't worry!!
you just check that the cluster lock dev's devivce name in cluster conf file is correct or not and then compile
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-29-2006 04:51 PM
тАО07-29-2006 04:51 PM
Re: Cluster Lock after vgexport
We have created some additional LV on Cluster aware VG of primary node so we are reflcting these LV on secondary node using vgexport & Vgimport.
regards.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-04-2006 08:30 PM
тАО08-04-2006 08:30 PM