Skip to main content

We've Moved!

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

Troubleshooting Hitachi NAS Universal Migrator

This section provides common problems and solutions.

Cannot create associations

Cannot create associates, as the remote server is inaccessible. For example:

mercury2n3(HNAS-4100):$ virtualization-path-create -t HNASfs -n demo_assoc -s nfs://mercuryc5/LNAS

Create virtualization path failed: The remote server is inaccessible

Additional information: NFS Status: RemoteTimeout

[virtualization-path-create took 30 s.]

  • Try with IP address rather than hostname, and/or check the DNS settings of your network.
  • Use remote-nfs-exports on the HNAS console to show what exports are available to the HNAS from the LNAS.

Hitachi NAS Universal Migrator associations paused

When using the virtualization-path-control command, the pause completes successfully, but the counts shown by the virtualization-path-list command are still seen to change.

This is because it is necessary to complete processing the objects that are currently being operated on before stopping work. If a directory is being virtualized that contains many entries, this may take some 10s of seconds.

Virtualization or migration does not complete

  1. Check the virtualization-path-list command to see if there are any failed files.

    NoteThe virtualization-path-files command could take some time to complete.
  2. Check the event log. The migration may not have completed due to insufficient space on HNAS, in which case it will pause and there will be no failed files.

  3. If step 1 shows failed files, identify the problematic files with the virtualization-path-files command.

    1. virtualization-path-files Inspect the files on the LNAS to ensure that they are correct in that file system.

    2. Use remote-nfs-errors to gain insight as to why they may have failed.

    3. virtualization-path-files --list-failed may just show "/" (that is, root).

  4. Fix problems, if they are not obvious, then the following strategies should allow you to continue.

    1. For failed files during virtualization, move the failing file out of the exported directory on the LNAS. Manually copy it over to the HNAS.

    2. For failed files during migration, remove the failing file from the HNAS. Manually copy the LNAS version of the file over to the HNAS.

  5. Once you think that you have fixed the problems use the virtualization-path-files command to retry the failed files.

    It is recommended that if it is only virtualization that has failed and migration has not been started, it may be simplest to delete the virtualization path and start again - all data is still contained on the LNAS at this point.

 

  • Was this article helpful?