Clustered Data ONTAP® 8.2
Logical Storage Management Guide
What logical storage is
How volumes work
What a FlexVol volume is
Capabilities that FlexVol volumes provide
Differences among FlexVol volume features
What an Infinite Volume is
Capabilities that Infinite Volumes provide
Comparison of FlexVol volumes and Infinite Volumes
How FlexVol volumes and Infinite Volumes share aggregates
How security styles affect data access
Improving client performance with traditional and lease oplocks
What system volumes are
Using FlexVol volumes
Differences between 64-bit and 32-bit FlexVol volumes
Interoperability between 64-bit and 32-bit FlexVol volumes
How FlexVol volumes work with Vservers
How the Vserver affects which aggregates can be associated with a FlexVol volume
How the Vserver can limit how many FlexVol volumes it can have
How the Vserver affects the language of the FlexVol volume
Restoring a Vserver's root volume
What volume junctions are
How you use space management capabilities
How volume guarantees work with FlexVol volumes
Enabling guarantees for FlexVol volumes
How the guarantee affects FlexVol volume space requirements
Considerations for using thin provisioning with FlexVol volumes
How file and LUN reservations work for FlexVol volumes
Considerations for setting fractional reserve for FlexVol volumes
How Data ONTAP can automatically provide more space for full FlexVol volumes
Selecting the first method to increase space for full FlexVol volumes
How a FlexVol volume can automatically change its size
Configuring a FlexVol volume to automatically change its size
Requirements for enabling both autoshrink and automatic Snapshot copy deletion
How the autoshrink functionality interacts with Snapshot copy deletion
How a FlexVol volume can reclaim free space from FlexClone LUNs
Deleting Snapshot copies automatically
How to determine space usage in a volume or aggregate
How to determine space usage in an aggregate
How you can determine and control a volume's space usage in the aggregate
What the volume footprint is
How you can determine and control space usage in a volume
How Snapshot copies and Snapshot reserve use space in a volume
When to use the df command and the space usage commands
Methods to create space in a FlexVol volume
Methods to create space in an aggregate
How the FlexVol volume and aggregate fullness alerts work
How volume fullness alerts work with the volume autogrow capability
Cautions and considerations for changing file or directory capacity
Considerations for changing the maximum number of files allowed on a FlexVol volume
Cautions for increasing the maximum directory size for FlexVol volumes
Rules governing node root volumes and root aggregates
Basic FlexVol volume management
Creating a FlexVol volume
Deleting a FlexVol volume
Controlling and monitoring I/O performance to FlexVol volumes by using Storage QoS
Displaying file or inode usage
Commands for managing FlexVol volumes
Commands for displaying space information
Moving and copying volumes (cluster administrators only)
How moving a FlexVol volume works
Commands for moving volumes
Moving a volume
SnapMirror transfers can affect volume move operations
Characteristics of how Data ONTAP copies FlexVol volumes
Copying a FlexVol volume
Using FlexCache volumes to accelerate data access
What a cached file contains
How FlexCache volumes serve read requests
Why you use FlexCache volumes
Considerations for working with FlexCache volumes
Limitations of FlexCache volumes
Example of FlexCache deployment in clustered Data ONTAP environment
What cache policies are
How data changes affect FlexCache volumes
How cache consistency is achieved
Cache-read Delegations
TTL values in cache policies
Write operation proxy
What cache hits and misses are
How autosizing of FlexCache volumes improves caching performance
How FlexCache volumes share space with other volumes
How FlexCache volumes are impacted during loss of connectivity
How NVRAM failures on the origin volume impact FlexCache volumes
How FlexCache volumes work during a failover
Comparison of FlexCache volumes and load-sharing mirrors
Commands for managing FlexCache volumes
Using FlexClone volumes to create efficient copies of your FlexVol volumes
Understanding FlexClone volumes
FlexClone volumes and shared Snapshot copies
How to identify shared Snapshot copies in FlexClone volumes
How you use volume SnapMirror replication with FlexClone volumes
Considerations for creating a FlexClone volume from a SnapMirror source or destination volume
How splitting a FlexClone volume from its parent works
FlexClone volumes and LUNs
Understanding data protection FlexClone volumes
Creating a FlexClone volume
Splitting a FlexClone volume from its parent
Determining the space used by a FlexClone volume
Using FlexClone files and FlexClone LUNs to create efficient copies of files and LUNs
Benefits of FlexClone files and FlexClone LUNs
How FlexClone files and FlexClone LUNs work
Considerations for working with FlexClone files and FlexClone LUNs
Creating a FlexClone file or FlexClone LUN
Viewing the space savings due to FlexClone files and FlexClone LUNs
How a FlexVol volume can reclaim free space from FlexClone LUNs
Configuring a FlexVol volume to automatically delete FlexClone LUNs
Preventing a specific FlexClone LUN from being autodeleted
Features supported with FlexClone files and FlexClone LUNs
How deduplication works with FlexClone files and FlexClone LUNs
How Snapshot copies work with FlexClone files and FlexClone LUNs
How access control lists work with FlexClone files and FlexClone LUNs
How quotas work with FlexClone files and FlexClone LUNs
How FlexClone volumes work with FlexClone files and FlexClone LUNs
How NDMP works with FlexClone files and FlexClone LUNs
How volume SnapMirror works with FlexClone files and FlexClone LUNs
How volume move affects FlexClone files and FlexClone LUNs
How volume copy works with FlexClone files and FlexClone LUNs
How space reservation works with FlexClone files and FlexClone LUNs
How an HA configuration works with FlexClone files and FlexClone LUNs
Using a load-sharing mirror to balance loads
Considerations when working with load-sharing mirrors
Mounting a FlexVol volume that has load-sharing mirrors for NFS clients
Mounting a FlexVol volume that has load-sharing mirrors for CIFS clients
Restriction when modifying the source volume
Creating a set of load-sharing mirrors
Creating a FlexVol volume for load-sharing
Creating load-sharing mirror relationships
Creating a baseline for a set of load-sharing mirrors
Adding a load-sharing mirror to a set of load-sharing mirrors
Initializing an individual load-sharing mirror
Updating a set of load-sharing mirrors
Aborting an update to a load-sharing mirror
Scheduling SnapMirror transfers
Changing mirror relationship schedules
Listing the schedule state of a mirror relationship
Showing the status of a particular load-sharing mirror
Determining whether load-sharing mirrors are up-to-date
Recovering a lost source FlexVol volume from a mirror
Deleting a mirror copy
Using qtrees to partition your FlexVol volumes
When to use qtrees
How qtrees compare with FlexVol volumes
Qtree name restrictions
What you can do with qtrees on a mirror
Converting a directory to a qtree
Converting a directory to a qtree using a Windows client
Converting a directory to a qtree using a UNIX client
Commands for managing qtrees
Using quotas to restrict or track resource usage
Why you use quotas
Overview of the quota process
Differences among hard, soft, and threshold quotas
Understanding quota notifications
What quota rules, quota policies, and quotas are
Quota targets and types
Special kinds of quotas
How default quotas work
How you use explicit quotas
How derived quotas work
How you use tracking quotas
How quotas are applied
Considerations for assigning quota policies
How quotas work with users and groups
How you specify UNIX users for quotas
How you specify Windows users for quotas
How default user and group quotas create derived quotas
How quotas are applied to the root user
How quotas work with special Windows groups
How quotas are applied to users with multiple IDs
How Data ONTAP determines user IDs in a mixed environment
How quotas with multiple users work
How you link UNIX and Windows names for quotas
How quotas work with qtrees
How tree quotas work
How user and group quotas work with qtrees
How default tree quotas on a FlexVol volume create derived tree quotas
How default user quotas on a FlexVol volume affect quotas for the qtrees in that volume
How qtree changes affect quotas
How deleting a qtree affects tree quotas
How renaming a qtree affects quotas
How changing the security style of a qtree affects user quotas
How quotas are activated
When you can use resizing
When a full quota reinitialization is required
How you can view quota information
How you can use the quota report to see what quotas are in effect
Why enforced quotas differ from configured quotas
Using the quota report to determine which quotas limit writes to a specific file
Commands for displaying information about quotas
When to use the volume quota policy rule show and volume quota report commands
Difference in space usage displayed by a quota report and a UNIX client
How a quota report accounts for disk space and file usage
How the ls command accounts for space usage
How the df command accounts for file size
How the du command accounts for space usage
Examples of quota configuration
Setting up quotas on a Vserver with FlexVol volumes
Making minor changes to existing quota limits
Reinitializing quotas after making extensive changes
Verifying status of quota upgrades
Commands to manage quota rules and quota policies
Commands to activate and modify quotas
Using Infinite Volumes
What an Infinite Volume is
Capabilities that Infinite Volumes provide
Creating an Infinite Volume (express setup)
Choosing aggregates for an Infinite Volume
Creating a Vserver with Infinite Volume
Creating an Infinite Volume using default settings
Setting up and managing an Infinite Volume (overview)
Setting up and managing an Infinite Volume with storage classes (overview)
Requirements for Infinite Volumes
Platforms supported by Infinite Volumes
Node requirements for Infinite Volumes
Vserver requirements for Infinite Volumes
Aggregate requirements for Infinite Volumes
Junction naming requirements for Infinite Volumes
Decisions to make before you create an Infinite Volume
Considerations when using storage classes
Considerations when using thin provisioning with Infinite Volumes
Space considerations for using incremental tape backup
Constituent size requirements for setting up data protection mirror relationships for Infinite Volumes
How Infinite Volumes use storage classes and data policies
What a storage class is
How storage classes affect which aggregates can be associated with Infinite Volumes
How storage classes relate to storage services
What rules and data policies are
How a data policy is automatically created and starts filtering data
Commands disabled for Infinite Volumes with storage classes
Tasks and tools for managing Infinite Volumes with storage classes and data policy
Interoperability between Infinite Volumes with storage classes and Data ONTAP features
How storage classes affect client access to Infinite Volumes
How storage classes affect Snapshot copies of Infinite Volumes
How storage classes affect data protection mirror relationships for Infinite Volumes
How storage classes affect tape backup of Infinite Volumes
Managing a data policy for a Vserver with Infinite Volume
Commands for managing a data policy for a Vserver with Infinite Volume
Editing rules in a data policy for a Vserver with Infinite Volume
Importing a data policy to a Vserver with Infinite Volume
Considerations for valid JSON formatting in data policies
Example of JSON data policy: filtering based on directory
Example of JSON data policy: filtering based on file name
Example of JSON data policy: filtering based on file owner
What Infinite Volume constituents are
What a namespace constituent is
What data constituents are
What a namespace mirror constituent is
When namespace mirror constituents are created
Planning aggregates for an Infinite Volume
How aggregates and nodes are associated with Infinite Volumes
How much space namespace-related constituents require
How data constituents use aggregate space
How node balancing affects an Infinite Volume's size and aggregate use
Creating Infinite Volumes for specific scenarios
How space is allocated inside a new Infinite Volume
Examples of how space is allocated in Infinite Volumes
Creating an Infinite Volume with dedicated aggregates
Selecting aggregates for an Infinite Volume and all Vservers in the cluster
Assigning aggregates for all Vservers in a cluster
Creating a Vserver with Infinite Volume
Creating an Infinite Volume using default settings
Creating an Infinite Volume in a dedicated cluster
Creating a Vserver with Infinite Volume in a dedicated cluster
Creating an Infinite Volume using default settings
Creating an Infinite Volume with a dedicated namespace aggregate
Selecting aggregates for an Infinite Volume and all Vservers in the cluster
Assigning aggregates for all Vservers in a cluster
Choosing aggregates for an Infinite Volume's namespace constituent
Creating a Vserver with Infinite Volume
Creating an Infinite Volume with manually selected aggregates
Preserving an aggregate for the namespace constituent during expansion
Creating an Infinite Volume that supports data protection on a different platform
Identifying the constituent sizes that platforms support
Choosing aggregates for an Infinite Volume
Creating a Vserver with Infinite Volume
Creating an Infinite Volume with small constituents
Converting to an Infinite Volume with storage classes
How client access works on Infinite Volumes
Comparison of namespaces for Infinite Volumes and FlexVol volumes
Where clients access Infinite Volumes
Why an Infinite Volume's size appears smaller from a client
How the mixed state of an Infinite Volume affects its availability
How locks work on Infinite Volumes
Managing Infinite Volumes
How operations run on Infinite Volumes
Viewing information about events on Infinite Volume constituents
Viewing constituents of an Infinite Volume
Naming convention for constituents
Restrictions on the private namespace of a Vserver with Infinite Volume
Restriction on moving or copying Infinite Volumes
Restriction on shrinking Infinite Volumes
Deleting an Infinite Volume
Monitoring space usage in Infinite Volumes
Commands for monitoring space usage in an Infinite Volume
Monitoring space usage in Infinite Volumes with storage classes
How you can determine and control a volume's space usage in the aggregate
What the volume footprint is
How to determine space usage in an aggregate
Methods to create space in an Infinite Volume or its aggregates
How an Infinite Volume distributes data across its constituents
Maximum number of files an Infinite Volume can store
Monitoring the number of files in an Infinite Volume
Expanding Infinite Volumes
How space is allocated when you expand an Infinite Volume
Expanding an Infinite Volume by increasing its use of existing aggregates
Determining which aggregates an Infinite Volume uses
Determining space availability in an Infinite Volume's aggregates
Resizing an Infinite Volume
Expanding an Infinite Volume by adding disks to its existing aggregates
Determining which aggregates an Infinite Volume uses
Adding disks to the aggregates that an Infinite Volume uses
Resizing an Infinite Volume
Expanding an Infinite Volume by associating it with more aggregates on existing nodes
Determining which aggregates an Infinite Volume uses
Associating more aggregates with an Infinite Volume
Resizing an Infinite Volume
Expanding an Infinite Volume by adding nodes
Determining which aggregates an Infinite Volume uses
Associating more nodes with an Infinite Volume
Resizing an Infinite Volume
Expanding Infinite Volumes with storage classes
Troubleshooting issues with Infinite Volumes
Completing an interrupted Infinite Volume creation
Managing size-related error messages when you create or expand an Infinite Volume
Troubleshooting a "footprint information" message when creating or expanding an Infinite Volume
This command is not supported for Infinite Volumes that are managed by storage services
Unsupported Data ONTAP features in Infinite Volumes
Unsupported space management capabilities for Infinite Volumes
Using deduplication and data compression to increase storage efficiency
How to set up efficiency operations
Configuring deduplication
How deduplication works
How deduplication works on Infinite Volumes
What deduplication metadata is
Guidelines for using deduplication
Performance considerations for deduplication
Enabling deduplication on a volume
Disabling deduplication on a volume
Configuring data compression
How data compression works
How compression works on Infinite Volumes
How data compression detects incompressible data
Enabling data compression on a volume
Disabling data compression on a volume
How efficiency works on Infinite Volumes with storage classes
Support for efficiency commands on Infinite Volumes with storage classes
Managing volume efficiency operations using policies
Using volume efficiency priorities to prioritize efficiency operations
Creating a volume efficiency policy to run efficiency operations
Assigning a volume efficiency policy to a volume
Modifying a volume efficiency policy
Viewing a volume efficiency policy
Deleting a volume efficiency policy
Managing volume efficiency operations using schedules
Running efficiency operations manually
Running efficiency operations depending on the amount of new data written
Using checkpoints to resume efficiency operation
Resuming an efficiency operation using the checkpoint option
Running efficiency operations manually on existing data
Modifying scheduling of efficiency operations
Monitoring volume efficiency operations
Viewing the status of efficiency operations on a FlexVol volume
Viewing the status of efficiency operations on an Infinite Volume
Viewing efficiency space savings on a FlexVol volume
Viewing efficiency space savings on an Infinite Volume
Viewing efficiency statistics of a FlexVol volume
Stopping volume efficiency operations
Information about removing space savings from a volume
Deduplication interoperability with Data ONTAP features
How fractional reserve works with deduplication
How Snapshot copies work with deduplication
How volume SnapMirror works with deduplication
How SnapRestore works with deduplication
How OnCommand Unified Manager server works with deduplication
How volume copy works with deduplication
How deduplication works with data compression
How FlexClone volumes work with deduplication
How HA pairs work with deduplication
How DataMotion for Volumes works with deduplication
How SnapVault backup works with deduplication
Data compression interoperability with Data ONTAP features
How fractional reserve works with data compression
How Snapshot copies work with data compression
How volume SnapMirror works with data compression
How tape backup works with data compression
How volume-based SnapRestore works with data compression
How single file SnapRestore works with data compression
How volume copy works with data compression
How deduplication works with data compression
How FlexClone volumes work with data compression
How FlexClone files work with data compression
How HA pairs work with data compression
How Flash cache cards work with data compression
How DataMotion for Volumes works with data compression
How Flash Pools work with data compression
How SnapVault backup works with data compression
Storage limits
Copyright information
Trademark information
How to send your comments