Enables you to set up a Clone LUN without completing its creation.
clone_lun ‑prepare ‑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]... { ‑lunNumber lun‑number | ‑nextLunNumber } | ‑hostGroupMap host‑group‑id‑or‑fqn { ‑lunNumber lun‑number | ‑nextLunNumber } }] [{‑fibreChannelAccess | ‑noFibreChannelAccess}] [‑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}]
The clone_lun -prepare command enables you to organize the details of a new Clone LUN without creating an active clone. You can define the characteristics for the new clone, such as Quality of Service (QoS) attributes, mapping, and storage capacity. When you are ready to complete the creation of the new Clone LUN, run the clone_lun -commit command.
Enables the Clone LUN to be accessible and available for use immediately after you run the clone_lun ‑commit command. To ensure accurate mapping relationships, use the ‑globalMapping option, the ‑hostmap option, or the ‑hostGroupMap option with the ‑active option. Enabling the Clone LUN to be accessible is the default.
Identifies that the Clone LUN can be used as a boot drive in the SAN.
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.
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.
By default, reference tag checking is enabled.
Permits access to the volume through the Fibre Channel (FC) ports. By default, FC access is enabled.
Maps the Clone LUN globally to all hosts using the specified lun-number.
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).
Specifies a mapping relationship between a Clone LUN and a SAN host. You identify the host by providing a unique ID (ID) or a fully qualified name (FQN).
Renders the LUN volume invisible on the network. An inactive volume is not accessible and cannot be used by a SAN host.
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.
Specifies a name for the Clone LUN. The name that you provide must be from 1 through 40 characters. To prevent parsing errors, use double quotation marks around names containing one or more spaces or dashes.
Tab
/ (slash) and \ (backslash)
. (dot) and .. (dot-dot)
Embedded tabs
Instructs the system to assign the next available logical unit number to the volume. This number is used to present an Oracle FS System Clone LUN to a SAN host or to a host group.
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.
Disables access to the Clone LUN through FC ports. By default, access is enabled.
premium. Indicates the highest priority for responding to requests in the processing queue. For Auto-Tier 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-Tier 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-Tier 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-Tier 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-Tier LUNs, busy LUN extents receive the lowest priority when the system migrates the data to the higher-performing storage tiers.
Specifies the FQN or unique identifier (ID) of the source LUN.
Prevents the Clone LUN from being detected or accessed by any SAN host.
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.
The following global options can be used for fully formed fscli commands:
The command completes successfully.
The command returns with an error.
The session times out.
Inspects the validity of the command syntax, not the semantics. Used to test the structure of a command without running the command. Does not determine whether errors would be produced if you issue a structurally correct command with the input provided.
Directs the CLI to prompt you to supply a session key when you issue the command. The CLI displays Sessionkey: as the prompt. To obtain a session key, log in with the ‑returnKey option specified. After the session is established, the session key is displayed in STDOUT. If you request a session key, the ‑sessionkey option is required syntax for all commands that are issued in a given session. In environments with more than one Oracle FS System, the session key is used to determine to which Oracle FS System to direct the command for validation. Session keys are also used to establish two or more CLI sessions when using a shared administrator account.