Upgrading to Solaris Volume Manager

Solaris Volume Manager fully supports seamless upgrade from Solstice DiskSuite versions 4.1, 4.2, and 4.2.1. Make sure that all volumes are in Okay state (not “Needs Maintenance” or “Last Erred”) and that no hot spares are in use. You do not need to do anything else special to Solaris Volume Manager for the upgrade to work—it is not necessary to change the configuration or break down the root mirror. When you upgrade your system, the Solstice DiskSuite configuration will be brought forward and will be accessible after upgrade through Solaris Volume Manager tools.

The Solaris 10 OS introduced the Service Management Facility (SMF), which provides an infrastructure that augments the traditional UNIX start-up scripts, init run levels, and configuration files. When upgrading from a previous version of the Solaris OS, verify that the SMF services associated with Solaris Volume Manager are online. If the SMF services are not online, you might encounter problems when administering Solaris Volume Manager.

To check the SMF services associated with Solaris Volume Manager, use the following form of the svcs command:

# svcs -a |egrep "md|meta"
disabled       12:05:45 svc:/network/rpc/mdcomm:default
disabled       12:05:45 svc:/network/rpc/metamed:default
disabled       12:05:45 svc:/network/rpc/metamh:default
online         12:05:39 svc:/system/metainit:default
online         12:05:46 svc:/network/rpc/meta:default
online         12:05:48 svc:/system/fmd:default
online         12:05:51 svc:/system/mdmonitor:default

If the Solaris Volume Manager configuration consists of a local set only, then these services should be online:

svc:/system/metainit

svc:/network/rpc/meta

svc:/system/mdmonitor

If the Solaris Volume Manager configuration includes disk sets, then these additional services should be online:

svc:/network/rpc/metamed

svc:/network/rpc/metamh

If the Solaris Volume Manager includes multi-node disk sets, then this service should be online in addition to the other services already mentioned:

svc:/network/rpc/mdcomm

For more information on SMF, see Chapter 14, Managing Services (Overview), in System Administration Guide: Basic Administration.