Solved!
Go to Solutionemcopy - access time not getting copied
I'm using EMCopy with /sdd flag to copy files from a Netapp volume to Isilon share and it is not copying the file "accessed" time value. The access time inherits the modified time values, create time is OK. Did anyone notice this issue. the "Access time tracking" is disabled on the cluster and I think this could be because of that. I had to use emcopy for this volume as there are issues with isi_vol_copy ( bugs) with 7.0.2.5 version. The isilon share has "run as root" privileges for the user and they are part of local administrator group on both arrays...so no issue there. Please let me know if you have faced this issue before and what resolved it
thanks in advance
-H
1748
0
Posted February 21st, 2014 10:00
Did you enable Access Time Tracking on the cluster? It is disabled by default but can be turned on easily.
Enable it and try a recopy with emcopy.
1753
0
Posted February 24th, 2014 11:00
Enabled "access time tracking" precision to 1 minute on the cluster but it still did not copy and update the access time of files on the Isilon. Robocopy also is not doing the access time stamp update to files on Isilon as on source files. The isi_vol_copy messes up the create date also let alone the access time. Does anyone had any success in copying access time of files to Isilon cluster ?
1753
0
Posted February 24th, 2014 17:00
Thanks for information on access time tracking. The file birth time issues is not recorded on 7.0.2.5 release notes and there are lot many other issues with isi_vol_copy command. Another disadvantage is it does not provide any count of number of folders/files it has copied. Has to rely on other tools to get accurate file and folder counts. Also it does not appear to be copying access time either. I'm still in search of a tool which can do the copy of file metadata correctly.
1753
0
Posted February 26th, 2014 13:00
What was the exact problem with robocopy?
1753
0
Posted February 27th, 2014 12:00
Robocopy works fine except that it will not copy "access" time of files and it is really slow even with Win2k8 /MT option. It is also not very good at copying special permission of files&folders especially if the sub folder NTFS permission is changed at the source.
1753
0
Posted February 28th, 2014 16:00
That's really interesting as it's the first I've heard of that. I used robocopy in coordination with isivolcopy to move ~800TB for a customer last year.
I'm assuming you have run as root in play on the shares per the BP for SMB migrations?
325
0
Posted October 30th, 2014 15:00
Customer stated “I know how to view and enable atime on Windows and Isilon and it is enabled and set to 1 hour, the problem is when my end user migrates from VNX to Isilon using EMcopy, the access time does not stay synced and carry over. The access time on the Isilon reflects the last modified timestamp instead.”
Ryan Mulcahy TSE
1753
0
Posted October 30th, 2014 15:00
Check and see if the Isilon is set to track atime. I think by default it is not. Many use cases do not require atime tracking and so you get a performance boost by not tracking it (you save a metadata update on every read).
-- Adam Fox
Advisory SE, Emerging Technology Division
1753
0
Posted October 30th, 2014 15:00
I am also running into similar issue:
# emcopy64 source dest /purge /s /sdd /xd Folders /d /secforce /o /r:0 /c /log:.\log.txt /th XX
So I have file1 on VNX I want to migrate to Isilon, The atime shows on VNX say Sept 1st, the modified date shows Sept 20th. when I migrate file1 to Isilon and look at the atime, it shows Sept 20th instead of Sept 1st.
keo_emc
3 Posts
1753
0
Posted February 24th, 2014 12:00
Access Time Tracking is for SmartPools policies not updating the access time on files.
Per your other post, there was a create time / birth time issue with isi_vol_copy in earlier versions of code and may be causing some of your troubles from your production cluster.
Check the release notes for 7.0.2.4 and 7.0.2.5.