Hi All: New to Host Copy and am currently planning a migration at a customer site for 2 TB of data. Have been testing PPME Host Copy at the office and the speed is terrible. I have been playing around with the throttle and suspend values and am not seeing any good results. So far it has taken 45 minutes to copy 500 mb of data. We don't have the fastest servers and and an older clariion but that is really bad. Any hints on what I might be doing wrong? Or is it just really slow? Thanks in advance and have a great day.
I don't have the atual answers for you, but based on my reading of the admin guide for PPME host copy I would expect the host copy to be significantly less than an array based replication. Since the host copy uses the host i/o to mirror the source volume to the target volume it will be a low priority thread as the application using the source volume will require priority access for it's LUN i/o. If the server is older, isn't a multi-core cpu, and doesn't have a lot of memory then this would contribute to the slowness as well.
Are you able to stop host i/o to the source lun and run a test using the highest transfer settings?
hi Aran: I can't find a way to actually stop the app once it is running. but I am having an issue with the target drive. As soon as you start the migration the target goes offline. Using windows 2003 so not sure why that would be. There are events in windows event viewer that indicate that the target drive no longer exsists.
I was referring to the application running on the server that is using the LUN, not PPME. I was just wondering as a test if the migration was quicker if the app (whether it is file serving, sql, etc...) were not accessing the LUN. Obivously that defeats the purpose of PPME, being that you want to migrate a LUN with the app online, I was just thinking of it for testing purposes.
you are not supposed to bring the target drive online where it's visible in Windows Explorer, target drive does not need to be formatted either. A step-by-step process is described in this paper.
I can't find a way to actually stop the app once it is running. but I am having an issue with the target drive. As soon as you start the migration the target goes offline. Using windows 2003 so not sure why that would be. There are events in windows event viewer that indicate that the target drive no longer exsists.
Referring back to my initial testing of PPME on a older server I copied a 100GB LUN (R5 4+1 Clariion CX3) in 1h34m on throttle 2, 56m on throttle1 and 35m on throttle 0. These times are for an idle server and idle disks.
AranH1
2163 Posts
423
0
Posted April 6th, 2010 10:00
Hi Rick,
I don't have the atual answers for you, but based on my reading of the admin guide for PPME host copy I would expect the host copy to be significantly less than an array based replication. Since the host copy uses the host i/o to mirror the source volume to the target volume it will be a low priority thread as the application using the source volume will require priority access for it's LUN i/o. If the server is older, isn't a multi-core cpu, and doesn't have a lot of memory then this would contribute to the slowness as well.
Are you able to stop host i/o to the source lun and run a test using the highest transfer settings?
Aran