Recover point on HPUX 11.23

[Jay_122]

Just finished installing EMC's recover point product.

I am using the brocade FA4-18 application blade in production and the clarion CX380 splitter in our DR site. The issue I am having is that every time I create a target / initiator binding, the physical paths to the HP server show as failed (no_hw) and new devices are created for the virtual LUNS. I thought that the OS should remain blissfully unaware of this change. Has anyone had similar issues? If so, how do I fix this?

Any help would be appreciated.

[CFA]

I just saw your question and hope you already have an answer. On HP-UX hosts prior to 11.31 using the legacy naming convention for luns (ctd's) you will have to export and re-import all your volumegroups during a recover point zoning. All of the ctd's will change during the recover point zoning. If you are using HP-UX 11.31 and the new agile disk convention (ex disk3) you will not have to rezone as the I/O stack is smart enough to recognize the change. I have complete instructions on how to rezone under recover point if you need them.