Simpler Navigation for Servers and Operating Systems
Completed: a much simpler Servers and Operating Systems section of the Community. We combined many of the older boards, so you won't have to click through so many levels to get at the information you need. Check the consolidated boards here as many sub-forums are now single boards.
cancel
Showing results for 
Search instead for 
Did you mean: 

Linux AS 3 Update 5, LVM ver 1.

Silver_1
Regular Advisor

Linux AS 3 Update 5, LVM ver 1.

All,

Aim:

Moving a volume group from machine A to a Service Guard cluster B and C where some packages are already running.

Just to let you know i am NOT moving the machine in to the cluster only moving the volume group where i have database files.

Once i can see the Volume group i am planning to create a package using this volume group where the failover can happen between machine B and C.

Problem:

Machine A (from i am moving the volume group)

[root@a root]# ll /dev/vg*/group
crw-r----- 1 root disk 109, 0 Aug 31 14:09 /dev/vg00/group
crw-r----- 1 root disk 109, 2 Sep 1 15:16 /dev/vg_03/group
crw-r----- 1 root disk 109, 1 Aug 31 14:09 /dev/vg_02/group
[root@a root]#

Machine B and C (to the volume group is moving)

[root@b root]# ll /dev/vg*/group
crw-r----- 1 root disk 109, 0 Aug 31 14:09 /dev/vg00/group
crw-r----- 1 root disk 109, 2 Sep 1 15:16 /dev/vg_04/group
crw-r----- 1 root disk 109, 1 Aug 31 14:09 /dev/vg_02/group
[root@b root]#

I am moving the vg vg_03 to B and C using the commands

a: vgchange -an vg_03
a: vgexport vg_03

b: vgimport vg_03 /dev/sdd

Does this work properly.

Do this import will create a new group file with minor number 3 ?


In HP UX we can create the device files whatever we needed and import the VG. But in the case of AS 3 i have seen that sometimes the import is creating the existing device files ie their will be 2 volume groups with same minor numbers.

Did any of you have done this before ?

TX