How to use live-upgrade with single disk, pre-patching steps? Post: 303033223

Sponsored Content

Operating Systems Solaris How to use live-upgrade with single disk, pre-patching steps? Post 303033223 by solaris_1977 on Monday 1st of April 2019 08:14:23 PM

04-01-2019

Registered User

How to use live-upgrade with single disk, pre-patching steps?

Hi,

I have Solaris-10 x86 (running on HP hardware), with 12 non-global zones running on this. I have to install latest patch cluster/set on this server. This server is not under backup schedule, so before installing patch cluster, I want to keep a backup. In case of any issue (bad patch or application break), I should be able to revert back to pre-patching status.
Now challenge is, due to hardware RAID, I can see only one disk and one zpool. There is sufficient space.
I am get examples of create image on alternate disk or alternate pool. But how will I do it when I have single disk and single zpool ?
Suggest please.

Code:

# zpool list
NAME    SIZE  ALLOC   FREE    CAP  HEALTH  ALTROOT
rpool  1.81T  84.1G  1.73T     4%  ONLINE  -
# echo|format
Searching for disks...done


AVAILABLE DISK SELECTIONS:
       0. c0t0d0 <DEFAULT cyl 60794 alt 2 hd 255 sec 252>
          /pci@0,0/pci8086,3408@1/pci103c,3245@0/sd@0,0
Specify disk (enter its number): Specify disk (enter its number):
#

Thanks

solaris_1977

View Public Profile for solaris_1977

Find all posts by solaris_1977

7 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Typical steps to be followed while applying an application patch upgrade on linux

what are the typical steps used by system adminstrators while applying an application patch upgrade

2. Solaris

Live Upgrade Patching Error: Unable to write vtoc

Attempting to patch several servers using live upgrade Release: Oracle Solaris 10 8/11 s10x_u10wos_17b X86 Error I'm receiving is in the message in the log below tail -15 /var/svc/log/rc6.log Legacy init script "/etc/rc0.d/K50pppd" exited with return code 0. Executing legacy init...

3. Solaris

Help me with Pre Installation Steps for Patching on Solaris Servers

What are the Pre-installation steps for patching on Solaris servers in real time ? :confused:

4. Solaris

Solaris patching issue with Live Upgrade

I have Solaris-10 sparc box with ZFS file-system, which is running two non global zones. I am in process of applying Solaris Recommended patch cluster via Live Upgrade. Though I have enough space in root file-system of both zones, everytime I run installcluster, it fails with complaining less...

5. Solaris

Live upgrade first steps

Hello Guys, I am a little confused about the first step in the live upgrade process. I will be glad if someone can clarify this for me. The pre-live upgrade patch, when do you add this patch to the OS you want to upgrade? 1. before creating the new boot environment? or 2. after creating...

6. Solaris

Solaris 10 patching using live upgrade with VxVM

Hello, I was assigned some Solaris machines and need to patch them to N-1, where N is the latest OS realease, which means, upgrade till one version before the latest one. I do not now a lot about Solaris. What I only know is that need to make use of live upgrade and be careful with VxVM...

7. Solaris

Patching using live upgrade - with non-globalzone

Hi all, I would like to ask what will be the best practice for the following setup / - c0t0d0s0 - current BE (named First) / - c0t0d1s0 - alternate BE (name Second) i have a non-global zone with zonepath in /zones/myzone /mnt/opt - c0t0d2s6 (shared between the 2 BE)...

LEARN ABOUT DEBIAN

mkqdisk

mkqdisk(8)						      Quorum Disk Management							mkqdisk(8)

NAME

       mkqdisk - Cluster Quorum Disk Utility

WARNING

       Use of this command can cause the cluster to malfunction.

SYNOPSIS

       mkqdisk [-?|-h] | [-L] | [-f label] [-c device  -l label] [-d [-d ...]]

DESCRIPTION

       The mkqdisk command is used to create a new quorum disk or display existing quorum disks accessible from a given cluster node.

OPTIONS

       -c device -l label
	      Initialize  a new cluster quorum disk.  This will destroy all data on the given device.  If a cluster is currently using that device
	      as a quorum disk, the entire cluster will malfunction.  Do not run this on an active cluster  when  qdiskd  is  running.	 Only  one
	      device  on  the  SAN should ever have the given label; using multiple different devices is currently not supported (it is expected a
	      RAID array is used for quorum disk redundancy).  The label can be any textual string up to 127 characters - and is therefore  enough
	      space to hold a UUID created with uuidgen(1).

       -f label
	      Find the cluster quorum disk with the given label and display information about it.

       -L     Display information on all accessible cluster quorum disks.

       -d     Increase debugging level.  Specify multiple times for more information.  Currently, specifying more than twice has no effect.

SEE ALSO

       qdisk(5), qdiskd(8), uuidgen(1)

								     July 2006								mkqdisk(8)