Hi,

Has anyone configured san based heart beat using HACMP5.2 ?

I believe you have to configure a concurrent vg disk. I would like to
know other peoples experiences with this and if it is reliable etc.

Thanks.

steven wrote:
> Hi,
>
> Has anyone configured san based heart beat using HACMP5.2 ?
>
> I believe you have to configure a concurrent vg disk. I would like to
> know other peoples experiences with this and if it is reliable etc.
>
> Thanks.

It's actually an enhanced concurrent vg disk, but it doesn't have to
vary-ed on any where - HACMP just uses areas reserved for the disk
heartbeat in the VGDA. And it was available as of HACMP 5.1.

Hello World,

ste_mc@zdnetmail.com (steven) wrote in message news:<334f538e.0411090645.4cd695a2@posting.google. com>...
> Hi,
>
> Has anyone configured san based heart beat using HACMP5.2 ?
>
> I believe you have to configure a concurrent vg disk. I would like to
> know other peoples experiences with this and if it is reliable etc.
>
> Thanks.

I've done it using a FAStT on a SAN. It works, and I haven't had any
problems. Create a volume on one of those splintery small free spaces
that you always seem to end up with, assign it to both machines,
create an Enhanced Concurrent enabled volume group and use the disk
for the heartbeat. Theoretically, you can use any shared
Enhanced-Concurrent VG, but why take any chance?

Concurrent VGs are nice, though. They take much less time to activate
on a takeover because the things are active already. This cuts down
your takeover time.

Cheers,
Menno.

>
> I've done it using a FAStT on a SAN. It works, and I haven't had any
> problems.

to add to this, ive done the same on a EMC clarion array. works well.