Veritas Access Online Help
- Getting started
- About Veritas Access
- Enabling certificate-based authentication in Veritas Access
- About the dashboard
- Setting up the storage type for provisioning
- About the CIFS shares
- About managing CIFS shares for Enterprise Vault
- About the NFS shares
- About an iSCSI target
- Creating an iSCSI target and provisioning LUNs
- About S3 buckets for NetBackup
- Using the Veritas Access product documentation
- Changing your password
- Important release information
- Managing storage
- About storage provisioning and management
- Adding disks to a storage pool
- Removing disks from a storage pool
- Removing disks from a cluster
- Viewing information about disks
- Accessing disk details
- Adding or removing a node
- Viewing information about a node in a cluster
- Accessing node details
- Configuring a disk
- Increasing the size of a disk
- Running scanbus
- Formatting a disk
- Marking a disk as spare
- About SmartIO for solid-state drives
- About storage provisioning and management
- Managing file sharing services
- Monitoring and troubleshooting
- Provisioning and managing file systems
- About scale-out file systems
- Generating the long-term data retention script
- Creating a file system
- Setting the maximum IOPS
- Creating a snapshot
- Restoring a snapshot
- Configuring a replication job
- Stopping or starting a replication job for VVR
- Pausing and resuming a replication job for VVR
- Enabling or disabling a replication job for VFR
- Synchronizing a replication job for VFR
- Failing over or failing back a replication job for VVR
- Failing over or failing back a replication job for VFR
- Unconfiguring a replication job for VFR
- Unconfiguring a replication job for VVR
- Viewing the list of iSCSI targets
- Adding an initiator for an iSCSI target
- Removing an initiator for an iSCSI target
- Adding portal IPs for an iSCSI target
- Setting up authentication for an iSCSI target
- Viewing the list of initiators for an iSCSI target
- Viewing the portal IPs for an iSCSI target
- Removing portal IPs for an iSCSI target
- Removing authentication settings for an iSCSI target
- Removing an iSCSI target
- Removing the file system store for an iSCSI target
- Viewing the list of LUNs for an iSCSI target
- Creating a LUN for an iSCSI target
- Increasing the size of a LUN for an iSCSI target
- Reducing the size of a LUN for an iSCSI target
- Removing a LUN for an iSCSI target
- Cloning a LUN for an iSCSI target
- Creating a snapshot of a LUN for an iSCSI target
- Viewing the list of snapshots for an iSCSI target
- Removing a LUN snapshot
- Restoring a LUN snapshot
- Provisioning and managing shares
- About file sharing protocols
- About concurrent access
- About concurrent access with NFS and S3
- Sharing directories using CIFS and NFS protocols
- Adding a share
- NFS protocol options
- CIFS protocol options
- About buckets and objects
- About Active Directory (AD)
- Logging on as an active directory user
- Creating access and secret keys for an active directory user
- Exporting an NFS share as an S3 bucket
- Viewing information about a share
- Accessing share details
- Configuring a favorite share
- Deleting a share
- Managing permissions for CIFS shares
- Managing clients for the NFS shares
- Managing policies
- About policies for storage provisioning
- About policies for long-term data retention
- About policies for archiving data using Enterprise Vault
- About policies for file systems
- About pattern matching for data movement policies
- Viewing information about policies
- Activating storage policy templates
- Activating long-term data retention policies
- Activating archival policies
- Creating an S3 bucket
- About cloud-storage tiering
- Adding a cloud tier for a scale-out file system
- About tiering policies
- Adding a secondary tier
- Viewing information about the secondary tier
- Adding or editing a tier policy on a secondary tier
- Creating a policy schedule
- Managing settings
- Viewing Veritas Access settings
- About the cloud gateway
- Viewing information about cloud services
- Adding and removing a cloud service
- Viewing discovery information about your cluster
- About the Lightweight Directory Access Protocol
- Configuring LDAP
- Configuring Active Directory
- About user management
- Managing local users
- Configuring the NTP server
- Starting or stopping the CIFS or NFS servers
- Starting or stopping the S3 server
- Adding or removing storage pools for S3 users
- Configuring the /etc/hosts file for mapping of S3 users
- Switching between NFS servers
- Accessing the RESTful APIs
- Registering a NetBackup master server or an EMM server
- Modifying a NetBackup media server list
- Viewing information about your NetBackup configuration with Veritas Access
- About cluster management
- Setting up the time and the time zone for the cluster
- About replication
- Viewing information about events
- Purging events
- About Veritas Access product licensing
- Configuring SmartIO
- Viewing information about SmartIO
- Setting object server default parameters
- Setting up the object server group-specific parameters
- Viewing information about S3
- About IP load balancing
- Configuring the KMS server
- About the CIFS service management
- Setting up the home directory
- About the File Transfer Protocol
- About Veritas Data Deduplication
- About alert management
- Index
About SmartIO writeback caching for applications running on Veritas Access file systems
Veritas Access supports writeback caching on solid-state drives (SSDs) for applications running on Veritas Access file systems. In this scenario, application reads and writes are satisfied from the cache whenever possible.
SmartIO provides write caching in the writeback mode. In writeback mode, an application write returns success after the data is written to the SmartIO cache, which is usually on an SSD. At a later time, SmartIO flushes the cache, which writes the dirty data to the disk. Writeback caching expects to improve the latencies of synchronous user data writes. Write order fidelity is not guaranteed while flushing the dirty data to the disk.
Writeback caching is superset of read caching. When writeback caching is enabled, read caching is implicitly enabled. Reads are satisfied from the cache if possible, and the file system transparently loads file data into the cache. Both read and writeback caching may be enabled for the same file at the same time.
The writeback caching mode gives good performance for writes, but also means that the disk copy may not always be up to date. If a cache device fails, a file that is cached in writeback mode may not be completely present on the disk. SmartIO has a mechanism to flush the data from the cache device when the device comes back online. Veritas Access provides additional protection from data loss with cache reflection. Cache reflection is enabled by default.
Writeback caching requires a cluster with exactly two nodes. Writeback caching cannot be enabled if the cluster has more than two nodes or if the cluster has a single node.
When writeback caching is enabled, SmartIO mirrors the writeback data at the file system level to the other node's SSD cache. This behavior, called cache reflection, prevents loss of writeback data if a node fails. If a node fails, the other node flushes the mirrored dirty data of the lost node as part of reconfiguration. Cache reflection ensures that writeback data is not lost even if a node fails with pending dirty data.
After writeback caching is enabled on the mount point, the qualified synchronous writes in that file system are cached. SmartIO determines if a write qualifies for writeback caching, using criteria such as the following:
The write request must be PAGESIZE aligned (multiple of 4 KB).
The write request is not greater than 2 MB.
The file on which the writes are happening is not mapped.
Writeback caching is not explicitly disabled by the administrator.
Writeback caching is not qualified if the cluster has more than two nodes.