- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Lock Disk and Service Guard
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
Forums
Discussions
Discussions
Discussions
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
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-17-2007 02:44 AM
07-17-2007 02:44 AM
I have a 2 node cluster. I have created a seperate vg with a 1gb disk as the lock disk.
The cluster is working fine. I can fail teh packages and it works fine.
But when i did a make_tape_recovery I got the following message. Any update on this message.
Backing Up Volume Group /dev/vgsavlock
* /usr/sbin/vgcfgbackup /dev/vgsavlock
vgcfgbackup: Warning: couldn't query physical volume "/dev/dsk/c19t1d1":
The specified path does not correspond to physical volume attached to this volume group
vgcfgbackup: Warning: couldn't query all of the physical volumes.
vgcfgbackup: Volume group not activated
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-17-2007 03:00 AM
07-17-2007 03:00 AM
Solutiondid you do a vgcfgbackup of this vg one both nodes AFTER marking it as a cluster lock vg?
does the lvmtab file on each node reflect the correct physical devcies?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-17-2007 03:05 AM
07-17-2007 03:05 AM
Re: Lock Disk and Service Guard
strings /etc/lvmtab
Try manually activating the volume group and see if you can.
vgchange -a y vgsavlock
echo $?
If it fails post the error message back here and the repose code in my echo statement.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-17-2007 03:21 AM
07-17-2007 03:21 AM
Re: Lock Disk and Service Guard
I use a Clarion with power path.
The /etc/lvmtab
/dev/vgsavlock
/dev/dsk/c19t1d1
The vgdisplay command output:
vgdisplay -v /dev/vgsavlock
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vgsavlock".
on second node
/dev/vgsavlock
/dev/dsk/c21t1d1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-17-2007 04:18 PM
07-17-2007 04:18 PM
Re: Lock Disk and Service Guard
if you are facing this problem on second node the most probable cause could be you have not exported the vg on second node.
and if yoiu are facing problem on the primary node, then you check the hdd (may be removed from the storage configuration.
Shardha
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-18-2007 02:10 AM
07-18-2007 02:10 AM
Re: Lock Disk and Service Guard
You should have the lock disk as a disk that is used in a package of your cluster. If the lock disk fails unless you have it actively used and the data mirrored of course you will never know it fails till both systems panic when a failover is necessary under certain circumstances. IF both nodes can communicate with each other the lock disk is not really used unless multiple networks fail.