Please enter search query.
Search <book_title>...
Veritas Access Appliance Cloud Storage Tiering Solutions Guide
Last Published:
2023-03-06
Product(s):
Appliances (8.1)
Platform: Veritas 3340,Veritas 3350
- Introduction to cloud storage tiering
- Configuring the cloud gateway
- Configuring the cloud as a tier using CLISH
- Configuring the cloud as a tier using GUI
Creating and scheduling a policy for a file system
A file system can have multiple on-premises tiers for storage. 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 file system as needed.
Use policies to define a set of data movement rules for the 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.
Creating a policy
To create a policy
- Create a data movement policy policy1, for file system fs1, to move the files with file name extensions of .txt 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 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 become 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 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 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 ======= ======== ======= =============== ================= policy2 fs1 delete tier1 - policy1 fs1 move primary tier1 Retrieval Option Pattern Atime Mtime State ================= ========= ====== ====== ========= Standard *.txt >2d >2d not running Standard *.doc >3d >3d running
- List all the policies set for file system fs1.
Storage> fs policy list Name FS name Action Source Tier Destination Tier ======= ======== ======= =============== ================= policy2 fs1 delete tier1 - policy1 fs1 move primary tier1 Retrieval Option Pattern Atime Mtime State ================= ========= ====== ====== ========= Standard \*.txt >2d >2d running Standard \*.doc >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: unknown Policy Run Status: completed Moved Data: 600.0 MB Total Moved Files: 6 Total Deleted Files: 3
- 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.
Scheduling a policy
Creating a policy schedule
- To create a policy schedule:
storage> fs policy schedule create fs1 23 20 ACCESS policy_schedule SUCCESS V-493-10-2945 Schedule create for file system fs1 done successfully.
- To list a policy schedule:
storage> fs policy schedule list fs10 File System Name Minute Hour Day of Month Month Day of Week ================ ====== ==== ============ ===== =========== fs1 23 20 * * * byos1> storage fs policy schedule remove fs1 ACCESS policy_schedule SUCCESS V-493-10-2947 Schedule for file system fs1 removed successfully.
- To remove a policy schedule:
storage> fs policy schedule remove fs1 ACCESS policy_schedule SUCCESS V-493-10-2947 Schedule for file system fs1 removed successfully.