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

• Configuring Sun ZFS and ZS3 Hardware

• Configuring Solaris File System (ZFS) Storage Servers

• 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

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

• Source CPAN - CPAN licensing apply

  • IO::Tty (version 1.10)

thirdparty
`-- pm
|-- CPAN
| |-- IO
| | |-- Pty.pm
| | |-- Tty
| | | `-- Constant.pm
| | `-- Tty.pm
| `-- auto
| |-- IO
| | `-- Tty
| | |-- Tty.bs
| | `-- Tty.so
| `-- Net

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 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 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 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 (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. 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 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.