Table of Contents
Advertisement
Advertisement
Table of Contents
Subscribe to Our Youtube Channel
Related Manuals for Dell EMC PowerVault MD Series
Summary of Contents for Dell EMC PowerVault MD Series
- Page 1 Dell EMC PowerVault MD 34XX/38XX Series Storage Arrays Administrator's Guide...
- Page 2 Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your product. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death.
-
Page 3: Table Of Contents
Contents 1 Introduction..............................12 Dell EMC PowerVault Modular Disk Storage Manager....................12 User interface..................................12 Enterprise management window............................ 13 Inheriting the system settings........................... 13 Array management window.............................14 Dell EMC PowerVault Modular Disk Configuration Utility................... 15 Related documentation..............................15 2 About your MD Series storage array......................16 Physical disks, virtual disks, and disk groups.........................16... - Page 4 Disk migration................................23 Disk roaming................................24 Host server-to-virtual disk mapping........................24 Host types...................................24 Advanced features................................24 Types of snapshot functionality supported......................25 Virtual disk copy................................. 25 Virtual disk recovery..............................26 Multi-path software.................................26 Preferred and alternate controllers and paths......................26 Virtual disk ownership..............................26 Load balancing..................................
- Page 5 Configuring SNMP alerts............................45 Battery settings................................47 Changing the battery settings..........................47 Setting the storage array RAID controller module clocks................... 48 4 Using iSCSI..............................49 Changing the iSCSI target authentication........................49 Entering mutual authentication permissions........................ 50 Creating CHAP secrets..............................50 Initiator CHAP secret..............................50 Target CHAP secret..............................50 Valid characters for CHAP secrets..........................
- Page 6 Changing the virtual disk modification priority.......................66 Changing virtual disk cache settings........................66 Changing segment size of virtual disk........................67 Changing the I/O type.............................. 68 Thin virtual disks................................68 Advantages of thin virtual disks..........................68 Physical vs virtual capacity an a thin virtual disk....................69 Thin virtual disk requirements and limitations......................69 Thin virtual disk attributes............................70 Thin virtual disk states...............................70...
- Page 7 Using free capacity..............................90 Using unconfigured capacity............................ 90 Disk group migration.................................91 Export disk group................................91 Import disk group............................... 92 Storage array media scan..............................92 Changing media scan settings..........................93 Suspending media scan.............................93 8 Disk pools and disk pool virtual disks......................94 Difference between disk groups and disk pools......................95 Disk pool restrictions...............................
- Page 8 Snapshot Virtual Disk read/write properties.......................109 Snapshot groups and consistency groups........................110 Snapshot groups............................... 110 Snapshot consistency groups..........................110 Understanding snapshot repositories..........................111 Consistency group repositories..........................111 Ranking repository candidates..........................111 Using snapshot consistency group to a Remote Replication................111 Creating snapshot images..............................112 Creating snapshot image............................112 Canceling a pending snapshot image........................113 Deleting snapshot image............................
- Page 9 Manually creating a consistency group Snapshot Virtual Disk repository............132 Disabling Snapshot Virtual Disk or consistency group Snapshot Virtual Disk........... 133 Re-creating a Snapshot Virtual Disk or consistency group Snapshot Virtual Disk........... 134 Changing the modification priority of an overall repository virtual disk............. 135 Changing the media scan setting of an overall repository virtual disk...............135 Changing the pre-read consistency check setting of an overall repository virtual disk........136 Increasing capacity of overall repository........................
- Page 10 Ready for use................................151 Linux host server reboot best practices........................151 Important information about special partitions......................152 Limitations and known issues............................152 Troubleshooting................................153 13 Configuring Asymmetric Logical Unit Access.................... 154 ALUA performance considerations..........................154 Automatic transfer of ownership..........................154 Native ALUA support on Microsoft Windows and Linux................... 154 Enabling ALUA on VMware ESXi ..........................155 Manually adding SATP rule in ESXi 5.x........................
- Page 11 SMrepassist utility................................182 Unidentified devices............................... 182 Recovering from unidentified storage array........................ 183 Starting or restarting the Host Context Agent software..................184 Starting the SMagent software in Windows......................184 Starting SMagent software in Linux........................184 19 Getting help.............................. 185 Contacting Dell EMC..............................185 Contents...
-
Page 12: Introduction
Dell EMC PowerVault Modular Disk Storage Manager Dell EMC PowerVault Modular Disk Storage Manager (MD Storage Manager) is a graphical user interface (GUI) application used to configure and manage one or more MD Series storage arrays. The MD Storage Manager software is located on the MD Series resource DVD. -
Page 13: Enterprise Management Window
• The menu bar, beneath the title bar—You can select menu options from the menu bar to perform tasks on a storage array. • The toolbar, beneath the menu bar—You can select options in the toolbar to perform tasks on a storage array. NOTE: The toolbar is available only in the EMW. -
Page 14: Array Management Window
Click OK. Array management window You can launch the AMW from the EMW. The AMW provides management functions for a single storage array. You can have multiple AMWs open simultaneously to manage different storage arrays. In the AMW, you can: •... -
Page 15: Dell Emc Powervault Modular Disk Configuration Utility
Utility NOTE: Dell EMC PowerVault Modular Disk Configuration Utility (MDCU) is supported only on MD Series storage arrays that use the iSCSI protocol. MDCU is an iSCSI Configuration Wizard that can be used with MD Storage Manager to simplify the configuration of iSCSI connections. -
Page 16: About Your Md Series Storage Array
Physical disks Only Dell EMC supported physical disks are supported in the storage array. If the storage array detects unsupported physical disks, it marks the disk as unsupported and the physical disk becomes unavailable for all operations. -
Page 17: Virtual Disks And Disk Groups
Status Mode Description Optimal Hot Spare in use The physical disk in the indicated slot is in use as a hot spare within a disk group. Failed Assigned, Unassigned, Hot Spare in use, The physical disk in the indicated slot has failed because of an or Hot Spare Standby unrecoverable error, an incorrect physical disk type or physical disk size, or by its operational state being set to failed. -
Page 18: Disk Pools
Maximum physical disk support limitations Although PowerVault MD Series storage arrays with premium feature kit can support up to 180 physical disks, RAID 0 and RAID 10 configurations with more than 120 physical disks are not supported. MD Storage Manager does not enforce 120-physical disk limit when you setup a RAID 0 or RAID 10 configuration. -
Page 19: Raid 0
RAID 0 CAUTION: Do not attempt to create virtual disk groups exceeding 120 physical disks in a RAID 0 configuration even if premium feature is activated on your storage array. Exceeding the 120-physical disk limit may cause your storage array to be unstable. RAID 0 uses disk striping to provide high data throughput, especially for large files in an environment that requires no data consistency. -
Page 20: Virtual Disk Operations
The segment size or stripe element size specifies the size of data in a stripe written to a single disk. The storage array supports stripe element sizes of 8 KB, 16 KB, 32 KB, 64 KB, 128 KB, and 256 KB. The default stripe element size is 128 KB. Stripe width, or depth, refers to the number of disks involved in an array where striping is implemented. -
Page 21: Virtual Disk Operations Limit
after the current cycle. If the media verification process on a disk group is stopped due to a RAID controller module restart, the storage array resumes the process from the last checkpoint. Virtual disk operations limit The maximum number of active, concurrent virtual disk processes per RAID controller module installed in the storage array is four. This limit is applied to the following virtual disk processes: •... -
Page 22: Disk Group Expansion
For more information about virtual disk capacity expansion, see Virtual disk expansion. Disk group expansion Because the storage array supports hot-swappable physical disks, you can add two physical disks at a time for each disk group while the storage array remains online. Data remains accessible on virtual disk groups, virtual disks, and physical disks throughout the operation. The data and increased unused free space are dynamically redistributed across the disk group. -
Page 23: Virtual Disk Migration And Disk Roaming
NOTE: Setting a high priority level impacts storage array performance. It is not advisable to set priority levels at the maximum level. Priority must also be assessed in terms of impact to host server access and time to complete an operation. For example, the longer a rebuild of a degraded virtual disk takes, the greater the risk for potential secondary disk failure. -
Page 24: Disk Roaming
destination storage array has been turned on and has successfully recognized the newly migrated physical disks, migration operations can continue. NOTE: Disk groups from multiple storage arrays must not be migrated at the same time to a storage array that has no existing physical disks. -
Page 25: Types Of Snapshot Functionality Supported
Types of snapshot functionality supported The following types of virtual disk snapshot premium feature is supported on the MD storage array: • Snapshot Virtual Disks using multiple point-in-time (PiT) groups — This feature also supports snapshot groups, snapshot images, and consistency groups. -
Page 26: Virtual Disk Recovery
Virtual disk recovery You can use the Edit host server-to-virtual disk mappings feature to recover data from the backup virtual disk. This functionality enables you to unmap the original source virtual disk from its host server, then map the backup virtual disk to the same host server. Ensure that you record the LUN used to provide access to the source virtual disk. -
Page 27: Load Balancing
• Different virtual disks have higher usage at different times of day. Load balancing A load balance policy is used to determine which path is used to process I/O. Multiple options for setting the load balance policies let you optimize I/O performance when mixed host interfaces are configured. You can choose one of these load balance policies to optimize I/O performance: •... -
Page 28: Interpreting Performance Monitor Data
Type of Sampling Interval Length of Time Maximum Number Ability to Save Data How Monitoring Performance Displayed of Objects Displayed Starts and Stops Monitoring when View Real-time Textual Performance Monitor dialog closes or AMW closes. Background 10 min 7 day rolling window Starts and stops manually. - Page 29 Performance Data Implications for Performance Tuning continue to meet application needs at an acceptable performance level. IOs/sec Factors that affect input/output operations per second (IOs/sec or IOPS) include these items: • Access pattern (random or sequential) • I/O size • RAID level •...
-
Page 30: Viewing Real-Time Graphical Performance Monitor Data
Performance Data Implications for Performance Tuning Higher latency might indicate that the I/O pattern is random in nature. Physical disks with random I/O will have greater latency than those with sequential streams. If a disk group is shared among several virtual disks, the individual virtual disks might need their own disk groups to improve the sequential performance of the physical disks and decrease latency. -
Page 31: Customizing The Performance Monitor Dashboard
Customizing the performance monitor dashboard The dashboard on the Performance tab initially contains five predefined portlets and one undefined portlet. You can customize all of the portlets to display the performance data that is most meaningful to you. In the Array Management Window (AMW), select the Performance tab. Do one of the following actions: •... -
Page 32: Viewing Real-Time Textual Performance Monitor
module level. The values reported for a RAID controller module, or a storage array might be greater than the sum of the values reported for all the virtual disks. The values reported for a RAID controller module or storage array include both host I/Os and I/Os internal to the storage array (metadata reads and writes), whereas the values reported for a virtual disk include only host I/Os. -
Page 33: Saving Real-Time Textual Performance Data
Saving real-time textual performance data A feature that real-time textual performance monitoring has that real-time graphical performance monitoring does not have is that you can save the data. Saving the data saves only one set of data from the most recent sampling interval. In the Array Management Window (AMW), do one of the following: •... -
Page 34: Viewing Information About The Current Background Performance Monitor Session
NOTE: For accurate data, do not change the system date or time while using background performance monitor. If you must change the system date, stop and restart the background performance monitor. To manually stop background performance monitoring, click the Stop link. Background performance monitoring automatically stops when you close the Enterprise Management Window (EMW). -
Page 35: Saving The Current Background Performance Monitor Data
The resulting graph shows all the data points from the current background performance monitoring session. NOTE: If you do not see a line that you defined on the graph, it might be overlapping another line. If you perform the View Current option before the first sampling interval elapses (10 minutes), the graph shows that it is initializing. -
Page 36: Invalid Objects In Performance Monitor
Invalid objects in Performance Monitor When viewing a performance graph, you might see objects marked with an asterisk (*). An asterisk indicates that the object is no longer valid. When an object becomes invalid, the performance graph contains missing data points. The data that was collected before the object became invalid is still available for viewing. -
Page 37: Discovering And Managing Your Storage Array
Discovering and managing your storage array You can manage a storage array in two ways: • Out-of-band management • In-band management The Enterprise Management Window (EMW) is the first page that loads when you open the Modular Disk Storage Manager (MDSM) and it allows you to discover, connect to, and manage MD3 storage arrays through in-band and out-of-band connectivity. -
Page 38: In-Band Management
In-band management Using in-band-management, commands, events, and data travel through the host-to-controller interface. Unlike out-of-band management, commands and events are mixed with data. NOTE: For detailed information about setting up in-band and out-of-band management see your system’s Deployment Guide at Dell.com/support/manuals. -
Page 39: Setting Up Your Storage Array
To add a storage array that uses out-of-band management, specify the host name or management port IP address of each controller in the storage array. To add an in-band storage array, add the host through which the storage array is attached to the network. NOTE: It can take several minutes for the MD Storage Manager to connect to the specified storage array. -
Page 40: Locating Storage Arrays
Locating storage arrays You can use the Blink option to physically locate and identify a storage array. To locate the storage array: Select the relevant storage array and do one of the following: • In the EMW, right-click the appropriate storage array, and select Blink Storage Array. •... -
Page 41: Adding Or Editing A Comment To An Existing Storage Array
The AMW for the selected storage array is displayed. In the AMW, select the Setup tab, and click Set a Storage Array Password. The Set Password dialog is displayed. If you are resetting the password, type the Current password. NOTE: If you are setting the password for the first time, leave the Current password blank. -
Page 42: Removing Storage Arrays
Removing storage arrays You can remove a storage array from the list of managed arrays if you no longer want to manage it from a specific storage management station. Removing a storage array does not affect the storage array or its data in any way. Removing a storage array only removes it from the list of storage arrays displayed in the Devices tab of the EMW. -
Page 43: Changing The Cache Settings On The Storage Array
Changing the cache settings on the storage array To change the storage array cache settings: In the AMW, select Storage Array > Change > Cache Settings. The Change Cache Settings window is displayed. In Start demand cache flushing , select or enter the percentage of unwritten data in the cache to trigger a cache flush . Select the appropriate Cache block size. -
Page 44: Configuring E-Mail Alerts
d Click OK. The Configure Alerts dialog is displayed. For a single storage array: Select the Devices tab. b Select the relevant storage array, then select Edit > Configure Alerts. The Configure Alerts dialog is displayed. Configure e-mail or SNMP alerts. For more information, see Configuring E-mail Alerts Configuring SNMP... -
Page 45: Configuring Snmp Alerts
Click OK. An alert icon is displayed next to each node in the Tree view where an alert is set. If required, verify if the e-mail is sent successfully: • Provide an SMTP mail server name and an e-mail sender address for the e-mail addresses to work. •... - Page 46 • For more specific notifications, you can configure the alert destinations at the storage management station, host, and storage array levels. Do one of the following actions based on whether you want to configure alerts for a single storage array or for all storage arrays. •...
-
Page 47: Battery Settings
• The Location field populates the variable sysLocation. • The Contact field populates the variable sysContact. Click Configure SNMP MIB-II Variables. b In the Name text box, the Location text box, and the Contact text box, enter the desired information. You can enter only printable ASCII characters. -
Page 48: Setting The Storage Array Raid Controller Module Clocks
The Battery Settings dialog is displayed. You can change these details about the battery learn cycle: • Schedule day • Schedule time Setting the storage array RAID controller module clocks You can use the Synchronize Clocks option to synchronize the storage array RAID controller module clocks with the storage management station. -
Page 49: Using Iscsi
Using iSCSI NOTE: The following sections are relevant only to MD xx 0i storage arrays that use the iSCSI protocol. Topics: • Changing the iSCSI target authentication • Entering mutual authentication permissions • Creating CHAP secrets • Changing the iSCSI target identification •... -
Page 50: Entering Mutual Authentication Permissions
Entering mutual authentication permissions Mutual authentication or two-way authentication is a way for a client or a user to verify themselves to a host server, and for the host server to validate itself to the user. This validation is accomplished in such a way that both parties are sure of the other’s identity. To add mutual authentication permissions: In the AMW, select the Setup tab. -
Page 51: Changing The Iscsi Target Identification
Changing the iSCSI target identification You cannot change the iSCSI target name, but you can associate an alias with the target for simpler identification. Aliases are useful because the iSCSI target names are not intuitive. Provide an iSCSI target alias that is meaningful and easy to remember. To change the iSCSI target identification: In the AMW, select the Setup tab. -
Page 52: Configuring The Iscsi Host Ports
Configuring the iSCSI host ports The default method for configuring the iSCSI host ports, for IPv4 addressing, is DHCP. Always use this method unless your network does not have a DHCP server. It is advisable to assign static DHCP addresses to the iSCSI ports to ensure continuous connectivity. For IPv6 addressing, the default method is Stateless auto-configuration. -
Page 53: Viewing Or Ending An Iscsi Session
Setting Description NOTE: For more information about creating and configuring a VLAN with MD Support Manager, in the AMW, click the Support tab, then click View Online Help. Ethernet Priority The network priority can be set from lowest to highest. Although network managers must determine these mappings, the IEEE has made broad recommendations: •... -
Page 54: Edit, Remove, Or Rename Host Topology
• Ethernet TCP/IP statistics • Target (protocol) statistics • Local initiator (protocol) statistics In the Options area, select: • Raw statistics — To view the raw statistics. Raw statistics are all the statistics that have been gathered since the RAID controller modules were started. -
Page 55: Event Monitor
Event monitor An event monitor is provided with Dell EMC PowerVault Modular Disk Storage Manager. The event monitor runs continuously in the background and monitors activity on the managed storage arrays. If the event monitor detects any critical problems, it can notify a host or remote system using e-mail, Simple Network Management Protocol (SNMP) trap messages, or both. -
Page 56: Linux
Linux To enable the event monitor, at the command prompt, type SMmonitor start and press <Enter>. When the program startup begins, the following message is displayed: SMmonitor started. To disable the event monitor, start terminal emulation application (console ox xterm) and at the command prompt, type SMmonitor stop, and press <Enter>. -
Page 57: About Your Host
Configuring host access Dell EMC PowerVault Modular Disk Storage Manager (MD Storage Manager) is comprised of multiple modules. One of these modules is the Host Context Agent, which is installed as part of the MD Storage Manager installation and runs continuously in the background. -
Page 58: Defining A Host
Defining a host You can use the Define Host Wizard in the AMW to define a host for a storage array. Either a known unassociated host port identifier or a new host port identifier can be added. A user label must be specified before the host port identifier may be added (the Add button is disabled until one is entered). To define a host: In the AMW, select the Host Mappings tab. -
Page 59: Removing Host Access
Removing host access To remove host access: In the AMW, select the Host Mappings tab. Select the host node from the object tree on the left pane. Perform one of these actions: • From the menu bar, select Host Mappings > Host > Remove. •... -
Page 60: Removing A Host From A Host Group
Removing a host from a host group You can remove a host from the object tree on the Host Mappings tab of the AMW. For more information, see Removing A Host Group. Moving a host to a different host group To move a host to a different host group: In the AMW, select the Host Mappings tab, select the host node in the object tree. -
Page 61: Starting Or Stopping The Host Context Agent
• Replacing a host connection • Changing a host type The MD Storage Manager automatically detects these changes for any host running the host agent software. Starting or stopping the Host Context Agent The Host Context Agent discovers the host topology. The Host Context Agent starts and stops with the host. The topology discovered by the Host Context Agent can be viewed by clicking Configure Host Access (Automatic) in the Configure tab in the MD Storage Manager. -
Page 62: Managing Host Port Identifiers
Managing host port identifiers You can do the following to manage the host port identifiers that are added to the storage array: • Add — Add or associate a new host port identifier to a particular host. • Edit — Change the host port identifier alias or user label. You can move (associate) the host port identifier to a new host. •... -
Page 63: Disk Groups, Standard Virtual Disks, And Thin Virtual Disks
Disk groups, standard virtual disks, and thin virtual disks Creating disk groups and virtual disks Disk groups are created in the unconfigured capacity of a storage array, and virtual disks are created in the free capacity of a disk group or disk pool. -
Page 64: Locating Disk Group
To create disk groups: To start the Create Disk Group Wizard, perform one of these actions: • To create a disk group from unconfigured capacity in the storage array, in the Storage & Copy Services tab, select a storage array and right-click the Total Unconfigured Capacity node, and select Create Disk Group from the pop-up menu. -
Page 65: Creating Standard Virtual Disks
Click OK. Creating standard virtual disks Keep these important guidelines in mind when you create a standard virtual disk: • Many hosts can have 256 logical unit numbers (LUNs) mapped per storage partition, but the number varies per operating system. •... -
Page 66: Changing The Virtual Disk Modification Priority
Changing the virtual disk modification priority You can specify the modification priority setting for a single virtual disk or multiple virtual disks on a storage array. Guidelines to change the modification priority of a virtual disk: • If more than one virtual disk is selected, the modification priority defaults to the lowest priority. The current priority is shown only if a single virtual disk is selected. -
Page 67: Changing Segment Size Of Virtual Disk
– Enable write caching with replication — to replicate cached data across two redundant RAID controller modules that have the same cache size. • Enable dynamic cache read prefetch CAUTION: Possible loss of data—Selecting the Enable write caching without batteries option lets write caching continue even when the batteries are discharged completely or are not fully charged. -
Page 68: Changing The I/O Type
The segment size modification operation begins. The virtual disk icon in the Details pane shows an Operation in Progress status while the operation is taking place. NOTE: To view the progress or change the priority of the modification operation, select a virtual disk in the disk group, and from the menu bar, select Storage >... -
Page 69: Physical Vs Virtual Capacity An A Thin Virtual Disk
However, in certain cases, standard virtual disks may provide a more suitable alternative compared to thin provisioning, such as in situations when: • you anticipate that storage consumption on a virtual disk is highly unpredictable or volatile • an application relying on a specific virtual disk is exceptionally mission critical Physical vs virtual capacity an a thin virtual disk When you configure a thin virtual disk, you can specify the following types of capacity: •... -
Page 70: Thin Virtual Disk Attributes
• The pre-read consistency check for a thin virtual disk cannot be enabled. • A thin virtual disk cannot serve as the target virtual disk in a Virtual Disk Copy. • A thin virtual disk cannot be used in a Remote Replication (Legacy) operation. Thin virtual disk attributes When you create a thin virtual disk from free capacity in an existing disk pool, you can manually set disk attributes or allow MD Storage Manager to assign default attributes. -
Page 71: Rollback On Thin Virtual Disks
Copy Services Feature Standard Virtual Disk in a Disk Group Standard Virtual Disk in a Disk Thin Virtual Disk Pool Remote Replication Supported Supported Not supported The source of a virtual disk copy can be either a standard virtual disk in a disk group, a standard virtual disk in a disk pool, or a thin virtual disk. - Page 72 Initializing thin virtual disk with same physical capacity CAUTION: Initializing a thin virtual disk erases all data from the virtual disk. • You can create thin virtual disks only from disk pools, not from disk groups. • By initializing a thin virtual disk with the same physical capacity, the original repository is maintained but the contents of the thin virtual disk are deleted.
- Page 73 Based on the value that you entered in the previous step, the Disk pool physical capacity candidates table is populated with matching repositories. Select a repository from the table. Existing repositories are placed at the top of the list. NOTE: The benefit of reusing an existing repository is that you can avoid the initialization process that occurs when you create a new one.
-
Page 74: Changing A Thin Virtual Disk To A Standard Virtual Disk
Existing repositories are placed at the top of the list. NOTE: The benefit of reusing an existing repository is that you can avoid the initialization process that occurs when you create a new one. If you want to change the repository expansion policy or warning threshold, click View advanced repository settings. •... -
Page 75: Choosing An Appropriate Physical Disk Type
Choosing an appropriate physical disk type You can create disk groups and virtual disks in the storage array. You must select the capacity that you want to allocate for the virtual disk from either unconfigured capacity, free capacity, or an existing disk pool available in the storage array. Then you define basic and optional advanced parameters for the virtual disk. -
Page 76: Creating A Security Key
• Import Key • Unlock Drives NOTE: If you have not created a security key for the storage array, the Create Key option is active. If you have created a security key for the storage array, the Create Key option is inactive with a check mark to the left. The Change Key option, the Save Key option, and the Validate Key option are now active. -
Page 77: Changing Security Key
• The password should be between eight and 30 characters long. • The password should contain at least one uppercase letter. • The password should contain at least one lowercase letter. • The password should contain at least one number. •... -
Page 78: Saving A Security Key
• In storage arrays with two RAID controller modules, both are present and working normally. To change the security key: In the AMW menu bar, select Storage Array > Security > Physical Disk Security > Change Key. The Confirm Change Security Key window is displayed. Type yes in the text field, and click OK. -
Page 79: Validate Security Key
Click Save. Make a record of the security key identifier and the file name from the Save Security Key Complete dialog, and click OK. Validate security key A file in which a security key is stored is validated through the Validate Security Key dialog. To transfer, archive, or back up the security key, the RAID controller module firmware encrypts (or wraps) the security key and stores it in a file. -
Page 80: Hot Spares And Rebuild
• The availability of enclosure loss protection for a disk group depends on the location of the physical disks that comprise the disk group. To make sure that enclosure loss protection is not affected, you must replace a failed physical disk to initiate the copyback process. See Enclosure Loss Protection. -
Page 81: Hot Spare Operation
NOTE: All SED physical disks supported on MD34xx/MD38xx are FIPS certified. For details, see the Supported physical disk Dell PowerVault MD Series Support Matrix at Dell.com/powervaultmanuals. section in the Attention: When a disk pool or disk group is secured, the only way to remove security is to delete the disk pool or disk group. -
Page 82: Enclosure Loss Protection
Physical Disk Security feature, and should not be confused with the pass phrase that is used to protect copies of a security key. However, Dell EMC recommends that you set a storage array password before you create, change, or save a security key or unlock secure physical disks. -
Page 83: Drawer Loss Protection
RAID Level Criteria for Enclosure Loss Protection Because a RAID level 1 disk group requires a minimum of two physical disks, enclosure loss protections cannot be achieved if your storage array has less than two expansion enclosures. RAID level 0 Because RAID level 0 does not have consistency, you cannot achieve enclosure loss protection. -
Page 84: Creating Host-To-Virtual Disk Mappings
The following are the guidelines to configure host-to-virtual disk mapping: • Each virtual disk in the storage array can be mapped to only one host or host group. • Host-to-virtual disk mappings are shared between controllers in the storage array. •... -
Page 85: Modifying And Removing Host-To-Virtual Disk Mapping
Modifying and removing host-to-virtual disk mapping You can modify or remove a host-to-virtual disk mapping for several reasons, such as an incorrect mapping or reconfiguration of the storage array. Modifying or removing a host-to-virtual disk mapping applies to both hosts and host groups. CAUTION: Before you modify or remove a host-to-virtual disk mapping, stop any data access (I/O) to the virtual disks to prevent data loss. -
Page 86: Removing Host-To-Virtual Disk Mapping
Removing host-to-virtual disk mapping To remove the host to virtual disk mapping: In the AMW, select the Host Mappings tab. Select a virtual disk under Defined Mappings. Perform one of these actions: • From the menu bar, select Host Mappings > LUN Mapping > Remove. •... -
Page 87: Removing A Host-To-Virtual Disk Mapping Using Linux Dmmp
To change the RAID level of a disk group: In the AMW, select the Storage & Copy Services tab and select a disk group. From the menu bar, select Storage > Disk Group > Change > RAID Level. Select the appropriate RAID level and click Yes to confirm the selection. The RAID level operation begins. -
Page 88: Restricted Mappings
Restricted mappings Many hosts are able to map up to 256 LUNs (0–255) per storage partition. However, the maximum number of mappings differs because of operating system variables, multipath failover driver issues, and potential data problems. The hosts listed in the table have these mapping restrictions. -
Page 89: Disk Group And Virtual Disk Expansion
• Hosts with different operating systems are attached to the same storage array. In this case, a storage partition is created for each host type You can use the Storage Partitioning Wizard to define a single storage partition. The Storage Partitioning Wizard guides you through the major steps required to specify which host groups, hosts, virtual disks, and associated logical unit numbers (LUNs) are to be included in the storage partition. -
Page 90: Virtual Disk Expansion
NOTE: You can also use the Command Line Interface (CLI) on both Windows and Linux hosts to add free capacity to a disk Dell EMC PowerVault MD 34XX/38XX Series Storage Arrays CLI Guide . group. For more information, see the... -
Page 91: Disk Group Migration
Disk group migration Disk group migration allows to you to migrate a disk group by exporting a disk group and then importing it to another storage array. You can also export a disk group to store data offline. When you export a disk group, all the physical disks become offline. To ensure that the export is successful, at least two physical disks that are not part of the disk group you are migrating must be present in the storage array. -
Page 92: Import Disk Group
Import disk group The import disk group operation adds the imported disk group to the target storage array. After you complete the import disk group operation, all of the physical disks have Optimal status. Any associated virtual disks or free capacity nodes are now shown in the MD Storage Manager installed on the target storage array. -
Page 93: Changing Media Scan Settings
virtual disks without consistency protection (RAID 1, RAID 5, and RAID 6 virtual disks), the error is not corrected but is reported to the event log. • Recovered media error — Data could not be read by the physical disk on the first attempt but was successfully read on a subsequent attempt. -
Page 94: Disk Pools And Disk Pool Virtual Disks
Disk pools and disk pool virtual disks Disk pooling allows you to distribute data from each virtual disk randomly across a set of physical disks. Disk pooling provides RAID protection and consistent performance across a set of physical disks logically grouped together in the storage array. Although there is no limit on the maximum number of physical disks that can comprise a disk pool, each disk pool must have a minimum of 11 physical disks. -
Page 95: Difference Between Disk Groups And Disk Pools
Difference between disk groups and disk pools Similar to a disk group, you can create one or more virtual disks in a disk pool. However, the disk pool differs from a disk group in the way data is distributed across the physical disks comprising the pool. Dynamic Disk Pool (DDP) feature dynamically distributes data, spare capacity, and protects information across a pool of disk drives. -
Page 96: Automatically Managing Unconfigured Capacity In Disk Pools
To send alert notifications when the usable capacity of the disk pool is reaching a specified percentage, perform the following steps: Click View notification settings. b Select the check box corresponding to a critical warning notification. You also can select the check box corresponding to an early warning notification. The early warning notification is available only after you select the critical warning notification. -
Page 97: Locating Physical Disks In A Disk Pool
Locating physical disks in a disk pool You can use the Blink option to physically locate and identify all of the physical disks that comprise a selected disk pool. To locate a disk pool: Select the Storage & Copy Services tab. Select the disk pool in the Tree view or the Table view. -
Page 98: Adding Unassigned Physical Disks To A Disk Pool
When the unconfigured (free) capacity in the disk pool reaches the specified percentage, an alert notification in the form of e-mail messages and SNMP trap messages are sent to the destination addresses that are specified in the Configure Alerts dialog. For more information about how to specify the destination addresses, see Configuring Alert Notifications. -
Page 99: Changing The Raid Controller Module Ownership Of A Disk Pool
• Degraded Reconstruction Priority — The degraded reconstruction priority level determines the priority of the data reconstruction operation when a single physical disk fails in a disk pool. • Critical Reconstruction Priority — The critical reconstruction priority level determines the priority of the data reconstruction operation when at least two physical disks fail in a disk pool. -
Page 100: Deleting Disk Pool
Keep these important guidelines in mind before you check data consistency: • Disk pools are configured only as RAID Level 6. • You cannot use this option on RAID Level 0 disk groups that have no consistency. • If you use this option on a RAID Level 1 disk group, the consistency check compares the data on the replicated physical disks. •... -
Page 101: Viewing Storage Array Logical Components And Associated Physical Components
– The disk pool contains a base virtual disk or a target virtual disk participating in a virtual disk copy operation with the status of In Progress. To delete a disk pool: Select the Storage & Copy Services tab. Select one or more disk pools. From the menu bar, select Storage >... -
Page 102: Changing Capacity On Existing Thin Virtual Disks
The Secure Physical Disks option is displayed in the Disk Pool menu. The Secure Physical Disks option is active if these conditions are true: • The selected storage array is not security enabled but is comprised entirely of security capable physical disks. •... - Page 103 The Use flash SSD cache check box is disabled if: • no SSD cache is available • the disk pool is comprised of only SSD physical disks • the disk pool has different data service attributes from the SSD cache •...
-
Page 104: Using Ssd Cache
Using SSD cache The SSD cache feature uses solid-state disk (SSD) physical disks to improve read-only performance in your storage array. SSD physical disks are logically grouped together to provide secondary cache for use with the primary cache in the RAID controller module memory. Using SSD cache improves application throughput and response times and delivers sustained performance improvement across diverse workloads, especially high-IOP workloads. -
Page 105: Choosing Ssd Cache Parameters
• Overall data accessed by an application is routinely less than potential SSD cache capacity. To determine whether this is the case, reviewing the number of virtual disks and sizes that are cached often yields a reliable estimate. The more virtual disks that are cached, the more likely it is that your application accesses more data capacity than can be configured in SSD cache. -
Page 106: Viewing Physical Components Associated With An Ssd Cache
Viewing physical components associated with an SSD cache To view the physical components associated with an SSD cache: In the AMW, select the Storage & Copy Services tab. In the tree view, select the SSD cache. and do one of the following: •... -
Page 107: Removing Physical Disks From An Ssd Cache
Removing physical disks from an SSD cache To remove physical disks from an SSD cache: In the AMW, select the Storage & Copy Services tab. In the tree view, select the SSD cache from which you want to remove physical disk(s). Do one of the following: •... -
Page 108: Deleting Ssd Cache
Deleting SSD cache To delete an SSD cache: In the AMW, select the Storage & Copy Services tab. In the tree view, select the SSD cache and do one of the following: • From the menu bar, select Storage > SSD Cache > Delete. •... -
Page 109: Premium Feature-Snapshot Virtual Disk
Premium feature—Snapshot Virtual Disk The following virtual disk snapshot premium feature is supported on the MD storage array: • Snapshot Virtual Disks using multiple point-in-time (PiT) groups A snapshot image is a logical image of the content of an associated base virtual disk created at a specific point-in-time, often known as a restore point. -
Page 110: Snapshot Groups And Consistency Groups
The following are the differences between the two: • Read-Only snapshot virtual disks provide the host read access to a copy of the data contained in the snapshot image. However, the host cannot modify the snapshot image. A Read-Only snapshot virtual disk does require an associated repository. •... -
Page 111: Understanding Snapshot Repositories
A consistency group, pools multiple virtual disks together, enabling you to take a snapshot of all virtual disks at the same point in time. This creates a synchronized snapshot of all the virtual disks and is especially suitable for applications that span multiple virtual disks. For example, a database application containing log files on one virtual disk and the database on another. -
Page 112: Creating Snapshot Images
Additionally, all member virtual disks belonging to both a snapshot consistency group and a Remote Replication group must belong to the same Remote Replication group. Creating snapshot images A snapshot image is a logical point-in-time image of the content of an associated base virtual disk. With snapshot images, you can create multiple copies of production data on your storage array much more quickly than full copies. -
Page 113: Canceling A Pending Snapshot Image
NOTE: Make sure you have either existing repositories, enough free capacity nodes, or available unconfigured capacity for the storage array on which you are creating the snapshot group repository, otherwise you cannot create the repository and an error message is displayed. Click Finish. -
Page 114: Scheduling Snapshot Images
Type yes in the text box and then click Delete to delete the snapshot image. Scheduling snapshot images MD Storage Manager allows you to schedule regular snapshot image creation to enable file recovery, and scheduled backups. You can create a schedule for an existing snapshot group or consistency group or when you initially create a snapshot group or consistency group. •... -
Page 115: Editing A Snapshot Schedule
Editing a snapshot schedule Use the Edit Snapshot Image Schedule option to modify the schedule settings defined for a snapshot group or consistency group. You can also use the Edit Snapshot Image Schedule option to temporarily suspend scheduled snapshot image creation by disabling the schedule. -
Page 116: Starting Snapshot Rollback
– Virtual disk Expansion (VDE) to increase the capacity of a virtual disk. – Migrating a disk group to a different RAID level. – Changing the segment size of a virtual disk. • You cannot start a rollback operation if the base virtual disk is participating in a virtual disk copy. •... -
Page 117: Canceling Snapshot Image Rollback
Canceling snapshot image rollback Use the Cancel Rollback option to cancel a rollback operation after it has been started. You can cancel an active rollback that is in progress (actively copying data), a pending rollback (in a pending queue awaiting resources to start), or a rollback that has been paused due to an error. -
Page 118: Creating Snapshot Group
• While the rollback operation has a status of In Progress There are five priority rates available: lowest, low, medium, high, and highest. • If the priority is set at the lowest rate, I/O activity is prioritized and the rollback operation takes longer time to complete. •... -
Page 119: Manually Creating A Consistency Group Repository
• Select Manual and click Next to define the properties for the snapshot group repository; then click Finish to continue with the snapshot group creation process. NOTE: Use this option if you want to specify all the customizable settings for the snapshot group repository. The Manual method is considered advanced and only those who understand physical disk consistency and optimal physical disk configurations should use this method. -
Page 120: Changing Snapshot Group Settings
attributes. If appropriate candidates are not returned using these settings, you can click Run Auto-Choose to provide automatic candidate recommendations. • The Difference column shows the mathematical difference between your selected capacity and the actual capacity of the repository candidate. If the repository candidate is new, the system uses the exact capacity size that you specified and displays zero (0) in the Difference column. -
Page 121: Deleting Snapshot Group
Type a new name for the snapshot group and then click Rename. Deleting snapshot group Use the Delete Snapshot Group option to delete a snapshot group. The system performs the following actions when a snapshot group is deleted: • Deletes all existing snapshot images from the snapshot group. •... -
Page 122: Creating Consistency Group
• Consistency group member snapshot virtual disk • Asynchronous remote replicated pair Select the Storage & Copy Services tab. Select the storage object for which you want to view the associated physical components and then select Individual Repository Virtual Disk > View Associated Physical Components. Creating consistency group A consistency group is simultaneous snapshots of multiple virtual disks, thus ensuring consistent copies of a group of virtual disks. -
Page 123: Manually Creating A Consistency Group Repository
NOTE: Use this option if you want to specify all the customizable settings for the repositories. The Manual method is considered advanced and only those who understand physical disk consistency and optimal physical disk configurations should use this method. Click Finish. In the navigation tree, the consistency group and its properties are displayed under the Consistency Groups node. -
Page 124: Renaming A Consistency Group
Click Finish. Renaming a consistency group Use the Rename Consistency Group option to change the name of the consistency group when the current name is no longer meaningful or applicable. Keep these guidelines in mind when you name a consistency group: •... -
Page 125: Adding A Member Virtual Disk To A Consistency Group
In addition, you can specify which policy to use when the capacity of the consistency group repository reaches its maximum defined percentage: – Automatically purge oldest consistency image— The system automatically purges the oldest consistency image in the consistency group, which releases the repository’s reserve space for reuse within the consistency group. •... -
Page 126: Removing Member Virtual Disk From Consistency Group
Removing member virtual disk from consistency group Use the Remove Member Virtual Disks option to remove a member virtual disk from an existing consistency group. When you remove a member virtual disk from a consistency group, the system automatically deletes the snapshot group associated with that member virtual disk. -
Page 127: Creating Snapshot Virtual Disk
Creating Snapshot Virtual Disk From the AMW, select the Storage & Copy Services tab. Do one of the following: • Select a base virtual disk, and then select Copy Services > Snapshot Virtual disk > Create. The Select Existing Snapshot Image or New Snapshot Image window is displayed. -
Page 128: Creating A Snapshot Virtual Disk Repository
• Select Automatic and click Finish to create the snapshot virtual disk repository with the default capacity settings. This option is the recommended one. • Select Manual and click Next to define the properties for the snapshot virtual disk repository. Then click Finish to continue with the snapshot virtual disk creation procedure. -
Page 129: Changing The Settings Of A Snapshot Virtual Disk
Changing the settings of a Snapshot Virtual Disk Use the Change Snapshot Virtual Disk Settings option to modify the repository settings that were configured when you created the snapshot virtual disk. You can modify the maximum percentage for the snapshot virtual disk repository to set a warning when the capacity of a snapshot virtual disk repository reaches the defined percentage. -
Page 130: Re-Creating A Snapshot Virtual Disk Or Consistency Group Snapshot Virtual Disk
Re-creating a Snapshot Virtual Disk or consistency group Snapshot Virtual Disk Use the Re-Create option when you want to re-create a snapshot virtual disk or consistency group snapshot virtual disk that you previously disabled. Re-creating a snapshot virtual disk or consistency group snapshot virtual disk takes less time than creating a new one. If you have a snapshot virtual disk or consistency group snapshot virtual disk that you no longer need, you can reuse it (and any associated snapshot repository virtual disk), instead of deleting it, to create a different snapshot virtual disk or consistency group snapshot virtual disk of the same base virtual disk. -
Page 131: Creating Consistency Group Snapshot Virtual Disk
• Copy Services > Snapshot Virtual disk > Rename. The Rename Snapshot Virtual Disk window is displayed. • Copy Services > Consistency Group Snapshot Virtual Disk > Rename. The Rename Consistency Group window is displayed. Type a new name for the snapshot virtual disk or consistency group snapshot virtual disk and then click Rename. Creating consistency group Snapshot Virtual Disk A consistency group snapshot virtual disk comprises multiple snapshot virtual disks to provide host access to a snapshot image that has been taken for each selected member virtual disk at the same moment in time. -
Page 132: Manually Creating A Consistency Group Snapshot Virtual Disk Repository
There is a 30-character limit. After you reach this limit, you can no longer type in the text box. If the consistency group name is 30 characters, then the default name for the group uses the base virtual disk name truncated enough to add the suffix “SV” and the sequence string. -
Page 133: Disabling Snapshot Virtual Disk Or Consistency Group Snapshot Virtual Disk
• When you define the capacity requirements for a repository, keep in mind any future requirements that you may have for other virtual disks in this disk group or disk pool. Make sure that you have enough capacity to meet your data storage needs, but you do not over allocate because you can quickly use up all the storage in your storage array. -
Page 134: Re-Creating A Snapshot Virtual Disk Or Consistency Group Snapshot Virtual Disk
If you disable the snapshot virtual disk or consistency group snapshot virtual disk, the system performs the following actions: • Retains the World-Wide Name (WWN) for the snapshot virtual disk or consistency group snapshot virtual disk. • Retains the snapshot virtual disk or consistency group snapshot virtual disk’s association with the same base virtual disk. •... -
Page 135: Changing The Modification Priority Of An Overall Repository Virtual Disk
• Copy Services > Consistency Group Snapshot Virtual Disk > Re-create. The Confirm Re-Create Consistency Group Snapshot Virtual Disk window is displayed. Select whether to re-create the snapshot virtual disk or consistency group snapshot virtual disk using an existing snapshot image, or a new snapshot image and then click Re-create. -
Page 136: Changing The Pre-Read Consistency Check Setting Of An Overall Repository Virtual Disk
Select either With consistency check or Without consistency check, and click OK. A consistency check scans the blocks in a RAID Level 5 virtual disk, or a RAID Level 6 virtual disk and checks the consistency information for each block. A consistency check compares data blocks on RAID Level 1 replicated physical disks. RAID Level 0 virtual disks have no data consistency. -
Page 137: Increasing Capacity Of Overall Repository
NOTE: Deleting a base virtual disk automatically deletes any associated snapshot virtual disk or consistency group snapshot virtual disk. You cannot delete a snapshot virtual disk that is in a virtual disk copy with a status of In Progress. To rename a snapshot virtual disk or consistency group snapshot virtual disk: From the AMW, select the Storage &... -
Page 138: Decreasing The Capacity Of The Overall Repository
Right click the selected storage object and select Overall Repository > Increase Capacity. The Increase Repository Capacity window is displayed. To increase capacity of the overall repository, do one of the following: • Select Add one or more existing repository virtual disks and then go to step 4. •... -
Page 139: Performing Revive Operation
• You cannot increase or decrease the repository capacity for a snapshot virtual disk that is read-only because it does not have an associated repository. Only snapshot virtual disks that are read-write require a repository. • When you decrease capacity for a snapshot virtual disk or a consistency group member snapshot virtual disk, the system automatically transitions the virtual disk to a Disabled state. -
Page 140: Premium Feature-Virtual Disk Copy
If you ordered this feature, you received a Premium Feature Activation card that shipped in the same box as your Dell PowerVault MD Series storage array. Follow the directions on the card to obtain a key file and to enable the feature. -
Page 141: Types Of Virtual Disk Copies
• Setting copy priority • Stopping a virtual disk copy • Recopying a virtual disk • Removing copy pairs Types of virtual disk copies You can perform either offline or online virtual disk copies. To ensure data integrity, all I/O to the target virtual disk is suspended during either type of virtual disk copy operation. -
Page 142: Virtual Disk Read/Write Permissions
Virtual disk read/write permissions After the virtual disk copy is complete, the target virtual disk automatically becomes read-only to the hosts. The target virtual disk rejects read and write requests while the virtual disk copy operation has a status of Pending or In Progress or if the operation fails before completing the copy. -
Page 143: Setting Read/Write Permissions On Target Virtual Disk
• The Copy Manager, which monitors virtual disk copies after they are created Setting read/write permissions on target virtual disk To set read/write permissions on the target virtual disk: In the AMW, click Storage & Copy Services. Select Copy Services > Virtual Disk Copy > Manage Copies. The Copy Manager window is displayed. -
Page 144: Failed Virtual Disk Copy
Failed virtual disk copy A virtual disk copy can fail due to these conditions: • A read error from the source virtual disk • A write error to the target virtual disk • A failure in the storage array that affects the source virtual disk or the target virtual disk When the virtual disk copy fails, a critical event is logged in the Event Log, and a Needs Attention icon is displayed in the AMW. -
Page 145: Storage Array Performance During Virtual Disk Copy
To copy the virtual disk: Stop all I/O activity to the source virtual disk and the target virtual disk. Unmount any file systems on the source virtual disk and the target virtual disk. In the AMW, select the Storage & Copy Services tab. Under Virtual Disks area, select the source virtual disk that you want to use for the online copy. -
Page 146: Stopping A Virtual Disk Copy
NOTE: There are five copy priority rates available: • lowest • • medium • high • highest If the copy priority is set at the lowest rate, I/O activity is prioritized, and the virtual disk copy takes longer. Stopping a virtual disk copy You can stop a virtual disk copy operation that has an In Progress status, a Pending status, or a Failed status. -
Page 147: Recopying The Virtual Disk
NOTE: If your operating system requires more instructions, you can find those instructions in your operating system documentation. Recopying the virtual disk You can use the Copy Manager to create a new virtual disk copy for a selected source virtual disk and a target virtual disk. Use this option when you have stopped a virtual disk copy and want to start it again or when a virtual disk copy has failed or completed. -
Page 148: Device Mapper Multipath For Linux
Device Mapper multipath for Linux Overview The MD Series storage arrays use a Linux operating system software framework, known as Device Mapper (DM), to enable multipath capabilities on Linux Host Servers. The DM multipath functionality is provided by a combination of physical disks and utilities. This chapter describes how to use those utilities to complete the process of enabling MD Series storage arrays on a Linux system. -
Page 149: Device Mapper Configuration Steps
Using the MD Storage Manager Use the MD Storage Manager to: • Map the host server to the MD Series storage array • Create the virtual disks • Map newly created arrays to your host server NOTE: Any arrays configured with MDCU automatically get added to the list of devices in the EMW. Device Mapper configuration steps To complete the DM multipathing configuration and make storage available to the Linux host server: Scan for virtual disks. -
Page 150: Create Fdisk Partition On Multipath Device Node
The output must be similar to this example, which shows the output for one mapped virtual disk. mpath1 (3600a0b80005ab177000017544a8d6b92) dm-0 DELL, MD3xxxx[size=5.0G][features=3 queue_if_no_path pg_init_retries 50][hwhandler=1 rdac][rw]\_ round-robin 0 [prio=6][active] \_ 5:0:0:0 8:32 [active][ready]\_ round-robin 0 [prio=1][enabled] \_ 4:0:0:0 8:16 [active][ghost] where: mpath1 is the name of the virtual device created by device mapper. -
Page 151: Create File System On Device Mapper Partition
If successful, the command does not display an output. To verify success and view exact partition naming, you can use these commands to see the full partition names assigned. # cd /dev/mapper# ls The following are some examples of the general mapping formats: •... -
Page 152: Important Information About Special Partitions
–F Flushes out all unused multipathing device maps. rescan_dm_devs Dell EMC provided script. Forces a rescan of the host SCSI bus and aggregates multipathing devices as needed. Use this command when: • LUNs are dynamically mapped to the hosts. -
Page 153: Troubleshooting
• If the root disk is not blacklisted in the multipath.conf file, a multipathing node may be created for the root disk. The command multipath –ll lists vendor/product ID, which can help identify this issue. • If upgrading from a previous version of SLES, uninstall and then reinstall the latest scsi_dh_rdac module on the updated SLES installation. -
Page 154: Configuring Asymmetric Logical Unit Access
Configuring Asymmetric Logical Unit Access If your MD Series RAID storage array supports Asymmetric Logical Unit Access (ALUA), active-active throughput allows I/O to pass from a RAID controller module to a virtual disk that is not owned by the RAID controller. Without ALUA, the host multipath driver is required to send data requests targeted to a specific virtual disk to the owning RAID controller module. -
Page 155: Enabling Alua On Vmware Esxi
Enabling ALUA on VMware ESXi VMware ESXi 5.x does not have Storage Array Type Plug-in (SATP) claim rules automatically set to support ALUA on the MD Series storage arrays. To enable ALUA, you must manually add the claim rule. Manually adding SATP rule in ESXi 5.x To manually add the SATP rule in ESXi 5.x: Run the following command: # esxcli storage nmp satp rule add –s VMW_SATP_ALUA –V DELL –M array_PID -c tpgs_on... -
Page 156: Setting Round-Robin Load Balancing Policy On Esxi-Based Storage Arrays
Setting round-robin load balancing policy on ESXi- based storage arrays NOTE: Perform this procedure after you have enabled ALUA on VMware ESXi and verified if the host server is using ALUA for the MD storage array. For more information, see Enabling ALUA On VMware ESX/ESXi Verifying If Host Server Is Using ALUA For MD Storage... -
Page 157: Premium Feature-Remote Replication
Premium feature—Remote Replication The following types of Remote Replication are supported on the MD storage array: • Remote Replication — Standard asynchronous replication using point-in-time images to batch the resynchronization between the local and remote site. This type of replication is supported on both Fibre Channel and iSCSI storage arrays (not between). •... -
Page 158: Types Of Remote Replication
• Statistics for each replicated pair. The replication repository is normally created automatically when you create a replicated pair. However, you can also create the repository manually. Types of Remote Replication The following are the types of Remote Replication premium features supported on your storage array: •... -
Page 159: Remote Replication Requirements And Restrictions
Remote Replication requirements and restrictions To use the standard Remote Replication premium feature, you must have: • Two storage arrays with write access and both these storage arrays must have sufficient space to replicate data between them. • Each storage must have a dual-controller Fibre Channel or iSCSI configuration (single-controller configurations are not supported). •... -
Page 160: Deactivating Remote Replication
If you had selected standard Remote Replication, click Finish. The Premium feature activation is complete. If you had selected Remote Replication (Legacy), in the Create Repositories window, select where the replication repository virtual disks for the Remote Replication (Legacy) feature must reside. Select one of the following: •... -
Page 161: Remote Replication Group Requirements And Guidelines
Because applications may use more than one virtual disk, Remote Replication groups must be replicated as a pair. All members of the Remote Replication group are synchronized as a coordinated data set to provide consistent backup to the remote site. Remote Replication group requirements and guidelines •... -
Page 162: Guidelines For Choosing Virtual Disks In A Replicated Pair
The two virtual disks -- one on the local storage array and one on the remote storage array -- essentially function as a single entity and allow you to manage the pair in tandem, not as two individual virtual disks. Guidelines for choosing virtual disks in a replicated pair The following guidelines apply: •... -
Page 163: Removing Replicated Pair From Remote Replication Group
The Remote Replicated pair is created. The following occurs: • Initial synchronization between the local storage array and the remote storage array automatically begins. • The replicated pair and its properties are displayed under the individual virtual disk node for the secondary virtual disk. •... -
Page 164: Management Firmware Downloads
Management firmware downloads Downloading RAID controller and NVSRAM packages A version number exists for each firmware file. The version number indicates whether the firmware is a major version or a minor version. You can use the Enterprise Management Window (EMW) to download and activate both the major firmware versions and the minor firmware versions. -
Page 165: Downloading Only Nvsram Firmware
To transfer the files to the RAID controller module without activating them, click Transfer files but don't activate them (activate later). Click Transfer. Keep these guidelines in mind: • If the Transfer button is inactive, ensure that you either select an NVSRAM file or clear the Transfer NVSRAM file with RAID controller module firmware check box. - Page 166 To download only NVSRAM firmware: To download the NVSRAM firmware from: • EMW — Go to step 7. • AMW — Go to step 2. In the AMW, select Upgrade > RAID Controller Module NVSRAM select the Support tab, and click Download Firmware. In Select download task, select Download RAID controller module NVSRAM and click OK.
-
Page 167: Downloading Physical Disk Firmware
The download starts and a progress indicator is displayed in the Status column of the Upgrade RAID Controller Module Firmware window. Downloading physical disk firmware CAUTION: When updating physical disk firmware, you should stop all I/O activity to the array to prevent data loss. The physical disk firmware controls various features of the physical disk. -
Page 168: Self-Monitoring Analysis And Reporting Technology (Smart)
NOTE: Due to a limitation with Linux, expansion enclosure EMM firmware updates must be performed using out-of-band management only. Failure to do so may result in the host server becoming unresponsive, and it may require a reboot. You can transfer a downloadable firmware file to the expansion enclosure EMM in the expansion enclosures attached to the storage array. CAUTION: Risk of possible loss of data or risk of damage to the storage array—Downloading the expansion enclosure EMM firmware incorrectly could result in loss of data or damage to the storage array. - Page 169 • An error is encountered on source disks during rebuild. NOTE: Data on an unreadable sector is no longer accessible. Management firmware downloads...
-
Page 170: Firmware Inventory
Firmware inventory A storage array is made up of many components, which may include RAID controller modules, physical disks, and enclosure management modules (EMMs). Each of these components contains firmware. Some versions of the firmware are dependent on other versions of firmware. -
Page 171: System Interfaces
Virtual disks used as source virtual disks for VSS snapshots must not have names longer than 16 characters. • Dell EMC is discontinuing support of the VSS and VDS hardware providers. For more information about deprecation, see the Dell EMC MD Series Storage Arrays Information Update. For supported software, see the Supported Management Software section in the Dell PowerVault MD Series Support Matrix at Dell.com/powervaultmanuals. - Page 172 • The number of snapshot virtual disks that can be created using a single snapshot set varies with the I/O load on the RAID controller modules. Under little or no I/O load, the number of virtual disks in a snapshot set must be limited to eight. Under high I/O loads, the limit must be three.
-
Page 173: Storage Array Software
Device health conditions When you open the Enterprise Management Window (EMW), the Dell EMC PowerVault Modular Disk Storage Manager (MD Storage Manager) establishes communication with each managed storage array and determines the current storage array status. The status is represented by icons next to the managed storage array. - Page 174 Status Icon Description Fixing Status A Needs Attention status has been corrected, and the managed storage array is transitioning to an Optimal state. Unsupported The node is not supported by this version of MD Storage Manager. Software Unsupported The storage array is running a level of software that is no longer supported by the MD Storage Manager.
-
Page 175: Trace Buffers
Status Icon Description Adding a Storage Array The Contacting Storage Array icon is shown in the Tree view and Table view until the status of each managed storage array is known. The Contacting Storage Array icon is shown in the EMW Status Bar and the AMW Status Bar, and the tooltip shows Contacting Storage arrays. -
Page 176: Retrieving Trace Buffers
Retrieving trace buffers To retrieve the trace buffers: From the AMW, select Monitor > Health > Retrieve Trace Buffers. The Retrieve Trace Buffers dialog is displayed. Select either RAID controller module 0, RAID controller module 1, or both. If the RAID controller module status message to the right of a check box indicates that the RAID controller module is offline, the check box is disabled. -
Page 177: Suspending Or Resuming A Support Data Collection Schedule
The Schedule Support Data Collection dialog is displayed. In the Storage arrays table, select one or more storage arrays for which you want to create a schedule. Click the Create/Edit button. The Create/Edit Schedule dialog is displayed. Select your desired settings and click OK. The Schedule Support Data Collection dialog is displayed. -
Page 178: Viewing The Event Log
• Warning events — Errors occurring on the storage array resulting in degraded performance or reduced ability to recover from additional errors. Access to data has not been lost, but the must be corrected to prevent possible loss of data access in the event of an additional error. -
Page 179: Viewing The Physical Associations
• Select Monitor > Reports > Storage Array Profile. • Select the Summary tab, and click View Storage Array Profile in the Monitor area. The Storage Array Profile dialog is displayed. The Storage Array Profile dialog contains several tabs, and the title of each tab corresponds to the subject of the information contained. - Page 180 responsive again. Before completing this procedure, make sure that you wait for some time before you decide that the storage array is still unresponsive. To recover from an unresponsive storage array: Check the Tree View in the EMW to see if all storage arrays are unresponsive. If any storage arrays are unresponsive, check the storage management station network connection to make sure that it can reach the network.
-
Page 181: Locating A Physical Disk
connection attempts. The type of management operations being performed and the number of management sessions taking place together determine the number of TCP/IP connections made to a RAID controller module. This problem is self-correcting because, after some TCP/IP connections terminate, the RAID controller module then becomes responsive to other connection attempts. 23 If the storage array is still unresponsive, a problem may exist with the RAID controller modules. -
Page 182: Capturing State Information
Capturing state information Use the Capture State Information option to capture information about the current state of your storage array and save the captured information to a text file. You can then send the captured information to your Technical Support representative for analysis. CAUTION: Potential to cause an unresponsive storage array –... -
Page 183: Recovering From Unidentified Storage Array
• If a storage array is managed by using both out-of-band management and in-band management using the same host, a management network connection problem may prevent direct communication with the storage array. However, you may still be able to manage the storage array over the in-band connections. -
Page 184: Starting Or Restarting The Host Context Agent Software
Starting or restarting the Host Context Agent software The Host Context Agent software module is the software component that resides on the server or management station that communicates with the MD Series storage arrays. The SMagent software automatically starts after you reboot the host. Starting the SMagent software in Windows Do one of the following: •... -
Page 185: Getting Help
Getting help Contacting Dell EMC NOTE: If you do not have an active Internet connection, you can find contact information on your purchase invoice, packing slip, bill, or Dell product catalog. Dell provides several online and telephone-based support and service options. Availability varies by country and product, and some services may not be available in your area.
Need help?
Do you have a question about the PowerVault MD Series and is the answer not in the manual?
Questions and answers