This section describes how to create VxVM disk groups in a cluster. The following table describes the types of VxVM disk groups you can configure in a Sun Cluster configuration and their characteristics.
Disk Group Type |
Use |
Registered with Sun Cluster? |
Storage Requirement |
---|---|---|---|
VxVM disk group |
Device groups for failover or scalable data services, global devices, or cluster file systems |
Yes |
Shared storage |
Local VxVM disk group |
Applications that are not highly available and are confined to a single node |
No |
Shared or unshared storage |
VxVM shared disk group |
Oracle Real Application Clusters (also requires the VxVM cluster feature) |
No |
Shared storage |
The following table lists the tasks to perform to create VxVM disk groups in a Sun Cluster configuration. complete the procedures in the order that is indicated.
Table 5–2 Task Map: Creating VxVM Disk Groups
Task |
Instructions |
---|---|
Create disk groups and volumes. | |
Register as Sun Cluster device groups those disk groups that are not local and that do not use the VxVM cluster feature. | |
If necessary, resolve any minor-number conflicts between device groups by assigning a new minor number. | |
Verify the disk groups and volumes. |
Use this procedure to create your VxVM disk groups and volumes.
Perform this procedure from a node that is physically connected to the disks that make the disk group that you add.
Perform the following tasks:
Make mappings of your storage disk drives. See the appropriate manual in the Sun Cluster Hardware Administration Collection to perform an initial installation of your storage device.
Complete the following configuration planning worksheets.
See Planning Volume Management for planning guidelines.
If you did not create root disk groups, ensure that you have rebooted each node on which you installed VxVM, as instructed in Step 12 of How to Install Veritas Volume Manager Software.
Become superuser on the node that will own the disk group.
Create the VxVM disk groups and volumes.
Observe the following special instructions:
SPARC: If you are installing Oracle Real Application Clusters, create shared VxVM disk groups by using the cluster feature of VxVM. Observe guidelines and instructions in How to Create a VxVM Shared-Disk Group for the Oracle RAC Database in Sun Cluster Data Service for Oracle RAC Guide for Solaris OS and in the Veritas Volume Manager Administrator's Reference Guide.
Otherwise, create VxVM disk groups by using the standard procedures that are documented in the VxVM documentation.
You can use Dirty Region Logging (DRL) to decrease volume recovery time if a node failure occurs. However, DRL might decrease I/O throughput.
For local disk groups, set the localonly property and add a single node to the disk group's node list.
A disk group that is configured to be local only is not highly available or globally accessible.
Start the clsetup utility.
phys-schost# clsetup |
Choose the menu item, Device groups and volumes.
Choose the menu item, Set localonly on a VxVM disk group.
Follow the instructions to set the localonly property and to specify the single node that will exclusively master the disk group.
Only one node at any time is permitted to master the disk group. You can later change which node is the configured master.
When finished, quit the clsetup utility.
Determine your next step:
SPARC: If the VxVM cluster feature is enabled, go to How to Verify the Disk Group Configuration.
If you created disk groups that are not local and the VxVM cluster feature is not enabled, register the disk groups as Sun Cluster device groups. Go to How to Register a Disk Group.
If you created only local disk groups, go to How to Verify the Disk Group Configuration.
If the VxVM cluster feature is not enabled, perform this procedure to register disk groups that are not local as Sun Cluster device groups.
SPARC: If the VxVM cluster feature is enabled or you created a local disk group, do not perform this procedure. Instead, proceed to How to Verify the Disk Group Configuration.
Become superuser on a node of the cluster.
Register the global disk group as a Sun Cluster device group.
Start the clsetup utility.
phys-schost# clsetup |
Choose the menu item, Device groups and volumes.
Choose the menu item, Register a VxVM disk group.
Follow the instructions to specify the VxVM disk group that you want to register as a Sun Cluster device group.
When finished, quit the clsetup utility.
Deport and re-import each local disk group.
phys-schost# vxdg deport diskgroup # vxdg import dg |
Restart each local disk group.
phys-schost# vxvol -g diskgroup startall |
Verify the local-only status of each local disk group.
If the value of the flags property of the disk group is nogdl, the disk group is correctly configured for local-only access.
phys-schost# vxdg list diskgroup | grep flags flags: nogdl |
Verify that the device group is registered.
Look for the disk device information for the new disk that is displayed by the following command.
phys-schost# cldevicegroup status |
Go to How to Verify the Disk Group Configuration.
Stack overflow – If a stack overflows when the device group is brought online, the default value of the thread stack size might be insufficient. On each node, add the entry set cl_haci:rm_thread_stacksize=0xsize to the /etc/system file, where size is a number greater than 8000, which is the default setting.
Configuration changes – If you change any configuration information for a VxVM device group or its volumes, you must register the configuration changes by using the clsetup utility. Configuration changes that you must register include adding or removing volumes and changing the group, owner, or permissions of existing volumes. See Administering Device Groups in Sun Cluster System Administration Guide for Solaris OS for procedures to register configuration changes that are made to a VxVM device group.
If device group registration fails because of a minor-number conflict with another disk group, you must assign the new disk group a new, unused minor number. Perform this procedure to reminor a disk group.
Become superuser on a node of the cluster.
Determine the minor numbers in use.
phys-schost# ls -l /global/.devices/node@1/dev/vx/dsk/* |
Choose any other multiple of 1000 that is not in use to become the base minor number for the new disk group.
Assign the new base minor number to the disk group.
phys-schost# vxdg reminor diskgroup base-minor-number |
This example uses the minor numbers 16000-16002 and 4000-4001. The vxdg reminor command reminors the new device group to use the base minor number 5000.
phys-schost# ls -l /global/.devices/node@1/dev/vx/dsk/* /global/.devices/node@1/dev/vx/dsk/dg1 brw------- 1 root root 56,16000 Oct 7 11:32 dg1v1 brw------- 1 root root 56,16001 Oct 7 11:32 dg1v2 brw------- 1 root root 56,16002 Oct 7 11:32 dg1v3 /global/.devices/node@1/dev/vx/dsk/dg2 brw------- 1 root root 56,4000 Oct 7 11:32 dg2v1 brw------- 1 root root 56,4001 Oct 7 11:32 dg2v2 phys-schost# vxdg reminor dg3 5000 |
Register the disk group as a Sun Cluster device group. Go to How to Register a Disk Group.
Perform this procedure on each node of the cluster.
Become superuser.
List the disk groups.
phys-schost# vxdisk list |
List the device groups.
phys-schost# cldevicegroup list -v |
Verify that all disk groups are correctly configured.
Ensure that the following requirements are met:
The root disk group includes only local disks.
All disk groups and any local disk groups are imported on the current primary node only.
Verify that all volumes have been started.
phys-schost# vxprint |
Verify that all disk groups have been registered as Sun Cluster device groups and are online.
phys-schost# cldevicegroup status |
Output should not display any local disk groups.
(Optional) Capture the disk partitioning information for future reference.
phys-schost# prtvtoc /dev/rdsk/cNtXdYsZ > filename |
Store the file in a location outside the cluster. If you make any disk configuration changes, run this command again to capture the changed configuration. If a disk fails and needs replacement, you can use this information to restore the disk partition configuration. For more information, see the prtvtoc(1M) man page.
(Optional) Make a backup of your cluster configuration.
An archived backup of your cluster configuration facilitates easier recovery of the your cluster configuration. For more information, see How to Back Up the Cluster Configuration in Sun Cluster System Administration Guide for Solaris OS.
Observe the following guidelines for administering VxVM disk groups in a Sun Cluster configuration:
VxVM device groups – VxVM disk groups that have been registered as device groups are managed by Sun Cluster software. After a disk group is registered as a device group, you should never import or deport that VxVM disk group by using VxVM commands. The Sun Cluster software can handle all cases where device groups need to be imported or deported. See Administering Device Groups in Sun Cluster System Administration Guide for Solaris OS for procedures about how to manage device groups.
Local disk groups – Local VxVM disk groups are not managed by Sun Cluster software. Use VxVM commands to administer local disk groups as you would in a nonclustered system.
If the output of the cldevicegroup status command includes any local disk groups, the displayed disk groups are not configured correctly for local-only access. Return to How to Create a Disk Group to reconfigure the local disk group.
Determine from the following list the next task to perform that applies to your cluster configuration. If you need to perform more than one task from this list, go to the first of those tasks in this list.
To create cluster file systems, go to How to Create Cluster File Systems.
To create non-global zones on a node, go to How to Create a Non-Global Zone on a Global-Cluster Node.
SPARC: To configure Sun Management Center to monitor the cluster, go to SPARC: Installing the Sun Cluster Module for Sun Management Center.
Install third-party applications, register resource types, set up resource groups, and configure data services. See the documentation that is supplied with the application software and the Sun Cluster Data Services Planning and Administration Guide for Solaris OS.