Universal Migrator is a new licensed migration feature built in to HNAS release 11.3 that allows for easy and minimally disruption migration to HNAS from a 3rd party NFSv3 NAS server. See the comments section for an update about atime.
Good Sharing Francisco Salinas.. Keep up the Good Work.
How are atime, ctime and mtime handled?
ctime and mtime are preserved through the whole virtualization/migration process. Note: if a client makes a change to a file, then its mtime will be updated as would be expected.
HNAS preserves atime during the virtualization phase i.e. performing virtualization will not alter the atime on the LNAS.
atime will be updated during the migration phase provided atime maintenance is enabled on the source LNAS and the destination HNAS file system. In some cases, this may not be desired. To prevent atime changes on the HNAS file system, disable atime on the destination HNAS file system. atime can be enabled after all migrations to that file system are completed.
If atime will be used as a criteria for HNAS Data Migrator (file tiering) then it would be advisable to disable atime on the destination HNAS file system until all migrations for that file system have been completed.
Good morning Francisco - the pre-HUM (is that the right acronym?) method of migrating data often entails using rsync from the legacy product. This throws off the atimes and makes subsequent use of HCP very difficult. Since the data was touched by rsync it is "new" and does not meet the customer-defined aging requirements to get archived off. Does your method of disabling atime on the source/destination help with this as well?
When I tested it, disabling atime maintenance resulted in no atime changes after migration with Universal Migrator (UM).
Retrieving data ...