Following are limitations in VAST Cluster 5.0.0-SP11:
Quotas
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.ORION-179496: NFS aliases are not supported with VAST Cluster's implementation of Remote Quota Protocol (
rquota).
Quality of Service
ORION-148295: QoS should be enabled on all views to avoid performance degradation issues.
ORION-148206: There may be some scenarios in which minimum service levels set by QoS policies are not met.
ORION-139524: Setting sa minimum limit for read operations does not limit write operations on the same view.
QoS provisioning is not supported for S3 clients.
User QoS feature is supported for NFS clients only.
NFS
ORION-115336: If one creates an NFSv4.1-only view and mount it, and then creates its parent view with NFSv3 only, IO operations on the NFSv4.1-only view succeed but mounts are not allowed.
NFSv3
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.
SMB
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.
S3
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.
VAST Catalog
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.
Global Snapshot Clones
This release does not support global snapshot clones with VAST Catalog enabled.
Multi-Cluster Management
The Multi-Cluster Management feature requires that each cluster participating in the inter-connection is running VAST Cluster 5.0.
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 (
.png?sv=2022-11-02&spr=https&st=2026-02-09T16%3A22%3A04Z&se=2026-02-09T16%3A37%3A04Z&sr=c&sp=r&sig=5ChDc9YaAQ%2FVGxDxdyFeQIx4gmHTHSTl5QazObvpOak%3D)
)), the VoC cluster is terminated. There is no option to remove a VoC cluster from Multi-Cluster Manager without also terminating it. (In the Multi-Cluster Management page in the VAST Web UI the button removes the VoC cluster from Multi-Cluster Management 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 Management instance.
Authentication & Authorization
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.
The following limitations apply to Multi-Forest Authentication:
VAST Cluster does not allow adding two different Active Directory configuration records with the same domain name but different settings for multi-forest authentication and/or auto-discovery.
Names of users' domains are not displayed in data flow analytics.
If a trusted domain becomes unavailable and then recovers, SMB clients can use it to connect to the VAST cluster only after a period of time, but not immediately upon domain recovery.
Clients cannot establish SMB sessions immediately after a trusted domain recovers from a domain failure.
If a group exists on an Active Directory domain in a trusted forest and the group scope is defined as DomainLocal, VAST Cluster does not retrieve such a group when querying Active Directory, so members of such a group are denied access despite any share-level ACLs that can rule otherwise.
If TLS is enabled, the SSL certificate has to be a CA-signed certificate that is valid for all of the domain controllers in all trusted forests. If the certificate is not valid for a domain controller, this domain controller is not recognized.
ORION-156168: In a multi-forest environment, after migrating a group account from the forest of the cluster’s joined domain to another forest, information about historical group membership is not kept, so users in the migrated group might not be able to access resources to which they used to have access prior to the migration.
VAST Prometheus Exporter
With VAST Cluster 5.0 and 4.7, the Prometheus exporter script at https://github.com/vast-data/vast-exporter is no longer supported. Instead, use the following the VAST API endpoints:
https://<VMS IP>/api/prometheusmetrics/https://<VMS IP>/api/prometheusmetrics/allhttps://<VMS IP>/api/prometheusmetrics/usershttps://<VMS IP>/api/prometheusmetrics/defraghttps://<VMS IP>/api/prometheusmetrics/viewshttps://<VMS IP>/api/prometheusmetrics/deviceshttps://<VMS IP>/api/prometheusmetrics/quotas
Call Home & Support
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.