Skip to main content

Solaris 10 Live upgrade steps

 Steps for Solaris 10 Live Upgrade
 Solaris Live Upgrade significantly reduces downtime caused by an operating system upgrade
 by allowing the system administrator to upgrade the operating system, or install a Flash
 Archive, while the system is in operation. The Live Upgrade process involves creating a dupli-
 cate of the running environment and upgrading that duplicate. The current running environ-
 ment remains untouched and unaffected by the upgrade....

Prepare the disk slice and partition for live upgrade:
disk 1 Partition:
c0d0s0    /
c0d0s1    swap
c0d0s2    backup
disk 2 partition:
c0d1s0    /(i'll use it to copy root)
the partition on second disk (/copy root) is same size as the root (/) partition and it must not appear in use in “/etc/vfstab”.
This example explains how to upgrade a Solaris 10 10/08 system to the Solaris 10 5/09 release. Solaris Live Upgrade has many capabilities but for a simple situation like upgrading a system to a new Solaris release, there are three commands:
lucreate :-to create the copy
luupgrade:- to upgrade the OS on the copy
luactivate :- to choose the environment to boot

Before upgrading, you must install the Solaris Live Upgrade packages from the release to which you are upgrading. New capabilities are added to the upgrade tools, so installing the new packages from the target release is important. In this example, you will upgrade from Solaris 10 3/05 to Solaris 10 1/06, so you must get the Solaris Live Upgrade packages from the Solaris 10 1/06 DVD.
1. Install Live Upgrade package.


bash-3.00# cd /cdrom/sol_10_509_x86/Solaris_10/Tools/Installers/
bash-3.00# ./liveupgrade20 -noconsole -nodisplay
2. Run the “lucreate” command to create a copy of the active boot environment.
bash-3.00# lucreate -c active_boot -n solarisnew -m /:c0d1s0:ufs
“solaris0ld” is the active environment
“solarisnew” is inactive boot environment
3. after the new boot environment is created, now begin the upgrade procedure:
bash-3.00# luupgrade -u -n solarisnew -s /cdrom/cdrom0
4. after finished on step 3, now time to activate the new environment.
bash-3.00# luactivate solarisnew
5. reboot
 thanks.........

Comments

Popular posts from this blog

Docker Container Management from Cockpit

Cockpit can manage containers via docker. This functionality is present in the Cockpit docker package. Cockpit communicates with docker via its API via the /var/run/docker.sock unix socket. The docker API is root equivalent, and on a properly configured system, only root can access the docker API. If the currently logged in user is not root then Cockpit will try to escalate the user’s privileges via Polkit or sudo before connecting to the socket. Alternatively, we can create a docker Unix group. Anyone in that docker group can then access the docker API, and gain root privileges on the system. [root@rhel8 ~] #  yum install cockpit-docker    -y  Once the package installed then "containers" section would be added in the dashboard and we can manage the containers and images from the console. We can search or pull an image from docker hub just by searching with the keyword like nginx centos.   Once the Image download...

Remote Systems Management With Cockpit

The cockpit is a Red Hat Enterprise Linux web-based interface designed for managing and monitoring your local system, as well as Linux servers located in your network environment. In RHEL 8 Cockpit is the default installation candidate we can just start the service and then can start the management of machines. For RHEL7 or Fedora based machines we can follow steps to install and configure the cockpit.  Following are the few features of cockpit.  Managing services Managing user accounts Managing and monitoring system services Configuring network interfaces and firewall Reviewing system logs Managing virtual machines Creating diagnostic reports Setting kernel dump configuration Configuring SELinux Updating software Managing system subscriptions Installation of cockpit package.  [root@rhel8 ~] #  dnf   install cockpit cockpit-dashboard  -y  We need to enable the socket.  [root@rhel8 ~] #  systemctl enable --n...

Add The Group Information IN Yum Repository in simple Two steps

= Yum groups and repositories = Yum supports the group commands   * grouplist   * groupinfo   * groupinstall   * groupremove   * groupupdate Groups are read from the "group" xml metadata that is optionally available from each repository. If yum has no repositories which support groups then none of  the group operations will work.  #yum grouplist    This will list the installed and available groups for your system in two    separate lists. If you pass the optional 'hidden' argument then all of     the groups which are set to 'no' in the group xml tag.   yum groupinfo groupname     This will give you detailed information for each group including:   description, mandatory, default and optional packages.       #yum groupinstall groupname      #yum groupupdate groupname   Despite their differing names both of these commands perform the same   func...