Dell Unity™ Family VNX® Series Data Import to Unity All Flash or Hybrid, or UnityVSA™ System User Guide
Multiprotocol lock policy
You can migrate the lock policy for each file system from VNX to Unity.
This policy controls whether CIFS and NFSv4 range locks must be honored. In NFSv2 and NFSv3, the locking policies are advisory but not mandatory. If the locking policy is not defined, nolock is the default setting for VNX and mandatory is the default setting for Unity.
The following table describes NFS client policy locking rules for VNX:
| Locking policy | NFS clients |
|---|---|
| nolock (default) | This policy enables you to open and write to a file CIFS or NFSv4 clients have locked. |
| wlock | This policy enables you to read but not write data to a file that CIFS or NFSv4 clients have locked. |
| rwlock | This policy does not allow you to read or write data to a file that CIFS or NFSv4 clients have locked. |
VNX-to-Unity lock policy mapping
The following table describes lock policy-mapping rules when migrating from VNX to Unity:
| VNX | Unity |
|---|---|
| rwlock or wlock | mandatory (default)
This policy uses the SMB and NFSv4 protocols to manage range locks for a file that is in use by another user. If there is concurrent access to the same locked data, a mandatory locking policy prevents data corruption. |
| nolock (default) | Advisory
This policy reports that a range lock conflict when a request is made, but it does not prevent the access to the file. This policy allows NFSv2 and NFSv3 applications that are not range-lock-compliant to continue working, but risks data corruption if there are concurrent writes. |
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: <>()\