What is the best tool to do data migration from NetApp to Isilon ? Running code 7.0.2.1 and 7.0.2.5 ( Prod and DR)
Facing lot of issues with isi_vol_copy tool while doing file migration from NetApp to Isilon. The volumes on the source array is <3TB in size, <80% utilized and there is enough space for checkpoints.
The isi_vol_copy command works, but files on Isilon have different "create date" time stamps. File properties, create date appear as "Wednesday, December 31, 1969, 7:00:00 PM" instead of the acutal create date of files.
Resolution: will be fixed in new onefs version.
Incremental copy fails with following error message on code 7.0.2.1.
Resolution: The issue Will be fixed in new onefs version. But a fresh new copy job to a different folder on the cluster worked.
inode number: 221847-1-0
flags: REMOVED|KEEP
LogMessage {type NDMP_LOG_NORMAL} {msg_id 0} {msg DUMP: Network communication error
} {associated_msg 0} {associated_msg_seq 0}
LogMessage {type NDMP_LOG_NORMAL} {msg_id 0} {msg DUMP: DUMP IS ABORTED
Isi_vol_copy can be used to migrate any type of data irrespective of SMB or NFS. The volumes that I need to migrate are CIFS only type. There is no primus available for these errors and if you open any isi_vol_copy SR with support they have only one solution and it will not resolve the issue. I will have to use third party migration tool for this.
I was getting error "FAILED ASSERTION m @ /b/mnt/src/sys/kern/isi_format.c:134" which then caused many errors like below.
db->get failed, err:No such file or directory
acl_db_get failed for aclino:1384703
The issue also caused isi_vol_copy to stop, requiring a restart many times.
After working with engineering for quite some time, the issue has been fixed in 7.2.1.3, however I didn’t not see any mention of it in the release notes, but i can confirm the issue is resolved completely.
As a unrelated note, I would like to mention that whenever the source Netapp did a autogrow on the source volume, I needed to delete the contents on the target directory and redo a isi_vol_copy full. I suspect this is because the inode mapping was changed. I have not seen this listed as a limitation, but it proved to be 100% consistent as a problem/solution for me.
Vanitha13
14 Posts
2880
0
Posted February 26th, 2014 07:00
Hi,
What type of files are you migrating, is it CIFS or NFS ?
I was not able to find anything with the error messages that are pasted, but came across 2 white paper which may be helpfull :
NFS FILE MIGRATION TO AN EMC ISILON CLUSTER ( Guidance for optimal data migration of NFS workflows )
SMB FILE MIGRATION TO EMC ISILON (Guidance for optimal data migration of SMB workflows)
let me know if this helps
Thanks
Vanitha