Data ONTAP 7.3 MultiStore Management Guide

• Copyright information
• Trademark information
• About this guide
• Audience
• Accessing Data ONTAP man pages
• Terminology
• FilerView as an alternative to the command-line interface
• Command, keyboard, and typographic conventions
• Special messages
• What MultiStore is
• Benefits of using MultiStore
• MultiStore for consolidating servers
• MultiStore for service providers and enterprises
• MultiStore for disaster recovery and data migration
• What the host storage system is
• What the default vFiler unit is
• MultiStore limits
• Host storage system's access to vFiler unit data
• Types of system administration tasks
  • Host storage system tasks
  • MultiStore management tasks
  • Tasks related to using Data ONTAP features on vFiler units
• MultiStore management
• How to create a vFiler unit
  • Enabling the MultiStore license
  • Disabling the MultiStore license
  • Storage guidelines
  • Language guidelines
  • Quota guidelines
  • Active/active considerations
  • SAN considerations
  • The vFiler commands
  • Ensuring that the network interface is ready
  • Assigning and configuring vFiler unit resources
  • Manually setting up a vFiler unit
• How to manage vFiler unit storage from the storage system
  • Effects of adding, removing, and moving vFiler unit resources
  • Adding resources to a vFiler unit
  • Requirements for moving and removing resources
  • Removing resources from a vFiler unit
  • Moving resources between vFiler units
  • Destroying a vFiler unit
  • Restoring a vFiler unit
• Default vFiler unit limits
• Maximum vFiler units allowed
• Viewing the current vFiler unit limit
• Increasing the vFiler unit limit
• Decreasing the vFiler unit limit
• Renaming a vFiler unit
• Stopping a vFiler unit
• Starting a vFiler unit
• Allowing a protocol for a vFiler unit
• Disallowing a protocol for a vFiler unit
• Displaying vFiler unit status
• Viewing commands that can be executed from a vFiler unit
• Executing commands from a vFiler unit
• Executing commands for a vFiler unit from the host storage system
• Executing commands for a vFiler unit using RSH
  • RSH commands
• Executing commands for a vFiler unit using SSH
  • SSH commands
• Effects of storage system reboot on a vFiler unit
• Volumes and qtrees on a vFiler unit
  • Effects of taking a vFiler unit volume offline
  • Changes required after volumes are renamed
  • Who can change qtree security styles and oplock settings
  • Differences in qtree command output
  • Viewing all qtrees and the owner vFiler units
• Backups for vFiler units
  • NDMP support
    • Available NDMP options
    • ndmpcopy support
    • NDMP command support
    • NDMP password support
• LUNs on a vFiler unit
  • What is supported on a vFiler unit
  • iSCSI LUNs and igroups on a vFiler unit
  • The iSCSI service on a vFiler unit
• Networking considerations
  • Effects of the routed daemon
  • Command for changing the routing table in the default IPspace
  • The /etc/dgateways file
  • IPsec on a vFiler unit
• SnapMirror on the host storage system
  • Considerations for using the snapmirror command
  • Determining the status of SnapMirror relationships
• Deduplication support on vFiler units
  • Benefits of deduplication support on vFiler units
  • Running deduplication commands on a vFiler unit
• SnapVault on the host storage system
  • Where to enter SnapVault commands
  • Considerations for using the snapvault command
  • Determining the status of SnapVault relationships
• SNMP used with a vFiler unit
  • vFiler unit data from MIBs
• What is not supported on a vFiler unit
• Monitoring performance and statistics
  • Displaying storage system statistics
  • Displaying uptime statistics
  • Displaying NFS statistics
  • Displaying CIFS statistics
• What IPspaces are
• What to consider for a vFiler unit participation in an IPspace
• Application of IPspaces
• How interfaces participate in an IPspace
• Routing in an IPspace
• Loopback interfaces in IPspaces
• Advantages of using VLAN tagging for IPspaces
  • Traffic separation
  • More IPspaces than interfaces are allowed
  • Secure delivery of packets to a vFiler unit in an IPspace
• Active/active configuration and IPspaces
  • What the IPspace naming requirement is
  • IPspace assignment requirement
  • What an asymmetric active/active setup is
  • Specifying partners in an asymmetric active/active setup
• Creating an IPspace
• IPspace and the routed daemon
• Listing IPspaces on a storage system
• Removing an IP address from an interface
• Assigning an interface to an IPspace
• Destroying IPspaces
• Creating a vFiler unit in a nondefault IPspace
• File access using NFS and CIFS
• How to access the vFiler unit's file system with NFS and CIFS
  • How to access a file system with CIFS
  • How to access a file system with NFS
• How to specify path names for NFS exports or CIFS shares
• How to prepare the vFiler unit for NFS
  • Starting the NFS protocol
  • Exporting all file systems in /etc/exports
• How to prepare the vFiler unit for CIFS
  • Tasks that can be performed only on the host storage system
  • Per vFiler unit limit with CIFS
  • Local user accounts for vFiler units
• Virus protection for CIFS
  • Who can configure virus scanning
  • Storage systems with which virus scanners can be registered
  • Virus scanning for vfiler0
  • Requirements for virus scanning on a vFiler unit other than vfiler0
  • Effect of virus scanner availability on CIFS access
  • Configuring virus scanning for a vFiler unit
• Disaster recovery
• How to prepare for disaster recovery
  • Checking and preparing the storage system
  • Storage checklist
  • Checking the network
  • Network checklist
• Setting up a disaster recovery vFiler unit
  • Secure communication for setup of disaster recovery
  • Creating a disaster recovery vFiler unit
  • Deleting the disaster recovery vFiler unit
  • What the vfiler dr configure command does
• Responding to a disaster
  • Activating the disaster recovery vFiler unit
  • What activating the disaster recovery vFiler unit does
  • How to reactivate the original vFiler unit after damage repair
  • Resynchronizing the vFiler unit
  • Handling resynchronization failures
  • Reactivating the original vFiler unit using SnapMirror commands
  • Reactivating the original vFiler unit using vFiler dr commands
  • Re-creating the vFiler unit on a replacement storage system
• Data migration
• What data migration is
• Secure communication for setup of data migration
• How migrating a vFiler unit affects clients
• Methods of data migration
• How to migrate a vFiler unit by copying data (SnapMirror)
  • Prerequisites for migrating a vFiler unit by copying data
  • What the vfiler migrate commands do
  • Adjusting client and network configurations if migrating to a different subnet
• How to migrate a vFiler unit without copying data (SnapMover)
  • What SnapMover vFiler unit migration is
  • Enabling SnapMover vFiler unit migration
  • Requirements for vFiler unit migration between active/active nodes
  • Guidelines for setting up volumes to support vFiler unit migration
  • What SnapMover vFiler unit migration does
  • Performing vFiler unit migration on volumes
  • Disabling SnapMover vFiler unit migration
• Disk space management using quotas
• How to manage quotas
  • Allowing or disallowing quotas for a volume
  • Quota specification management
  • Turning quotas on or off from a vFiler unit
• When quota thresholds and soft quotas are exceeded
• How you can resize quotas
• How the quotas file works
• Displaying quota status
• Displaying a quota report