- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- VG activation modes difference
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-18-2007 06:42 AM
тАО07-18-2007 06:42 AM
in all my cluster packages VG are getting activated with exclusive option
vgchange -a e
now i want to change that into
vgchange -a y
can anyone tell me wat impact that change will make and after changing that would i be able to shift my package to failover node?
And is there anyother cluster file needs to be changed except *.cntl?
and what steps i need to perform to make that change is it's a production node and i dont wana take any risk.
Thanks in advance waiting for a quick response.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-18-2007 06:49 AM
тАО07-18-2007 06:49 AM
Re: VG activation modes difference
http://docs.hp.com/en/B2355-60105/vgchange.1M.html
and you will see that you don't want to change this.
vgchange -a e
is pretty normal for a VG in a cluster.
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-18-2007 07:02 AM
тАО07-18-2007 07:02 AM
Re: VG activation modes difference
Actually i need to synch my BC volumes with my production volumes.
As right now my production volumes are activated in exculsive mode so after resync i cant mount my BC volumes on any other node.
As during vgchange, it gives me error
vgchange: Activation mode requested for the volume group "/dev/BC1_xpvgsieapp" conflicts with configured mode.
So to resolve that, i need to activate my VG's in production without exclusive option.
I hope you'll understand my prb. waiting for your feedback
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-18-2007 07:15 AM
тАО07-18-2007 07:15 AM
Re: VG activation modes difference
Good catch on the reason for the issue but bad idea on the resolution. You need to keep the vgs activated in exclusive mode on the production servers. Any number of errors will result if you don't do that - not the least of which is your packages won't start.
The correct action is to run vgchgid on the bcvs. It's absolutely essential to ensure you run vgchgid on *all* the BCVs simultaneously - in one call.
vgchgid will change the volume group ID on the disks. It comes up with a new ID every time it's run so if you dont' run it on all the BCVs simultaneously, you'll have to resync the BCVs with the production and star t over.
The process you want to import the bcvs will look something like:
set -A bcvs $(list-o-bcvs-that-belong-to-one-vg)
/usr/sbin/vgchgid ${bcvs[*]}
mkdir /dev/vg_backup
mknod /dev/vg_backup/group c 64 0x0#0000
vgimport -m ${map} vg_backup ${bcvs[*]}
HTH;
Doug
------
Senior UNIX Admin
O'Leary Computers Inc
linkedin: http://www.linkedin.com/dkoleary
Resume: http://www.olearycomputers.com/resume.html
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-18-2007 07:15 AM
тАО07-18-2007 07:15 AM
Re: VG activation modes difference
As stated in the man page, you need to disable the cluster mode (-c n) (and halt the package) to be able to use "-a y".
Maybe "-a r" can help you.
If you don't want to stop this node, do nothing.
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-18-2007 07:27 AM
тАО07-18-2007 07:27 AM
Re: VG activation modes difference
http://docs.hp.com/en/B2355-60105/vgchgid.1M.html
to understand the background.
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-18-2007 10:28 AM
тАО07-18-2007 10:28 AM
Re: VG activation modes difference
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-18-2007 06:19 PM
тАО07-18-2007 06:19 PM
Re: VG activation modes difference
Thanks for all your replies. I tried VGCHGID but the problem is that the command is hanged for so long and didnt gave me any result.
Could anyone tell me wats the reason for that.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-19-2007 12:59 AM
тАО07-19-2007 12:59 AM
Re: VG activation modes difference
You did split the bcvs before running the vgchgid command, right? That command is damn near instantaneous so any delay is a cause for concern.
Please post the commands exactly as you typed them so we can get a better idea what happened.
Doug
------
Senior UNIX Admin
O'Leary Computers Inc
linkedin: http://www.linkedin.com/dkoleary
Resume: http://www.olearycomputers.com/resume.html
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-19-2007 02:10 AM
тАО07-19-2007 02:10 AM
Re: VG activation modes difference
As Doug has already said you need vgchgid and then vgimport.
The high level steps for using BC copies is -
Take a vgexport -v -p -m vg01.map /dev/vg01
and so on for all the VGs on the production [ the -p is very important so that actual export does not happen, only map file gets created] Copy the map files onto server you will use for BC volumes.
1. Take BC copies into PSUS state
2. Split the BC pairing to bring the LDEVs to PAIR statee
3. On the server where you want to use the BC volumes (assuming the BC vols are visible to the server) - do a
vgchgid /dev/rdsk/cxtydz /dev/rdsk/...
for disks [ BC vols ] belonging to same VG
4. mkdir /dev/vg...
mknod ....
5. vgimport -m map_from_prod_vols /dev/vg.. /dev/dsk/cxtydz ...
6. vgchange -a y /dev/..
7. Mount filesys
Also please provide the exact steps and exact commands you have used to help you further.
Regards,
Ninad