Quote:
My scenario just talks about using a failover server if primary crashes.
That is exactly what a HA cluster is...
main difference is it has spare (true or virtual) devices like network etc...
where in case of heartbeat interruption, does a failover on the remaining server by mounting all the failover packages and setting up a lan with the IP and hostname of the failed server...
Quote:
I won't be using same volume on primary and failover server same time.
I hope not...(I know...) but you could by mistake...
---
When you import a VG you import its configuration in order to be able to use the VG coming from elsewhere... I do this because all the servers I configure have internal disks in mirror but for the OS only...I can easily upgrade a server by exporting-changing box and import again process...
In your case you want both server to be able to use (not share..) the VG and so on the first you would use the -p option of vgexport (with of course -f (or/and) -m) to generate the file you copy on the other system to use with vgimport.
-p option is "preview", it does all except remove the VG from the system....
vgchange is the way you activate/deactivate the VG. It can only be active on one server at a time but only you know which because of the vgchange, if by mistake you have activated on both same time it will not take long before both servers announce FS corruption and may possibly crash...
