Data ONTAP 7.3 Storage Management Guide

• Copyright information
• Trademark information
• About this guide
• Audience
• Terminology
• FilerView as an alternative to the command-line interface
• Command, keyboard, and typographic conventions
• Special messages
• Data ONTAP storage architecture overview
• How Data ONTAP works with disks
• What disk types Data ONTAP supports
• Disk connection architectures
  • Fibre Channel Arbitrated Loop (FC-AL) disk connection architecture
  • Serial attached SCSI (SAS) disk connection architecture
• Available disk capacity by disk size
• Disk speeds
• Disk formats
• Disk names
  • Disk IDs for FC-AL connected disks
  • Disk IDs for SAS-connected disks
  • Disk names for direct-attached disks
  • Disk names for switch-attached disks
• RAID disk types
• Disk pools
• How disk sanitization works
  • Disk sanitization limitations
  • What happens if disk sanitization is interrupted
  • How selective disk sanitization works
    • Tips for creating and backing up aggregates containing data that will be sanitized
• Commands to display disk information
• Commands to display disk space information
• How Data ONTAP monitors disk performance and health
  • When Data ONTAP takes disks offline temporarily
  • How Data ONTAP reduces disk failures using Rapid RAID Recovery
  • How the maintenance center works
    • When Data ONTAP can put a disk into the maintenance center
    • Putting a disk into the maintenance center manually
  • How Data ONTAP uses continuous media scrubbing to prevent media errors
    • How continuous media scrub impacts system performance
    • Why continuous media scrubbing should not replace scheduled RAID-level disk scrubs
• How disk ownership works
• How software-based disk ownership works
  • How disk ownership autoassignment works
    • What autoassignment does
    • When autoassignment is invoked
  • Software-based disk ownership guidelines
  • When a storage system uses software-based disk ownership
• How hardware-based disk ownership works
  • Data ONTAP automatically recognizes and assigns disks for hardware-based disk ownership
• How disks are assigned to spare pools when SyncMirror is enabled
• Storage system models that support hardware-based disk ownership or both types
• How you use the wildcard character with the disk command
• Managing disk ownership
• Determining whether a system has hardware-based or software-based disk ownership
• Changing between hardware-based and software-based disk ownership
  • Changing from hardware-based to software-based disk ownership
  • Changing from software-based to hardware-based disk ownership for stand-alone systems
  • About changing from software-based to hardware-based disk ownership for active/active configurations
• Displaying disk ownership
• Assigning disk ownership
• Modifying disk assignments
• Reusing disks that are configured for software-based disk ownership
  • Automatically erasing disk ownership information
  • Manually erasing software-based disk ownership information
  • Recovering from accidental conversion to software-based disk ownership
• Managing disks
• Adding disks to a storage system
• Removing disks from a storage system
  • Removing a failed disk
  • Removing a hot spare disk
  • Removing a data disk
• Replacing disks that are currently being used in an aggregate
• Removing data from disks using disk sanitization
  • Removing data from disks using selective disk sanitization
    • Selectively sanitizing data contained in FlexVol volumes
    • Selectively sanitizing data contained in traditional volumes
• Stopping disk sanitization
• Managing storage subsystems
• Enabling or disabling a host adapter
• Commands you use to view storage subsystem information
• How Data ONTAP uses RAID to protect your data and data availability
• RAID protection levels
  • What RAID-DP protection is
  • What RAID4 protection is
• RAID disk types
• How RAID groups work
  • How RAID groups are named
  • About RAID group size
  • Maximum number of RAID groups
  • Maximum and default RAID group sizes
  • Considerations for sizing RAID groups
• Protection provided by RAID and SyncMirror
• How Data ONTAP works with hot spares
  • Hot spare best practices
  • What disks can be used as hot spares
  • What a matching spare is
  • What an appropriate hot spare is
  • About degraded mode
  • About low spare warnings
• How Data ONTAP handles a failed disk with an available hot spare
• How Data ONTAP handles a failed disk that has no available hot spare
• How Data ONTAP handles media errors during reconstruction
• RAID status
• How RAID-level disk scrubs verify data integrity
  • How you schedule automatic RAID-level scrubs
  • How you run a manual RAID-level scrub
• Customizing the size of your RAID groups
• Controlling the impact of RAID operations on system performance
• Controlling the performance impact of RAID data reconstruction
• Controlling the performance impact of RAID-level scrubbing
• Controlling the performance impact of plex resynchronization
• Controlling the performance impact of mirror verification
• How aggregates work
• How unmirrored aggregates work
• How mirrored aggregates work
• Aggregate states and status
• How you can use disks with mixed speeds in the same aggregate
• How to control disk selection in a heterogeneous disk pool
• Checksum type rules used when you add disks to an aggregate
• Managing aggregates
• Creating an aggregate
• Increasing the size of an aggregate
  • What happens when you add disks to an aggregate
  • Forcibly adding disks to aggregates
  • What happens when you add larger disks to an aggregate
• Taking an aggregate offline
• Bringing an aggregate online
• Putting an aggregate into restricted state
• Changing the RAID level of an aggregate
  • Changing an aggregate's RAID level from RAID4 to RAID-DP
  • Changing an aggregate's RAID level from RAID-DP to RAID4
• Determining how the space in an aggregate is being used
• Destroying an aggregate
• Undestroying an aggregate
• Physically moving an aggregate
• How volumes work
• A comparison of FlexVol volumes and traditional volumes
  • How FlexVol volumes work
  • How traditional volumes work
• Limits on how many volumes and aggregates you can have
• Attributes you can set for volumes
• How volumes use the language attribute
  • How file access protocols affect what language to use for your volumes
• How you manage duplicate volume names
• Volume states and status
• About the CIFS oplocks setting
• How security styles affect access to your data
  • How UNIX permissions are affected when files are edited using Windows applications
  • What the default security style is for new volumes and qtrees
• How Data ONTAP can automatically provide more free space for full volumes
• About FlexClone volumes
• How FlexClone volumes work
• Operations that aren't supported on FlexClone volumes or their parent
• FlexClone volumes and space guarantees
• FlexClone volumes and shared Snapshot copies
• How you can identify shared Snapshot copies in FlexClone volumes
• How you use volume SnapMirror replication with FlexClone volumes
  • About creating a volume SnapMirror relationship using an existing FlexClone volume or its parent
  • About creating a FlexClone volume from volumes currently in a SnapMirror relationship
• How splitting a FlexClone volume from its parent works
• FlexClone volumes and LUNs
• About FlexCache volumes
• FlexCache hardware and software requirements
• Limitations of FlexCache volumes
• Types of volumes you can use for FlexCache
• How the FlexCache Autogrow capability works
• How FlexCache volumes use space management
• How FlexCache volumes share space with other volumes
• How you display FlexCache statistics
• What happens when connectivity to the origin system is lost
• How the NFS export status of the origin volume affects FlexCache access
• How FlexCache caching works
  • Files are the basic caching unit
  • How cache consistency is achieved
    • Delegations
    • Attribute cache timeouts
    • Write operation proxy
  • Cache hits and misses
• Typical FlexCache deployments
  • WAN deployment
  • LAN deployment
• About using LUNs in FlexCache volumes
• What FlexCache status messages mean
• How FlexCache volumes connect to their origin volume
• General volume operations
• Migrating from traditional volumes to FlexVol volumes
  • Preparing your destination volume
  • Migrating your data
  • Completing your migration
• Putting a volume into restricted state
• Taking a volume offline
• Bringing a volume online
• Renaming a volume
• Destroying a volume
• Increasing the maximum number of files allowed on a volume
• Changing the language for a volume
• FlexVol volume operations
• Creating a FlexVol volume
• Resizing a FlexVol volume
• Configuring a FlexVol volume to grow automatically
• Configuring automatic free space preservation for a FlexVol volume
• Displaying a FlexVol volume's containing aggregate
• FlexClone volume operations
• Creating a FlexClone volume
• Splitting a FlexClone volume from its parent
• Determining the parent volume and base Snapshot copy for a FlexClone volume
• Determining the space used by a FlexClone volume
• FlexCache volume operations
• Creating FlexCache volumes
• Displaying free space for FlexCache volumes
• Configuring the FlexCache Autogrow capability
• Flushing files from FlexCache volumes
• Displaying FlexCache client statistics
• Displaying FlexCache server statistics
• Displaying FlexCache status
• Traditional volume operations
• Creating a traditional volume
• How space management works
• What kind of space management to use
• What space guarantees are
  • What kind of space guarantee traditional volumes provide
  • How you set space guarantees for new or existing volumes
• What space reservation is
• What fractional reserve is
  • Setting fractional reserve
  • Reasons to set fractional reserve to zero
• How space reservation and fractional reserve settings persist
• How Data ONTAP can automatically provide more free space for full volumes
• Space reservation and fractional reserve examples
• Estimating how large a volume needs to be
  • Calculating the total data size
  • Determining the volume size and fractional reserve setting when you need Snapshot copies
  • Determining the volume size when you do not need Snapshot copies
• How aggregate overcommitment works
• Considerations for bringing a volume online in an overcommited aggregate
• About qtrees
• When you use qtrees
• How many qtrees you can have
• How qtrees compare with volumes
• Managing qtrees
• Creating a qtree
• Displaying qtree status
• Displaying qtree access statistics
• 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
• Deleting a qtree
• Renaming a qtree
• Managing CIFS oplocks
• About the CIFS oplocks setting
• Enabling or disabling CIFS oplocks for the entire storage system
• Enabling CIFS oplocks for a specific volume or qtree
• Disabling CIFS oplocks for a specific volume or qtree
• Changing security styles
• About quotas
• Why you use quotas
• Overview of the quota process
  • About quota notifications
• 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 work with users and groups
  • How you specify UNIX users in the quotas file
  • How you specify Windows users in the quotas file
    • How you specify a user name in pre-Windows 2000 format
    • How you specify a Windows domain using the QUOTA_TARGET_DOMAIN directive
  • 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 you link UNIX and Windows names for quotas
    • How you map names using the same quotas file entry
    • How you map names using the QUOTA_PERFORM_USER_MAPPING directive
      • About using wildcard entries in the usermap.cfg file
• How quotas work with qtrees
  • How tree quotas work
  • How user and group quotas work with qtrees
  • How quotas are inherited from volumes by qtrees
• Differences among hard, soft, and threshold quotas
• How the quotas file works
  • The syntax of quota entries
    • How the Quota Target field works
    • How the Type field works
    • How the Disk field works
    • How the Files field works
    • How the Threshold field works
    • How the Soft Disk field works
    • How the Soft Files field works
  • How Data ONTAP reads the quotas file
  • What character encodings are supported by the quotas file
  • Sample quotas file
• About activating or reinitializing quotas
• About modifying quotas
  • When you can use resizing
  • When a full quota reinitialization is required
• 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 quota reports work
  • What fields quota reports contain
  • How quota report options affect quota reports
  • How the ID field is displayed in quota reports
• Progressive quota examples
• Managing quotas
• Activating quotas
• Reinitializing quotas
• Deactivating quotas
• Canceling quota initialization
• Resizing quotas
• Deleting quotas
  • Deleting a quota by removing resource restrictions
  • Deleting a quota by removing the quotas file entry
• Managing quota message logging
• Displaying a quota report
• Abbreviations