Setting up LNAS and HNAS for virtualization

Data Migrator Administration Guide for Hitachi NAS Platform

Part Number

Before using the Hitachi NAS Universal Migrator, you must prepare the systems by associating the HNAS to the LNAS. The following steps describe this process. Note that your preparation must use the device names and IP addresses of your actual system.

Assuming a legacy NAS device with hostname LNAS at IP address, exporting a directory existing_data_dir as existing_export using NFSv3. The LNAS is configured such that a sub directory .snapshot exists in the root of existing_data_dir, to allow browsing of snapshot data.

  1. Create a file system, <hnasfs>, using storage appropriate to contain the data set to be migrated from the LNAS.
  2. Create NFS exports to the file system, and any other HNAS configuration, as necessary. The directory on the HNAS file system that will be the root of the association must be empty.
    If you want to create exports within the root of the association, uncheck the Create path if does not exist checkbox on the SMU. If you use the CLI , use the nfs-export add command with the -i and -d (DONTCREATE) options for example, nfs-export add -i -d source_root/data1 FS1 /source_root/data1. This will ensure the root of the association remains empty until the virtualization starts.
  3. Add a new IP address to the LNAS, which the HNAS will use for the migration (assuming the LNAS's existing IP address will move to the HNAS when it is introduced into the environment).
  4. Create the association, <assoc1> at the HNAS console, using the following commands:
    virtualization-path-create -t <hnasfs> -n <assoc1> -s nfs://lnas/existing_export

    This can be modified if necessary using the following command:

    Note: This command cannot be used after issuing:

    virtualization-path-control -t <hnasfs> -n <assoc1> --start

    When the association has been created, virtualization-path-list will show Seen Dirs as 1, which is the root of the LNAS export.
  5. Add the .snapshot directory to the list of excluded directories for the association:
    virtualization-path-excluded-directory-add -t <hnasfs> -n <assoc1> -d .snapshot

    Again, this can be changed (virtualization-path-excluded-directory-list, virtualization-path-excluded-directory-delete) up to the point that virtualization-path-control -t hnasfs -n assoc1 --start is used.

  6. Prevent any further client access to the LNAS by renaming, or otherwise changing, the export. Ensure that existing export NFSv3 export is configured on the LNAS in such a way as to meet the suggested best practices. At this point all other methods for clients to directly connect to the LNAS should be disabled (for example, CIFS shares).
  7. If necessary, transfer IP addresses from the LNAS to the HNAS (apart from the one created in step 4).