Solstice DiskSuite 4.2.1 Installation and Product Notes

Converting to Solstice DiskSuite 4.2.1

Depending on the operating level and version of Solstice DiskSuite you are running on your system, the upgrade procedure will vary.

If you are converting to Solstice DiskSuite 4.2.1, your system will fall into one of the following three categories:

SPARC or x86 systems running Solaris 2.3 or Solaris 2.4 with Online: DiskSuite 2.0 or Online: DiskSuite 3.0
SPARC systems running Solaris 2.5, Solaris 2.5.1, or Solaris 2.6 with Solstice DiskSuite 4.0 or 4.1
x86 systems running Solaris 2.5, Solaris 2.5.1, Solaris 2.6, or Solaris 7 with Solstice DiskSuite 4.0, 4.1, or 4.2

The following subsections provide instructions for upgrading systems in each category to Solstice DiskSuite 4.2.1.

How to Convert to DiskSuite 4.2.1 on Systems Running Solaris 2.3 or Solaris 2.4 With Online: DiskSuite 2.0 or Online: DiskSuite 3.0

You must first upgrade your system to Solstice DiskSuite 4.0 and Solaris 2.5, using the instructions in the DiskSuite 4.0 Installation notes. Then you can use the instructions in the following subsections to upgrade to Solstice DiskSuite 4.2.1. Follow the upgrade procedure in the Solaris 2.5 and Solstice DiskSuite 4.0 product notes.

How to Convert to DiskSuite 4.2.1 on SPARC Systems Running DiskSuite 4.0, 4.1, or 4.2

The procedure in this section only works for customers who have SPARC machines running Solstice DiskSuite 4.0, 4.1 or 4.2 on Solaris 2.5, 2.5.1, 2.6, or Solaris 7 and upgrading to Solaris 8.

Caution -

Before you begin this procedure, back up all file systems. See the ufsdump(1M) man page for details.

Repair any mirrors that have errors.

Save the metadb configuration, the metadevice configuration, the device bindings, and /etc/vfstab on a remote or a floppy disk.

One or more of these files can be overwritten when you reboot the machine, upgrade the operating system, or install the new version of DiskSuite. Here are some example commands that save the metadb configuration, the metadevice configuration, and /etc/vfstab on a local floppy disk:

# /usr/sbin/metadb > /dev/fd/metadb.cfg
# /usr/sbin/metastat -p > /dev/fd/metadevice.cfg
# cp /etc/vfstab /dev/fd/meta_vfstab
# ls -l /dev/rdsk/*s0 > /dev/fd/binding
# cp /etc/path_to_inst /dev/fd/path_to_inst

The following example commands save the metadb configuration, the metadevice configuration, and the /etc/vfstab to another machine called other_machine on the network connected to the system being upgraded:

# /usr/sbin/metadb -i > /net/other_machine/save/metadb.cfg
# /usr/sbin/metastat -p > /net/other_machine/save/metadevice.cfg
# cp /etc/vfstab /net/other_machine/save/meta_vfstab
# ls -l /dev/rdsk/*s0 > /net/other_machine/save/bindings
# cp /etc/path_to_inst /net/other_machine/dev/fd/path_to_inst

Caution -

Make sure you save the metadb configuration, metadevice configuration and /etc/vfstab before going on to the next step in this procedure. Inability to restore any of them after the upgrade will result in data loss, and can result in complete system failure.

Clear any trans metadevices that may be used during the Solaris upgrade (for example, /usr, /var, and /opt).

See Solstice DiskSuite 4.2.1 User's Guide for information on clearing (removing logging from) trans metadevices. If you are uncertain which trans metadevices should be cleared, clear all trans metadevices.

In /etc/vfstab comment out file systems mounted on metadevices that are not simple metadevices or simple mirrors.

A simple metadevice is composed of a single component with a Start Block of 0. A simple mirror is composed of submirrors, all of which are simple metadevices.

Convert the remaining (simple) mirrors to one-way mirrors with the metadetach command.

Upgrade will be performed on a single submirror of each mirror. The other submirrors will be synced up with metattach after the upgrade.

If root (/) is mounted on a metadevice or mirror, set the root file system to be mounted on the underlying component of the metadevice or the underlying component of the remaining attached submirror.

Use the metaroot command to do this safely.

Edit the /etc/vfstab file to change any file systems or swap devices still mounted on metadevices or mirrors after Step 3.

Mount the file systems on the underlying component of the metadevices or the underlying component of the remaining attached submirrors.

Remove symbolic links to the DiskSuite startup file so that it is no longer initialized at boot time.
# rm /etc/rcS.d/S35lvm.init /etc/rc2.d/S95lvm.sync
These links will be added back later by reinstalling DiskSuite after the Solaris upgrade.

Halt the machine and upgrade to the Solaris 8 operating environment, then reboot the machine.

Caution -
Make sure you upgrade the correct slice. On machines with mirrored root file systems, the Solaris installation software displays all slices used in the root mirror as available for upgrade. Choose the slice that the system boots from. The section, "How to Find the System Boot Slice When Upgrading the Solaris Operating System", explains how to locate the boot slice.

Note -
If you have unbundled software running on your system, refer to the product documentation for any information about upgrading before upgrading to Solaris 8 operating environment and Solstice DiskSuite 4.2.1.

Install the Solstice DiskSuite 4.2.1 software using the instructions in "Initial Installation of Solstice DiskSuite" of this document.

This will re-establish the symbolic links removed in Step 8.

If root (/) was originally mounted on a metadevice or mirror, set the root (/) file system to be mounted back on the original metadevice or mirror.

Use the metaroot command to do this safely.

Edit the /etc/vfstab file to change any file systems or swap devices edited in Step 7 to be mounted back on their original metadevice or mirror.

Edit the /etc/vfstab file to uncomment the file systems commented out in Step 4.

Reboot the machine to remount the file systems.

Use the metattach command to reattach and resync any submirrors detached in Step 5.

Recreate the cleared trans metadevices. See Solstice DiskSuite 4.2.1 User's Guide for information on creating trans metadevices.

How to Convert to DiskSuite 4.2.1 and Solaris 8 on x86 Systems Running Solaris 2.5 or 2.5.1 and DiskSuite 4.0 or 4.1

The procedure in this section only works for customers who have x86 machines running Solstice DiskSuite 4.0 or 4.1 on Solaris 2.5 or Solaris 2.5.1 and are upgrading to Solaris 8.

Caution -

Before you begin this procedure, back up all file systems. See the ufsdump(1M) man page for details.

Repair any mirrors that have errors.

Save the metadb configuration, the metadevice configuration, the device bindings, and /etc/vfstab on a remote or a floppy disk.

# /usr/sbin/metadb > /dev/fd/metadb.cfg
# /usr/sbin/metastat -p > /dev/fd/metadevice.cfg
# cp /etc/vfstab /dev/fd/meta_vfstab
# ls -l /dev/rdsk/*s0 > /dev/fd/binding
# cp /etc/path_to_inst /dev/fd/path_to_inst

# /usr/sbin/metadb -i > /net/other_machine/save/metadb.cfg
# /usr/sbin/metastat -p > /net/other_machine/save/metadevice.cfg
# cp /etc/vfstab /net/other_machine/save/meta_vfstab
# ls -l /dev/rdsk/*s0 > /net/other_machine/save/bindings
# cp /etc/path_to_inst /net/other_machine/dev/fd/path_to_inst

Caution -

Clear any trans metadevices that may be used during the Solaris upgrade (for example, /usr, /var, and /opt).

See Solstice DiskSuite 4.2.1 User's Guide for information on clearing (removing logging from) trans metadevices. If you are uncertain which trans metadevices should be cleared, clear all trans metadevices.

In /etc/vfstab comment out file systems mounted on metadevices that are not simple metadevices or simple mirrors.

A simple metadevice is composed of a single component with a Start Block of 0. A simple mirror is composed of submirrors, all of which are simple metadevices.

Convert the remaining (simple) mirrors to one-way mirrors with the metadetach command.

Upgrade will be performed on a single submirror of each mirror. The other submirrors will be synced up with metattach after the upgrade.

If root (/) is mounted on a metadevice or mirror, set the root file system to be mounted on the underlying component of the metadevice or the underlying component of the remaining attached submirror.

Use the metaroot command to do this safely.

Edit the /etc/vfstab file to change any file systems or swap devices still mounted on metadevices or mirrors after Step 3.

Mount the file systems on the underlying component of the metadevices or the underlying component of the remaining attached submirrors.

Remove symbolic links to the DiskSuite startup files so that it is no longer initialized at boot time.
# rm /etc/rcS.d/S35lvm.init /etc/rc2.d/S95lvm.sync
These links will be added back later by reinstalling DiskSuite after the Solaris upgrade.

Halt the machine and upgrade to Solaris 8, then reboot the machine.

Caution -
Make sure you upgrade the correct slice. On machines with mirrored root file systems, the Solaris installation software displays all slices used in the root mirror as available for upgrade. Choose the slice that the system boots from. The section, "How to Find the System Boot Slice When Upgrading the Solaris Operating System", explains how to locate the boot slice.

Install the Solstice DiskSuite 4.2.1 software using the instructions in the "Initial Installation of Solstice DiskSuite" section of this document.

This will re-establish the symbolic links removed in Step 8.

If root (/) was originally mounted on a metadevice or mirror, set the root (/) file system to be mounted back on the original metadevice or mirror.

Use the metaroot command to do this safely.

Edit the /etc/vfstab file to change any file systems or swap devices edited in Step 7 to be mounted back on their original metadevice or mirror.

Edit the /etc/vfstab file to uncomment the file systems commented out in Step 4.

Reboot the machine to remount the file systems.

Use the metattach command to reattach and resync any submirrors detached in Step 5.

Recreate the cleared trans metadevices. See Solstice DiskSuite 4.2.1 User's Guide for information on creating trans metadevices.

How to Convert to DiskSuite 4.2.1 and Solaris 8 on x86 Systems Running Solaris 2.5, 2.5.1, 2.6, or 7 and DiskSuite 4.0 or 4.1

If you are running Solaris 2.5, Solaris 2.5.1, Solaris 2.6, or Solaris 7 on an x86 machine using Solstice DiskSuite 4.0 or 4.1, use the following procedure to upgrade to Solaris 8 and DiskSuite 4.2.1.

Run the metacvt(1M) command included with the DiskSuite 4.2.1 software distribution. The metacvt command is located in the /tools subdirectory on the CD. Make sure you save the S94SUNmd.cvt output.

Refer to the metacvt man page for detailed instruction on how to use this command and a list of actions the command performs.

Caution -
The metacvt command generates a script called S94SUNWmd.cvt. Make sure you save this script in a location that will not be overwritten during the software upgrade.

Reboot the system and upgrade the operating system to the new version.

If a mirrored system partition must be resized to accommodate the new system files, resize each submirror that mirrors the partition to match the partition's new size.

Caution -
Do not perform an initial installation. An initial installation will reformat the system disks and destroy the data on them. It may also change the disk device bindings and invalidate the metadevice configuration saved in the S94SUNmd.cvt output.

Caution -
Make sure you upgrade the correct slice. On machines with mirrored root file systems, the Solaris installation software displays all slices used in the root mirror as available for upgrade. Choose the slice that the system boots from. The section, "How to Find the System Boot Slice When Upgrading the Solaris Operating System", explains how to locate the boot slice.

Remove all the old Solstice DiskSuite packages that may reside on the system.

Install the Solstice DiskSuite 4.2.1 software using the instructions in the "Initial Installation of Solstice DiskSuite".

Run the S94SUNmd.cvt script.

Refer to the S94SUNmd.cvt(1M) man page for additional information on the script.

Reboot the system.