You are on page 1of 2

4/25/2014

Help - fluid Operations

eCloudManager 4.1 Reference Guide > 4 Datacenter Preparation/Configuration > 4.4 Storage Setup
Previous Next

4.4.2 EMC Symmetrix


The EMC Symmetrix is the flagship storage array distributed by EMC. It offers a number of features beyond the traditional thin provisioning features, such as remote backups. When preparing an EMC Symmetrix array for use by the eCM, the recommendations from EMC should be followed. The eCM needs certain aspects of a Symmetrix array to be set, like access control and the formation of RAID groups. The EMC Symmetrix has the concept of regular devices, thin devices and meta-devices. Regular devices are LUNs which get allocated the entire space they will require on the disks; thin devices do not do this but rather only allocate the space that is currently needed. Meta-devices are concatenations of devices which allow users to circumvent the device size limits, set forth by the EMC Symmetrix.

SID This is the Symmetrix identifier. This is what the eCM provider uses to identify the Symmetrix through the Solution Enabler. To uniquely identify the Symmetrix, a 4-digit number is required but it can also be a 2-digit number if there is no overlap. When using a Solution Enabler with multiple Symmetrixs attached, only one provider is required but multiple SIDs can be specified in order to identify all arrays. To see more detailed information go to section 7.3.3 Storage Cloning Cloning operations can be performed on thin, regular and meta-devices. The cloning operation creates full copies which are available immediately after the start of the cloning operation. For each source device, 16 active clone sessions are allowed. Once this limit is reached, active clone sessions have to be severed in order to reduce the count of active clone sessions. Clones will always result in thick devices, i.e. the entire space allotted to the devices will be reserved. Furthermore, clones in active sessions cannot be used as sources for snap or clone operations until the active session has been terminated. Snapping Snapshots are space-saving copies of devices, i.e. the target of a snap is always a thin device or a thin metadevice. Snapshots are available immediately after the snapping process has started. For each source device, 128 active snapshot sessions are allowed. Once this quota has been filled, further snapshots can only be made if at least one active snap session is terminated. Snaps cannot be made of snap targets, nor can they be made of clone targets. These restrictions are posed by the EMC Symmetrix and can therefore not be circumvented. Composite Groups A composite group is a set of devices on which operations can be performed, either on the set as a whole or on individual devices. A composite group is similar to a device group, except that it can span multiple local Symmetrix arrays, i.e. devices of multiple arrays within the same data center can be part of the same composite group. Composite groups allow users to create consistent, restart (ability to restart) copies of their volumes spanning multiple Symmetrix arrays. Starting with Solutions Enabler 6.3, devices can be part of multiple composite groups. Composite groups are identical to device groups, with the difference that device groups cannot span multiple local Symmetrix arrays. For this reason, the eCM only supports composite groups, since they provide more flexibility. The creation of these groups is usually performed transparently.
http://help.fluidops.com/help/index.jsp?topic=%2Fecm.help-4.1%2FDocuments%2F442emcsymmetrix.htm 1/2

4/25/2014

Help - fluid Operations

Specifying the following in the symapi/configfile on the Solution Enabler enables the ability for devices to be part of more than one group (device and / or composite groups): SYMAPI_ALLOW_DEV_IN_MULT_GRPS = ENABLE | DISABLE The file can be found in: /var/symapi/config (on Linux systems) C:\Program files\EMC\Symapi\config (on Windows systems)

Preparation for Symmetrix Usage To allow the eCloudManager to interact with the EMC Symmetrix, the following setup is highly recommended: Separate SolutionEnabler 7.x with SYMCLI / API 7.x for each EMC Symmetrix array o Each SolutionEnabler should run on a separate Virtual Machine and should have at least 8 Gatekeeper Devices. However, it is highly recommended to use 12 Gatekeeper Devices. Install eCloudManager remoteCLI Agent on each VM on which the SolutionEnabler is installed (see section 475.3 Remote CLI Agent for the EMC Symmetrix) In addition, the following environment variables have to be set for the user under which the remoteCliAgent is running: o SYMCLI_MULTI_VIRTUAL_SNAP=ENABLED o SYMCLI_CLONE_LARGER_TGT=ENABLED o SYMCLI_LDEV_NAMING = SYMDEV o SYMCLI_CTL_ACCESS = PARALLEL Ensure that the AUTO_META feature is disabled

Once these steps have been completed successfully, the eCloudManager will be ready to interact with the EMC Symmetrix Storage Array. As a general guideline, the following settings are encouraged to maximize the performance of the Storage Array and the eCloudManager. A separate Initiator group for each ESX cluster is highly recommended A separate Masking View for each Initiator Group is highly recommended A set of DATA DEVs with 250 GB (larger = better) to build up a Thin Pool A set of SAVE DEVs with 250 GB (larger = better) to build up a Snap Pool Templates setup in TDEVs are recommended (space efficient) All disks in RDMs (including swap and OS) o Mix TDEV and Thick DEVs if required For monitoring the EMC Symmetrix Storage Array, it is possible to set the number of devices that are updated simultaneously, using the SymDevPollNumber (see 7.2.4 Storage). A good value to start is 10 000. If there are many SRDF sessions on the Symmetrix Array, this value has to be reduced to 100 or below to ensure a timely update. Whether or not this parameter has to be changed can be seen in the Provider state page (see 10.5.4 Provider Configuration). If the provider responsible for the EMC Symmetrix shows an error message, then the SymDevPollNumber can be reduced.

http://help.fluidops.com/help/index.jsp?topic=%2Fecm.help-4.1%2FDocuments%2F442emcsymmetrix.htm

2/2