Sponsored Content
The Lounge War Stories Data Centre meets Vacuum Cleaner Post 303014201 by gull04 on Wednesday 7th of March 2018 04:10:19 AM
Old 03-07-2018
Data Centre meets Vacuum Cleaner

Hi Folks,

I have just spent a couple of days resolving some problems at the remote DR data centre, sorting out the problems caused by the over zealous use of a Vacuum cleaner of all things.

We have a backup server a SUN V480R with a Storedge 3510 and expansion attached which suffered a significant unexplained failure, all tracked back to an ID selector being touched by the nozzle of said vacuum cleaner - it looks like things went as follows over a period of time.

When the array was installed the setup was disks 0-9 were setup as a 10way stripe with disks 10 and 11 as hot standby disks. Over a period of time, a disk in the expansion (disk 3) failed and the and the first available spare (disk 10) built from the surviving mirror.

At this point the situation that existed left us exposed in a way which wasn't really appreciated, in that the one of the arrays had both mirrors of one part of the stripe. That would be the part that had the exposed ID selector switch, the one that the Vacuum Cleaner nozzle could change causing the failure of one whole stripe and one slice of an other stripe. The result as you can imagine was somewhat unpredictable, which is exactly what the Sun manual for the array says.

To add insult to injury the contents of the 3510 array, was the Legato Networker Backup Catalogue from the 24 drive ATL - making the recovery somewhat awkward.

What's the point of the story - don't let some idiot into a data centre with a Vacuum Cleaner.

Regards

Gull04
 

6 More Discussions You Might Find Interesting

1. News, Links, Events and Announcements

The HP-UX Porting and Archive Centre

If you're looking for an easy source of free software for HP-UX, look no further. A consortium of major universities and HP user groups have banded together and operate what is simply the finest free software site in existence. The world's best HP-UX software engineers have ported each package... (0 Replies)
Discussion started by: Perderabo
0 Replies

2. Solaris

Sun Management Centre

Hi Guys, Does anyone ever use Sun MC before? If yes, can u share with me how to do the installation. Thanks (1 Reply)
Discussion started by: raziayub
1 Replies

3. Shell Programming and Scripting

Cleaner method for this if-then statement?

I have a script that runs once per month. It performs a certain task ONLY if the month is January, April, July, or October. MONTH=`date +%m` if || || || ; then do something else do a different thing fi Is there a neater way of doing it than my four separate "or" comparisons? That... (2 Replies)
Discussion started by: lupin..the..3rd
2 Replies

4. Shell Programming and Scripting

Cleaner way to use shell variable in awk /X/,/Y/ syntax?

$ cat data Do NOT print me START_MARKER Print Me END_MARKER Do NOT print me $ cat awk.sh start=START_MARKER end=END_MARKER echo; echo Is this ugly syntax the only way? awk '/'"$start"'/,/'"$end"'/ { print }' data echo; echo Is there some modification of this that would work? awk... (2 Replies)
Discussion started by: hanson44
2 Replies

5. Shell Programming and Scripting

A cleaner way to rearrange column

Hello, I have some tab delimited text data, index name chg_p chg_m 1 name,1 1 0 2 name,2 1 1 3 name,3 1 0 4 name,4 1 0 5 name,5 1 1 I need to duplicate the "index" column, call it "id" and insert it after the... (8 Replies)
Discussion started by: LMHmedchem
8 Replies

6. Shell Programming and Scripting

Maybe a cleaner way to generate a file?

greetings, to be clear, i have a solution but i'm wondering if anyone has a cleaner way to accomplish the following: the variable: LSB_MCPU_HOSTS='t70c7n120 16 t70c7n121 16 t70c7n122 16 t70c7n123 16 t70c7n124 16 t70c7n125 16 t70c7n126 16 t70c7n127 16 t70c7n128 16 t70c7n129 16 t70c7n130 16... (2 Replies)
Discussion started by: crimso
2 Replies
vxrootmir(1M)															     vxrootmir(1M)

NAME
vxrootmir - create a mirror of a Veritas Volume Manager root disk SYNOPSIS
/etc/vx/bin/vxrootmir [-g diskgroup] [-t tasktag] [-p Pool_1,Pool_2,...] [[-v] [-b] [-R] root_mirror] DESCRIPTION
The vxrootmir command creates mirrors of all of the volumes on a Veritas Volume Manager (VxVM) rootable boot disk, and makes the new disk bootable. A disk to be used as a mirror can be specified either by its VM disk name (disk media name) or by its device name (disk access name). If a disk media name is specified, it is validated to make sure that it exists and that it has been properly initialized. This validation includes making sure that the private region is at the same location and has the same length as the private region on the primary root disk, and that the sum of the lengths of all of the subdisks located on the primary root disk will fit within the available space in the public region of the specified disk. If a disk access name is specified, it is validated to make sure it exists and is not in use, and that the total length of all the subdisks on the primary root disk will fit within the public region. The disk is then initialized to contain a private region with the same offset and length as the private region on the primary root disk. A new disk media name is assigned to the disk formed from the prefix rootdisk followed by the next available number (for example, rootdisk02, rootdisk03, and so on). All volumes that have a subdisk on the primary VxVM root disk are mirrored on the specified disk. When the root volume (rootvol) is mir- rored, the vxassist command executes vxbootsetup to set up the new disk as a boot disk. The -p option allows you to mirror the volumes on the root disk as stripe columns across several disks. The argument to this option is a list of disks that are to be used for the stripe column mirrors. If not enough disks are specified, vxrootmir prints a message to the standard error output, including information on how many disks are required, and then exits. When initialized for VxVM use, these stripe column disks are named with the prefix rootaux followed by the next available number (for example, rootaux01, rootaux02, and so on). OPTIONS
-b If the system was booted from the VxVM root disk that is being mirrored, this option uses the setboot command to set the alter- nate boot disk to the specified mirror. If the system was booted from another root disk (such as an LVM root disk), an alternate root disk is not set. If the -v option is also specified, information is displayed on the current setboot settings, and on whether the alternate boot disk is set to the specified mirror. -g diskgroup Specifies the boot disk group. -p Pool_1,Pool_2,... Specifies the disks that are to be used for stripe column targets when mirroring the VxVM root disk. The disks can be specified either as disk access names, or as disk media names if they have previously been initialized for use with VxVM. If specified as disk access names, the disks are checked for existence, correct size, and availability for use. -R Indicates that only the volumes required to boot successfully from the new mirror are to be mirrored. -t tasktag Marks any tasks that are registered to track the progress of an operation with the tag tasktag. This option is passed to vxas- sist when mirroring volumes, so any child tasks are also tagged with tasktag. -v Displays verbose output including timestamps for operations in progress. This option is useful as mirroring large volumes can take a long time. ARGUMENTS
daname Specifies the disk to be used as a mirror by its disk access name (such as c0t2d0). dmname Specifies the disk to be used as a mirror by its disk media name (such as rootdisk03). EXAMPLES
This example shows the vxrootmir command being invoked in its simpliest form: /etc/vx/bin/vxrootmir c5t1d0 The next example shows how to use the -R option with vxrootmir. # /etc/vx/bin/vxrootmir -v -b -R c5t10d0 vxrootmir: 10:10: Gathering information on the current VxVM root configuration vxrootmir: 10:10: Checking specified disk(s) for usability vxrootmir: 10:10: Preparing disk c5t10d0 as a VxVM disk vxrootmir: 10:10: Adding disk c5t10d0 to rootdg as rootdisk02 vxrootmir: 10:10: Mirroring only volumes required for root mirror boot vxrootmir: 10:10: Mirroring volume standvol vxrootmir: 10:11: Mirroring volume swapvol vxrootmir: 10:18: Mirroring volume rootvol vxrootmir: 10:20: Current setboot values: vxrootmir: 10:20: Primary: 0/4/0/1.11.0 vxrootmir: 10:20: Alternate: 0/4/0/1.13.0 vxrootmir: 10:20: Making c5t10d0 (0/4/0/1.10.0) the alternate boot disk vxrootmir: 10:20: Disk c5t10d0 is now a mirrored root disk The final example shows how to specify a list of disks for use as stripe column mirrors: # /etc/vx/bin/vxrootmir -v -p c5t11d0,c5t12d0,c5t13d0 c5t10d0 vxrootmir: 12:11: Gathering information on the current VxVM root configuration vxrootmir: 12:11: Checking specified disk(s) for usability vxrootmir: 12:11: Preparing disk c5t10d0 as a VxVM disk vxrootmir: 12:11: Adding disk c5t10d0 to rootdg as rootdisk02 vxrootmir: 12:11: Preparing disk c5t11d0 as a VxVM disk vxrootmir: 12:11: Adding disk c5t11d0 to rootdg as DM rootstpm01 vxrootmir: 12:11: Preparing disk c5t12d0 as a VxVM disk vxrootmir: 12:11: Adding disk c5t12d0 to rootdg as DM rootstpm02 vxrootmir: 12:11: Preparing disk c5t13d0 as a VxVM disk vxrootmir: 12:11: Adding disk c5t13d0 to rootdg as DM rootstpm03 vxrootmir: 12:11: Mirroring all volumes on root disk vxrootmir: 12:11: Mirroring volume standvol vxrootmir: 12:12: Mirroring volume swapvol vxrootmir: 12:19: Mirroring volume rootvol vxrootmir: 12:21: Mirroring volume optvol vxrootmir: 12:24: Mirroring volume usrvol vxrootmir: 12:27: Mirroring volume homevol vxrootmir: 12:28: Mirroring volume tmpvol vxrootmir: 12:28: Mirroring volume varvol vxrootmir: 12:36: Disk c5t10d0 is now a mirrored root disk NOTES
If the vxrootmir command aborts for any reason, or if you interrupt the command during execution, an attempt is made to clean up the VxVM objects that had been generated up to the time of the abort or interruption. All mirror plexes that had already been added, or that were in the process of being added when the interruption occurred, are removed. All Data Media (DM) objects that were created are also removed. If a plex or a DM object cannot be removed, an explanatory message is displayed. SEE ALSO
setboot(1M), vxassist(1M), vxbootsetup(1M), vxintro(1M), vxmirror(1M), vxtask(1M) VxVM 5.0.31.1 24 Mar 2008 vxrootmir(1M)
All times are GMT -4. The time now is 11:58 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy