Before you register a storage server, you require the following privileges and licenses to successfully use Snap Clone:

• Configuring NetApp Hardware

• Configuring Sun ZFS and ZS3 Hardware

• Configuring Solaris File System (ZFS) Storage Servers

• Configuring EMC Storage Servers

• Obtaining NetApp Hardware Privileges

• Obtaining NetApp Hardware Licenses

• Creating NetApp Storage Credentials

• Configuring NetApp 8 Cluster Mode Hardware

• NetApp 8 Configuration Supported with Cluster Mode

• Preparing the NetApp 8 Storage and SVM

'api-volume-*', 'api-*', 'cli-*' 

• api-aggr-list-info

• api-aggr-options-list-info

• api-file-delete-file

• api-file-get-file-info

• api-file-read-file

• api-license-list-info

• api-nfs-exportfs-append-rules

• api-nfs-exportfs-delete-rules

• api-nfs-exportfs-list-rules

• api-nfs-exportfs-modify-rule

• api-snapshot-create

• api-snapshot-delete

• api-snapshot-list-info

• api-snapshot-reclaimable-info

• api-snapshot-restore-volume

• api-snapshot-set-reserve

• api-system-api-get-elements

• api-system-api-list

• api-snapshot-set-schedule

• api-system-cli

• api-system-get-info

• api-system-get-ontapi-version

• api-system-get-version

• api-useradmin-group-list

• api-useradmin-user-list

• api-volume-clone-create

• api-volume-clone-split-estimate

• api-volume-create

• api-volume-destroy

• api-volume-get-root-name

• api-volume-list-info

• api-volume-list-info-iter-end

• api-volume-list-info-iter-next

• api-volume-list-info-iter-start

• api-volume-offline

• api-volume-online

• api-volume-restrict

• api-volume-set-option

• api-volume-size

• cli-filestats

• login-http-admin

• flex_clone

• nfs

• snaprestore

1. Create ROLE em_smf_admin_role' with all the recommended capabilities, such as api-aggr-list-info,api-file-delete-file, and the like.

2. Create GROUP em_smf_admin_group with the ROLE em_smf_admin_role.

3. Create USER em_smf_admin with GROUP em_smf_admin_group and a secure password.

• NetApp 8 Configuration Supported with Cluster Mode

• Preparing the NetApp 8 Storage and SVM

• Snap Clone features are supported only with SVM (Vserver).

• Registration of a physical cluster node is not supported.

• Multiple SVMs can be registered with Enterprise Manager Cloud Control 13c. All the registered SVMs are managed independently.

• The NetApp 8 c-mode hardware should have an SVM created. If not, you should create an SVM which will be registered with the Enterprise Manager.

• The SVM should have a network interface (LIF) with both Management and Data access. The domain name and IP address of this interface should be provided on the Storage Registration page in the Enterprise Manager.

• There should be at least one aggregate (volume) assigned to the SVM. The aggregates should not be shared between the SVMs.

• The SVM should have a user account that has the vsadmin-volume role assigned for ontapi access.

  The user credentials should be supplied on the Storage Registration page in the Enterprise Manager.

• The root volume of SVM should have an export policy with a rule that allows Read Only access to all hosts. If you are using NFS v4, then the Superuser access needs to be granted from the Modify Export Rule dialog box.

  Note:

  • A directory named em_volumes is created with permissions 0444 inside the root volume of SVM. This directory will be used as an Enterprise Manager name space for the junction point.

  • All the storage volumes created will use the junction point /em_volumes in the name space.

  Note:

  When you register an SVM in Enterprise Manager Cloud Control, the details of all the aggregates assigned to it are fetched. The total size of an aggregate is required to set the quota, perform space computation, and for reporting.

  Presently, NetApp does not provide any Data ONTAP API to fetch the aggregate total size from an SVM. As a workaround, the available size of an aggregate is considered as the total size and is set as the Storage Ceiling during first Synchronize run. Storage Ceiling is the maximum amount of space that Enterprise Manager can use in an aggregate.

  If the total space of an aggregate is increased on the storage, you can increase the Storage Ceiling till you consume the available space in that aggregate.

• Obtaining Sun ZFS Hardware Privileges

• Obtaining Sun ZFS Hardware Licenses

• Creating Sun ZFS Storage Credentials

• changeProtocolProps

• changeSpaceProps

• clone and createShare

• destroy

• rollback

• takeSnap

1. Create ROLE em_smf_admin_role.

2. Create AUTHORIZATIONS for the ROLE em_smf_admin_role.

3. Set SCOPE as nas.

4. Set the recommended permissions, such as, allow_changeProtocolProps, allow_changeSpaceProps, and the like to true.

5. Create USER em_smf_admin and set its ROLE property as em_smf_admin_role.

   Note:

   The user em_smf_admin must be a dedicated user to be used by Oracle Enterprise Manager. Oracle does not recommend sharing this account for any other purposes.

• Obtaining Solaris File System (ZFS) Privileges

• Obtaining Solaris File System (ZFS) Licenses

• Setting Up Solaris File System (ZFS) Storage Servers

• clone

• create

• destroy

• mount

• rename

• rollback

• share

• snapshot

• quota

• reservation

• sharenfs

• canmount

• recordsize

This section contains the following:

• Prerequisites for Setting Up Solaris File System (ZFS) Storage Servers

• Requirements for Storage Area Network Storage

• Recommendations for Solaris File System (ZFS) Pools

• Configuring Solaris File System (ZFS) Users and Pools

• Ensure that zfs_arc_max is not set in /etc/system. If it needs to be set ensure that it is set to a high value such as 80% of RAM.

• Ensure that the storage server is configured with multiple LUNs. Each LUN should be a maximum of 1TB. A minimum 2 LUNs of 1TB each is recommended for a Snap Clone. Each LUN should have a mirror LUN which is mounted on the host over a different controller to isolate failover. A LUN can be attached to the Solaris host over Fibre Channel for better performance.

  Note:

  If Fibre Channel is not available, any direct attached storage or iSCSI based LUNs are sufficient.

• All LUNs used in a pool should be equal in size. It is preferable to use less than 12 LUNs in a pool.

• Apart from LUNs, the storage needs cache and log devices to improve zpool performance. Both these devices should ideally be individual flash/SSD devices. In case it's difficult to procure individual devices, one can use slices cut from a single device. Log device needs to be about 32GB in size and also have redundancy and battery backup to prevent data loss. Cache device can be about 128GB in size and need not have redundancy.

• It is recommended to create large LUNs and lesser number of LUNs. The maximum recommended size for a LUN is 3TB.

• LUNs should come from different SAN storage pools or an entirely different SAN storage device.

  These LUNs are needed for mirroring, to maintain the pool level redundancy. If your SAN storage maintains a hardware level redundancy, then you can skip this requirement.

• The LUNs should be exposed over Fiber Channel.

• Create the Storage pool with multiple LUNs of the same size. You can add more disks to the storage pool to increase the size based on your usage.

• The storage pool created on the Solaris File System (ZFS) storage server should use the LUNs coming from a different SAN storage pool or an entirely different SAN storage device. You can skip this if your SAN storage maintains hardware level redundancy.

• To repair data inconsistencies, use ZFS redundancy such as mirror, RAIDZ, RAIDZ-2 or RAIDZ-3 to repair data inconsistencies, regardless of whether RAIDZ is implemented at the underlying storage device.

• For better throughput and performance, use cache and log devices. Both these devices should ideally be on individual flash/SSD devices. In case of difficulty in procuring individual devices, you can use slices cut from a single device.

  It is recommended to have the Log device at about 50% of RAM and also have redundancy and battery backup to prevent data loss. Cache device size could be based on the size of the workload and the pool.

  Cache device do not support redundancy. This is optional.

• While creating the pool, it has to be sized to accommodate the test master database along with the cloned databases. A clone will co-exist with the parent database in the same storage pool. Therefore, you should plan for test master and clone capacity well ahead.

  For example, The size of the test master is 1TB and you expect to create 10 clones with each of them expected to differ from the test master by 100G. Then, the storage pool should be minimum 2.5TB in size.

• Maintain the storage pool with at least 20% free space. If the free space falls below this level, then the performance of the pool degrades.

# /sbin/useradd -d /home/emzfsadm -s /bin/bash emzfsadm
# passwd emzfsadm

You need to configure the ZFS pool that is used to host volumes, and grant privileges on this pool to the user created. The emzfsadm user should have the privileges on all the zpools and its mount points in the system.

To configure the ZFS pool, refer to the following table and run the following commands:

# zpool create lunpool mirror lun1=c9t5006016E3DE0340Ed0 mir1=c10t5006016E3DE0340Ed2 mirror lun2=c9t5006016E3DE0340Ed1 mir2=c10t5006016E3DE0340Ed3 log ssd1=c4t0d0s0 cache ssd2=c4t0d1s0
 

Example format output is as follows:

bash-4.1# /usr/sbin/format
Searching for disks...done
 
AVAILABLE DISK SELECTIONS:
       0. c9t5006016E3DE0340Ed0 <DGC-VRAID-0532-1.00TB>
          /pci@78,0/pci8086,3c08@3/pci10df,f100@0/fp@0,0/disk@w5006016e3de0340e,0
       1. c9t5006016E3DE0340Ed1 <DGC-VRAID-0532-1.00TB>
          /pci@78,0/pci8086,3c08@3/pci10df,f100@0/fp@0,0/disk@w5006016e3de0340e,1
       2. c10t5006016E3DE0340Ed2 <DGC-VRAID-0532-1.00TB>
          /pci@78,0/pci8086,3c08@3/pci10df,f100@0/fp@0,0/disk@w5006016e3de0340e,2
       3. c10t5006016E3DE0340Ed3 <DGC-VRAID-0532-1.00TB>
          /pci@78,0/pci8086,3c08@3/pci10df,f100@0/fp@0,0/disk@w5006016e3de0340e,3


[ We need to find the size of pool that was created ]
# df -k /lunpool
Filesystem           1024-blocks        Used   Available Capacity  Mounted on
lunpool              1434746880          31  1434746784     1%    /lunpool
 
[ We use the Available size shown here to set quota as shown below ]
 
# zfs set quota=1434746784 lunpool
 
# zfs allow emzfsadm clone,create,destroy,mount,rename,rollback,share,snapshot,quota,reservation,sharenfs,canmount,recordsize,logbias lunpool
 
# chmod A+user:emzfsadm:add_subdirectory:fd:allow /lunpool
 
# chmod A+user:emzfsadm:delete_child:fd:allow /lunpool

• Supported Configuration for EMC Storage Servers

• Requirements for EMC Symmetrix VMAX Family and Database Servers

• Preparing the Storage Area Network

• Understanding VMAX Terminology

• Preparing the EMC VMAX Storage

• Preparing the EMC VNX Storage

• Preparing Database Servers

• Setting Privileged Host Monitoring Credentials

• EMC VMAX 10K and VNX 5300 are certified to use. Higher models in the same series are expected to work.

• Only Linux and Solaris operating systems are supported. Other operating systems are not yet supported.

• Multi-pathing is mandatory.

• Only EMC PowerPath, and Solaris MPxIO are supported.

• Switched fabric is supported. Arbitrated loop is not supported.

• Emulex (LPe12002-E) host bus adapters are certified to use. Other adapters are expected to work.

• SCSI over Fibre Channel is supported. iSCSI, NAS are not yet supported.

• Oracle Grid Infrastructure 11.2 is supported.

• Oracle Grid Infrastructure 12.1 with Local ASM Storage option is supported. Flex ASM is not supported.

• ASM Filter Driver is not supported.

• ASM support is only for raw devices. File System is not supported.

• Support for Thin Volumes (TDEV) on VMAX.

• Support for only LUNs on VNX. NAS is not yet supported.

• EMC VMAX Enginuity Version: 5876.251.161 and above

• SMI-S Provider Version: V4.6.1.6 and above

• Solutions Enabler Version: V7.6-1755 and above

The requirements for database server are as follows:

Oracle Database Requirements

• Oracle Database 10.2.0.5 and higher

Operating System Requirements

• Oracle Linux 5 update 8 (compatible with RHEL 5 update 8) and above

• Oracle Linux 6 (compatible with RHEL 6) and above

• Oracle Solaris 10 and 11

Multipathing Requirements

• EMC PowerPath Version 5.6 or above as available for Linux Operating System release and kernel version

• EMC PowerPath Version 5.5 or above as available for Oracle Solaris 11.1 release

• EMC PowerPath Version 6 is not supported.

• Solaris MPxIO as available in latest update

Oracle Grid Infrastructure Requirements

• Oracle Grid Infrastructure 11.2

• Oracle Grid Infrastructure 12.1. Flex ASM is not supported.

SAN Fabric Configuration

Configure your SAN fabric with multipathing by ensuring the following:

• You must have redundancy at storage, switch and server level.

• Perform the zoning such that multiple paths are configured from the storage to the server.

• Configure the paths such that a failure at a target port, or a switch or a host bus adapter will not cause unavailability of storage LUNs.

• Configure gatekeepers on the host where EMC SMI-S provider is installed. To configure gatekeepers, refer to the documentation available on the EMC website:

SMI-S Provider

You should install the SMI-S provider and Solutions Enabler on one of the servers in the fabric where the storage is configured. To install and configure the SMI-S provider, refer to the documentation available on the EMC website:

The SMI-S provider URL and login credentials are needed to interact with the storage. An example of an SMI-S Service Provider URL is https://rstx4100smis:5989.

These details are needed when you register a storage server. You are required to do the following:

• Ensure that the VMAX or VNX storage is discovered by the SMI-S provider.

• Add the VNX storages to the SMI-S provider.

• Create a user account with administrator privileges in the SMI-S provider to access the VMAX or VNX storage.

• Set a sync interval of 1 hour.

For more information on VMAX storage and terminologies, refer to the document EMC Symmetrix VMAX Family with Enginuity available in the EMC website.

• Ensure that all the Host Initiator ports are available from the storage side.

• It is recommended to create one initiator group per host with corresponding initiators to increase security. The 'Consistent LUNs' property of the immediate parent Initiator Group of the initiators should to set to 'No'

• Create a Port Group called ORACLE_EM_PORT_GROUP to be used by Oracle Enterprise Manager for creating Masking Views. This port group should contain all the target ports that will be viewed collectively by all the hosts registered in the Enterprise Manager Cloud Control system.

  For example, host1 views storage ports P1 and P2, and host2 views storage ports P3 and P4. Then, the ORACLE_EM_PORT_GROUP should include all ports P1, P2, P3 and P4. Include only the necessary target ports as needed by the development infrastructure.

• Create a separate Virtual Provisioning Pool also known as Thin Pool, and dedicate it for Oracle Enterprise Manager.

• Ensure that the TimeFinder license is enabled to perform VP Snap

• Ensure that all host initiator ports are available from the storage side.

• Ensure that the initiators belonging to one host are grouped and named after the Host on the EMC VNX storage.

• Create one storage group with one host for each of the hosts registered in Enterprise Manager.

  For example, if initiators i1 and i2 belong to host1, register the initiators under the name Host1. Create a new storage group SG1 and connect Host1 to it. Similarly, create one storage group for each of the hosts that are to be added to Enterprise Manager.

• Servers should be physical and equipped with Host Bus Adapters. NPIV and VMs not supported.

• Configure your servers with recommended and supported multipath software. If you use EMC PowerPath, then enable the PowerPath license.To enable the PowerPath license, use the following command:

  emcpreg -install
  

• If you need the servers to support Oracle Real Application Clusters, then install Oracle Clusterware.

  Note:

  ASM and Clusterware have to be installed and those components have to be discovered in Enterprise Manager as a target. Once ASM and Clusterware are installed, additional ASM disk groups can be created from Enterprise Manager.

• Enable Privileged Host Monitoring credentials for all the servers. If the server is part of a cluster, then you should enable privileged host monitoring credential for that cluster.

  For more details on enabling privileged host monitoring credentials, refer to Oracle Enterprise Manager Framework, Host, and Services Metric Reference Manual.

• If you are using Linux, you should configure Oracle ASMLib, and set the asm_diskstring parameter to a valid ASM path. For example:

  /dev/oracleasm/disks/

  Update the boot sequence such that the ASMLib service is run first, and then the multipath service.

  To install Oracle ASMLib, refer to the following website:

  http://www.oracle.com/technetwork/server-storage/linux/install-082632.html

  To configure Oracle ASMLib on multipath disks, refer to the following website:

  http://www.oracle.com/technetwork/server-storage/linux/multipath-097959.html

1. From the Setup menu, click on Security and then select Monitoring Credentials.

2. On the Monitoring Credentials page, select Cluster or Host according to your requirement and then. click Manage Monitoring Credentials.

   
   

   

   
   

3. On the Cluster Monitoring Credentials page, select Privileged Host Monitoring Credentials set for the cluster or host and click Set Credentials.

   
   

   

   
   

4. In the dialogue box that appears, specify the credentials, and click Save.

5. After the host monitoring credentials are set for the cluster, refresh the cluster metrics. Verify if the Storage Area Network metrics get collected for the hosts.

   
   

   

   
   

A Proxy Agent is required when you register a NetApp, Sun ZFSSA or Solaris File System (ZFS) File System.

Before you register a NetApp storage server, meet the following prerequisites:

• Acquiring Third Party Licenses

• Uploading Storage Vendor SDK

• Overriding the Default SDK

• Overriding Third Party Server Components

• Source CPAN - CPAN licensing apply

  • IO::Tty (version 1.10)

  • XML::Simple (version 2.20)

  • Net::SSLeay (version 1.52)

• Open Source - Owner licensing apply

  • OpenSSL(version 1.0.1e)

1. Download the NetApp Manageability SDK version 5.0R1 for all the platforms from the following NetApp support site: http://support.netapp.com/NOW/cgi-bin/software

2. Unzip the 5.1 SDK and package the Perl NetApp Data OnTap Client SDK as a tar file. Generally, you will find the SDK in the lib/perl/NetApp folder. The tar file when extracted should look as follows:

   NetApp.tar
   - netapp
     - Na	Element.pm
     - NaServer.pm
     - NaErrno.pm
   

   For example, the Software Library entity Storage Management Framework Third Party/Storage/NetApp/default should have a single file entry that contains NetApp.tar with the above tar structure.

   Note:

   Ensure that there is no extra space in any file path name or software library name.

3. Once the tar file is ready, create the following folder hierarchy in software library: Storage Management Framework Third Party/Storage/NetApp

4. Upload the tar file as a Generic Component named default.

   Note:

   YTo upload the tar file, you must use the OMS shared filesystem for the software library.

   The tar file should be uploaded to this default software library entity as a Main File.

To override the existing SDK for a storage server, upload the tar file to the Software Library entity. The tar file should have the structure as mentioned in Step 3 of the previous section.

The Software Library entity name should be the same as the storage server name.

For example, if the storage server name is mynetapp.example.com, then the Software Library entity must be as follows:

Storage Management Framework Third Party/Storage/NetApp/mynetapp.example.com

thirdparty
|-- lib
| |-- engines
| | |-- lib4758cca.so
| | |-- libaep.so
| | |-- libatalla.so
| | |-- libcapi.so
| | |-- libchil.so
| | |-- libcswift.so
| | |-- libgmp.so
| | |-- libgost.so
| | |-- libnuron.so
| | |-- libpadlock.so
| | |-- libsureware.so
| | `-- libubsec.so
| |-- libcrypto.a
| |-- libcrypto.so
| |-- libcrypto.so.1.0.0
| |-- libssl.a
| |-- libssl.so
| `-- libssl.so.1.0.0
`-- pm
|-- CPAN
| |-- IO
| | |-- Pty.pm
| | |-- Tty
| | | `-- Constant.pm
| | `-- Tty.pm
| |-- Net
| | |-- SSLeay
| | | `-- Handle.pm
| | `-- SSLeay.pm
| |-- XML
| | `-- Simple.pm
| `-- auto
| |-- IO
| | `-- Tty
| | |-- Tty.bs
| | `-- Tty.so
| `-- Net
| `-- SSLeay
| |-- SSLeay.bs
| |-- SSLeay.so

Ensure that the tar file is uploaded to the Software Library entity which is named after the platform name, x86_64. The Software Library entity must be under the following:

Storage Management Framework Third Party/Server

The x86_64 entity, when uploaded is copied to all the storage proxy hosts irrespective of which storage server it would be processing. To use this entity on a specific storage proxy agent, name the entity after the host name.

For example, Storage Management Framework/Third Party/Server/x86_64 will be copied to any storage proxy host which is on an x86_64 platform. Similarly, Storage Management Framework Third Party/Server/myhost.example.com is copied only to myhost.example.com, if it is used as a storage proxy host.

The host name is given a higher preference than the platform preference.

1. From the Setup menu, click on Provisioning and Patching, and then select Storage Registration.
2. On the Storage Registration page, in the Storage section, click on Register, and then select either NetApp Storage Appliance or Sun ZFS Storage Appliance, based on which storage server you want to register.

   Note:

   If you see a No named credentials available message, it means that no credentials are registered or the credentials are owned by another user.

   
   

   

   
   

   Note:

   You need the EM_STORAGE_ADMINISTRATOR role to complete the storage registration.

3. On the NetApp or Sun ZFS Storage Registration page, in the Storage section, do the following:
   
   

   

   
   

   • Enter the storage server name in the Name field. Ensure that the name is the valid host name and contains no spaces and invalid characters.

   • Select the protocol.

     Note:

     For NetApp storage, the connection is over http or https. For Sun ZFS storage, the connection is over ssh.

   • Select the Storage Credentials, or click on the green plus sign to add.

     Note:

     These credentials will be used by the Management Agent to execute storage (NetApp or Sun ZFS) APIs.

     Only credentials owned by the user are displayed here.

     In the display box that appears, enter the storage server name and password. Confirm the password and click OK.

   • Enter storage name aliases (optional).

     The storage name alias should be in lowercase.

     Note:

     A storage name alias is any name that may have been used when mounting a volume from the storage.

     For example: IP address, FQDN, DNS alias, and the like.

     A storage alias is necessary to identify the database targets on the storage. The database targets are identified by mapping the mount points to the files used by the database. For example, if the storage mystorage.com has an alias mystorage.net, and a database uses a data file mounted as mystorage.net:/u01, then mystorage.net must be added as an alias for the discovery to work.

     When you register the storage, use the admin interface as the storage name. List the data interfaces in the storage alias section. The registered storage name will be used to perform registration operations and while mounting the volumes on target host, it will give preference to interfaces listed as storage aliases.

4. In the Agent to Manage Storage section, do the following:

   • Click Add to add a Management Agent host. A Storage Agent display box appears. Select a Management Agent from the Target Name column of the table. Then, click Select.

     Note:

     The Management Agent list displays only Linux X64 Management Agents.

     
     

     

     
     
     
     

     

     
     

     The Management Agent selected is used for performing operations on the storage server.

   • Once a Management Agent is selected, the Management Agent credentials are found and a named credential for the host is displayed.

     Note:

     The Management Agent credentials are used to connect to the Management Agent from Oracle Management Service.

     Multiple Management Agents can be configured to monitor the storage device. Click Add to choose a second Management Agent if required.

     Note:

     Configuring multiple Management Agents to monitor the storage device provides you with a backup in the event that an host is down or the Management Agent is under blackout.

   • Click Submit to register the storage server.

1. From the Setup menu, click on Provisioning and Patching, and then select Storage Registration.
2. On the Storage Registration page, in the Storage section, click on Register, and then select Solaris File System (ZFS)

   Note:

   If you see a No named credentials available message, it means that no credentials are registered or the credentials are owned by another user.

   
   

   

   
   

   Note:

   You need the EM_STORAGE_ADMINISTRATOR role to complete the storage registration.

3. On the Register File System (ZFS) page, in the Storage section, do the following:

   • Enter the Solaris system name in the Name field. Ensure that the name is the valid host name or IP address and contains no spaces and invalid characters.

   • Select the protocol.

   • Select the Storage Credentials, or click on the green plus sign to add.

     Note:

     These credentials will be used by the Management Agent to execute Solaris file system APIs.

     Only credentials owned by the user are displayed here.

     In the display box that appears, enter the storage server name and password. Confirm the password and click OK.

   • Enter storage name aliases (optional).

     The storage name alias should be in lowercase.

     Note:

     A storage name alias is any name that may have been used when mounting a volume from the storage.

     For example: IP address, FQDN, DNS alias, and the like.

     Storage alias is necessary to identify the database targets on the storage. The database targets are identified by mapping the mount points to the files used by the database. For example, if the storage mystorage.com has an alias mystorage.net, and a database uses a data file mounted as mystorage.net:/u01, then mystorage.net must be added as an alias for the discovery to work.

     When you register the storage, use the admin interface as the storage name. List the data interfaces in the storage alias section. The registered storage name will be used to perform registration operations and while mounting the volumes on target host, it will give preference to interfaces listed as storage aliases.

     
     

     

     
     
4. In the Synchronize Schedule section, specify the frequency to synchronize the storage details with the hardware.

   Ensure that the zpools setup is completed before clicking Submit. To setup the zpools, refer to Configuring Solaris File System (ZFS) Users and Pools.

1. From the Setup menu, click on Provisioning and Patching, and then select Storage Registration.
2. On the Storage Registration page, in the Storage section, click on Register, and then select EMC Storage Array.
   
   

   

   
   

   Note:

   If you see a No named credentials available message, it means that no credentials are registered or the credentials are owned by another user.

   Note:

   You need the EM_STORAGE_ADMINISTRATOR role to complete the storage registration.

3. On the Register EMC Storage Appliance page, in the Storage section, do the following:

   • Specify the storage server name in the Name field. Ensure that the name is the valid storage name and contains no spaces and invalid characters.

   • For EMC storage, the connection is over SMI-S protocol. Specify the SMI-S Provider URL.

   • Specify the SMI-S User Credentials, or click on the green plus sign to add.

     Note:

     These credentials are used by the Enterprise Manager to interact with the EMC storage appliance.

     The credentials should be of the Administrator in the SMI-S provider and not that of the storage.

     Only credentials owned by the user are displayed here.

     In the display box that appears, enter the SMI-S User name and password. Confirm the password and click OK.

4. In the Synchronize Schedule section, specify the frequency to synchronize the storage details with the hardware.
   
   

   

   
   

   Click Submit.

1. On the Storage Registration page, in the Storage section, click Synchronize.

   Note:

   When you click on Synchronize, a deployment procedure is submitted which discovers all databases monitored by Enterprise Manager Cloud Control which can be used for Snap Clone.

   Windows databases are not discovered as part of storage discovery. This is because the Windows storage NFS collection does not happen at all. For further details please refer to the MOS note 465472.1

   You need EM_STORAGE_OPERATOR role along with GET_CREDENTIAL privilege on the Storage Server and Storage Management Agent credentials to be able to synchronize the storage.

2. A confirmation box appears. Click OK.
   
   

   

   
   

   This action now submits a one-time synchronization job.

   Note:

   The synchronization job fetches latest storage information, and recomputes the mapping between storage volumes and databases.

3. On the Storage Registration page, in the Storage section, to view the procedure details of the Management Agent host, click on the value (for example, Scheduled) in the Status column.
   
   

   

   
   
4. On the Provisioning page, in the Procedure Steps section, click View, and then select Expand All. Keep clicking the Refresh button on the page to view the procedure activity as it progresses.
   
   

   

   
   

   The synchronization status of the Management Agent on the Storage Registration page, changes to Succeeded once the synchronization process is complete.

5. To update a synchronize schedule of a registered storage server, select a storage server on the Storage Registration page and then click on Edit. On the Edit Storage page, in the Synchronize Storage section, edit the repetition time and frequency of the synchronize job.
   
   

   

   
   

   Note:

   The frequency of a synchronization job is set at 3 hours by default.

   Click Submit.

1. From the Setup menu, click on Provisioning and Patching, and then select Storage Registration.
2. On the Storage Registration page, in the Storage section, select a storage server from the list of registered storage servers.
3. Select Remove.

   On the Remove Storage page, select the storage server that you want to deregister, and then click Submit.

   The storage server is now deregistered.

1. On the Storage Registration page, in the Storage section, select the EMC Symmetrix VMAX Family or EMX VNX storage on which you want to create thin volumes.
2. In the Details section, select the Contents tab, and then click Create Thin Volume.
   
   

   

   
   
3. In the Storage Details section, the ASM Disk Group is set to Create with External Redundancy, by default. ASM Disk Group creation is optional. If you want to create an ASM Disk Group with redundancy you can skip this step for now by selecting Do not create. I will create later. You can then later create it using the Oracle Enterprise Manager ASM target home page or the ASM Configuration Assistant.
4. Click Add to create multiple LUNs of same size and create an ASM disk group with those volumes. You can create one or more disk groups at a time.
5. Select the thin pool/storage pool, and then specify the number of thin volumes, and the size for the thin volume.

   Note:

   It is recommended to create larger LUNs and lesser number of LUNs.

   For example, if you want a disk group of size 200 GB, create 1 LUN of size 200 GB and make a disk group out of it. Do not create 10 x 20 GB LUNs for it.

   Note:

   A thin volume of size more than 240GB is not permitted by default on a VMAX storage. To create thin volumes of size more than 240GB, request the storage administrator to enable auto meta on the VMAX. The storage administrator can remove this restriction or in the alternative, create multiple thin volumes of size less than 240GB.

   To create LUNs of size more than 240GB, contact the storage administrator to enable auto meta.

   Do not create LUNs of size more than 2TB.

6. In the Host Details section, specify a host or a cluster, or select one by clicking the Search icon. The disks will be created on the ASM instance present on this host or cluster. A single disk partition is created on all the presented disks.

   Note:

   Only Linux and Solaris hosts are supported.

7. Specify the root and grid infrastructure credentials. Only the credentials that you own are listed.
   
   

   

   
   

   Click Submit.

   Note:

   Once a Create Target request succeeds and a diskgroup has been created, you must manually set the attributes of the diskgroup in compatible.asm and compatible.rdbms depending on the version of the database that will be installed on the diskgroup.

Example 19-1 Understanding Space Utilization on EMC Storage Servers

Writable space implementation on EMC Storage Server is different from NetApp, Sun ZFS SA, and Sun ZFS storage servers. In NetApp, Sun ZFS SA, and Sun ZFS storage servers, writable space defined in a service template will be allocated from the storage pool to the clone database even if data is not written to the volume. In EMC storage servers (VMAX and VNX) space is only reserved on the storage pool. The space is consumed only when data is written to the volume or LUN.

For example, if you define 10GB writable space in a service template, in NetApp, Sun ZFS SA, and Sun ZFS, space of 10GB will be allocated to the clone database from storage pool even if data is not written to the volume. In an EMC storage, space is consumed only when data is written to the volume or LUN.

In Enterprise Manager, to create thin volumes (ASM Disk groups/LUNS) up to the maximum size defined for the storage pool, select the Contents tab on the Storage Registration page, and then select Create Thin Volume.The test master database can then be created on ASM Disk groups or LUNs.

The following graphic shows the Test Master database and the created clone database:

The following graphic shows the storage volume of the Test Master database:

The following graphic shows storage volume of the clone database:

Note:

ASM disk groups, as discussed, can be created using the Create Thin Volumes option. However, they can also be created using other methods. The following example illustrates the space usage on EMC VMAX and VNX storage servers:

Let us assume the Storage Pool is of size 1 TB and Storage ceiling is set to 1 TB.

Scenario 1:

If an Enterprise Manager Storage Administrator creates 2 ASM disk groups, as an example, DATA and REDO of sizes 125GB and 75GB respectively through the Create Thin Volume method and the Test Master database is created on those disk groups, used space on DATA and REDO disk groups are 100GB and 50GB respectively (remaining free space on DATA and REDO disk groups are 25GB), then each clone database created by a self service user will be allocated 25GB of writable space on the DATA and REDO disk groups.

New data written to the cloned database is the actual used space and can grow up to 25GB on each disk group. The DATA and REDO disk groups in this scenario.

The Enterprise Manager Storage Administrator will be able to create 600GB LUNs through the Create Thin volume method, assuming a clone database is created from a 200GB Test Master database. The size of the clone database will also be deducted from available space. The Self Service User will be able to create multiple clones. The number of clone databases that can be created cannot be estimated as it depends on the amount of new data written to the initial clone database in that storage pool.

Scenario 2:

If an Enterprise Manager Storage Administrator creates 2 ASM disk groups, as an example, DATA and REDO of sizes 850GB and 150GB respectively through the Create Thin Volume method, and the Test Master database is created on those ASM disk groups, used space on the DATA and REDO disk groups are 750GB and 50GB respectively (remaining free space on DATA and REDO is 100GB), then each clone database created by a self service user will be allocated 100GB of writable space on DATA and REDO disk groups.

New data written to the cloned database is the actual used space and can grow up to 100GB on each disk group. The DATA and REDO disk groups in this scenario.

Similar to Scenario 1, the Self Service User will be able to create multiple clones, but number of clone databases cannot be estimated. The Enterprise Manager Storage Administrator will not be able to create additional disk groups in scenario 2. This is the major difference when compared to Scenario 1.

In both scenarios, only the actual used space of the clones will be subtracted from the Storage Ceiling.The general formula for writable disk space is the difference between the LUN size and the actual space occupied by data.

1. On the Storage Registration page, in the Storage section, select a storage server from the list of registered storage servers.

   Note:

   The Storage Registration page displays only the databases which you have VIEW_STORAGE privilege on.

2. Click Manage Access.
   
   

   

   
   
3. On the Manage Access page, do the following:

   • Click Change, if you need to change the Owner of the registered storage server.

     Note:

     The Owner of a registered storage server can perform all actions on the storage server, and grant privileges and roles to other Administrators.

     
     

     

     
     

   • Click Add Grant to grant privileges to an Administrator, Role or both.

   • On the Add Grant page, enter an Administrator name or select the type, and then click Go.

   • Select an Administrator from the list of Administrators or Roles, and then click Select.

4. On the Manage Access page, you can change privileges of an Administrator or Role by selecting the Administrator or Role from the Grantee column, and then clicking Change Privilege.
5. In the Change Privilege display box, you can select one of the three following privileges:

   • View Storage (ability to view the storage)

   • Manage Storage (ability to edit the storage)

   • Full Storage (ability to edit or remove the storage)

   Click OK.

6. You can also revoke a grant to an Administrator by selecting the Administrator from the Grantee column, and then clicking Revoke Grant.
7. When you are done with granting, revoking, or changing privileges to Administrators or Roles, click Submit.