Sponsored Content
Operating Systems Solaris Sun solaris 5.9 to 5.10 upgrade Post 302638545 by juan.brein on Thursday 10th of May 2012 11:28:10 AM
Old 05-10-2012
I always run Live Upgrade over physical devices, never did it over Metadevices , it should work as it is documented, but I think is kind of better to remove some extra layers in case you have to roll back / troubleshoot boot issues.

In this case you would have to break the mirror like this:

# metadetach d0 d20
# metaroot /dev/dsk/c1t0d0s0

At this point verify /etc/system and /etc/vfstab, the system has to boot from the /dev/dsk/c1t0d0s0, not from the /dev/md/dsk/d0

Reboot the system:
# init 6

Finish to remove the rest of the metadevices associated with the root filesystem:

# metaclear d20
# metaclear d0
# metaclear d10

Now you are ready to run the lucreate like this:

# lucreate -c sol9 -n sol10 -m /:/dev/dsk/c1t1d0s0:ufs

These extra steps will require an additional reboot as you can see... but since it is a Major upgrade I think it worth it.

One more thing, Live Upgrade will take some time and remember performance can be impacted during that time.

Another tip is, do not remove the sol9 environment until you are not sure everything is working perfectly... I would let the Database run for a couple of days and then recreate the mirror

Finally, backup backup backup, and roll back plan... documented just in case... is not a good idea to learn how to roll back when you realise the Database is not coming back.

Talking about DB, make sure the DB version u use is supported by Solaris 10, most of then they do... but you never know.

Any question let me know

Good luck
 

6 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Memory upgrade Sun Blade 150

I would like to upgrade the memory in my Sun Blade 150 workstation. In reading through Sun's Blade 150 DIMM Installation Guide, it indicates that the memory must be "certified by Sun for the Sun Blade 150 system." Does anyone know if any SDRAM, PC133 • CL=2 • Unbuffered • ECC • 133MHz • 3.3V ... (2 Replies)
Discussion started by: here2learn
2 Replies

2. Solaris

Sun Blade 100 Memory Upgrade

Hi, I've been a member for a while but have never posted. I have a Sun Blade 100 desktop and I just installed Solaris 10 and it is unbearably slow. I only have 128 Meg of RAM and need to upgrade. I have searched and found many online resources that have RAM, but I was wondering if anyone has... (12 Replies)
Discussion started by: BrewDudeBob
12 Replies

3. Solaris

Solaris 9 to Solaris 10 upgrade on Sun Fire 3800

Hello there! I have Sun Fire 3800 with very old Solaris 9 and I need to perform upgrade to concurrent Solaris 10 version, preserving current OS configuration. I supose to make it using Live Upgrade, but according to Solaris Live Upgrade Software: Minimum Patch Requirements page, I need to... (5 Replies)
Discussion started by: Sapfeer
5 Replies

4. Solaris

live upgrade SUN cluster

Hi, Guys On this weekend I have to upgrade Solaris 10 2 node SUN cluster from u4 to u9. I have not touch Sun cluster for a while so I need some help. Can anybody let me know what I have to do specifically for this upgrade? Thank you very much (4 Replies)
Discussion started by: alex57
4 Replies

5. Solaris

Couldn't upgrade Solaris 10 x86 from Sun Fire x2200 to Dell Precision Wrkst

:)Dear Solaris Experts, I need to clone a Solaris 10 x86 system using a ufsdump backup from the following source & target servers: Sun Fire x2200 M2 with Quad Core Processor # /usr/platform/`uname -i`/sbin/prtdiag System Configuration: Sun Microsystems Sun Fire X2200 M2 with Quad Core... (8 Replies)
Discussion started by: gjackson123
8 Replies

6. Solaris

Sun-Fire-V490 Printer Issue After Upgrade of Solaris

Hey Guys I am new here, dont know if any one can assist me with this issue. I have a Sun-Fire-V490 machine that was upgraded to version 9 and patched a few months back. Problem is a few network printers managed by the server is printing an extra page that comes out before and after every print... (0 Replies)
Discussion started by: mprogams
0 Replies
metarename(1M)						  System Administration Commands					    metarename(1M)

NAME
metarename - rename metadevice or switch layered metadevice names SYNOPSIS
/usr/sbin/metarename [-s setname] metadevice1 metadevice2 /usr/sbin/metarename [-s setname] [-f] -x metadevice1 metadevice2 /usr/sbin/metarename -h DESCRIPTION
There are two ways to use metarename, one with and one without the -x option. The first method (without -x) renames an existing metadevice to a new name. This makes managing the metadevice namespace easier. The metadevice being renamed cannot be mounted or open, nor can the new name already exist. For example, to rename a metadevice that contains a mounted file system, you would first need to unmount the file sys- tem. With the second way to use metarename, using the -x option, metarename switches (exchanges) the names of an existing layered metadevice and one of its subdevices. In Solaris Volume Manager terms, a layered metadevice can be either a mirror or a trans metadevice. The -x option enables you to switch the metadevice names of a mirror and one of its submirrors, or a trans metadevice and its master device. metarename -x makes it easier to mirror or unmirror an existing stripe or concatenation, and to remove a trans device. When used to mirror an existing stripe or concatenatation, you must stop access to the device. For example, if the device contains a mounted file system, you must first unmount the file system before doing the rename. You can also use the metarename -x command to untrans a trans metadevice from an existing device. This applies only to the master device. You cannot remove a logging device with metarename. Before you can rename a trans device, you must detach the logging device. Then you must stop access to the trans metadevice itself. You cannot rename or switch metadevices that are in an error state or that have subcomponents in an error state, or metadevices actively using a hot spare replacement. You can only switch metadevices that have a direct child/parent relationship. You could not, for example, directly exchange a stripe in a mirror that is a master device with the trans metadevice. You must use the -f flag when switching members of a trans metadevice. Only metadevices can be switched, not slices. OPTIONS
The following options are supported: -f Force the switching of trans metadevice members. -h Display a help message. -s setname Specifies the name of the diskset on which metarename will work. Using the -s option will cause the command to perform its administra- tive function within the specified diskset. Without this option, the command will perform its function on the local metadevices. -x Exchange the metadevice names metadevice1 and metadevice2. metadevice1 Specifies the metadevice to be renamed or switched. metadevice2 Specifies the target metadevice name for the rename or switch operation. EXAMPLES
Example 1: Renaming a Metadevice This example renames a metadevice named d10 to d100. Note that d100 must not exist for the rename to succeed. # metarename d10 d100 Example 2: Creating a Two-Way Mirror This example creates a two-way mirror from an existing stripe named d1 with a mounted file system, /home2. # metainit d2 1 1 c13d0s1 # metainit -f d20 -m d1 # umount /home2 # metarename -x d20 d1 # metattach d1 d2 # mount /home2 First, a second concatenation d2, is created. (d1 already exists.) The metainit command creates a one-way mirror, d20, from d1. Next, you umount the file system and switch d1 for d20, making d1 the top-level device (mirror). You attach the second submirror, d2, to create a two-way mirror. Lastly, you remount the file system. Example 3: Mounting a Mirrored File System on Stripe This example takes an existing mirror named d1 with a mounted file system, and ends up with the file system mounted on a stripe d1. # umount /fs2 # metarename -x d1 d20 # metadetach d20 d1 # metaclear -r d20 # mount /fs2 First, you unmount the file system, then switch the mirror d1 and its submirror d20. This makes the mirror into d20. Next, you detach d1 from d20, then delete the mirror d20 and its other submirror. You then remount the file system. Example 4: Deleting a Trans Metadevice This example deletes a trans metadevice named d10 while its mount point is /myhome. The master device, which is a stripe, is named d2. The logging device, also a stripe, is named d5. # umount /myhome # metadetach d10 # metarename -f -x d10 d2 # metaclear d2 # metaclear d5 # fsck /dev/md/dsk/d10 # mount /myhome You umount the file system first, then detach the trans metadevice's logging device. The trans metadevice is switched with the master device, making the trans metadevice d2 and the underlying stripe d10. You clear the trans metadevice d2 and the logging device d5. d10 must be fsck'd, and then the file system is remounted. EXIT STATUS
The following exit values are returned: 0 Successful completion. >0 An error occurred. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWmdu | +-----------------------------+-----------------------------+ SEE ALSO
mdmonitord(1M), metaclear(1M), metadb(1M), metadetach(1M), metahs(1M), metainit(1M), metaoffline(1M), metaonline(1M), metaparam(1M), metarecover(1M), metareplace(1M), metaroot(1M), metaset(1M), metassist(1M), metastat(1M), metasync(1M), metattach(1M), md.tab(4), md.cf(4), mddb.cf(4), md.tab(4), attributes(5), md(7D) Solaris Volume Manager Administration Guide LIMITATIONS
Renaming and exchanging metadevice names can only be used for metadevices. A physical slice cannot be renamed to a metadevice, nor can a metadevice be exchanged with a physical slice name. Metadevice names are strings of the pattern d<xyz> where xyz is a value between 0 and 8192. You cannot use logical names for metadevices. NOTES
Trans metadevices have been replaced by UFS logging. Existing trans devices are not logging--they pass data directly through to the under- lying device. See mount_ufs(1M) for more information about UFS logging. SunOS 5.10 8 Aug 2003 metarename(1M)
All times are GMT -4. The time now is 01:25 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy