Unsolved
This post is more than 5 years old
10 Posts
0
3355
Using EMCopy migrating files always Aborts
Dear everybody:
I tried to use EMCopy.exe to migrate files and data(about 179GB) from a source rive f: provided by HP EVA to the destination drive z:(300GB free space) by EMC VNX in windows server 2008.
I used command with Administrator rights: emcopy_v4_07.exe F:\ Z:\F /o /a /s /log:c:\emcopyF.txt
It takes about 1 hour to finish the process, and the state is shown below:
source：179Gb 365493files 38592folders
destination：97.6Gb 191155files 23407folders
Apparently, the copy was not completed leaving about 82GB data uncopied.
And yellow warning are shon below:
I can not figure out why it happened.
Many thanks if u can give me some advice.
christopher_ime
2K Posts
0
March 20th, 2012 21:00
The version you are running is fairly old. I would recommend downloading the latest and trying again and then if it persists investigating further. Currently, v4.14 is available from PowerLink via the following breadcrumb trail:
Home > Support > Product and Diagnostic Tools > Celerra Tools > Windows Migration Tools > EMCOPY
christopher_ime
2K Posts
1
March 20th, 2012 21:00
Also, review the following EMC KB article:
emc245596: "EMCOPY 4.0x shows multiple errors like 'Trying to DELETE due to copy ABORT' and 'DELETED due to copy ABORT'"
Talks about why you are receiving it and recommended best practice.
Also, you will see in v4.14 release notes the following enhancement:
[...]
- Added enhancement of the recovery mechanism in case of brutal abort due to client or application crashes or in case of long duration loss of network. Next copy in differential mode will detect inconsistent files and redo the copy
[...]
PandaDa_978074
10 Posts
0
March 26th, 2012 21:00
Thanks for your help, Christopher.
However, I still find yellow warning mentioned above using lastest version of EMCopy .
Finally, I tried to use command /xd to exclude these files which seems to being always used and finished the migration.
For this excluded files which is not business-critical files, although yellow warning still existed, I found them copied to the destination.
It seems to be ok now.
I supposed file OPEN status caused yellow warning, even after I rebooted the server and stopped related applications.
Anyway, many thanks for your advice.