Limitations in 5.1.0-SP6

ORION-208873: Quotas and quota accounting are not supported on subpaths of a replicated protected path on the destination peer. For example, if a protected path is replicated to a destination directory /dest-dir, you cannot set a quota on /dest-dir/mydir.

(RESOLVED IN 5.2.1) ORION-219500: When retrieving quotas through the NFS Remote Quota protocol (rquota), the maximum quota size that can be retrieved is 16TB.

(RESOLVED IN 5.3.0) ORION-179496: NFS aliases are not supported with VAST Cluster's implementation of Remote Quota Protocol (rquota).

(RESOLVED IN 5.2.0) ORION-165483: When a user QoS policy is set to limit both bandwidth and IOPS, the sum of write metrics on two views accessed by this user can be much lower than the policy limit.

ORION-148295: QoS should be enabled on all views to avoid performance degradation issues.

ORION-115336: If one creates an NFSv4.1-only view and mounts it, and then creates its parent view with NFSv3 only, IO operations on the NFSv4.1-only view succeed but mounts are not allowed.

ORION-158953: NFSv4.2 security labels are not available in VAST Catalog.

In rare cases with large numbers of files and directories, the existence of a view with Global Synchronization enabled under a protected path can block the removal of the protected path.

ORION-169707: When the Hyper-V management tool tries to list VAST Hyper-V SMB shares on an SMB server, the The RPC server is not available error can occur if the SMB server is specified using its FQDN. To avoid this error, specify the IP address of the SMB server instead of the FQDN.

ORION-160323: After updating permissions for an SMB share in Windows Explorer, a duplicate SMB share can be displayed. The duplicate SMB share disappears upon a refresh (F5).

(RESOLVED IN 5.2.0) ORION-130460: VAST Cluster does not show any previous versions for a file or directory that has the same name as a file or directory that has been deleted and resides in the same directory as the deleted file or directory.

ORION-134730: An attempt to restore a file can fail if after the restore has started, a quota is set on the path where the file resides.

(RESOLVED IN 5.2.0) ORION-137905: If an application saves changes to a file by recreating the file, or when the client otherwise deletes a file or a directory and creates a new one with the same name, no previous versions can be displayed for the file or directory. To restore such a file or directory, you need to restore one of its parent directories.

An object to be uploaded via a S3 presigned POST request must have only ASCII characters in its name.

A POST policy (used for S3 presigned POST requests) can be up to 4800 bytes.

(RESOLVED IN 5.2.0) ORION-175401: If a user gets renamed, for example by editing the user name in VAST Web UI, the identity policy attached to the user would still show the old user name.

ORION-190674: Once created, an S3 bucket cannot be renamed or moved to a different path. Thus, for example, if you try to change the bucket’s path when modifying a view in VAST Web UI, the change does not take effect and the view will still be listed with the old path.

ORION-143808: S3 versioning is not supported with global snapshot clones. An attempt to put a versioned object to a bucket at the global snapshot's destination path fails with an internal error.

(RESOLVED IN 5.3.3) ORION-211474: The Create permissions for the Logical realm are required to access the VAST Audit Log via VMS (in VAST Web UI: DataBase -> VAST Audit Log).

ABAC is supported on views controlled with SMB and Mixed Last Wins security flavors.

ABAC is not supported with NFSv3 and S3.

(RESOLVED IN 5.2.0) ORION-167553: ABAC tags are case-sensitive. For example, tags AB and ab are considered different values, which may cause permission deny errors for the users.

(RESOLVED IN 5.2.0) ORION-166268: If a user is assigned ABAC attributes that allow read/write access to an ABAC-tagged view but the associated view policy sets All Squash for the host, the host would encounter a Permission Denied error when trying to list files and directories on the view.

ORION-163697: When an SMB user accesses a file for which the user has ABAC set to read-only, a lock is placed on the file although the user does not have read/write permissions for the file.

The maximum path length supported by VAST Catalog is 1024 characters.

When VAST Catalog is enabled, replication is limited to two peers (group replication is not supported with VAST Catalog). 

VAST Catalog must be disabled before a protected path can be deleted. 

(RESOLVED IN 5.3.0) ORION-206485: User-defined row IDs can be set through the VAST Connector only. Setting row IDs in VAST Web UI or VAST CLI is not supported.

(RESOLVED IN 5.2.0) ORION-189068: Managed applications cannot be created if the number of CNodes in the cluster is 2 (two) or less.

Having Global Access and replication on the same path is not supported.

Lease expiration time can only be set when creating a global access protected path. You cannot change lease expiration time when you modify a global access path.

(RESOLVED IN 5.3.0) ORION-164710: When making capacity estimations for a directory, remote files and subdirectories are not taken into account. This means that in some cases, e.g. if local and remote capacity figures differ significantly and the remote capacity amounts to a significant portion of the overall capacity, the reported capacity and data reduction estimations can be skewed and would not reflect the real data reduction.

For example, if a parent directory contains one subdirectory with file1 and file2, each of 2GB in logical capacity and 1GB in physical capacity, and another subdirectory with remote files file3 and file4, each of 100GB logical capacity and 100GB physical capacity, VAST Cluster would show the parent directory's data reduction ratio of 2:1, while the real ratio would be closer to 1:1.

VAST Dataspace requires that each cluster participating in the inter-connection is running VAST Cluster 5.0 or later.

ORION-146276: The ability to select multiple rows and perform bulk actions on them is disabled in VAST Dataspace grids in VAST Web UI.

ORION-135966: The inter-connecting clusters must have connectivity to each other through the clusters' management networks.  

ORION-132073: When you remove a VoC cluster from a Multi-Cluster Manager cloud service instance (using the removal button on the cluster's card ()), the VoC cluster is terminated. There is no option to remove a VoC cluster from Multi-Cluster Manager without also terminating it. (In the VAST Dataspace page in the VAST Web UI, the button removes the VoC cluster from VAST Dataspace and does not terminate it.)

ORION-137875: In case of Multi-Cluster Manager failure, VoCs provisioned by the instance cannot be connected to a Multi-Cluster Manager instance.

ORION-145141: Creating a tenant with EKM encryption is not supported on VoC clusters.

ORION-113036: After you reregister the same VoC cluster in Uplink, information about the previously registered instance of this cluster is no longer available in Uplink.

ORION-143944: When using Kerberos/NTLM Authentication to authorize SMB users from non-trusting domains, the DOMAIN\username format cannot be used to specify users of remote domains. The username@domain format must be used instead.

ORION-134299: When the tenant is set to use Kerberos/NTLM authentication to authorize SMB users from non-trusting domains, both NFS and SMB must use the native SMB authentication (Kerberos), and not Unix-style UID/GIDs.

ORION-141763: Before enabling or disabling NTLM authentication, you need to leave the cluster's joined Active Directory domain. After NTLM authentication is enabled or disabled, rejoin the domain.

(RESOLVED IN 5.2.0) ORION-138793: After you disable use of Kerberos/NTLM Authentication to authorize users from non-trusting domains (e.g. turn off the Use native SMB authentication option in VAST Web UI tenant settings), users that previously had access, would still have access although the feature is now disabled.

The following limitations apply to Multi-Forest Authentication:

The DBox HA feature cannot be enabled on new installations of VAST Cluster 5.1.

(RESOLVED IN 5.1.0-SP56) ORION-223443 Root permissions are required to establish an SSH connection by node name.

When creating a support bundle with the METADATA preset, only one CNode can be selected for the bundle. Selecting any DNode(s) or multiple CNodes together with the METADATA preset results in an error.