SRM LUN ID between protected and protection site

[PetervandenBosc]

I use async storage replication on EMC CX320c storage. I want to implement SRM, what about the LUN id's?

Te replicated storage partition got different LUN id's examle VMFS lun id on protected site is 403 this storage partition is replicated to LUN id 100.

Is this configuration a problem?

[Michelle_Laveri]

I use async storage replication on EMC CX320c storage. I want to implement SRM, what about the LUN id's?

Te replicated storage partition got different LUN id's examle VMFS lun id on protected site is 403 this storage partition is replicated to LUN id 100.

Is this configuration a problem?

I don't think so, quite often the LUN ID will be differ when the LUN or Snapshot is presented to the recovery ESX hosts anyway.

Remember VMFS has UUID value which contains a LUN referrence, this can be used by ESX to detect that the LUN is snapshot - because the LUN ID of LUN, doesn't match the LUN ID held in the VMFS metadata.

SRM automatically resignatures and relabelles the snapshot LUN for you...

Have you tried it to see what happens - you can't beat experimentation...

Does the EMC PDF guide saying anything particular about needing matching LUN IDs?

My array (not an EMC) always shows a different LUN ID, never caused a problem.

Regards

Mike Laverick

RTFM Education

http://www.rtfm-ed.co.uk

Author of the SRM Book: http://www.lulu.com/content/4343147

[Itzikr]

Different LUN ID's should be ok, but note that there are special configuration for snap names in SRM & Clariion

VMWARE_SRM_SNAP_LUNID is one of them, so read the docs on powerlink..

Itzik

reich_itzik@emc.com