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
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.