Veritas Access Administrator's Guide
- Section I. Introducing Veritas Access
- Section II. Configuring Veritas Access
- Adding users or roles
- Configuring the network
- About configuring the Veritas Access network
- About bonding Ethernet interfaces
- Bonding Ethernet interfaces
- Configuring DNS settings
- About the IP addresses for the Ethernet interfaces
- About Ethernet interfaces
- Displaying current Ethernet interfaces and states
- Configuring IP addresses
- Configuring Veritas Access to use jumbo frames
- Configuring VLAN interfaces
- Configuring NIC devices
- Swapping network interfaces
- Excluding PCI IDs from the cluster
- About configuring routing tables
- Configuring routing tables
- Changing the firewall settings
- IP load balancing
- Configuring authentication services
- Section III. Managing Veritas Access storage
- Configuring storage
- About storage provisioning and management
- About configuring disks
- About configuring storage pools
- Configuring storage pools
- About quotas for usage
- Enabling, disabling, and displaying the status of file system quotas
- Setting and displaying file system quotas
- Setting user quotas for users of specified groups
- About quotas for CIFS home directories
- About Flexible Storage Sharing
- Limitations of Flexible Storage Sharing
- Workflow for configuring and managing storage using the Veritas Access CLI
- Displaying information for all disk devices associated with the nodes in a cluster
- Displaying WWN information
- Importing new LUNs forcefully for new or existing pools
- Initiating host discovery of LUNs
- Increasing the storage capacity of a LUN
- Formatting or reinitializing a disk
- Removing a disk
- Configuring data integrity with I/O fencing
- Configuring ISCSI
- Veritas Access as an iSCSI target
- Configuring storage
- Section IV. Managing Veritas Access file access services
- Configuring your NFS server
- About using NFS server with Veritas Access
- Using the kernel-based NFS server
- Using the NFS-Ganesha server
- Switching between NFS servers
- Recommended tuning for NFS-Ganesha version 3 and version 4
- Accessing the NFS server
- Displaying and resetting NFS statistics
- Configuring Veritas Access for ID mapping for NFS version 4
- Configuring the NFS client for ID mapping for NFS version 4
- About authenticating NFS clients
- Setting up Kerberos authentication for NFS clients
- Using Veritas Access as a CIFS server
- About configuring Veritas Access for CIFS
- About configuring CIFS for standalone mode
- Configuring CIFS server status for standalone mode
- Changing security settings
- Changing security settings after the CIFS server is stopped
- About Active Directory (AD)
- About configuring CIFS for Active Directory (AD) domain mode
- Setting NTLM
- About setting trusted domains
- Specifying trusted domains that are allowed access to the CIFS server
- Allowing trusted domains access to CIFS when setting an IDMAP backend to rid
- Allowing trusted domains access to CIFS when setting an IDMAP backend to ldap
- Allowing trusted domains access to CIFS when setting an IDMAP backend to hash
- Allowing trusted domains access to CIFS when setting an IDMAP backend to ad
- About configuring Windows Active Directory as an IDMAP backend for CIFS
- Configuring the Active Directory schema with CIFS-schema extensions
- Configuring the LDAP client for authentication using the CLI
- Configuring the CIFS server with the LDAP backend
- Setting Active Directory trusted domains
- About storing account information
- Storing user and group accounts
- Reconfiguring the CIFS service
- About mapping user names for CIFS/NFS sharing
- About the mapuser commands
- Adding, removing, or displaying the mapping between CIFS and NFS users
- Automatically mapping of UNIX users from LDAP to Windows users
- About managing home directories
- About CIFS clustering modes
- About migrating CIFS shares and home directories
- Setting the CIFS aio_fork option
- About managing local users and groups
- Enabling CIFS data migration
- Configuring Veritas Access to work with Oracle Direct NFS
- About using Veritas Access with Oracle Direct NFS
- Best practices for improving Oracle database performance
- About the Oracle Direct NFS architecture
- About Oracle Direct NFS node or storage connection failures
- Configuring an Oracle Direct NFS storage pool
- Configuring an Oracle Direct NFS file system
- Configuring an Oracle Direct NFS share
- Configuring an FTP server
- About FTP
- Creating the FTP home directory
- Using the FTP server commands
- About FTP server options
- Customizing the FTP server options
- Administering the FTP sessions
- Uploading the FTP logs
- Administering the FTP local user accounts
- About the settings for the FTP local user accounts
- Configuring settings for the FTP local user accounts
- File sharing for a scale-out file system using FTP
- Configuring your NFS server
- Section V. Managing the Veritas Access Object Store server
- Section VI. Monitoring and troubleshooting
- Section VII. Provisioning and managing Veritas Access file systems
- Creating and maintaining file systems
- About creating and maintaining file systems
- About scale-out file systems
- Erasure coding in a cluster file system (CFS) for NFS use case
- About encryption at rest
- Considerations for creating a file system
- Best practices for creating file systems
- Choosing a file system layout type
- Determining the initial extent size for a file system
- About striping file systems
- About creating a tuned file system for a specific workload
- About FastResync
- About scale-out fsck
- Setting retention in files
- Setting WORM over NFS
- Manually setting WORM-retention on a file over CIFS
- About managing application I/O workloads using maximum IOPS settings
- Creating a file system
- Bringing the file system online or offline
- Listing all file systems and associated information
- Modifying a file system
- Managing a file system
- Destroying a file system
- Upgrading disk layout versions
- Creating and maintaining file systems
- Section VIII. Configuring cloud storage
- Configuring the cloud gateway
- Configuring cloud as a tier
- Configuring the cloud as a tier for scale-out file systems
- Moving files between tiers in a scale-out file system
- About policies for scale-out file systems
- Obtaining statistics on data usage in the cloud tier in scale-out file systems
- Workflow for moving on-premises storage to cloud storage for NFS shares
- Section IX. Provisioning and managing Veritas Access shares
- Creating shares for applications
- Creating and maintaining NFS shares
- About NFS file sharing
- Displaying file systems and snapshots that can be exported
- Exporting an NFS share
- Displaying exported directories
- About managing NFS shares using netgroups
- Unexporting a directory or deleting NFS options
- Exporting an NFS share for Kerberos authentication
- Mounting an NFS share with Kerberos security from the NFS client
- Exporting an NFS snapshot
- Creating and maintaining CIFS shares
- About managing CIFS shares
- Exporting a directory as a CIFS share
- Configuring a CIFS share as secondary storage for an Enterprise Vault store
- Exporting the same file system/directory as a different CIFS share
- About the CIFS export options
- Setting share properties
- Hiding system files when adding a CIFS normal share
- Displaying CIFS share properties
- Allowing specified users and groups access to the CIFS share
- Denying specified users and groups access to the CIFS share
- Exporting a CIFS snapshot
- Deleting a CIFS share
- Modifying a CIFS share
- Making a CIFS share shadow copy aware
- Creating CIFS shares for a scale-out file system
- Using Veritas Access with OpenStack
- Section X. Managing Veritas Access storage services
- Deduplicating data
- Compressing files
- About compressing files
- Use cases for compressing files
- Best practices for using compression
- Compression tasks
- Compressing files
- Showing the scheduled compression job
- Scheduling compression jobs
- Listing compressed files
- Uncompressing files
- Modifying the scheduled compression
- Removing the specified schedule
- Stopping the schedule for a file system
- Removing the pattern-related rule for a file system
- Removing the modified age related rule for a file system
- Configuring SmartTier
- About Veritas Access SmartTier
- How Veritas Access uses SmartTier
- Configuring the policy of each tiered file system
- Adding tiers to a file system
- Adding or removing a column from a secondary tier of a file system
- Configuring a mirror to a tier of a file system
- Listing all of the files on the specified tier
- Displaying a list of SmartTier file systems
- About tiering policies
- About configuring the policy of each tiered file system
- Best practices for setting relocation policies
- Relocating a file or directory of a tiered file system
- Displaying the tier location of a specified file
- About configuring schedules for all tiered file systems
- Configuring schedules for tiered file systems
- Displaying the files that may be moved or pruned by running a policy
- Allowing metadata information on the file system to be written on the secondary tier
- Restricting metadata information to the primary tier only
- Removing a tier from a file system
- Configuring SmartIO
- About SmartIO for solid-state drives
- About configuring SmartIO
- About SmartIO read caching for applications running on Veritas Access file systems
- Setting up SmartIO read caching for Veritas Access
- About SmartIO writeback caching for applications running on Veritas Access file systems
- Tuning the writeback caching
- Flushing dirty data from a writeback cache area
- Setting up SmartIO writeback caching for VxFS file systems
- Verifying the VxFS cache area and monitoring the caching
- Setting the caching mode
- Customizing the caching behavior
- Viewing the caching statistics for a cache area
- Configuring episodic replication
- About Veritas Access episodic replication
- How Veritas Access episodic replication works
- Starting Veritas Access episodic replication
- Setting up communication between the source and the destination clusters
- Setting up the file systems to replicate
- Setting up files to exclude from an episodic replication unit
- Scheduling the episodic replication
- Defining what to replicate
- About the maximum number of parallel episodic replication jobs
- Managing an episodic replication job
- Replicating compressed data
- Displaying episodic replication job information and status
- Synchronizing an episodic replication job
- Behavior of the file systems on the episodic replication destination target
- Accessing file systems configured as episodic replication destinations
- Creating a recovery point objective (RPO) report
- Episodic replication job failover and failback
- Configuring continuous replication
- About Veritas Access continuous replication
- How Veritas Access continuous replication works
- Starting Veritas Access continuous replication
- Setting up communication between the source and the destination clusters
- Setting up the file system to replicate
- Managing continuous replication
- Displaying continuous replication information and status
- Unconfiguring continuous replication
- Continuous replication failover and failback
- Using snapshots
- Using instant rollbacks
- About instant rollbacks
- Creating a space-optimized rollback
- Creating a full-sized rollback
- Listing Veritas Access instant rollbacks
- Restoring a file system from an instant rollback
- Refreshing an instant rollback from a file system
- Bringing an instant rollback online
- Taking an instant rollback offline
- Destroying an instant rollback
- Creating a shared cache object for Veritas Access instant rollbacks
- Listing cache objects
- Destroying a cache object of a Veritas Access instant rollback
- Configuring Veritas Access with the NetBackup client
- About Veritas Access as a NetBackup client
- Prerequisites for configuring the NetBackup client
- About the NetBackup Snapshot Client
- About NetBackup snapshot methods
- Enabling or disabling the NetBackup SAN client
- Workflow for configuring Veritas Access for NetBackup
- Registering a NetBackup master server or adding an optional media server
- Displaying the excluded files from backup
- Displaying the included and excluded files for backups
- Adding or deleting patterns to the list of files in backups
- Configuring or resetting the virtual IP address used by NetBackup
- Configuring the virtual name of NetBackup
- Displaying the status of NetBackup services
- Configuring backup operations using NetBackup or other third-party backup applications
- Performing a backup or restore of a Veritas Access file system over a NetBackup SAN client
- Performing a backup or restore of a snapshot
- Installing or uninstalling the NetBackup client
- Configuring Veritas Access for NetBackup cloud storage
- Section XI. Reference
Creating and scheduling a policy for a scale-out file system
By default, a scale-out file system has a single disk tier, which is the on-premises storage for the scale-out file system. You can add a cloud service as an additional tier. After a cloud tier is configured, you can move data between the tiers of the scale-out file system as needed.
Use policies to define a set of data movement rules for the scale-out file system. Each file system can include a policy for deletion and a policy for data movement between tiers.
Be careful when specifying the criteria for moving files. Conflicting policies may cause data to move from one tier to another tier. A best practice is to use policies with a smaller data set first before applying those policies to file systems using a schedule.
A data movement policy can use the following criteria to indicate which files or directories to move between tiers:
pattern
atime
mtime
You can also perform a dry run of a policy.
See the storage_fs(1) policy section of the manual page for detailed examples.
To create a policy
- Create a data movement policy policy1 for file system fs1 to move the files with file name extensions of .txt and .pdf from the primary tier (disk tier) to tier1 (cloud tier), which did not get accessed or modified for the last two days.
Storage> fs policy add operation=move policy1 fs1 primary tier1 *.txt,* .pdf atime >2d mtime >2d ACCESS policy SUCCESS V-288-0 Policy policy1 for fs fs1 added successfully.
- Retrieve data from Amazon Glacier. Create a policy pol1 to move all the files with the file name extension of .txt from Amazon Glacier to the primary tier using the Bulk retrieval option.
Files are copied to on-premises and then deleted from Amazon Glacier. The time when the files are available on-premises depends on the type of retrieval option selected.
Storage> fs policy add operation=move pol1 gfs2 gtier primary retrieval_option=Bulk \*.txt
- Create a data deletion policy policy2 for file system fs1 to move the files with file name extensions of .txt and .pdf from tier1 (cloud tier), which did not get accessed or modified for the last two days.
Storage> fs policy add operation=delete policy2 fs1 tier1 \*.txt, \*.pdf atime >2d mtime >2d ACCESS policy SUCCESS V-288-0 Policy policy2 for fs fs1 added successfully.
- Modify data movement policy policy1 for file system fs1 to move the files with the file name extension of .doc, which did not get accessed or modified for the last three days.
Storage> fs policy modify policy1 \*.doc atime >3d mtime >3d ACCESS policy SUCCESS V-288-0 Policy policy1 modified successfully.
- List all the policies.
Storage> fs policy list Name FS name Action Source Tier Destination Tier Retrieval Option Pattern ======= ======== ======= =============== ================= ================= ============ policy2 fs1 delete tier1 - Standard \*.txt, \*.pdf policy1 fs1 move primary tier1 Standard \*.doc Atime Mtime State ====== ====== ========= >2d >2d not running >3d >3d running
- List all the policies set for file system fs1.
Storage> fs policy list fs1 Name FS name Action Source Tier Destination Tier Retrieval Option Pattern ======= ======== ======= =============== ================= ================= ============ policy2 fs1 delete tier1 - Standard \*.txt, \*.pdf policy1 fs1 move primary tier1 Standard \*.doc Atime Mtime State ====== ====== ======== >2d >2d running >3d >3d not running
- Delete policy policy1 set for file system fs1.
Storage> fs policy delete policy1 fs1 ACCESS policy SUCCESS V-288-0 Policy policy1 for fs fs1 deleted successfully.
- Rename policy2 to policy3.
Storage> fs policy rename policy2 policy3 ACCESS policy SUCCESS V-288-0 Policy policy2 renamed to policy3.
- Show the status of policy run for the policy Policy1.
Storage> fs policy status Policy1 Policy Name: Policy1 ================================================= Policy Run Type: normal Policy Run Status: running Total Data (Files): 93.1 GB (100000) Moved/Deleted Data (Files): 47.7 MB (879) Last File Visited: file100.txt
- Abort the currently running policy Policy1.
Storage> fs policy abort Policy1 ACCESS policy INFO V-288-0 Policy Policy1 aborted successfully.
- Start a dry run of the policy Policy1.
Storage> fs policy dryrun Policy1 ACCESS policy INFO V-288-0 Policy Policy1 dryrun started in background, please check 'fs policy status' for progress.
- Pause the currently running policy Policy1.
Storage> fs policy pause Policy1 ACCESS policy INFO V-288-0 Policy Policy1 paused successfully.
- Run the currently paused policy Policy1.
Storage> fs policy run Policy1 Policy Policy1 is not running currently, as it was killed/paused. Would you like to start new run (y/n): y ACCESS policy INFO V-288-0 Policy Policy1 run started in background, please check 'fs policy status' for progress.
- Resume the currently paused policy Policy1.
Storage> fs policy resume Policy1 ACCESS policy INFO V-288-0 Policy Policy1 resume started in background, please check 'fs policy status' for progress.