This section explains how to register a storage resource in a storage pool.
The registration method varies depending on the type of storage resource.
For Physical L-Servers
Virtual Storage Resources
Refer to "Virtual Storage Resources and Disk Resources for Physical L-Servers".
Disk Resources
Refer to "Virtual Storage Resources and Disk Resources for Physical L-Servers".
iSCSI Boot Disks
To register iSCSI boot disks, execute the iSCSI boot operation command (rcxadm iscsictl).
For details on the rcxadm iscsictl command, refer to "5.10 rcxadm iscsictl" in the "Reference Guide (Command/XML) CE".
When registering a disk for iSCSI boot in a storage pool, it is recommended to use the appropriate physical storage unit resource allocation method (thin provisioning or thick provisioning) for that disk.
This does not affect the allocation method of storage resources in the storage pool.
Note
If iSCSI boot information already registered is specified, the registered information continues to exist.
If the registered information is changed, delete the iSCSI boot information using the unregister subcommand, and then register the iSCSI boot information by using the register subcommand again.
For Virtual L-Servers
Virtual Storage Resources
Refer to "Virtual Storage Resources and Disk Resources for Physical L-Servers".
Do not register virtual storage resources corresponding to the Solaris 11 zfs root pool, to the storage pool.
[Solaris Zones (Solaris 10)]
It is not necessary to register virtual storage resources.
Disk Resources [KVM] [Solaris Zones (Solaris 10)] [OVM for SPARC]
Register the raw devices or partitions recognized by VM hosts (for Solaris Zones, the global zone) as disk resources.
When a VM host not managed with server management software is used, it is not necessary to register disk resources.
Disk resources can be registered by executing the rcxadm disk register command.
When performing migration of VM guests (for Solaris Zones, non-global zones) corresponding to virtual L-Servers, register devices that are shared between VM hosts as disk resources defined to be shared.
For details on the rcxadm disk command, refer to "3.3 rcxadm disk" in the "Reference Guide (Command/XML) CE".
Note
[KVM] [Solaris Zones (Solaris 10)] [OVM for SPARC]
For disk resources used by virtual L-Servers, the content of disks will remain when disks are detached from the L-Server, or when the L-Server itself is deleted.
When using disk resources that are registered in global pools, perform operation carefully, as the disk resources can be allocated to any users.
When using disk resources for virtual L-Servers, it is recommended to operate the disks in a local pool, and delete data on the disks during deletion of L-Servers or detachment of disks.
Use the following methods to delete the data on disks.
Using an OS, perform disk formatting while the L-Server is connected
Using a function of the storage, perform disk formatting (For ETERNUS)
Create a LUN again
[KVM]
Disk resources created beforehand
The content of disk resources created beforehand remains without being deleted, as explained above.
Disk resources created from virtual storage are deleted.
Deletion of the content of disk resources created beforehand
The deletion of the content of disks can be automated by specifying "true" for "CLEAN_VM_GUEST_DISK_RESOURCE" in the definition file "storage.rcxprop" when the deletion of the content of the disks of all KVM virtual L-Servers in the system is possible.
When you specify the deletion of the content of the disks for each virtual L-Server, specify "false" for "CLEAN_VM_GUEST_DISK_RESOURCE" in the definition file "storage.rcxprop".
Refer to "8.6.1 Creating Definition Files" in the "Setup Guide CE".
Register the disk resources that one VM host can use in one storage pool. Creating the L-Server might fail when disk resources have been divided between two or more storage pools.
When registering a disk resource for virtual L-Servers in a storage pool, it is recommended to use the appropriate physical storage unit resource allocation method (thin provisioning or thick provisioning) for that disk resource.
This does not affect the allocation method of storage resources in the storage pool.
Virtual Storage Resources and Disk Resources for Physical L-Servers
Use the following procedure to register a storage resource:
In the ROR console orchestration tree, right-click the target storage pool, and select [Register Resources] from the popup menu.
The [Register Resources] dialog is displayed.
Select the storage resource to register from [Resources].
When creating a specified size of disk automatically from the virtual storage during L-Server creation, select [Virtual storage].
When [Virtual Storage] is selected, the virtual storage resources which can be registered are displayed in the resource list.
Select the virtual storage resource which you want to register using the [Select] checkbox of the resources, or select all registered virtual storage resources by checking [Select all].
Note
Virtual storage resources cannot be selected for EMC storage.
Virtual storage resources cannot be selected for the Storage Server on which FalconStor NSS operates.
Do not register virtual storage resources corresponding to the Solaris 11 zfs root pool, to the storage pool.
Virtual storage resources corresponding to VSAN datastores can only be registered to storage pools for which Thin Provisioning attributes are configured.
When creating virtual disks from virtual storage resources corresponding to VSAN datastores, the virtual disks are formatted according to the method defined in the virtual machine storage policy.
For this reason, even if storage pools are configured with Thin Provisioning attributes, the virtual disks created from VSAN datastores may not be configured with Thin Provisioning attributes.
Example
When 100(%) has been configured in [Object space reservation] in the virtual machine storage policy used at the following timings, virtual disks created from VSAN datastores are configured with Thick Provisioning attributes.
- Creation of L-Servers
- Attachment of virtual disks to L-Servers
When using a disk that has been created in advance as an L-Server, select [Disk resource].
When the following items are specified as search conditions, the list of the relevant disk resources that can be registered is displayed.
Select a virtual storage where there is a disk that has been created in advance.
Enter the size of the disk resource.
Enter the lowest value of the disk size to be searched as a number with up to one decimal place, in units of gigabytes. Check the [Minimum value] checkbox, and enter a value lower than the maximum value.
Enter the highest value of the disk size to be searched as a number with up to one decimal place, in units of gigabytes. Check the [Maximum value] checkbox, and enter a value higher than the minimum value.
Depending on the value of the second decimal place of the disk size, matching disks may not be able to be displayed in the result. For search conditions, specify a size allowing for errors.
Specify the name of the disk to be found.
Begins with
Specify when searching for disks whose names begin with the specified string.
Includes
Specify when searching for disks whose names include the specified string.
Select the disk resource which you want to register using the [Select] checkbox of the displayed disk resources, or select all registered disk resources by clicking the [Select all] button.
When using Thin Provisioning or Automatic Storage Layering, the displayed resources that can be registered differ depending on whether Thin Provisioning attributes of storage pools are configured or not.
For details on resources which can be registered, refer to "10.1.1 Allocating Storage" in the "Design Guide CE".
Click the [OK] button.
The storage resource is registered.
Note
When using a LUN that has been created in advance and a LUN for iSCSI boot as a disk resource, if the L-Server is deleted or disks are deleted from L-Servers, the content of disks will remain (is not deleted).
When using disk resources that are registered in global pools, perform operation carefully, as the disk resources can be allocated to any users.
When using a LUN that has been created in advance as a disk resource, it is recommended to operate the LUN in a local pool, and delete data on the disk during deletion of L-Servers or detachment of disks.
Use the following methods to delete the data on disks.
Using an OS, perform disk formatting while the L-Server is connected
Using a function of the storage, perform disk formatting (For ETERNUS)
Create a LUN again
