topic Re: error when using vgchange - c n in Operating System - HP-UX

error when using vgchange - c n

skv in Spb — Tue, 21 Jul 2009 13:38:33 GMT

All of good day!

There is such a configuration:
two servers SD, each 11.31 HP-UX.
ServiceGuard v.19
multiple disk groups are connected to XP24000
on the array is BC.

the third server to HP-UX v. 11.31, but not SG.
this server presented S-vol of the cluster.
I want to execute the command vgchange-cn after split BC
But an error on the impossibility of implementation.

Re: error when using vgchange - c n

Mel Burslan — Tue, 21 Jul 2009 14:10:42 GMT

Your English is very hard to understand. Please perform a screen-capture and post it, so that we can see the commands you are running and the error messages you are getting.

Re: error when using vgchange - c n

Vinod Kumar Yadav — Tue, 21 Jul 2009 14:34:18 GMT

Hi,

Please paste the error of whil execute the command vgchange -c n on which vg.

Then we can know the correct answer.

Thanks
Vinod

Re: error when using vgchange - c n

Duncan Edmonstone — Tue, 21 Jul 2009 15:38:34 GMT

You should be able to run "vgchange -c n" on the third node *after* you have imported the VG, but before you have activated it... you don't need to run it on either of the cluster nodes... so after you split your BC, on your 3rd (non SG) node:

vgimport ....
vgchange -c n ...
vgchange -a y ...

of course you need to have made your SVOL writeable - you haven't defined it as read-only have you?

HTH

Duncan

Re: error when using vgchange - c n

Prashanth Waugh — Tue, 21 Jul 2009 15:49:12 GMT

Hi,
let me guess ur setup.

1) node 1 is in production part of cluster
2)node 2 is in production and part of cluster
3) i think ur using the third node for backup or test server.ur presenting the bc copy to the the node 3 server which is not part of SG.

==========================================
the producton volume groups will be sysnc with BC volume group and production vgs will be the part of cluster package. i think after spliiting the BC that VG vill not be the part of cluster. so it will give the error.

Regards
Prashant

Re: error when using vgchange - c n

skv in Spb — Wed, 22 Jul 2009 05:39:09 GMT

this is true
>1) node 1 is in production part of cluster
>2)node 2 is in production and part of cluster
>3) i think ur using the third node for backup >or test server.ur presenting the bc copy to >the the node 3 server which is not part of SG.

the first (SG) server I use vgexport -v -p -s -m /...
copy the map file the third (not SG) server
and do:
- vgimport -m -s -v ....
- vgchange -c n ...
error -

Re: error when using vgchange - c n

Duncan Edmonstone — Wed, 22 Jul 2009 05:41:58 GMT

> - vgimport -m -s -v ....
> - vgchange -c n ...
> error -

I'd imagine that's *not* the message you get on the screen - what error message *do* you get?

HTH

Duncan

Re: error when using vgchange - c n

skv in Spb — Wed, 22 Jul 2009 05:46:11 GMT

Now send the log to the terminal can not.
I'll try later

Re: error when using vgchange - c n

bright image — Wed, 22 Jul 2009 08:59:15 GMT

You will need to split your business copy before running vgchange -c n as it will write to the disks. It will fail if the disks are not writable.

Please ensure your business copy is split and read/write before running the vgchange -c n command.

Re: error when using vgchange - c n

skv in Spb — Wed, 22 Jul 2009 09:01:56 GMT

Yes, of course, BC is split.

Re: error when using vgchange - c n

Prashanth Waugh — Wed, 22 Jul 2009 15:39:00 GMT

Hi,

The sequence should be like that

1)create the map file using vgexport -v -s -p -m
2)split the bc
3)vgchange -a n
4)vgimport the map file on node 3
5)vgchange -a y
------------------------------------
I would like clear one thing here see the BC copy will be on stoarge level nad will not be part of cluster.only production volume vill be the part of cluster. then no need to do the vgchange -c n .

Re: error when using vgchange - c n

Prashanth Waugh — Fri, 24 Jul 2009 12:13:34 GMT

Hi SKV,

Your prolem solved or not. If your problem solved Pls share ur experience.

Thanks,
Prashant