Go to main content

Oracle® Solaris Cluster 4.3 Upgrade Guide

Exit Print View

Updated: February 2017
 
 

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

Perform this procedure if a dual-partition upgrade fails and the state of the cluster meets all of the following criteria:

  • The nodes of the first partition are upgraded.

  • None of the nodes of the second partition are yet upgraded.

  • None of the nodes of the second partition are in cluster mode.

You can also perform this procedures if the upgrade has succeeded on the first partition but you want to back out of the upgrade.


Note -  Do not perform this procedure after dual-partition upgrade processes have begun on the second partition. Instead, perform How to Recover from a Failed Dual-Partition Upgrade.

Before You Begin

Before you begin, ensure that all second-partition nodes are halted. First-partition nodes can be either halted or running in noncluster mode.

Perform all steps as the root role.

  1. Boot each node in the second partition into noncluster mode by completing the following steps.
    • SPARC:
      ok boot -x
    • x86:
      1. In the GRUB menu, use the arrow keys to select the appropriate Oracle Solaris entry and type e to edit its commands.

        For more information about GRUB based booting, see Booting a System in Booting and Shutting Down Oracle Solaris 11.3 Systems.

      2. In the boot parameters screen, use the arrow keys to select the kernel entry and type e to edit the entry.
      3. Add -x to the multiboot command to specify that the system boot into noncluster mode.
      4. Press Enter to accept the change and return to the boot parameters screen.

        The screen displays the edited command.

      5. Type b to boot the node into noncluster mode.

        Note - This change to the kernel boot parameter command does not persist over the system boot. The next time you reboot the node, it will boot into cluster mode. To boot into noncluster mode instead, perform these steps to again add the –x option to the kernel boot parameter command.
  2. On each node in the second partition, run the scinstall -u recover command.
    phys-schost# scinstall -u recover

    The command restores the original CCR information, restores the original /etc/vfstab file, and eliminates modifications for startup.

  3. Boot each node of the second partition into cluster mode.
    phys-schost# shutdown -g0 -y -i6

    When the nodes of the second partition come up, the second partition resumes supporting cluster data services while running the old software with the original configuration.

  4. Restore the original software and configuration data from backup media to the nodes in the first partition.
  5. Boot each node in the first partition into cluster mode.
    phys-schost# shutdown -g0 -y -i6

    The nodes rejoin the cluster.