Can you export/import without deactivate in MCSG?

[Geoff Wild]

Currently migrating 2 node cluster from one EMC frame to another.
I'm doing this with Host Based mirroring via LVM.
Can you export/import without deactivate in MCSG?
I don't want to take the package down on the primary node....

Rgds...Geoff

[Geoff Wild]

Sorry - this should be in "service guard" not "databases" :(

[Pete Randall]

Geoff,

I believe you have to deactivate. I just took a look at the man page but couldn't find any info one way or the other. You could always just try the vgexport and see whether it insists that it be deactivated first.


Pete

[Massimo Bianchi]

Hi,
the answer is YES !

If, on the second node, you also want to take a vgbackup, use these steps:
- import the vg
- vgchange -a r vgXXXXXX
- vgcfgbackup vgXXXXXX
- vgchange -a n vgXXXXX

should do the trick


But i'm thinking of a drawback: the lock disk.
It is written in the dsk...

so, you can do all the procedure, but you will have warning in the syslog for the missing lock disk.

At the end, to do a clean work, it's best to close the cluster, do the lvm work, change the ascii config file and re-apply the cluster config. If you can live with it, you can also do the simple mirroring.



Good friday !

HTH,
Massimo

[Geoff Wild]

now I've done it - double posted....sigh...

Anyways...here's some more info:

I vgextend'ed the volume groups on the primary node.
Then, for each lvol,
lvextend -m 1 /dev/vgXX/lvXX /dev/dsk/

After the mirroing is complete, lvreduce the /dev/dsk/ for each lvol.

Online - 0 downtime.

Now, I need to get vgs/lvs on the 2nd node fixed - but I don't want to halt the package....

What about a vgchange -S y ???

Rgds...Geoff

[melvyn burnard · Accepted solution]

removed origional post, and moved this one.
and the answer to a normal vgexport -p is yes
on hte second node you would simply vgexport the vg, mkdir vgdir, mknod group file, vgimport.
However, wiht a Shared activation mode VG, i.e. in Sg OPS Edition, I would be VERY wary about doing htis.

[John Meissner]

To export the VG it can be active... it'll give you an error message... but it will create the map file regardless. To import you need to have it deactivated

[Geoff Wild]

Well wonders never cease - didn't put the vg's in "shared" mode - and I was still able to run a vgimport on the second node!

With MC/SG - you do NOT need to deactivate volume groups on the primary node to import on the secondary node.

Rgds...Geoff