Exporting VG

[Stojcevski Dejan]

Short question:
When I do vgexport what I actually delete: /etc/lvmtab or /dev/vgxx/** or both?
I know that the data in BDRA on the disks is not affected.
Dejan.

[Pete Randall · Accepted solution]

Both, unless you're using the -p option.


Pete

[Franky_1]

Hi,

you delete the device files under /dev/vgxx/
as well as the corresponding entries in /etc/lvmtab

Regards

Franky

[Bharat Katkar]

Hi Dejan,
Actually Both are affected.
When u do vgexport, that vg get removed from lvmtab and the /dev/vgxx gets deleted.

But if you do vgexport with -p option then nothing is disturbed but this allows you to create map of that VG which you can use for replicating the VG structure on the other node.

Hope that helps.
Regards,

[Stojcevski Dejan]

OK, so when I do vgimport i am actually putting the /etc/lvmtab and /dev/vgxx/* into the new system (normally with the -p option previoselly used to make a file). If the disks have the same HW paths in the new server that I actually transfer the VG to that computer. Is this correct? Are there any other steps do be done? (Everything is going normally meaning no need for vgscan etc...)?
Dejan.

[Bharat Katkar]

hi Dejan,
You can do vgimport and get the entire VG structure onto another system.
Now even though the H/w paths are not same then also you can import it successfully. Only thing you have take care of is to identfy the PV's correctly that belongs to that VG.

Then you can do this:

# vgimport -m vgname ..

That works fine.
Regards,

[Geoff Wild]

Prior to the vgimport - you also have to create the vgXX dir and group file:

mkdir /dev/vgXX
mknod /dev/vgXX/group c 64 0xHH0000

Where XX is the volume group number in decimal - like say vg10 and HH is the minor number (must be unique!) in hex - like 0a

Rgds...Geoff