About the Data Migration utility


About the Data Migration utility

The Data Migration utility lets you migrate data from a source (non-FileStore) system to a FileStore system with minimal user intervention.

Data migration supports multiple and simultaneous tasks, with each migration process being a single task. While the data migration process is active, the non-FileStore source file system is available to clients. For data consistency, the source file system should be in Read Only mode during the final migration.

To access data on the source file system, FileStore acts like an NFS client. FileStore performs an NFS import on the source file system to the FileStore system.

Data is migrated from the source system to the local file system using RSYNC, a software application for synchronizing files and directories for UNIX systems.

During the initial run, the entire contents of the source file system are copied. For the first run, Symantec recommends using an empty file system for the destination file system or directory. After the initial run, if there are any changes to the source, you can migrate the data again. RSYNC checks the content on the source files system on FileStore and then only copies the deltas.

Data migration process status is based on the number of files transferred, not on the size of the files. Once all the files are transferred, the migration task ends.

To set up data migration, you configure a set of migration units to migrate data from one directory to another. A migration unit is defined as an ordered set of entries, and each entry type is a directory with a full pathname. In FileStore, full pathnames begin with the file system name.

Entry numbers (1 entry) in a migration unit must match exactly between remote and local migration units.

Remote Migration Local Migration    
Unit             Unit            Example
================ =============== =========================================                
1 entry          1 entry         /share/dir1             fs0/dir2


Before you configure data migration, make sure that the destination file system has enough disk space to store the migrated data. For migration purposes, the destination file system should have 10 percent more disk space than the disk space required to store the source data. In addition, if you use Dynamic Storage Tiering (DST), make sure that the destination file system has enough space to store the data migrated from source files in the primary tier.

The following are FileStore CLI commands for managing data migration tasks from a non-FileStore source system to a FileStore system:

  • Storage> migrate list

  • Storage> migrate status

  • Storage> migrate add

  • Storage> migrate delete

  • Storage> migrate start

  • Storage> migrate stop

Table: Migration states




The task is created and ready to run.


The task is running.


The task has completed the latest run.


The task is stopped for the latest run.


The resources that are used by the task were not available when the task was created.

Terms of use for this information are found in Legal Notices.



Did this article answer your question or resolve your issue?


Did this article save you the trouble of contacting technical support?


How can we make this article more helpful?

Email Address (Optional)