Modify caching policies of Flash Pool local tiers (aggregates)
-
PDF of this doc site
- Cluster administration
-
Volume administration
- Logical storage management with the CLI
-
NAS storage management
- Configure NFS with the CLI
- Manage NFS with the CLI
-
Manage SMB with the CLI
- Manage file access using SMB
- SAN storage management
- Security and data encryption
-
Data protection and disaster recovery
- Data protection with the CLI
Collection of separate PDF docs
Creating your file...
You should modify the caching policy of a volume only if a different caching policy is expected to provide better performance. You can modify the caching policy of a volume on a Flash Pool local tier (aggregate).
You must determine whether you want to modify your caching policy.
In most cases, the default caching policy of “auto” is the best caching policy that you can use. The caching policy should be changed only if a different policy provides better performance for your workload. Configuring the wrong caching policy can severely degrade volume performance; the performance degradation could increase gradually over time. You should use caution when modifying caching policies. If you experience performance issues with a volume for which the caching policy has been changed, you should return the caching policy to “auto”.
-
Use the CLI to modify the volume's caching policy:
volume modify -volume volume_name -caching-policy policy_name
The following example modifies the caching policy of a volume named “vol2” to the policy “none”:
volume modify -volume vol2 -caching-policy none