Skip to main content

We've Moved!

Product Documentation has moved to docs.hitachivantara.com
Hitachi Vantara Knowledge

Viewing data migration paths

You can view the data migration paths in the NAS Manager.

  1. Navigate to Home Storage Management Data Migration Paths.

    GUID-CC40944F-FEB0-439A-BEB4-918F6FB0C8B0-low.png

    The following table describes the fields on this page:

    Field/Item Description
    Primary File System The file system from which data will be migrated.
    Primary Virtual Volume If a virtual volume has been selected as primary storage, this field displays the name of the virtual volume from which data will be migrated.
    Secondary Target Type Destination target to which the data will be migrated.
    Secondary File Systems Displays the secondary file system.
    EVS The EVS hosting the file system from which data will be migrated.
    Status Status of the data migration path. The status should always be OK; if otherwise, migrated files might be inaccessible.
    details Displays the details of the selected data migration path.
    Add WFS/HNAS Path Displays the Add WFS/HNAS Path page.
    Add Cloud Path Displays the Add Cloud Path page.
    delete Deletes the specified migration policy.
    Policies and Schedules Displays the Data Migration page.
    Data Migration Rules Displays the Data Migration Rules page.
    Data Migration Cloud Accounts Displays the Cloud Accounts and Destinations page.

Configuring Data Migrator paths

There are different types of paths between primary and secondary storage.

  • Primary storage (typically Fibre Channel disk arrays) is the source for data migrations.
  • Secondary storage (typically SATA disk arrays) is the target for data migrations. Note that there are two types of paths to secondary storage:
    • Local paths - these are paths to secondary storage attached to the same EVS, storage server, or cluster. Local paths can be added using the NAS Manager.
    • External Paths - these are paths to secondary storage that is attached to a remote server (a NAS Platform, or another server using the NFS protocol, or a Hitachi Content Platform using the HTTP protocol). External paths cannot be added using the NAS Manager. Instead, you must use CLI commands.

After Data Migrator has been configured, data is migrated from primary to secondary storage based on the data migration rules and schedules, freeing up space and extending the capacity of the primary storage.

CautionDysfunctional backups alert! Accessing files directly on secondary storage might alter access and modification times of the files, resulting in unexpected results when performing backups. The organizational structure of migrated data on secondary storage does not mirror that of primary storage.
CautionLost access to migrated files alert! If only the primary or only the secondary file system is moved to a different EVS, access to migrated files will be lost. If both the primary and the secondary file systems are moved to the same EVS, access to migrated files will be retained. When moving file systems, File System Relocation is the recommended method, because, when using File System Relocation, if the file system being moved is a member of a data migration path, both the data migration source file system and the target file system are relocated. See the File Services Administration Guide for more information.
CautionExclusive migration pathing! Once a migration path has been assigned to a virtual volume, a subsequent migration path cannot be created to its hosting file system. Also, once a migration path has been assigned to a file system, subsequent migration paths cannot be created from virtual volumes hosted by that file system.
NoteWhen defining data migration paths, specify a file system or virtual volume as the primary storage. Once a file system is selected as primary storage, that entire file system, including all virtual volumes is included as a part of the data migration policy. Therefore, in order to create individual policies for different parts of a file system, create virtual volumes and assign each virtual volume a unique migration path.

Adding a local WFS/HNAS data migration path

You can add a data migration path in the NAS Manager.

  1. Navigate to Home Storage Management Data Migration Paths.

  2. Click Add WFS/HNAS Path.

    GUID-56877650-DF91-44EE-9411-FE03C5B2849A-low.png

    The following table describes the fields on this page:

    Section Item/Field Description
    Primary EVS/File System The EVS and file system of the primary storage. This defines the source of the data migration path. To change the currently selected EVS and file system, click change....
    Virtual Volume By default, data migration policies include the entire file system. To configure migrations on a per virtual volume basis, fill this check box and select the virtual volume to be used as the primary storage for this data migration path.
    Secondary Available File systems to which the data will be migrated (the destination file system). Select the destination file system from the list. The file systems you select should be on secondary storage.
    Note When creating a policy for testing purposes, select "None (Test Only)." Running this policy will then determine the outcome of the migration operation without actually moving data.

    In most cases you should specify a single destination file system to create a "single-target" migration path. However, if the amount of data is too large for a single target file system, you may want to nominate multiple file systems as targets to create a "multi-target" migration path.

    For "multi-target" migration paths, you should be aware of the following:

    • Data is distributed between the destination file systems based on the amount of free space available on those file systems. If the destination file system is expandable, the data distribution algorithm calculates free space not based on the file system's current size, but on the maximum size to which a file system can be expanded.

    • Once specified, multi-target paths may not be modified through NAS Manager. If you need to change the migration path targets, for instance to add an additional destination file system, you must use the migration-expand-target command through the CLI.

    NoteWe can add a path for an internal migration through NAS Manager. For external migrations, use the following CLI command: migration-add-external path -s Source_File_Name -n Logic_Name -t nfs://EVS-IP_Target/Export_Name_Target.
    Selected

    The file systems selected to be the destination of the migration.

  3. Select the primary file system or virtual volume whose data will be migrated to a file system in secondary storage. Ensure that both the primary and secondary data belong to the same EVS.

  4. Verify your settings, then click OK to save or cancel to decline.

About external data migration paths

External data migration paths are not defined through NAS Manager. Instead, CLI commands are used to specify the path to external secondary storage. These commands are:

  • migration-add-external-path
  • migration-change-external-path
  • migration-delete-external-path
  • migration-expand-external-path

For information about these commands, refer to the Command Line Reference, or the man page for each command.

You should specify a unique external path for each file system being migrated to a remote server.

After an external migration path has been defined, it will be visible and available for selection in the NAS Manager Data Migration Paths page.

NoteDo not define an external migration path from one EVS in a cluster to another EVS in the same cluster. The reason for this restriction is that it would be dangerous to try to migrate from one EVS of a cluster to another EVS of the same cluster. If the destination (target) EVS fails during the migration, it could fail over to the same node as the source EVS, which would cause all the migrated files to become inaccessible.

After the external migration path has been configured using the CLI, all remaining external migration management tasks may be performed through NAS Manager, including specifying migration policies, rules, and schedules.

NoteWhen adding external migration paths, make sure that the remote server's IP address or host name is correct and, if using a host name, make sure that the host name is resolvable (fully qualified domain names are also acceptable).

 

  • Was this article helpful?