OpenReplicator hotpull issues.

I can still explain the steps, though i did not directly involve at this site, All of the 4-servers were give outage of 1 hour.

there are 4 servers on the list for migration;

server1- standalone windows box

1. remove the HP Mpio(not sure here reboot is required here)
   
2. Install powerpath (reboot and validate powerpath), after the powerpath install is validated shutdown the server. (Can suggest here if this step can be done fast in anyway).
   
3. As session is already created, activated the copy with donor_update, verified datacopy is 5% brought up verified that data is intact. migration succesful.
   

server2- standalone windows box

1. same as server1
   
2. same as server1
   
3. As session is already created, activated the copy with donor_update, verified datacopy is 5% brought up to verify, but the 500gb Drive 500 GB drive was seen as 100 GB formatted and 400+ GB’s raw disk, migration not succesful backed out to HP EVA.
   

server3- standalone windows box

1. same as server1
   
2. same as server1
   
3. As session is already created, activated the copy with donor_update, verified datacopy is 5% brought up to verify, but did not contain any data on the 100GB drive (VMAX LUN), as the original source has approx 400MB on the HP drive (EVA LUN), looks like data is not copied, migration not succesful.
   

server3- standalone windows box

1. same as server1
   
2. same as server1
   
3. As session is already created, activated the copy with donor_update, verified datacopy is 5% brought up to verify,which resulted 115GB of raw unformatted disk from VMAX, migration not succesful.
   

Do not know if we are missing anything, help is appreciated!

can you describe the process of your migration ?

for the ones with extra raw capacity, is the device on VMAX identical to the one on HP ?  Also are devices on HP are regular basic partition or dynamic ?

All the target devices are carved larger  than source HP devices, I am really not sure of the basic or dynamic partitions., can you please generalise if basic or if dynamic partitions does that really we need to check ??

Thanks..

ok, if devices on VMAX are larger than HP then that explains the extra raw capacity you see in Disk Administrator. Remember OR is block level copy so it will copy one to one.  I guess the intent was to migrate to VMAX and increase space at the same time, nothing wrong with that. On windows it's very easy to add that extra capacity. You will use diskpart utility to extend the partition so all that unconsumed space will become part of your existing partition, thus more space.

The reason i asked about dynamic drive is because some people are not familiar with diskpart so instead of extending existing device, they request an additional device and then combine the two together. On windows that can be achieved with dynamic partitions. So if you were to migrate one of those "logical" devices, you would have to OR copy all the component devices that make up that one dynamic drive. If you google it ..you will find a lot of info on Microsoft Technet website. With that said ..try to stay away from dynamic drives, they can be PITA

Thanks Dynamox, Though the Intention was not to increase the space, By the device standards having at VMAX side, we are needed to give extra space to meet up the the source capacity:

For example1, EVA LUN is 350 GB, VMAX with 6*67 gb meta the size became 404.58 GB, so As you said this extra 100 GB will be extra space will be Raw capacity after the migration and can be easily extended using diskpart.

Here I am just understanding dynamic disk, for example2 if  a dynamic disk of 100gb composed of 4 individual component LUNs 4*25gb, then If want to migrate the enitire storage as it is the case now not Just the single disk.so if we want to   miorate so I present the 100gb to migrate but not 4*25gb  separate LUNs, is this true ?

Also I am curious to know how do the VMAX drive looks like when the Copy is In progress, for example if you take same example1, after we bring up the server after 5% copy is done,is it at this point of time we see 350GB as allocated and remaining as free on the 404.58 GB or after entire migration is completed.

Thanks for the help..

we do not care if it is basic or dynamic but all we see on a SERVER is how many PHYSICALDRIVEs of what capacity it has today, then create the same or greater size Target LUNs  on symmetrix VMAX side..right..additionaly is it a good practice to activating the copy for all the servers in a single session/file..?

Also, I want to know if we want to take care of the LUN addressing while mapping the devices on the Control symmetrix VMAX   side, for example, windows host may see it has LUNs addressed as 1, 2 and 3 something, should we maps to the same LUN address while mapping the control devices to the symmetrix FAs ?...

SAN_AK wrote: Also, I want to know if we want to take care of the LUN addressing while mapping the devices on the Control symmetrix VMAX   side, for example, windows host may see it has LUNs addressed as 1, 2 and 3 something, should we maps to the same LUN address while mapping the control devices to the symmetrix FAs ?...

windows does not care, as long as you re-assigned the same drive letter.

SAN_AK wrote: we do not care if it is basic or dynamic but all we see on a SERVER is how many PHYSICALDRIVEs of what capacity it has today, then create the same or greater size Target LUNs  on symmetrix VMAX side..right

yep

additionaly is it a good practice to activating the copy for all the servers in a single session/file..?

that is up to you. I like to create individual file for each server, that gives me more granular control.