You can mount the target DS by enabling image access - this presents a r/w image of that replica LUN (has to be masked to the servers). From there you would storage vmotion it to another datastore as Idan states and then use it as the target for RP4VM's once that is built. When you protect a VM in RP4VM, you can chose to have it create a new VM like for like on the target site or manually point it to an existing VM (in this case the one you copied from the traditional RP test) and that will act as a pre-seed for replication:  [IMAGE]
We currently have a VNX 5400 in production and a VNX 5200 in DR.  We have Recover Point setup with each LUN in it's own consistency group.  SRM is installed but not configured yet.  All LUNs are 100% in sync between production and DR. Please note we are using Virtual RP appliances  We have decided that based on our needs that RP4VM is a better fit for us.  I have not yet started this install but plan on doing so this week.  My question is - Is it possible to use the data we already have synced to start our RP4VM syncs?  I'm guessing not and that I'll need to remove RP from the environment and setup RP4VM fresh and do full syncs of each VM across the replication network.  Assuming that's the case can I run RP and RP4VM at the same time so that I can create a new LUN that is not synced with RP, move 1 VM into that, use RP4VM to sync it, then do the next VM until complete?  My concern would of course be the splitters.  Thanks in advance for any input and time/bandwidth saving suggestions.  Craig
Convert from RP to RP4VM