Here is the Answer. you have to every Replicated or Disaster Recovered LUN has it own Signature so you have to mount the volume manually. so, Stop the replication between LUNs, no matter you do it from source or destination, just break the Replication. If you double click on the "REPLICATED LUN" on the destination storage, in the "REPLICATION Tab" you will find the warning about replicating or something. you have to remove the replication tag from the destination LUN, for doing that you have to use Unisphere CLI. (uemcli /stor/prov/luns/lun -id set -replDest no ) you can find the LUN ID using show (uemcli /stor/prov/luns/lun show) LUN is ready, if you get back to replication tab of destination LUN you will find the REPLICATION BUTTON and that's mean the LUN is ready to mount. SSH to one of the ESXi Hosts and use command blow to find the LUN you want to mount: esxcfg-volume –l You can keep the LUN signature if you want just mount and check, but if you wanna use it in new environment its better to re signature it with -r command. So lets mount: esxcfg-volume –M uuid/lable   sorry for bad english/    
Dear Engineers I have two storage Unity 600 and We have launched a replication  between these two storages.I want to unplug the destination storage device and connect it to some hosts separately and mount VMFS volumes for some reason. Anyways, I have stopped replication and even marked the destination LUN's as read/write again with this command in "Unisphere Cli", (uemcli /stor/prov/luns/lun -id set -replDest no ) But while I have completely disabled synchronization and also made LUNs Writable again, the virtual infrastructure does not recognize the allocated spaces as VMFS Datastore and recognizes them as new device and wants to format space for new datastore. do you guys have any idea about how i can stop the replication and use destination LUNs as VMFS datastore again ? thanks
synchronization and Replicating unity problem