This section explains the preparations for setting up storage.
Supported Storage Configurations
The supported storage configurations are as follow:
LUNs managed by ETERNUS
Preparations for Storage Environments [Solaris Zones (Solaris 11)]
Create a zfs storage pool in the global zone.
In order to use zfs storage pools in Resource Orchestrator, it is necessary to configure thin provisioning.
Register virtual storage resources in a storage pool with Thin Provisioning attributes set to allocate them as the thin formatted disk resources to an L-Server.
zfs storage pools cannot be registered as virtual storage resources in a storage pool without thin provisioning attributes set.
Thick format disk resources cannot be created from virtual storage resources.
For how to set thin provisioning attributes for a storage pool, refer to "20.2 Creating" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
For details on the display of storage capacity and the calculation method for the free space of storage pools, refer to "20.6 Viewing" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Preparations for Storage Environments [Solaris Zones (Solaris 10)]
When using disks in non-global zones, prepare a LUN for each non-global zone.
Mount a LUN for each zone path of a non-global zone.
Configure a non-global zone in the mounted LUN.
Configure /etc/vfstab so that LUNs corresponding to the zone paths used by virtual L-Servers will be mounted.
For the zone path used by the virtual L-Server, provide only the owner of the directory with read, write, and execution permissions (700).
The storage affinity switchover method can be used as a server switchover function.
For details on how to configure the server switchover, refer to "8.1.6 Settings when Switching Over SPARC M10/M12 or SPARC Enterprise Servers".
For details on the function, refer to "Chapter 4 Server Switchover" in the "Operation Guide VE".
Only the server switchover function or the migration function can be used.
Perform design of the configuration based on the function that you will be using.
When using the server switchover function, the following configurations are necessary:
Design the area used for the non-global zone so that it can be referred to in the same way both before and after switchover.
Use the switchover SAN area for server switchover.
When using the server switchover function, non-global zones are not automatically started.
Perform configuration so that non-global zones are automatically started when global zones are started after server switchover.
When using the migration function, or [Relocate at startup] has been configured for the L-Server boot location, the following configurations are necessary.
Perform configuration so that LUNs corresponding to the zone paths used by virtual L-Servers will not be automatically mounted.
When using the migration function of this product, unmount the disk that is the migration source, and then mount the disk that is the migration destination. At this time, the zone paths defined in the disk resource and the /etc/vfstab mount settings for the zone paths are used for migration.
Therefore, perform connection and setting so the disk on which a non-global zone is to be created can be mounted on both the migration source and destination.
However, do not mount it in a location other than the global zone where the non-global zone operates.
Note
Do not execute the mounting of LUNs in other global zones when the LUN is shared from two or more global zones and the LUN corresponds to the zone path that a virtual L-Server uses. There is a possibility that the data of the LUN will be damaged due to an access conflict when a virtual L-Server that uses this LUN is created.
