devices changed and deported volumn will not activate

[Randy Rayfield]

We mirrored VG's from a DMX2000 to a EVA5000 using Veritas. We split the mirrors, deported the VG's and migrated both the systems and the EVA to another datacenter. We are attempting to bring back up the VG's, and Veritas on HP is having issues because the controller number has changed, and does not match up with the deported disks. Any clue's as to how to get around this?

This worked fine on both Solaris and Tru64 machines moved, and all the HPUX servers are all jacked up.

Any help would be $$GREATLY$$ appreciated.

[Steven E. Protter]

Shalom,

This is likely to be a LUN configuration issue. The control station for the EVA-5000 needs to be checked. Probably the wrong WWN name is associated with the LUN or they were not given the correct LUN numbers.

SEP

[Randy Rayfield]

I don't think this is the issue. We see all the disks, but they are not recognized as the VG. If I were to compare it to LVM, the mapfile I am importing from needs to have the controller # (C*t5d0) changed.

[Randy Rayfield]

We had to wipe the private region of the disk and re-create it with some scripts and help from Veritas.