Sponsored Content
Operating Systems Solaris How to configure my SAN with Sun V880 servers to run Oracle 9i Post 80924 by 98_1LE on Saturday 13th of August 2005 10:14:26 PM
Old 08-13-2005
The internal disks in a V880 are on an internal loop, and cannot participate in the SAN.

As for configuring the "SAN", that depends on the actual storage array, switches, & HBA's that you have. Generally speaking you will need to format the parity groups into LDEV's, run fiber, present LUN's to a port, configure LUN security, then configure the zones on the switch. Then assuming you are using Sun HBA's (QLogic) with the leadville drivers, you `cfgadm -c configure c# c#` the controllers, and put a VTOC on the disks.

You can use either Veritas Volume Manager and file system, or Veritas storage foundation for Oracle which also comes in an HA flavor (VCS). Veritas brings some flexibility, simplicity, and performance, but is expensive. Sun Disk Suite (SDS) and the ufs file system ship with Solaris.

If you are hardware RAID 10 on your array, I would use concatonated volumes. I usually put the ORACLE_BASE/HOME undert /app/oracle, and put the database under /u01 thru /u05, and use /u06 for archive logs. If I need a local slice for backups, I put it at /app/backups.

If using vxfs, make sure to use the largest block size that equals or is a multiple of your db/tablespace block size.

All of my V880's only have 6 internal 72GB disks. I usually use two for the OS mirrored with SDS, and the other four for rootdg with pre 4.0 vxvm. With 4.x, I make them a disk group, and would put your Oracle binaries and indexes on those disks, and the rest of the database on the SAN.

Realize that if you put disks on the SAN and the internal disks in the same disk group/set, you may have errors on boot or in single user because the drivers for the SAN HBA's have not loaded, and only part of the disk group will be visible.

Be sure to put noatime as a mount option in the vfstab, and if using ufs, also logging.
 

9 More Discussions You Might Find Interesting

1. UNIX Benchmarks

Sun V880 Solaris 9

notes: System Configuration: Sun Microsystems sun4u Sun Fire 880 System clock frequency: 150 MHz Memory size: 8192 Megabytes Run E$ CPU CPU Brd CPU MHz MB Impl. Mask --- --- ---- ---- ------- ---- A 0 750 8.0 US-III 5.4 B 1 ... (0 Replies)
Discussion started by: tnorth
0 Replies

2. Solaris

Sun v440/v880 network adapter teaming

Is it possible to team two network adapters for fault tolerance in a Sun v440 or v880 Solaris 8 box? If so how would I go about doing so? (1 Reply)
Discussion started by: ghuber
1 Replies

3. Solaris

Sun V880

I have two mechine, one is SUN V880 and another is IBM p570. I run the same script on V880 and p570 , why the cpu usage always under 50% on V880 but the cpu usage can growth to 100% on p570. (4 Replies)
Discussion started by: golden
4 Replies

4. Solaris

Thoughts/experiences of SAN attaching V880 to EMC SAN

Hi everyone, I wonder if I can canvas any opinions or thoughts (good or bad) on SAN attaching a SUN V880/490 to an EMC Clarion SAN? At the moment the 880 is using 12 internal FC-AL disks as a db server and seems to be doing a pretty good job. It is not I/O, CPU or Memory constrained and the... (2 Replies)
Discussion started by: si_linux
2 Replies

5. UNIX for Dummies Questions & Answers

unable to telnet from win xp to sun fire v880 server

Hi everybody i am trying to telnet to sun server from win xp machine but getting message "x21 error connection closed by remote user". i had make changes in /etc/default/login & /etc/fuser file still i have not getting telnet access. my win xp machines ip is 10.205.121.177 & sun server ip is... (1 Reply)
Discussion started by: pshelke
1 Replies

6. Solaris

configure solaris 10 mail to relay email alerts from SAN switch

I want to be able to use an account on a solaris 10 server, eg root@myhost to act as a relay to forward mail to my domain account me@mycompany.com The reason for this is to configure root@myhost as a mail relay on Brocade SAN switches - so that when a port goes bad i get an email alert.... (0 Replies)
Discussion started by: wibidee
0 Replies

7. Solaris

How configure SAN to server?

Hi all, I have a server with Solaris version 9. I wanted to mount SAN storage to my server. I am new at this. Can anyone give me an overview on how to this. Any documents will be fine also. Please let me know if any information is required. Thanks in advance. Below shows the HBA port: ... (11 Replies)
Discussion started by: beginningDBA
11 Replies

8. Hardware

Help needed for non-SUN-HDD (original Seagate) in V880

Hello, we have a hardware error on a 36GB HDD within a SunFire V880. Disk seems to be really dead, cause changing the slot of the disk, moves the error along. So we bought a similar, but original) Seagte-Disk (on ebay) and screwed it in the HDD-Cage. Disk is now known in format, but is... (5 Replies)
Discussion started by: etomer_sk
5 Replies

9. Solaris

Could you run this benchmark? (Especially if you have a V880 or V890)

Hi all I am currently using a T5120 to write and run some simulation code I've been working on which heavily relies on large matrix multiplication procedures. I am posting this to call out for some of you run and share the results of a simple benchmark I've written to compare the matrix... (1 Reply)
Discussion started by: toguro123
1 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 04:23 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy