S7a Failover problems

[millsra]

In Falls Church Va. we have a S7a san attached to 2 brocade 12000 silkworms with an EMC 8730 storage array. We are using SRDF to replicate our data to our DR site in Philadelphia to another 8730 frame with 2 silkwork 12000's and a DR server that is also an S7a. The server that is in Philadelphia has less memory and CPU's than our production server. The problem we are incountering is that when we try to fail over the server to Philly we are getting hung on boot for a 552 LED error code. (Unable to varyon rootvg). We boot over SCSI (since IBM will not open the code to allow boot over fiber)and our data is fiber connected through 2 6227 (LP700) hba's. We are running AIX 4.3.3 ML07 and 10. (Couple different servers with the same problem.

My question is has anyone else encountered this and if so do you know of any viable suggestions or workarounds to successfully fail a S7a over to our DR site. Our Data center move depends on getting this to work.

Thanks in advance.

 

[millsra]

I guess noone else has seen a problem like this?

 

[nabob1]

Case in point - how was your R1 - R2 defined, there are a lot of underlying issues which may be holding up your failover, one can not give an accurate assesment without knowing the exact manner in which the SRDF was set up, sorry mate.

 

[millsra]

I am not sure what you might be looking for as far as R-1-R-2 set up. We are in adaptive copy mode between the 2 if that is what you are referring to. If not and you have more specific criteria please let me know. I really need to get this to work.

Thanks in advance