Sponsored Content
Operating Systems Solaris Unmirror and Remirror for Solaris 10 Post 302274473 by StarSol on Wednesday 7th of January 2009 04:33:49 PM
Old 01-07-2009
Unmirror and Remirror for Solaris 10

Happy New Year to all.

I am working on Solaris 10 testing as we are moving from Solaris 8. When I JumpStart Solaris 10, SW mirroring (RAID1) is enabled by default and metastat -p shows:

d10 -m d11 d12 1
d11 1 1 c1t0d0s0
d12 1 1 c1t1d0s0
d20 -m d21 d22 1
d21 1 1 c1t0d0s1
d22 1 1 c1t1d0s1
d30 -m d31 d32 1
d31 1 1 c1t0d0s7
d32 1 1 c1t1d0s7

One of the objective is to come up with a procedure to un-mirror the disks before an upgrade or patching activity and then re-mirror if successful, or start with the other disk if unsuccessful to get back to the state before the upgrade. I did some research and found this procedure on Sun BigAdmin (Automating Unmirror and Remirror for Solaris Volume Manager Volumes) (BigAdmin Submitted Tech Tip: Automating Unmirror and Remirror for Solaris Volume Manager Volumes). I could successfully un-mirror and re-mirror very quick but did not do a more detailed testing yet.

Has anybody tried this? I have few concerns/questions and wondering if you can help:

- We normally have customized applications and database running on the server, is applying this procedure safe to them (especially the database)? In other words, the database is constantly updated, if you run the un-mirror script it will detach one of the disks and hence one disk will be updated with the changes before a reboot is attempted before the un-mirror is complete.
- When the un-mirror is complete and the system is rebooted, which disk the server is using?
- If upgrade or patching activity fails and you decide to revert back and start from the other disk, how to do that?
- Finally, does anyone recommend a better way or method?
 

4 More Discussions You Might Find Interesting

1. Solaris

Unable to login using ssh,telnet onto my solaris machine with solaris 10 installed

Hi, I am unable to login into my terminal hosting Solaris 10 and get the below error message "Server refused to allocate pty ld.so.1: sh: fatal: libc.so.1: open failed: No such file or directory " Is there anyways i can get into my machine and what kind of changes are required to be... (7 Replies)
Discussion started by: sankasu
7 Replies

2. Solaris

dual boot solaris/solaris zfs file system

Hi, I am running into a some problems creating a dual boot system of 2 solaris instances using ZFS file system and I was wondering if someone can help me out. First some back ground. I have been asked to change the file system of our server from UFS to ZFS. Currently we are using Solaris... (3 Replies)
Discussion started by: estammis
3 Replies

3. AIX

Unmirror and machine not booted after restart

My box is aix 5.3, i have done unmirror and restart, machine count't boot up missing disk in sms, BLV, is in hdisk3 when i go through maintenance mode, many command not work such as... bosboot bootlist pls suggest me... (5 Replies)
Discussion started by: reply.ravi
5 Replies

4. Solaris

How to add Solaris text console to Solaris grub2 menu?

Hi, I am new to sloaris and just instlled the solaris 11.2, i know little more about linux, i open the /boot/grub/grub.cfg in solaris and there is many other entries forl solaris 11.2 one of them is for 'Oracle Solaris 11.2 text console' but at boot grub2 only show the first default entry that... (1 Reply)
Discussion started by: shamsat
1 Replies
vxbrk_rootmir(1M)														 vxbrk_rootmir(1M)

NAME
vxbrk_rootmir - break off a mirror of a VxVM root disk to create a separate root disk generation SYNOPSIS
/etc/vx/bin/vxbrk_rootmir [-g diskgroup] [-v] [-b] [-t tasktag] {daname|dmname} DESCRIPTION
The vxbrk_rootmir command creates a mirror of a Veritas Volume Manager (VxVM) rootable boot disk, breaks the mirror, and then makes the broken-off mirror into a completely separate root disk that is suitable for booting by itself. Except the specified target disk, the bootdg should not contain any disks other than valid root mirror disks. A valid root mirror disk should have mirrors of all volumes in the bootdg. Thus, all disks must be exactly identical in terms of the volumes contained. The given disk access name, daname, or disk media name, dmname, is first checked to see if it is already a valid root disk mirror. If so, the mirror is broken off from the current VxVM root disk, and regenerated into a unique VxVM root disk. If the specified disk is not a valid root disk mirror, and is unused for other purposes, the vxrootmir command is first called to mirror the specified disk from the cur- rent VxVM root disk. After the mirroring operation is complete, the mirror is then broken off, and regenerated into a unique VxVM root disk. OPTIONS
-b Uses the setboot command to set the alternate boot disk to the specified disk. If the -v option is also specified, information is displayed about the current setboot settings. -g diskgroup Specifies the disk group into which the newly broken-off mirror is to be placed. The disk group is created if it does not already exist. If the disk group already exists, the broken-off mirror is added to it. If this option is not specified, the disk group of the broken-off mirror is set to the current default disk group. However, the generation number is made different from the default disk group to prevent the mirror from being automatically imported. -t tasktag Marks any tasks that are registered to track the progress of an operation with the specified tag, tasktag. This option is passed to vxrootmir if it is necessary first to mirror the specified disk that is to be broken off. -v Displays verbose output, including timestamps for operations that are in progress. This option is passed to vxrootmir if it is neces- sary first to mirror the specified disk that is to be broken off. ARGUMENTS
daname Specifies the disk to be used as the broken off mirror by its disk access name (such as c0t2d0). dmname Specifies the disk to be used as the broken off mirror by its disk media name (such as rootdisk03). EXAMPLES
This example shows the vxbrk_rootmir command being executed on a disk that already contains a valid root mirror: /etc/vx/bin/vxbrk_rootmir -g brkdg -vb c4t15d0 VxVM vxbrk_rootmir INFO V-5-2-4023 17:47: Checking specified disk(s) for presence and type VxVM vxbrk_rootmir INFO V-5-2-4025 17:47: DA c4t15d0s2, DM rootdisk06 is a valid root mirror VxVM vxbrk_rootmir INFO V-5-2-4052 17:47: Saving configuration data for later restoration VxVM vxbrk_rootmir INFO V-5-2-4022 17:47: Breaking off root mirror on DA c4t15d0s2 VxVM vxbrk_rootmir INFO V-5-2-4054 17:47: Setting broken off mirror on c4t15d0s2 as unique root disk VxVM vxbrk_rootmir INFO V-5-2-2566 17:47: Preparing disk c4t15d0s2 as a VxVM root disk VxVM vxbrk_rootmir INFO V-5-2-4046 17:47: Patching devnodes, fstab and volboot file in new Root FS VxVM vxbrk_rootmir INFO V-5-2-4045 17:47: Patching /stand/bootconf file to contain new root disk VxVM vxbrk_rootmir INFO V-5-2-2462 17:48: Current setboot values: VxVM vxbrk_rootmir INFO V-5-2-4048 17:48: Primary: 0/0/2/0.2.0 VxVM vxbrk_rootmir INFO V-5-2-4010 17:48: Alternate: 0/2/1/0.8.0.255.2.5.0 VxVM vxbrk_rootmir INFO V-5-2-4042 17:48: Making c4t15d0s2 (0/2/1/0.8.0.255.1.15.0) the alternate boot disk VxVM vxbrk_rootmir INFO V-5-2-4028 17:48: Disk c4t15d0s2 is now a broken off root disk The next example shows the command being executed on a disk that does not contain a valid root mirror, and which requires vxrootmir be called to mirror the root disk first: /etc/vx/bin/vxbrk_rootmir -g brkdg -vb c5t5d0 VxVM vxbrk_rootmir INFO V-5-2-4023 16:25: Checking specified disk(s) for presence and type VxVM vxbrk_rootmir INFO V-5-2-4043 16:25: Mirroring root disk VxVM vxrootmir INFO V-5-2-2501 16:25: Gathering information on the current VxVM root configuration VxVM vxrootmir INFO V-5-2-2441 16:25: Checking specified disk(s) for usability VxVM vxrootmir INFO V-5-2-2566 16:25: Preparing disk c5t5d0 as a VxVM root disk VxVM vxrootmir INFO V-5-2-3766 16:25: Disk c5t5d0 is now EFI partitioned disk c5t5d0s2 VxVM vxrootmir INFO V-5-2-2410 16:25: Adding disk c5t5d0s2 to brkdg as DM rootdisk03 VxVM vxrootmir INFO V-5-2-1646 16:25: Mirroring all volumes on root disk VxVM vxrootmir INFO V-5-2-1648 16:25: Mirroring volume standvol VxVM vxrootmir INFO V-5-2-1648 16:26: Mirroring volume swapvol VxVM vxrootmir INFO V-5-2-1648 16:30: Mirroring volume rootvol VxVM vxrootmir INFO V-5-2-1648 16:31: Mirroring volume homevol VxVM vxrootmir INFO V-5-2-1648 16:31: Mirroring volume tmpvol VxVM vxrootmir INFO V-5-2-1648 16:31: Mirroring volume usrvol VxVM vxrootmir INFO V-5-2-1648 16:34: Mirroring volume optvol VxVM vxrootmir INFO V-5-2-1648 16:36: Mirroring volume varvol VxVM vxrootmir INFO V-5-2-1616 16:40: Disk c5t5d0s2 is now a mirrored root disk VxVM vxbrk_rootmir INFO V-5-2-4052 16:40: Saving configuration data for later restoration VxVM vxbrk_rootmir INFO V-5-2-4022 16:40: Breaking off root mirror on DA c5t5d0s2 VxVM vxbrk_rootmir INFO V-5-2-4054 16:40: Setting broken off mirror on c5t5d0s2 as unique root disk VxVM vxbrk_rootmir INFO V-5-2-2566 16:40: Preparing disk c5t5d0s2 as a VxVM root disk VxVM vxbrk_rootmir INFO V-5-2-4046 16:41: Patching devnodes, fstab and volboot file in new Root FS VxVM vxbrk_rootmir INFO V-5-2-4045 16:41: Patching /stand/bootconf file to contain new root disk VxVM vxbrk_rootmir INFO V-5-2-2462 16:41: Current setboot values: VxVM vxbrk_rootmir INFO V-5-2-4048 16:41: Primary: 0/0/2/0.2.0 VxVM vxbrk_rootmir INFO V-5-2-4010 16:41: Alternate: 0/2/1/0.8.0.255.2.0.0 VxVM vxbrk_rootmir INFO V-5-2-4042 16:41: Making c5t5d0s2 (0/2/1/0.8.0.255.2.5.0) the alternate boot disk VxVM vxbrk_rootmir INFO V-5-2-4028 16:41: Disk c5t5d0s2 is now a broken off root disk SEE ALSO
vxbootsetup(1M), vxdg(1M), vxintro(1M), vxrootmir(1M), vxtask(1M) VxVM 5.0.31.1 24 Mar 2008 vxbrk_rootmir(1M)
All times are GMT -4. The time now is 08:19 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy