Administrator Guide
Table Of Contents
- Dell EMC PowerVault ME4 Series Storage System Administrator’s Guide
- Contents
- Getting started
- New user setup
- Configure and provision a new storage system
- Using the PowerVault Manager interface
- System concepts
- About virtual and linear storage
- About disk groups
- About RAID levels
- About ADAPT
- About SSDs
- About SSD read cache
- About spares
- About pools
- About volumes and volume groups
- About volume cache options
- About thin provisioning
- About automated tiered storage
- About initiators, hosts, and host groups
- About volume mapping
- About operating with a single controller
- About snapshots
- About copying volumes
- About reconstruction
- About quick rebuild
- About performance statistics
- About firmware updates
- About managed logs
- About SupportAssist
- About CloudIQ
- About configuring DNS settings
- About replicating virtual volumes
- About the Full Disk Encryption feature
- About data protection with a single controller
- Working in the Home topic
- Guided setup
- Provisioning disk groups and pools
- Attaching hosts and volumes in the Host Setup wizard
- Overall system status
- Configuring system settings
- Managing scheduled tasks
- Working in the System topic
- Viewing system components
- Systems Settings panel
- Resetting host ports
- Rescanning disk channels
- Clearing disk metadata
- Updating firmware
- Changing FDE settings
- Configuring advanced settings
- Changing disk settings
- Changing system cache settings
- Configuring partner firmware update
- Configuring system utilities
- Using maintenance mode
- Restarting or shutting down controllers
- Working in the Hosts topic
- Working in the Pools topic
- Working in the Volumes topic
- Viewing volumes
- Creating a virtual volume
- Creating a linear volume
- Modifying a volume
- Copying a volume or snapshot
- Abort a volume copy
- Adding volumes to a volume group
- Removing volumes from a volume group
- Renaming a volume group
- Remove volume groups
- Rolling back a virtual volume
- Deleting volumes and snapshots
- Creating snapshots
- Resetting a snapshot
- Creating a replication set from the Volumes topic
- Initiating or scheduling a replication from the Volumes topic
- Manage replication schedules from the Volumes topic
- Working in the Mappings topic
- Working in the Replications topic
- About replicating virtual volumes in the Replications topic
- Replication prerequisites
- Replication process
- Creating a virtual pool for replication
- Setting up snapshot space management in the context of replication
- Replication and empty allocated pages
- Disaster recovery
- Accessing the data while keeping the replication set intact
- Accessing the data from the backup system as if it were the primary system
- Disaster recovery procedures
- Viewing replications
- Querying a peer connection
- Creating a peer connection
- Modifying a peer connection
- Deleting a peer connection
- Creating a replication set from the Replications topic
- Modifying a replication set
- Deleting a replication set
- Initiating or scheduling a replication from the Replications topic
- Stopping a replication
- Suspending a replication
- Resuming a replication
- Manage replication schedules from the Replications topic
- About replicating virtual volumes in the Replications topic
- Working in the Performance topic
- Working in the banner and footer
- Banner and footer overview
- Viewing system information
- Viewing certificate information
- Viewing connection information
- Viewing system date and time information
- Viewing user information
- Viewing health information
- Viewing event information
- Viewing capacity information
- Viewing host information
- Viewing tier information
- Viewing recent system activity
- Other management interfaces
- SNMP reference
- Using FTP and SFTP
- Using SMI-S
- Using SLP
- Administering a log-collection system
- Best practices
- System configuration limits
- Glossary of terms
● The Adaptive option works well for most applications: it enables adaptive read-ahead, which allows the controller to
dynamically calculate the optimum read-ahead size for the current workload.
● The Stripe option sets the read-ahead size to one stripe. The controllers treat NRAID and RAID-1 disk groups internally as if
they have a stripe size of 512 KB, even though they are not striped.
● Specific size options let you select an amount of data for all accesses.
● The Disabled option turns off read-ahead cache. This is useful if the host is triggering read ahead for what are random
accesses. This can happen if the host breaks up the random I/O into two smaller reads, triggering read ahead.
About thin provisioning
Thin provisioning is a virtual storage feature that allows a system administrator to overcommit physical storage resources.
This allows the host system to operate as though it has more storage available than is actually allocated to it. When physical
resources fill up, the administrator can add physical storage by adding additional disk groups on demand.
Paging is required to eliminate the lack of flexibility associated with linear mapping. Linear mapping limits the ability to easily
expand the physical storage behind the thin-provisioned volume. Paged mapping allows physical resources to be disparate and
noncontiguous, making it much easier to add storage on the fly.
For example, contrast the methods for creating a volume for Microsoft Exchange Server data:
● Typically, administrators create a storage-side volume for Exchange and map that volume with an assigned Logical Unit
Number (LUN) to hosts, and then create a Microsoft Windows volume for that LUN. Each volume has a fixed size. There are
ways to increase the size of a storage-side volume and its associated Windows volume, but they are often cumbersome. The
administrator must make a trade-off between initial disk costs and a volume size that provides capacity for future growth.
● With thin provisioning, the administrator can create a very large volume, up to the maximum size allowed by Windows. The
administrator can begin with only a small number of disks, and add more as physical storage needs grow. The process of
expanding the Windows volume is eliminated.
NOTE:
For a thin-provisioned volume mapped to a host, when data is deleted from the volume not all of the pages, or
space associated with that data will be deallocated, or released. This is especially true for smaller files. To deallocate the
pages in Windows, select the mapped volume and do either of the following:
● Perform a quick format.
● View its properties, select the Tools tab, and under Defragmentation, click Optimize.
Pool overcommit behavior
The standard behavior for thin provisioning depends on whether the pool overcommit feature is disabled or enabled.
● When the overcommit feature is disabled, the host does not lose read or write access to the pool volumes when the pool
reaches or exceeds the high threshold value.
● When the overcommit feature is enabled, the storage system sends the data protect sense key Add, Sense: Space
allocation failed write protect to the host when the pool reaches or exceeds the high threshold value. If the
host is rebooted after the pool reaches or exceeds the high threshold value, the host loses read and write access to the pool
volumes. The only way to regain read and write access to the pool volumes is to add more storage to the pool.
About automated tiered storage
Automated Tiered Storage is a virtual storage feature that automatically moves data residing in one class of disks to a more
appropriate class of disks based on data access patterns, with no manual configuration necessary.
● Frequently accessed data can move to disks with higher performance.
● Infrequently accessed data can move to disks with lower performance and lower costs.
Each virtual disk group, depending on the type of disks it uses, is automatically assigned to one of the following tiers:
● Performance – This highest tier uses SSDs, which provide the best performance but also the highest cost. For more
information on SSDs, see About SSDs on page 19.
● Standard – This middle tier uses enterprise-class spinning SAS disks, which provide good performance with mid-level cost
and capacity.
● Archive – This lowest tier uses midline spinning SAS disks, which provide the lowest performance with the lowest cost and
highest capacity.
24
Getting started