Tweet this document:
Follow us on Twitter:
The EMC Storage Integrator (ESI) for Oracle VM version 3.3 is a plug-in that enables Oracle VM to discover and provision EMC Storage arrays. The Integration Module is built upon the Oracle VM Storage Connect (OCS) framework. The framework provides a set of storage discovery and provisioning Application Programming Interfaces (API) that enhance the ability to manage and provision EMC storage in an Oracle VM environment.
These are the steps for installing the ESI for Oracle VM plug-in. We encourage you to visit EMC online support to updates to the ESI installation steps.
Edit the ESI for Oracle VM configuration file:
The ESI for Oracle VM uses isa.conf to define its runtime behavior. For example:
The properties in the above table can be set in the isa.conf file. This file is manually created in plain text under the directory:
The root user must have permissions to the isa.conf file.
Register a VMAX storage Array
The Oracle VM administrator will have to work with the EMC storage administrator for this one time registration of the storage array. As the list below does have sensitive information the recommendation is to have the EMC storage administrator enter the information.
Repeat these steps for each VMAX array that supports Oracle VM.
Once the VMAX storage array has been registered the Oracle VM administrator can refresh the list of available storage arrays and see the newly added EMC storage array(s). Clicking on the storage array the Oracle VM administrator will see storage available for use.
Create and remove thin LUNs
Provisioning storage is very easy as the Oracle VM administrator would follow the normal steps in creating a storage repository to present to the Oracle VM server(s) as a storage pool. Once the storage repository is available the administrator can add the storage resources to virtual machines.
It is important to know how storage is created on the EMC arrays as part of the preparing and configuring storage resources. The parameter “AutoMetaEnabled” directs the EMC storage array to create a thin device on of two ways:
Tip: Planning thin devices for Oracle databases The maximum size of a stand thin device in a Symmetrix VMAX is 240 GB. If a larger size is needed, then a metavolume comprised of thin devices can be created. When host striping is used, like Oracle ASM, it is recommended that the metavolume be concatenated rather than striped since the host will provide a layer of striping, and the thin pool is already striped based on data devices.
After the repository is created all the Oracle VM administrator needs to do is present the repository. Presenting the repository involves selecting which Oracle VM servers can use the current storage repository. It’s that easy!
Use Auto-Provisioning (LUN masking)
Making the discovered array usable by your Oracle VM servers involves access groups. An access group has a name and sometimes a description but most importantly the administrator can select from a list of available storage initiators and assign which storage initiators belong to the access group. A storage initiator is similar to an email address as it allows communication between people. Adding a storage initiator to a access group means the administrator is granting access to the underlying storage. Not adding or removing a storage initiator from an access group is called, “masking” and is a way to prevent access to the storage array.
Creating clones is a simple four step process that enables the Oracle VM administrator to very quickly create point in time copies of virtual machines. A newly created clone is immediately accessible to the host, even while data copying is occurring in the background. Here are the steps:
The ability to create very quick clones of virtual machines enables DBA teams and application owners to save time in activities like patching and functional testing. At EMC we have embraced the use of virtualization and automation to drive Database-as-a-Service within the company and can now provision Oracle, SQL Server and other databases in one hour. To learn more I recommend reading, “EMC IT’s Database-as-a-Service” paper and viewing the video, “EMC IT’s eCALM Demo.”
What I found amazing about writing this blog is how easy it is to start using the EMC Storage Integrator for Oracle VM and the immediate benefits of auto discovery, fast storage provisioning and ease of management. I was able to summarize the installation steps in about half a page! EMC is integrating up the Oracle stack enabling the Oracle VM administrator and DBA to do more with our storage arrays and this ESI integration is a strong example. Other points of integration include our FREE Plug-in for Oracle Enterprise Manager 12c and the new application (Oracle database) awareness in Unisphere 8.0. Hope you enjoyed reading this blog and let us know if you are using the ESI storage integrator.