vgexport and vgimport in MC/ServiceGuard Cluster Pairs

[Cliff Lim Kok Hwee]

Gd Day Forum,

Currently I need to remove a filesystem /mnt/PACKAGEA/data from a package named PACKAGEA. This requires me to perform a vgexport and vgimport subsequently.

Query: The package is running on the secondary node instead of primary node. Can I perform the mentioned below on the secondary node?

- Filesystem removal
- vgexport -p -s -v -m /tmp/vg.map

And then perform the following on the primary node using the map file generated from the secondary node:

- vgexport vg
- vgimport -v -s -m /tmp/vg.map

thanks/cliff

[Bharat Katkar]

Hi,
What i would do is:

1. Halt the package PACKAGEA on secondary node.

2. Remove the concerned VG from Cluster.
vgchange -c n

3. Activate VG and do vgexport -p to create map file

Regards,

[Gavin Clarke]

I wouldn't claim to be an expert, this link does it with the package still up.

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=180447

See instruction 6 on Chris McCray's answer.

I also don't think service guard cares whether the volume group is mounted on the primary node or not.

Guru's if I'm wrong please say.

[Cliff Lim Kok Hwee]

Hi Guys,

Can I conclude that the vgexport at secondary to generate map file and follow by vgexport and vgimport at primary node does not matter even though the package was suppose to be running on the primary node?

regards/cliff

[melvyn burnard]

You say you are removing a file system, but are you then removing the logical volume?

If not, then there is no need to vgexport/vgimport.
If you are removing the lvol, then you need to ensure that the file system is not in use, unmmount it, remove any reference to it in the package control script on all nodes to prevent any attempt to unmount/mount it.
Then you need to remove the lvol on the vg (on the secondary node I guess), which will sort out the vg/lv info on that node.
Then do a vgexport -p of the vg to a map file, copy the map file to the primary node, vgexport the vg there, make the directory and group file correctly, then vgimport.

Of course, if you have to stop the application to unmount the file system, you will have to halt the package first, then vgchange -a e the vg to do the work.

[Cliff Lim Kok Hwee]

Hi Guys,

I will be removing the logical volume. I understand I will need to modify the package control file at secondary node and sync it to the primary node.

Query: Can I conclude that the vgexport at secondary to generate map file and follow by vgexport and vgimport at primary node does not matter even though the package was suppose to be running on the primary node? Will there be any concern/issue with that?

Regards/cliff

[melvyn burnard · Accepted solution]

you are correct, it makes no difference which node you do the vgexport on, and then the vgimport, as long as you folow the steps correctly. (I have seen some people forget to use the -p option with vgexport when creating the map file )