clone_lun ‑add

Creates a clone of an existing LUN on the Oracle FS System.

SYNOPSIS

clone_lun ‑add 
   ‑name clone‑lun‑name
   ‑source source‑lun‑id‑or‑fqn
   [‑capacity capacity]
   [‑priority {premium | high | medium | low | archive}]
   [‑volumeGroup volume‑group‑id‑or‑fqn]
   [{ ‑unmapped
    | ‑globalMapping lun‑number
    | { ‑hostmap host‑id‑or‑fqn [, host‑id‑or‑fqn]...
      | ‑hostGroupMap host‑group‑id‑or‑fqn
      }
      ‑lunNumber lun‑number
    }]
   [{‑fibreChannelAccess | ‑noFibreChannelAccess}]
   [{‑iscsiAccess | ‑noIscsiAccess}]
   [‑maskedControllerPorts /controller[/slot[/port]]
                     [, /controller[/slot[/port]]]... ]
   [{‑active | ‑inactive }]
   [{‑disableRefTagChecking | ‑enableRefTagChecking}]
   [‑bootLun | ‑noBootLun]

   [{‑sessionKey | ‑u admin‑user ‑oracleFS oracle‑fs‑system}]
   [{‑outputformat | ‑o} { text | xml }]
   [{‑timeout timeout‑in‑seconds | ‑verify | ‑usage | ‑example | ‑help}]

DESCRIPTION

Use the clone_lun ‑add command to create a point-in-time, read-write snapshot of a LUN that can be accessed immediately. When you create a Clone LUN, the properties of the source LUN are applied to the clone by default. You can assign different mapping, performance settings, and QoS characteristics by using the clone_lun ‑add options.

The Clone LUN consumes space from the repository that was allocated for clones when the source LUN was created. You can adjust the amount of space that is available for clones of a LUN by using the lun ‑modify command.

Note: Only administrators with primary administrator, admin1, or admin2 roles are authorized to run the clone_lun ‑add command.

OPTIONS

‑active

Makes a Clone LUN visible on the network so that the clone can be discovered and accessed by a SAN host. By default, the Clone LUN is active.

‑bootLun

Identifies that the Clone LUN can be used as a boot drive in the SAN.

‑capacity

Specifies the storage space in gigabytes for the clone. Specify this value if you want the capacity of the clone volume to be different from the capacity of the source volume. This value must be equal to or larger than the source volume. This space is sometimes referred to as addressable capacity.

‑disableRefTagChecking

Instructs the HBA to bypass the check of whether a host has written to a specific area of the LUN before the host reads from that same area. If this option is omitted, read-before-write error events can be generated.

If this option is omitted, reference tag checking is enabled by default.

‑enableRefTagChecking

Instructs the HBA to check whether a SAN host has written to a specific area of the LUN before the host reads from that area. When a host reads from a specific area before writing to that area, the Oracle FS System generates a read-before-write error event.

Note: This check is sometimes called a reference tag check and is a part of the process for ensuring data protection integrity.

By default, reference tag checking is enabled.

‑fibreChannelAccess

Allows users to access to the volume through the Fibre Channel (FC) ports. By default, FC access is enabled.

‑globalMapping

Maps the Clone LUN globally to all hosts using the specified lun-number.

‑hostGroupMap

Specifies a mapping relationship between a Clone LUN and a host group. You identify the host group mapping by providing a fully qualified name (FQN) or a unique ID (ID).

‑hostmap

Specifies a mapping between a Clone LUN and a SAN host. You identify the host by providing a unique ID (ID) or a fully qualified name (FQN).

‑inactive

Renders the LUN volume invisible on the network. An inactive volume is not accessible and cannot be used by a SAN host.

‑iscsiAccess

Allows access to the Clone LUN through the iSCSI ports.

‑lunNumber

Identifies the logical unit number of a LUN or of a Clone LUN to present to a SAN host or to a host group.

Note: The clone_lun ‑add command does not map the new Clone LUN if the host or host group already contains a LUN with the specified number. You can run the clone_lun ‑modify command to map the new Clone LUN after determining the number to use.

‑maskedControllerPorts

Restricts access to the Clone LUN through one or more Controller ports. Use the following format to mask all of the ports in a Controller, to mask all of the ports for a given Controller slot, or to mask only a specific Controller port: /⁠controller[/⁠slot[/⁠port]]

For controller, provide a string that includes the FQN or ID of the Controller.
For slot, specify the HBA slot number.
For port, specify the port number.

If you do not include this option, the Clone LUN becomes accessible on all Controller ports on the assigned node by default.

‑name

Specifies the name of the Clone LUN that you are creating on the Oracle FS System. Use double quotation marks around names containing dashes.

The following characters are invalid in a LUN name:

Non-printable characters, including ASCII 0 through 31, decimal
/ (slash) and \ (backslash)
. (dot) and .. (dot-dot)
Embedded tabs

Note: The clone_lun ‑add command does not map the new Clone LUN if the Oracle FS System already contains a LUN with the specified name within the same volume group. You can run the clone_lun ‑modify command to map the new LUN after determining the name to assign.

‑noBootLun

Identifies that the Clone LUN cannot be used as a boot drive in the SAN. Not using the Clone LUN as a boot drive is the default.

‑noFibreChannelAccess

Disables access to the new Clone LUN through FC ports. By default, access is enabled.

‑noIscsiAccess

Disables access to the Clone LUN through use of the iSCSI protocol. By default, the Clone LUN is not accessible through the iSCSI protocol.

‑priority

Identifies the priority that the system gives to various operational aspects of a logical volume. These operational aspects include the Controller processing queue, the SAN interface requests, and the migration of the auto-tiered LUN extents.

Note: The processing-queue priority defines the percentage of the Controller CPU cycles that are dedicated to the volume.

Valid priority levels:

Premium: Indicates the highest priority for responding to requests in the processing queue. For auto-tiered LUNs, busy LUN extents receive the highest priority when the system migrates the data to the higher-performing storage tiers.
High: Indicates the next highest priority for responding to requests in the processing queue. For auto-tiered LUNs, busy LUN extents receive the next highest priority when the system migrates the data to the higher-performing storage tiers.
Medium: Indicates an intermediate priority for responding to requests in the processing queue. For auto-tiered LUNs, busy LUN extents receive an intermediate priority when the system migrates the data to the higher-performing storage tiers.
Low: Indicates the next to lowest priority for responding to requests in the processing queue. For auto-tiered LUNs, busy LUN extents receive the next to lowest priority when the system migrates the data to the higher-performing storage tiers.
Archive: Indicates the lowest priority for responding to requests in the processing queue. For auto-tiered LUNs, busy LUN extents receive the lowest priority when the system migrates the data to the higher-performing storage tiers.

‑source

Specifies the FQN or unique identifier (ID) of the source LUN.

‑unmapped

Prevents the Clone LUN from being detected or accessed by any SAN host.

‑volumeGroup

Specifies the FQN or the ID of the volume group to which the Clone LUN is assigned. If you do not include this option, the Clone LUN is assigned to the root level volume group.

EXAMPLE

Task

Create a Clone LUN.

Parameters

The name of the Clone LUN: CLONE_DISK1
The fully qualified name (FQN) of the source LUN: /⁠user1_vg/⁠DISK1

$ fscli clone_lun ‑add ‑name CLONE_DISK1 ‑source /⁠user1_vg⁠/DISK1