JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris Cluster Upgrade Guide     Oracle Solaris Cluster 3.3 3/13
search filter icon
search icon

Document Information

Preface

1.  Preparing to Upgrade Oracle Solaris Cluster Software

2.  Performing a Standard Upgrade to Oracle Solaris Cluster 3.3 3/13 Software

3.  Performing a Dual-Partition Upgrade to Oracle Solaris Cluster 3.3 3/13 Software

4.  Performing a Live Upgrade to Oracle Solaris Cluster 3.3 3/13 Software

5.  Performing a Rolling Upgrade

6.  Completing the Upgrade

7.  Recovering From an Incomplete Upgrade

Cluster Recovery After an Incomplete Upgrade

How to Recover from a Failed Dual-Partition Upgrade

x86: How to Recover From a Partially Completed Dual-Partition Upgrade

Recovering From Storage Configuration Changes During Upgrade

How to Handle Storage Reconfiguration During an Upgrade

How to Resolve Mistaken Storage Changes During an Upgrade

Index

Recovering From Storage Configuration Changes During Upgrade

This section provides the following repair procedures to follow if changes were inadvertently made to the storage configuration during upgrade:

How to Handle Storage Reconfiguration During an Upgrade

Any changes to the storage topology, including running Oracle Solaris Cluster commands, should be completed before you upgrade the cluster to Oracle Solaris 10 software. If, however, changes were made to the storage topology during the upgrade, perform the following procedure. This procedure ensures that the new storage configuration is correct and that existing storage that was not reconfigured is not mistakenly altered.

Before You Begin

Ensure that the storage topology is correct. Check whether the devices that were flagged as possibly being replaced map to devices that actually were replaced. If the devices were not replaced, check for and correct possible accidental configuration changes, such as incorrect cabling.

  1. On a node that is attached to the unverified device, become superuser.
  2. Manually update the unverified device.
    phys-schost# cldevice repair -n node[,…] device

    See the cldevice(1CL) man page for more information.

  3. Update the DID driver for the nodelist.
    phys-schost# cldevice refresh -n node[,…]
  4. Repeat Step 2 through Step 3 on all other nodes that are attached to the unverified device.

Next Steps

Return to the remaining upgrade tasks. Go to Step 4 in How to Upgrade Oracle Solaris Cluster 3.3 3/13 Software (Standard Upgrade).

How to Resolve Mistaken Storage Changes During an Upgrade

If accidental changes are made to the storage cabling during the upgrade, perform the following procedure to return the storage configuration to the correct state.


Note - This procedure assumes that no physical storage was actually changed. If physical or logical storage devices were changed or replaced, instead follow the procedures in How to Handle Storage Reconfiguration During an Upgrade.


Before You Begin

Return the storage topology to its original configuration. Check the configuration of the devices that were flagged as possibly being replaced, including the cabling.

  1. On each node of the cluster, become superuser.
  2. Update the DID driver on each node of the cluster.
    phys-schost# cldevice refresh -n node[,…]

    See the cldevice(1CL) man page for more information.

  3. If the cldevice command returned any error messages in Step 2, make further modifications as needed to correct the storage configuration, then repeat Step 2.

Next Steps

Return to the remaining upgrade tasks. Go to Step 4 in How to Upgrade Oracle Solaris Cluster 3.3 3/13 Software (Standard Upgrade).