Veritas™ Access 7.2

Veritas Access provides a scale-out file system that manages a single namespace spanning over on-premises storage and cloud storage, which provides better fault tolerance for large data sets. Currently a scale-out file system can hold up to 266 TB. Unlike a standard file system, a scale-out file system is Active/Passive, which means that the file system can be online on only one node of the cluster at a time. A scale-out file system is always active on the node where its virtual IP address is online. A virtual IP address is associated with a scale-out file system when the file system is exported.

Veritas Access only supports access to scale-out file systems using NFS-Ganesha. NFS shares that are created on scale-out file systems must be mounted on the NFS clients using the virtual IP address that is associated with the NFS share.

A scale-out file system is structured as a layered file system that includes a set of storage containers. The data that is stored in the cloud (Amazon S3) can be one of the storage containers. One of the storage containers stores the metadata and the other containers store the actual data. This data can be on-premises or can be in Amazon S3. This modular structure allows the scale-out file system to be more resilient in cases where high capacity or fault tolerance is needed. A scale-out file system accomplishes this without compromising on file system performance.

See Characteristics of a scale-out file system

You can configure Amazon S3 as a cloud container. Amazon S3 is the only supported cloud provider. Data can be moved between the on-premises container and the cloud container.

Scale-out file system specifications:

  • Twenty percent of a scale-out file system's size is devoted to the metadata container. The maximum size of a metadata container is 10 TB.

  • You can resize (grow) a scale-out file system up to 266 TB.

  • The minimum size of a scale-out file system is 10 GB.

Veritas™ Access 7.2

Veritas Access provides a scale-out file system that manages a single namespace spanning over on-premises storage and cloud storage, which provides better fault tolerance for large data sets. Currently a scale-out file system can hold up to 266 TB. Unlike a standard file system, a scale-out file system is Active/Passive, which means that the file system can be online on only one node of the cluster at a time. A scale-out file system is always active on the node where its virtual IP address is online. A virtual IP address is associated with a scale-out file system when the file system is exported.

Veritas Access only supports access to scale-out file systems using NFS-Ganesha. NFS shares that are created on scale-out file systems must be mounted on the NFS clients using the virtual IP address that is associated with the NFS share.

A scale-out file system is structured as a layered file system that includes a set of storage containers. The data that is stored in the cloud (Amazon S3) can be one of the storage containers. One of the storage containers stores the metadata and the other containers store the actual data. This data can be on-premises or can be in Amazon S3. This modular structure allows the scale-out file system to be more resilient in cases where high capacity or fault tolerance is needed. A scale-out file system accomplishes this without compromising on file system performance.

See Characteristics of a scale-out file system

You can configure Amazon S3 as a cloud container. Amazon S3 is the only supported cloud provider. Data can be moved between the on-premises container and the cloud container.

Scale-out file system specifications:

  • Twenty percent of a scale-out file system's size is devoted to the metadata container. The maximum size of a metadata container is 10 TB.

  • You can resize (grow) a scale-out file system up to 266 TB.

  • The minimum size of a scale-out file system is 10 GB.