Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Cluster Upgrade Guide Oracle Solaris Cluster |
1. Preparing to Upgrade Oracle Solaris Cluster Software
2. Performing a Standard Upgrade to Oracle Solaris Cluster 3.3 5/11 Software
3. Performing a Dual-Partition Upgrade to Oracle Solaris Cluster 3.3 5/11 Software
4. Performing a Live Upgrade to Oracle Solaris Cluster 3.3 5/11 Software
5. Performing a Rolling 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
This section provides information to recover from incomplete upgrades of an Oracle Solaris Cluster configuration.
If you experience an unrecoverable error during dual-partition upgrade, perform this procedure to back out of the upgrade.
Note - You cannot restart a dual-partition upgrade after the upgrade has experienced an unrecoverable error.
ok boot -x
The GRUB menu appears similar to the following:
GNU GRUB version 0.97 (639K lower / 1047488K upper memory) +----------------------------------------------------------------------+ | Solaris 10 /sol_10_x86 | | Solaris failsafe | | | +----------------------------------------------------------------------+ Use the ^ and v keys to select which entry is highlighted. Press enter to boot the selected OS, 'e' to edit the commands before booting, or 'c' for a command-line.
For more information about GRUB based booting, see Booting an x86 Based System by Using GRUB (Task Map) in System Administration Guide: Basic Administration.
The GRUB boot parameters screen appears similar to the following:
GNU GRUB version 0.97 (639K lower / 1047488K upper memory) +----------------------------------------------------------------------+ | root (hd0,0,a) | | kernel /platform/i86pc/multiboot | | module /platform/i86pc/boot_archive | |+----------------------------------------------------------------------+ Use the ^ and v keys to select which entry is highlighted. Press 'b' to boot, 'e' to edit the selected command in the boot sequence, 'c' for a command-line, 'o' to open a new line after ('O' for before) the selected line, 'd' to remove the selected line, or escape to go back to the main menu.
[ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename. ESC at any time exits. ] grub edit> kernel /platform/i86pc/multiboot -x
The screen displays the edited command.
GNU GRUB version 0.97 (639K lower / 1047488K upper memory) +----------------------------------------------------------------------+ | root (hd0,0,a) | | kernel /platform/i86pc/multiboot -x | | module /platform/i86pc/boot_archive | +----------------------------------------------------------------------+ Use the ^ and v keys to select which entry is highlighted. Press 'b' to boot, 'e' to edit the selected command in the boot sequence, 'c' for a command-line, 'o' to open a new line after ('O' for before) the selected line, 'd' to remove the selected line, or escape to go back to the main menu.-
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.
You can alternatively run the scinstall command from the /usr/cluster/bin directory.
phys-schost# cd /cdrom/cdrom0/Solaris_arch/Product/sun_cluster/Solaris_ver/Tools phys-schost# ./scinstall -u recover
Specifies upgrade.
Restores the /etc/vfstab file and the Cluster Configuration Repository (CCR) database to their original state before the start of the dual-partition upgrade.
The recovery process leaves the cluster nodes in noncluster mode. Do not attempt to reboot the nodes into cluster mode.
For more information, see the scinstall(1M) man page.
This method requires that all cluster nodes remain in noncluster mode during the upgrade. See the task map for standard upgrade, Table 2-1. You can resume the upgrade at the last task or step in the standard upgrade procedures that you successfully completed before the dual-partition upgrade failed.
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 superuser.
The GRUB menu appears similar to the following:
GNU GRUB version 0.95 (631K lower / 2095488K upper memory) +-------------------------------------------------------------------------+ | Solaris 10 /sol_10_x86 | | Solaris failsafe | | | +-------------------------------------------------------------------------+ Use the ^ and v keys to select which entry is highlighted. Press enter to boot the selected OS, 'e' to edit the commands before booting, or 'c' for a command-line.
For more information about GRUB-based booting, see Booting an x86 Based System by Using GRUB (Task Map) in System Administration Guide: Basic Administration.
The GRUB boot parameters screen appears similar to the following:
GNU GRUB version 0.95 (615K lower / 2095552K upper memory) +----------------------------------------------------------------------+ | root (hd0,0,a) | | kernel /platform/i86pc/multiboot | | module /platform/i86pc/boot_archive | +----------------------------------------------------------------------+ Use the ^ and v keys to select which entry is highlighted. Press 'b' to boot, 'e' to edit the selected command in the boot sequence, 'c' for a command-line, 'o' to open a new line after ('O' for before) the selected line, 'd' to remove the selected line, or escape to go back to the main menu.
Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename. ESC at any time exits.
phys-schost# grub edit> kernel /platform/i86pc/multiboot -x
The screen displays the edited command.
GNU GRUB version 0.95 (615K lower / 2095552K upper memory) +----------------------------------------------------------------------+ | root (hd0,0,a) | | kernel /platform/i86pc/multiboot -x | | module /platform/i86pc/boot_archive | +----------------------------------------------------------------------+ Use the ^ and v keys to select which entry is highlighted. Press 'b' to boot, 'e' to edit the selected command in the boot sequence, 'c' for a command-line, 'o' to open a new line after ('O' for before) the selected line, 'd' to remove the selected line, or escape to go back to the main menu.-
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 to add the -x option to the kernel boot parameter command.
phys-schost# /usr/cluster/bin/scinstall -u recover
The command restores the original CCR information, restores the original /etc/vfstab file, and eliminates modifications for startup.
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.
phys-schost# shutdown -g0 -y -i6
The nodes rejoin the cluster.