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
Cache Power Changes to write-through if cache backup power is not fully charged or fails. Enabled by
default.
CompactFlash Changes to write-through if CompactFlash memory is not detected during POST, fails during
POST, or fails while the controller is under operation. Enabled by default.
Power Supply Failure Changes to write-through if a power supply unit fails. Disabled by default.
Fan Failure Changes to write-through if a cooling fan fails. Disabled by default.
Over-temperature
Failure
Forces a controller shutdown if a temperature is detected that exceeds system threshold limits.
Disabled by default.
3. In the Auto-Write Through Cache Behaviors section, either select to enable or clear to disable the options:
Revert when Trigger Condition
Clears
When enabled, the cache policy changes back to write-back caching after the
trigger condition is cleared. When disabled, the cache policy remains write-through
caching after the trigger condition is cleared. Enabled by default.
Notify Other Controller Notifies the partner controller that a trigger condition occurred. Enable this option
to have the partner also change to write-through mode for better data protection.
Disable this option to allow the partner to continue using its current caching mode
for better performance. In a dual-controller system this option is disabled by default.
In Single Controller mode this option is grayed out.
4. Click Apply. If you disabled Cache Power or CompactFlash, a confirmation prompt appears. Choose Apply to accept the
changes, or Cancel to discard the changes.
Configuring partner firmware update
In a dual-controller system in which partner firmware update is enabled (the default), when you update firmware on one
controller, the system automatically updates the partner controller. Disable partner firmware update only if requested by a
service technician.
Change the partner firmware update setting
1. In the System topic, select Action > Advanced Settings > Firmware.
2. Either select (enable) or clear (disable) the Partner Firmware Update option.
3. Click Apply.
Configuring system utilities
The System Utilities tab lets you configure background scrub for disk groups and individual disks, set utility priority, and enable
or disable managed logs.
Configuring background scrub for disk groups
You can enable or disable whether the system continuously analyzes disks in disk groups to find and fix disk errors. This
command will fix parity mismatches for RAID 5 and 6; find but not fix mirror mismatches for RAID 1 and 10. It will not fix media
errors.
You can use a disk group while it is being scrubbed. Background disk group scrub runs at background utility priority, which
reduces to no activity if processor usage is above a certain percentage or if I/O is occurring on the disk group being scrubbed.
A disk group scrub may be in process on multiple disk groups at once. A new disk group will first be scrubbed 20 minutes after
creation. After a disk group is scrubbed, scrub will start again after the interval specified by the Disk Group Scrub Interval
hours option.
When a scrub is complete, event 207 is logged and specifies whether errors were found and whether user action is required.
Enabling background disk group scrub is recommended.
72
Working in the System topic