Contents

Dell Symmetrix VMAX 20K V4.0 Storage PRODUCT GUIDE PDF

1 of 23
1 of 23

Summary of Content for Dell Symmetrix VMAX 20K V4.0 Storage PRODUCT GUIDE PDF

PRODUCT GUIDE

This guide presents the following topics:

Product description................................................................................................... 2 System prerequisites ................................................................................................ 4 Installation ............................................................................................................... 4 Upgrading ESI for Oracle VM...................................................................................... 7 Using ESI for Oracle VM............................................................................................. 9 Getting help............................................................................................................ 23

Note: This document was accurate at publication time. Go to EMC Online Support (https://support.emc.com) to ensure that you are using the latest version of this document.

EMC Storage Integrator 4.0 for Oracle VM

Product Guide P/N 300-015-428 REV 04

September 2015

Interoperability differences between OSC and EMC Unisphere

Product description EMC Storage Integrator (ESI) 4.0 for Oracle VM version 3.3.3 is a plug-in that enables Oracle VM (OVM) to discover and provision EMC storage arrays. The ESI plug-in is built upon the Oracle Storage Connect (OSC) framework. The framework provides a set of storage discovery and provisioning application programming interfaces (APIs) that enhance the ability to manage and provision storage devices in an OVM environment.

Note: For more information about the OSC framework and APIs, visit the Oracle website.

ESI for Oracle VM supports the following storage management and provisioning operations for EMC storage arrays:

LUN discovery and inquiry

Thin LUN/MetaLUN creation and removal

Auto-provisioning (LUN masking)

Register and refresh arrays

Clone device creation and removal

Snap device creation and removal

ESI for Oracle VM uses EMC SMI-S Provider or the Representational State Transfer (REST) interface to do the actual storage management work. SMI-S Provider supports the Storage Networking Industry Association (SNIA) Storage Management Initiative (SMI), an American National Standards Institute (ANSI) standard for storage management.

For storage provisioning and management operations, the ESI plug-in uses the SMI-S Provider interface for EMC VNX, EMC VMAX, and EMC VMAX3 storage arrays. The plug-in uses the REST interface for EMC XtremIO storage arrays.

Note: The MetaLUN feature is not supported for VNX,VNX3, and XtremIO arrays.

Interoperability differences between OSC and EMC Unisphere EMC Unisphere and EMC Solutions Enabler (SE) are the traditional storage provisioning and management interfaces for EMC storage arrays. Unisphere is a fully-functional storage provisioning tool for VMAX, VMAX3, and VNX arrays, and OSC simplifies storage array management for other array vendors. OSC uses a simplified management object model, but it does not exactly fit into a VMAX, VMAX3, or VNX object model. Some interoperability issues occur for mixed use of the EMC plug-in and Unisphere. In general, storage objects created by OSC should be consistently managed only by OSC. Similarly, storage objects (such as masking view, storage group, and so on) that are created by Unisphere should be managed only by Unisphere. Some interoperability issues occur when users attempt to manage the same storage objects with both the EMC OSC plug-in and Unisphere.

Unisphere provides all aspects of VMAX, VMAX3, and VNX management, including directors, disks, devices, pools, auto-provisioning, and so on. OSC provides a subset of functionality. The EMC XtremIO storage management application also provides

2 EMC Storage Integrator 4.0 for Oracle VM Product Guide

Interoperability differences between OSC and EMC Unisphere

easy-to-use tools for performing most of the cluster operations. OSC uses the XtremIO RESTful API, which has an HTTP-based interface for storage provisioning operations. Table 1 shows the differences between OSC, Unisphere, and XtremIO terminology.

LUN masking

LUN masking in OSC differs significantly from Unisphere, and interoperability cannot be implemented between them.

The basic guideline for LUN masking is that OSC and Unisphere should never interfere with each other. Do not use Unisphere to modify OSC-managed masking groups and views, and do not use OSC to modify masking groups and views managed by Unisphere. Violating these guidelines may cause unexpected errors.

To distinguish OSC-managed masking groups and views from masking groups and views managed by Unisphere, a default osc_ prefix (or any user-defined prefix) is added to the name of OSC-managed objects. Never modify OSC-managed objects with Unisphere. OSC blocks the association of any OSC-managed initiator groups, storage groups, and port groups to masking views managed by Unisphere. Any modifications performed outside of OSC may cause unexpected failures.

To specify an access group prefix other than the default osc prefix, type the following command in the configuration file:

AccessGroupPrefix = User_Defined_Prefix /opt/storage-connect/plugins/emc/isa/isa.conf

For example, to define the mycomp prefix, type the following line in the configuration file:

AccessGroupPrefix = mycomp

Notes:

To avoid operation failures, configure the prefix before you configure the OSC usage, and do not change the configuration after you create the access group.

Table 1 OSC Unisphere, and XtremIO terminology matrix

OSC terms Unisphere terms XtremIO terms

Storage server or storage array

VMAX, VMAX3, or VNX array XtremIO array

Storage element VMAX, VMAX3, or VNX device XtremIO volume

Volume group Thin pool (for thin device creation only)

Storage resource pool (for VMAX3 arrays)

XtremIO cluster shown as a volume group with the volume group named with the cluster name

Access group Initiator group (with default prefix osc_ or a user-defined prefix) for VMAX and VMAX3 arrays

Storage group (with default prefix osc_ or a user-defined prefix) for VNX arrays

Initiator group (with default prefix osc or a user-defined prefix)

Present or unpresent LUN masking, to make a LUN visible or invisible to a host

LUN mapping allows the ports of the host to access the volume

EMC Storage Integrator 4.0 for Oracle VM Product Guide 3

Installing ESI for Oracle VM

If the OVM manager manages multiple servers, the isa.conf file must be consistent across all the servers. Configure the same value for AccessGroupPrefix in all of the managed servers.

Editing the ESI for Oracle VM configuration file provides more details about how to edit the configuration file.

Known problems and interoperability for OSC with Unisphere and Solutions Enabler in the EMC Storage Integrator 4.0 for Oracle VM Release Notes provides more details about OSC and Unisphere interoperability.

The EMC XtremIO Management Application is used to perform storage management and provisioning operations on XtremIO arrays. The other restrictions in these notes also apply to XtremIO arrays.

System prerequisites Table 2 lists all the configurations supported for version 4.0 of ESI for Oracle VM version 3.3.3.

Installation This section describes how to install, uninstall, and deploy ESI for Oracle VM, and also includes details on how to edit the configuration file to define runtime behavior for the plug-in.

Installing ESI for Oracle VM Before you run the installation program, confirm that the system configuration is listed in the System prerequisites and verify that you have root access to the Oracle VM server.

To install ESI for Oracle VM:

1. Download the installation package file from EMC Online Support (https://support.emc.com).

2. Log on as the root user to the Oracle VM server.

Table 2 Environment and system requirements

Type Name Supported version

Oracle environment Oracle VM Manager and Oracle VM Server

3.3.3

Array management server EMC SMI-S Provider 4.6.2.9 (VMAX and VNX) 8.0.1, 8.0.2 (VMAX3)

Disk array (VMAX, VMAX3, VNX, or XtremIO)

VMAX arrays EMC EnginuityTM 5874

VMAX3 arrays EMC Enginuity 5977

VNX arrays Fibre Logic Array Runtime Environment (FLARE)/OE 5.32 and 5.33

XtremIO arrays Version 3.0.2 build 14 or later and version 4.0

4 EMC Storage Integrator 4.0 for Oracle VM Product Guide

Uninstalling ESI for Oracle VM

3. Type the following command to install the package, as shown in Figure 1:

# rpm -ivh ./emc-osc-isa- 4.0.0.x-1.el6.x86_64.rpm

Figure 1 Install ESI

Uninstalling ESI for Oracle VM To uninstall ESI for Oracle VM, type the following command to remove the package, as shown in Figure 2:

# rpm -e ./emc-osc-isa-4.0.0.x-1.e16.x86_64

Figure 2 Uninstall ESI

Deploying ESI for Oracle VM ESI for Oracle VM is deployed to an Oracle VM environment and is installed on an Oracle VM Server. It requires the EMC SMI-S Provider server to provision and manage VMAX arrays. The provider server runs on a standalone Windows or Linux management host. EMC SMI-S Provider Release Notes on EMC Online Support provide installation and configuration instructions.

The SMI-S Provider server is based on Solutions Enabler, so it requires the same setup and connectivity to the VMAX array, such as zoning and configuring gatekeeper devices. The OVM server (where the ESI plug-in is installed and runs) requires TCP/IP network connections to the SMI-S Provider server and connectivity to the storage array. The SMI-S Provider server cannot be installed on OVM servers because OVM servers have a restricted environment.

For the XtremIO array, the REST server that runs on the XMS array enables you to control and manage the array by providing GUI and RESTful API services to clients with all communications, by using standard TCP/IP connections.

EMC Storage Integrator 4.0 for Oracle VM Product Guide 5

Editing the ESI for Oracle VM configuration file

Editing the ESI for Oracle VM configuration file ESI for Oracle VM uses isa.conf to define its runtime behavior. To change the default behaviors, manually create a plain text file named isa.conf under /opt/storage-connect/plugins/emc/isa/ on the Oracle VM server after installation.

Permissions of the isa.conf file must be readable by the root user. Any line starting with # will be ignored by ESI for Oracle VM. Table 3 describes the ESI plug-in runtime settings.

Table 3 isa.conf properties

Properties Values Descriptions

AccessGroupPrefix A string composed of alphanumerical characters, _ or -

Note: For example: osc1_

User defined prefix for OSC-managed initiator group, port group, device group, and masking view on VMAX, VMAX3, VNX, and XtremIO arrays. This prefix makes it easier to differentiate between OSC-managed groups and other managed groups.

AutoMetaEnabled True or False A flag to indicate whether a VMAX auto meta is enabled or disabled.

Note: VNX, VMAX3, and XtremIO arrays do not support meta devices. Devices up to 16 TB in size can be created on these arrays. These arrays handle the creation of maximum size LUNs.

LogLevel debug Set the verbose logging flag for troubleshooting.

VolumeGroupPrefix A prefix or the exact pool name. Multiple comma-separated values can be specified.

Note: For example: esi, osc_pool1

Note: To apply these configuration changes on the configured arrays, remove and re-register the arrays.

Filters and lists only the desired volume groups in the storage array.

Note: This configuration is only applicable for VMAX and VNX arrays and will not affect VMAX3 and XtremIO arrays.

6 EMC Storage Integrator 4.0 for Oracle VM Product Guide

Editing the ESI for Oracle VM configuration file

Upgrading ESI for Oracle VM To upgrade the ESI plug-in from version 3.0 to 4.0:

1. Uninstall the version 3.0 plug-in.

2. Install the version 4.0 plug-in.

Note: To upgrade ESI for Oracle VM from version 3.2.8 or 3.3.1 to version 3.3.3 of the Oracle VM server, refer to the Oracle migration guide. Contact Oracle support if you encounter any issues during the upgrade.

To upgrade the storage servers from version 3.0 to version 4.0:

Note: When you perform the upgrade, also back up the configuration file so that it can be restored after you complete the upgrade.

1. Navigate to Storage > SAN servers > Edit.

2. Select the EMC storage plug-in from the drop-down list.

3. Click OK.

After you successfully upgrade ESI for Oracle VM, you must rediscover the OVM server from the Servers and VMs tab for all the OVM servers where ESI for Oracle VM is installed.

To rediscover the OVM server:

Note: Stop the ovs-agent service on the OVM server while uninstalling and installing the OSC plug-in RPMs.

1. In Servers and VMs, click Rediscover Server, as shown in Figure 3.

Figure 3 Rediscover the OVM server

EMC Storage Integrator 4.0 for Oracle VM Product Guide 7

Editing the ESI for Oracle VM configuration file

2. In Configuration, select the plug-in that you are upgrading, and then click OK, as shown in Figure 4.

Figure 4 Select the plug-in to be upgraded

In Storage, the green + confirms that the plug-in was successfully upgraded, as shown in Figure 5.

Note: You will see a red + if the upgrade was unsuccessful. Repeat the steps until you are successful.

Figure 5 Upgrade confirmation

8 EMC Storage Integrator 4.0 for Oracle VM Product Guide

Registering a storage array

Using ESI for Oracle VM This section describes how to use ESI for Oracle VM, including the following topics:

Register a storage array

LUN discovery and inquiry

Create and remove thin LUNs

Auto-provisioning (LUN masking)

Create access groups

Edit access groups

Add or remove initiators from an access group

Start or stop presenting physical disks

Create snapshots

Create clones

Registering a storage array

You must install ESI for Oracle VM on an OVM server and then discover the plug-in through OVM Manager before a storage array can be registered.

To register and refresh a SAN storage array:

1. Click Storage > SAN Servers > Discover SAN Server, as shown in Figure 6.

Figure 6 Rediscover the server

2. In the Access Information (if required) dialog box, enter the following details, as shown in Figure 8, and then click Next:

NameUser defined name for an EMC storage array.

Storage Plug-inSelect EMC FC SCSI Plugin.

EMC Storage Integrator 4.0 for Oracle VM Product Guide 9

Registering a storage array

Plug-in Private DataStorage array ID, or use the last several digitals of the storage array ID, if they uniquely identify the storage array. For example:

Both SYMMETRIX+000195900311 or 311 are valid, but SYMMETRIX+00019 is invalid. This field is required in case there are multiple storage arrays managed by EMC SMI-S Provider.

XtremIO is valid for an XtremIO Version 3.0.

XtremIO_ is valid for XtremIO Version 4.0. The cluster name is required only for XtremIO Version 4.0.

Admin HostHost name or IP address of the host where SMI-S Provider is installed. For the XtremIO array, specify the IP address used to connect to the XMS server.

Notes:

XtremIO version 4.0 supports multiple clusters managed by a single XMS. Oracle VM does not support registering multiple storage arrays that are simultaneously managed by a single XMS, which allows Oracle VM to manage and use one XtremIO cluster for a specified XMS.

To find the cluster name, click Find Cluster in the XtremIO Storage Management Application, as shown in Figure 7.

Figure 7 Find the cluster name

Admin UsernameUsername to connect to the SMI-S Provider/XMS Server. The default value is admin.

Admin PasswordPassword to connect to the SMI-S Provider. The default value is #1Password. For the XtremIO array, specify the password used for the admin user. The default value is Xtrem10

Admin PasswordPassword to connect to the SMI-S Provider. The default value is #1Password. For the XtremIO array, specify the password used for the admin user. The default value is Xtrem10.

10 EMC Storage Integrator 4.0 for Oracle VM Product Guide

Registering a storage array

Figure 8 SAN Server registration for VMAX, VMAX3, and VNX arrays

3. In the Add Admin Servers dialog box, select the OVM server to be used for the storage operations from the Available Servers(s) list.

4. Click the arrow to move the OVM server to the Selected Servers(s) list, and then click Finish, as shown in Figure 9.

Figure 9 Select the OVM server

EMC Storage Integrator 4.0 for Oracle VM Product Guide 11

LUN discovery and inquiry

5. Click Storage > SAN Servers > the selected server > Refresh to refresh the storage array that you added, as shown in Figure 10.

Figure 10 Refresh the server

LUN discovery and inquiry After registering a storage array, refresh the storage array to list available storage access groups, volume groups, and devices.

Inquiry capabilities of a storage device include size, device World Wide Name (WWN), status, LUN ID, associated volume group, and access group, if any.

Only thin Fixed Block Architecture (FBA) devices are discoverable. Business Continuance Volumes (BCVs), clones, and R1 local devices are discoverable if they are also thin FBA devices. Count key data devices (CKDs), data devices (DATADEVs), save devices (SAVEDEVs), R2 target devices, and gate keeper (GK) devices are not discoverable.

The format of extra information associated with a storage device is as follows:

[UNMANAGED BCV/R1] LUN_ID [(A MIRROR/CLONE OF LUN_ID: COPY_STATE)]

Note: Items in square brackets ([ ]) indicate terms that are specific to special configurations and are not applied to every LUN.

where the following values are used:

UnmanagedLUN is not managed by OSC access group

BCVLUN is a BCV device

R1LUN is an R1 device

LUN_IDVMAX, VMAX3, VNX, or XtremIO device number

A mirror/clone (or snapshot) of LUN_ID: COPY_STATELUN is a replica target device (mirror or clone) with the copy state information

12 EMC Storage Integrator 4.0 for Oracle VM Product Guide

Creating and removing thin LUNs

Note: XtremIO volumes with a Network Address Authority (NAA) name and page83 ID are listed by Oracle VM. The ESI plug-in ensures that the page83 ID is set for all volumes, clones, and snapshots created by Oracle VM.

Creating and removing thin LUNs Only thin devices can be created.

If the size specified is larger than the threshold of a standard device, a VMAX meta device is created as follows:

If auto meta is disabled on the VMAX array, the ESI plug-in creates the required meta members first, then forms a concatenated meta device using the newly-created member devices. Striped meta devices cannot be created in this way.

If auto meta is enabled on the VMAX array, add the following line in the configuration file /OPT/STORAGE-CONNECT/PLUGINS/EMC/ISA/ISA.CONF on the Oracle VM server:

AutoMetaEnabled = true

Notes:

VNX, VMAX3, and XtremIO arrays do not support meta devices and the AutoMetaEnabled configuration parameter is not applicable for these arrays. You can create maximum-sized LUNs in these arrays.

Editing the ESI for Oracle VM configuration file, provides more details about how to edit the configuration file.

The ESI plug-in depends on the VMAX auto meta feature to complete the device creation request. The physical disk size created by the auto meta feature may be greater than expected because the size must be a multiple of the VMAX Auto Meta Member Size attribute.

For VMAX arrays, you can also specify the meta member size using the Extra Information field of the Create Physical Disk dialog box. Use meta_member_size= to define the meta member size.

If the AutoMetaEnabled parameter is not set in the configuration file, the plug-in attempts to query whether the auto meta feature is enabled on the storage array when SMI-S Provider 4.6.2.9 or greater is used. If this query is unsuccessful, AutoMetaEnabled uses the default value of FALSE.

For VMAX arrays, if meta_member_size is specified while the VMAX auto meta is disabled, the ESI plug-in will always try to create a concatenated meta device according to the specified member size.

Volume group (storage pool) management occurs outside of OSC. Volume groups must be pre-configured before OSC usage.

Although BCVs and R1 devices are discoverable, they cannot be created through OVM. To remove these devices, follow the general Solutions Enabler guidelines for VMAX arrays. EMC Solutions Enabler Symmetrix Array Control CLI Product Guide, on EMC Online Support, provides more information.

EMC Storage Integrator 4.0 for Oracle VM Product Guide 13

Auto-provisioning (LUN masking)

Auto-provisioning (LUN masking) To make a device accessible from Oracle VM server, you need to present it to an access group. The equivalent of an access group is an initiator group (in VMAX, VMAX3, and XtremIO) and a storage group (in VNX), which includes a list of host initiator WWNs.

After being presented, VMAX device information is updated in OVM. Access groups of a storage device are changed to the access group name. The device path becomes available on the Oracle VM server and the device is ready to use for OVM.

Ensure that you correctly configure zoning on the Fibre Channel switch before LUN masking. All host initiators must have Fibre Channel logins on the storage array to successfully add them to an access group. Adding an initiator to an access group in Oracle VM Manager requires a connection to the storage array with the Oracle VM server.

Creating access groups

To create and edit access groups:

1. Click Storage > SAN Servers, and then select the SAN storage array for the access group that you are creating.

2. Select a Perspective of Access Groups, and then click +, as shown in Figure 11.

Figure 11 Storage tab

3. In the Create an Access Group dialog box, type an Access Group Name and a Description, and then click Next, as shown in Figure 12.

14 EMC Storage Integrator 4.0 for Oracle VM Product Guide

Creating access groups

Note: Do not include spaces in the Access Group Name. For example, use Access_Group_1 or AccessGroup1 instead of Access Group 1.

Figure 12 Create an access group

4. In the Select Initiators dialog box, select an initiator from the Available Storage Initiators list.

5. Click the arrow to move the initiator into the Selected Storage Initiators list, and then click Next, as shown in Figure 13.

Figure 13 Select an initiator

6. From the Present Physical Disks dialog box, select one or more physical disks from the Available Physical Disks list.

EMC Storage Integrator 4.0 for Oracle VM Product Guide 15

Adding or removing initiators in an access group

7. Click the arrow to move the disk into the Selected Physical Disks list, and then click Finish, as shown in Figure 14.

Figure 14 Present physical disks

Adding or removing initiators in an access group

To add an initiator to an access group:

1. Click Storage Initiators and select an initiator from the Available Storage Initiators list.

2. Click the arrow to move the initiator into the Selected Storage Initiators list, and then click Next, as shown in Figure 15.

To remove an initiator from an access group:

1. Click Storage Initiators and select an initiator from the Selected Storage Initiators list.

2. Click the arrow to move the initiator into the Available Storage Initiators list, and then click Next, as shown in Figure 15.

Figure 15 Add an initiator to an access group

16 EMC Storage Integrator 4.0 for Oracle VM Product Guide

Start or stop presenting physical disks

Start or stop presenting physical disks

To start a physical disk:

1. Select Physical Disks and select a physical disk from the Available Physical Disks list.

2. Click the arrow to move the initiator into the Selected Physical Disks list, and then click OK, as shown in Figure 16.

To stop a physical disk:

1. Select Physical Disks and select a physical disk from the Selected Physical Disks list.

2. Click the arrow to move the physical disk into the Available Physical Disks list, and then click OK, as shown in Figure 16.

Figure 16 Start or stop presenting a physical disk

Creating clone devices To create a clone device:

1. Click Storage and select Perspective: Physical Disks.

EMC Storage Integrator 4.0 for Oracle VM Product Guide 17

Creating clone devices

2. Select a Volume Group, right-click the storage element, and then slect Clone, as shown in Figure 17.

Figure 17 Selecting a clone

3. Type the clone name.

4. Select Storage Array as the clone target type.

5. Select the EMC Storage Array as the clone target.

6. Select Thin Clone as the clone type, and then click OK, as shown in Figure 18.

Figure 18 Specifying the clone details

After the clone is created, the clone becomes immediately accessible to its host, even while data copying is occurring in the background.

A source device can have multiple clones (different point-in-time copies) at the same time. However, the name for all clone devices is the same as the source device with a _clone suffix. OVM does not provide a way to type a user-friendly name while creating a clone.

18 EMC Storage Integrator 4.0 for Oracle VM Product Guide

Creating snapshots

Note: Clones from snapshots are not supported, regardless of whether they are synchronous or asynchronous.

OSC clone functionality is limited to creation and removal. The advanced EMC TimeFinder clone features such as Recreate and Restore are not available in OSC. Always create a clone for a new point-in-time copy.

Note: Because XtremIO supports only snapshots, the clones shown for XtremIO arrays are actually snapshots. OSC API getCloneLimits() and getSnapLimits() commands are not supported for XtremIO arrays.

Creating snapshots

Snapshots that you create are listed under the volume group where the source storage element resides. Snapshots created with ESI can also be deleted, but cannot be restored. Snapshots cannot exist independently without a source. For that reason, source storage elements cannot be removed unless all associated snapshots are also removed.

For VMAX arrays with Enginuity version 5876 or above, the plug-in creates an EMC VP Snap. For earlier versions of Enginuity, the plug-in creates a TimeFinder Snap. Snapshot creation is extended from existing clone support by naming the replica with an _EMC_SNAP suffix. The ESI plug-in lists only OSC-managed snapshots and snapshots managed by Unisphere are filtered out.

VMAX3 arrays with Enginuity version 5977 use the new SnapVX snapshot technology, which is the only type of snapshot supported by the ESI plug-in.

To create a snapshot:

1. Click Storage and select a Perspective of Physical Disks.

2. Select a Volume Group, right-click the storage element, and then select Clone, as shown in Figure 19.

Figure 19 Selecting a clone

EMC Storage Integrator 4.0 for Oracle VM Product Guide 19

Creating snapshots

3. Type the snapshot Name, which must end with _EMC_SNAP.

4. Select Storage Array as the Clone Target Type.

5. Select the EMC storage array as the Clone Target.

6. Select Thin Clone as the Clone Type.

7. Click OK, as shown in Figure 20.

Figure 20 Specifying the clone physical disk details

8. Click the snapshot created under the selected volume group to view details for the following arrays:

a. VMAX and VNX arrays, as shown in Figure 21.

Figure 21 View snapshot details for VMAX and VNX arrays

20 EMC Storage Integrator 4.0 for Oracle VM Product Guide

Creating snapshots

b. VMAX3 arrays, as shown in Figure 22.

Figure 22 View snaphot details for VMAX3 arrays

c. XtremIO arrays, as shown in Figure 23.

Figure 23 View snapshot details for XtremIO arrays

Snapshot troubleshooting

The following problems can occur when you create snapshots:

For VMAX arrays with Enginuity version 5876 or greater, snapshots will fail if the storage volume contains TimeFinder snap devices.

For snapshot operations, the job description and job summary are displayed as storage_clone instead of storage_snap. This can be ignored.

When auto meta is not enabled on the VMAX array, snapshots of a MetaLUN are not supported.

Creating a snapshot of a MetaLUN fails for a VMAX array if AutoMetaEnabled is set to FALSE in the plug-in configuration file. If this occurs, an error message, such as the following example, is displayed:

Job Failed - Create Replica. error 1 : C:ERROR_CLASS_SOFTWARE F:ERROR_FAMILY_NOT_SUPPORTED R:1000002 Not Supported: Creating composite volume targets with different size members.

EMC Storage Integrator 4.0 for Oracle VM Product Guide 21

Creating snapshots

Cloning of a MetaLUN operation can fail if the AutoMetaEnabled parameter is changed in the plug-in configuration file or in the storage array after creation of the source MetaLUN. If this occurs, an error message, such as the following example, is displayed:

A configuration mismatch was detected among members of your META device(s)

22 EMC Storage Integrator 4.0 for Oracle VM Product Guide

Creating snapshots

Getting help EMC support, product, and licensing information can be obtained as follows:

Product informationFor documentation, release notes, software updates, or information about EMC products, go to EMC Online Support at:

https://support.emc.com

Technical supportGo to EMC Online Support and click Service Center. You will see several options for contacting EMC Technical Support. Note that to open a service request, you must have a valid support agreement. Contact your EMC sales representative for details about obtaining a valid support agreement or with questions about your account.

Copyright 2014-15 EMC Corporation. All rights reserved. Published in the USA.

Published September 2015

EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.

The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

EMC2, EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and other countries. All other trademarks used herein are the property of their respective owners.

For the most up-to-date regulatory document for your product line, go to EMC Online Support (https://support.emc.com).

<

Manualsnet FAQs

If you want to find out how the V4.0 Dell works, you can view and download the Dell Symmetrix VMAX 20K V4.0 Storage PRODUCT GUIDE on the Manualsnet website.

Yes, we have the Product Guide for Dell V4.0 as well as other Dell manuals. All you need to do is to use our search bar and find the user manual that you are looking for.

The Product Guide should include all the details that are needed to use a Dell V4.0. Full manuals and user guide PDFs can be downloaded from Manualsnet.com.

The best way to navigate the Dell Symmetrix VMAX 20K V4.0 Storage PRODUCT GUIDE is by checking the Table of Contents at the top of the page where available. This allows you to navigate a manual by jumping to the section you are looking for.

This Dell Symmetrix VMAX 20K V4.0 Storage PRODUCT GUIDE consists of sections like Table of Contents, to name a few. For easier navigation, use the Table of Contents in the upper left corner.

You can download Dell Symmetrix VMAX 20K V4.0 Storage PRODUCT GUIDE free of charge simply by clicking the “download” button in the upper right corner of any manuals page. This feature allows you to download any manual in a couple of seconds and is generally in PDF format. You can also save a manual for later by adding it to your saved documents in the user profile.

To be able to print Dell Symmetrix VMAX 20K V4.0 Storage PRODUCT GUIDE, simply download the document to your computer. Once downloaded, open the PDF file and print the Dell Symmetrix VMAX 20K V4.0 Storage PRODUCT GUIDE as you would any other document. This can usually be achieved by clicking on “File” and then “Print” from the menu bar.