Hello bakunin/filesophizer,

Thank you very much for your response.

I have another few questions (in purple). Im sorry for being paranoid... Thanks for being patient with me!

(A) If I did not want to enable the concurrent mode, can I still use the `chdev -l hdiskXX -a pv=yes` command?

In other words, will I be safe if I VARYOFFVG from the working server and then run the chdev command? (This way I wont need to change the concurrent mode settings on the disk).

To answer Filesophizer question: This disk is shared between the two servers, but we only want 1 server to be able to mount and read/write to it at a time b/c it hosts our database. Thus I dont want concurrent mode enabled. I want to be able to shutdown my Aki (working server who can varyonvg/mount), and allow my Hag server to varyonvg. It wont varyonvg because the lspv between the two servers are different. Hag does not have the PVID's in his lspv and so I think(?) that is why he cannot varyonvg the hdisks 2-7. Also, The hdisks are set to "Active", not "Concurrent" at the moment.

So...

(B) How can I make the lspv's the same while leaving concurrent mode off, so that only 1 server can varyonvg at a time and both servers have access?

Here is the lspv differences (from my previous post on page 1 of this thread):
1) lspv from Aki (working machine, he can varyonvg and varyoffvg)
hdisk0 000b80bfce436320 rootvg active
hdisk1 000b80bf05467e80 None
hdisk2 000b80bf27ceb498 vg00 active
hdisk3 000b80bf6c9b41f8 vg01 active
hdisk4 000b80bf6c9a3a8d vg02 active
hdisk5 000b80bffbb9f2af vg03 active
hdisk6 000b80bffbb6bf7b vg04 active
hdisk7 000b80bf27dc7320 vg05 active

2) lspv from Hag (notice the PVIDs are empty, so maybe this is why he cant varyonvg hdisks 2-7):
hdisk0 000268fceda1da0 rootvg active
hdisk1 000268fdfe25883 db01vg active
hdisk2 none None
hdisk3 none None
hdisk4 none None
hdisk5 none None
hdisk6 none None
hdisk7 none None

And finally... as always...

Thank you so much for your help!!!!