Dell Unity™ Family VNX® Series Data Import to Unity All Flash or Hybrid, or UnityVSA™ System User Guide
Importing VNX file systems with File Level Retention (FLR) enabled
Dell EMC Unity systems running OE version 4.5 or later support both FLR-E and FLR-C. When importing an FLR-enabled file system from a VNX system to a Dell EMC Unity system, ensure the Dell EMC Unity system is running operating environment (OE) version 4.5 or later.
NOTE: Dell EMC Unity systems running OE 4.4 or earlier do not support FLR, and the default import setting is to not import such file systems. However, you can override the default, and those file systems will be imported as normal target file systems (UFS64) without FLR protection. This means that after cutover, locked files can be modified, moved, or deleted on the target Dell EMC Unity system, but not on the source VNX system. This can cause the two file systems to be in an inconsistent state.
Limitations related to host access and NFS datastores
After cutover, for FLR-enabled file systems that are being imported from a VNX system, the host cannot set the Retention Period to a time between the source epoch year and 2017 that translates to a future time. The epoch year on Dell EMC Unity systems is permanently set to 2017.
NOTE: For example, if the source epoch year is 2003, do not set the atime to a time between 2003 and 2017. This is because any time between 2003 and 2017 translates to a future time that cannot be represented by the source epoch year 2003. The host can do that after the import session commits.
When performing a VDM import of FLR-enabled file systems to a Unity system, the source VNX Data Mover must be running the DHSM service for the import to succeed. Also, if the source DHSM service authentication is set to None, you do not need to configure the DHSM credentials, username and password, on the Unity system for import. However, if the source DHSM service authentication is set to either Basic or Digest, you must configure those credentials at the Unity system as part of the import configuration. If DHSM is not already configured on the source file system, refer to the VNX system's Unisphere online help or the VNX Command Line Interface Reference for File for information about setting up the DHSM configuration on the source VNX system.
Unity systems do not support FLR on NFS datastores. Therefore, VNX FLR-enabled file systems cannot be imported to Unity as NFS datastores. They can only be imported as file system objects.
NOTE: If the source VNX file system is FLR-enabled, you cannot change the target resource from a file system to an NFS datastore. This action is not allowed.
Port requirements for DHSM when FLR is enabled
The default DHSM service port is 5080 on both VNX and Unity systems. However, the VNX Data Mover (the physical Data Mover that hosts the VDM that is being imported) that is configured with the DHSM service can be set to a different port than the default. This port must match on both systems in order for the import of FLR-enabled file systems to succeed. To import FLR-enabled file systems when the source VNX Data Mover is using another port instead of the default, do one of the following before creating the file import:
- If possible, change the VNX Data Mover that is configured with the DHSM service to use the default port 5080.
- If the DHSM service port change cannot be made on the VNX system, on the Unity system use the
svc_nas service command to change the value of the
remoteDhmsPort parameter for the
imt facility to reflect the same DHSM service port as that set on the VNX.
NOTE: Changing the value of the remoteDhmsPort parameter requires a reboot of the storage processors on the Unity system so that the change takes effect.
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\