- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- managing shared vgs without MCSG
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
04-01-2003 08:56 AM
04-01-2003 08:56 AM
managing shared vgs without MCSG
I need to manage two volume groups in two servers.
It's like this:
VG01 will be active, exclusively, on serverA, and VG02 in serverB.
If serverA fails (crash, network, etc.), I want to activate vg01 on serverB and vice-versa.
any ideas on how to do this without MCSG?
tia,
Pedro
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-01-2003 09:12 AM
04-01-2003 09:12 AM
Re: managing shared vgs without MCSG
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-01-2003 09:17 AM
04-01-2003 09:17 AM
Re: managing shared vgs without MCSG
I'm assuming that your mechanism to share the device between A & B is already in place - a fibre channel switch, perhaps?
Given that, here's the steps I went through:
1. run a make_tape_recovery and do a full backup
2. vgchange -a n vg01 on server A
3. vgexport -p -s -m /tmp/vg01map /dev/vg01
4. copy the map file to the other server
5. mkdir /dev/vg01
6. mknod /dev/vg01/group c64 0x010000
7. vgimport -s -m /tmp/vg01map /dev/vg01
8. repeat above for vg02 on server B
Now, when one of the server fails, everything is ready to go and all you have to do is activate the volume group with
vgchange -a y /dev/vg01
You do have to use extreme caution to avoid activating the volume group on both servers at the same time. The man page claims this can't be done, but I managed to trash a data base when I ended up with it active on both machines.
Pete
Pete
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-01-2003 12:04 PM
04-01-2003 12:04 PM
Re: managing shared vgs without MCSG
once you configure as shared vg ,you can use Event monitoring service to monitor the VGs if system gets down ,you can configure to activate the vgs through EMS on the other machine.
Rizwan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-02-2003 01:02 AM
04-02-2003 01:02 AM
Re: managing shared vgs without MCSG
Ok. I think it's better to have MCSG to control the vgs on bot systems.
As I need to move it if I have a network problem, and I do not know how to send the comand to the other node on such case (of course I could use the backup lan card to do it, but I think it does not worth the trouble), so I will install and configure SG.
thanks.
Pedro