Veritas Access Administrator's Guide
- Section I. Introducing Veritas Access
- Section II. Configuring Veritas Access
- Adding users or roles
- Configuring the network
- Configuring authentication services
- Section III. Managing Veritas Access storage
- Configuring storage
- 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 the NFS server
- Setting up Kerberos authentication for NFS clients
- Using Veritas Access as a CIFS server
- About Active Directory (AD)
- About configuring CIFS for Active Directory (AD) domain mode
- About setting trusted domains
- About managing home directories
- About CIFS clustering modes
- About migrating CIFS shares and home directories
- About managing local users and groups
- Configuring an FTP server
- Using Veritas Access as an Object Store server
- Configuring the NFS server
- Section V. Monitoring and troubleshooting
- Section VI. Provisioning and managing Veritas Access file systems
- Creating and maintaining file systems
- Considerations for creating a file system
- Modifying a file system
- Managing a file system
- Creating and maintaining file systems
- Section VII. Configuring cloud storage
- Section VIII. Provisioning and managing Veritas Access shares
- Creating shares for applications
- Creating and maintaining NFS shares
- Creating and maintaining CIFS shares
- Using Veritas Access with OpenStack
- Integrating Veritas Access with Data Insight
- Section IX. Managing Veritas Access storage services
- Compressing files
- About compressing files
- Compression tasks
- Configuring SmartTier
- Configuring SmartIO
- Configuring episodic replication
- Episodic replication job failover and failback
- Configuring continuous replication
- How Veritas Access continuous replication works
- Continuous replication failover and failback
- Using snapshots
- Using instant rollbacks
- Compressing files
- Section X. Reference
Configuring the policy of each tiered file system
To display the policy of each tiered file system
- To display the policy of each tiered file system, enter the following:
Storage> tier policy list
For example:
Storage> tier policy list FS Create on Days MinAccess Temp PERIOD == ========= ==== ============== ====== fs1 primary 2 3 4
Each tiered file system can be assigned a policy. A policy that is assigned to a file system has three parts:
file creation
Specifies on which tier the new files are created.
inactive files
Indicates when a file has to be moved from the primary tier to the secondary tier. For example, if the days option of the tier is set to 10, and if a file has not been accessed for more than 10 days, then it is moved from the primary tier of the file system to the secondary tier.
access temperature
Measures the number of I/O requests to the file during the period as designated by the period. In other words, it is the number of read or write requests that are made to a file over a specified number of 24-hour periods, divided by the number of periods. If the access temperature of a file exceeds minacctemp (where the access temperature is calculated over a period of time previously specified) then this file is moved from the secondary tier to the primary tier.
To modify the policy of a tiered file system
- To modify the policy of a tiered file system, enter the following:
Storage> tier policy modify fs_name {primary|secondary} days minacctemp period
fs_name
The name of the tiered file system from which you want to modify a policy.
tier
Causes the new files to be created on the primary or the secondary tier. You need to input either primary or secondary.
days
Number of days from which the inactive files move from the primary to the secondary tier.
minacctemp
The minimum access temperature value for moving files from the secondary to the primary tier.
period
The number of past days used for calculating the access temperature.
To display the prune policy of a tiered file system
- To display the prune policy of a tiered file system, enter the following:
Storage> tier policy prune list
By default, the prune policy status of a tiered file system is disabled. The delete_after indicates the number of days after which the files can be deleted.
To modify the prune policy of a tiered file system
- To modify the prune policy of a tiered file system, enter the following:
Storage> tier policy prune modify fs_name delete_after
fs_name
Name of the tiered file system from which you want to modify the prune policy.
delete_after
Number of days after which the inactive files are deleted.
To remove the prune policy of a tiered file system
- To remove the prune policy of a tiered file system, enter the following:
Storage> tier policy prune remove fs_name
where fs_name is the name of the tiered file system from which you want to remove the prune policy.
To run the policy of a tiered file system
- To run the policy of a tiered file system, enter the following:
Storage> tier policy run fs_name
where fs_name indicates the name of the tiered file system for which you want to run a policy.
To remove the policy of a tiered file system
- To remove the policy of a tiered file system, enter the following:
Storage> tier policy remove fs_name
where fs_name indicates the name of the tiered file system from which you want to remove a policy.
You can run the policy of a tiered file system, which would be similar to scheduling a job to run your policies, except in this case running the policy is initiated manually. The Storage> tier policy run command moves the older files from the primary tier to the secondary tier, or prunes the inactive files on the secondary tier, according to the policy setting.