Server access to New EVA4400 and old (xcs5030)EVA6000

[hh454]

We are currently installing a new EVA4400 and want to connect a server(s) to migrate data from our existing EVA6000. My concern is that the EVA6000 has older unsupported 5030 XCS code(beacuse of an old hp-ux 11.0 system) and the EVA4400 has current code.
The new server will have the latest HBA drivers to support the EVA4400.
Is there any risk presenting storage from a older XCS? This is a test to see if we can migrate data from one EVA to another. This older version isn't listed in the SAN design guide anymore.

We can't update code on our EVA6000 until we upgrade our hp-ux system or replace it.

Both EVA's will be in their own zone with the server that will will copy the data over.

Is there any risk to our production EVA6000 or any other prod servers or our fabric?

thanks in advance-

[IBaltay · Accepted solution]

Hi,
to see the real situation create the following:
1.the test LUN on the EVA6000
2.the new server host group on the EVA 6000
3. assign the test LUN to the new server host group
4. check its visibility
5. do the test writes/reads from it

if it works, then it should be fine also for the migration

[Steven Clementi]

Harry:

I can not see why you would not be able to present Storage from both EVA's.

As long as you have separated your EVA's via zoning, they will not be able to talk to each other... and even if they did, it is not likely that they could do any harm to each other. The server can only see the Virtual disks, so it too should not cause any problems.

Of course, it is nice to have a backup for those situations where you are unsure.


Steven

[hh454]

Thanks for the replys. I think we will go ahead with our test. If we have any technical problems I'm sure hp support will request that we have the latest code on all associated components.