Sponsored Content
Full Discussion: MPIO reliability
Operating Systems AIX MPIO reliability Post 302450618 by zaxxon on Friday 3rd of September 2010 09:00:59 AM
Old 09-03-2010
No clue if that was the case back then. Currently I found mixed settings like paths having the same priority and paths on another box with different priorities according to which virtualized storage they primarily talk to (while having algroithm=fail_over).
I also asked a coworker about it some seconds ago who told me he has the task to check and set all paths to different priorities.
I will keep it in mind, checking for path priority, just in case we have those strange effects again.
 

8 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

Optimizing the system reliability

My product have around 10-15 programs/services running in the sun box, which together completes a task, sequentially. Several instances of the each program/service are running in the unix box, to manage the load and for risk-management reasons. As of now, we dont follow a strict strategy in... (2 Replies)
Discussion started by: Deepa
2 Replies

2. UNIX for Advanced & Expert Users

AIX MPIO and EMC

We are looking at running MPIO for it's redundancy and load balancing benefits. Does anyone know what pieces of software or modules are needed on the VIO server to get load balancing to work. Remember we are using EMC's DMX3500 storage system. We no longer want to use Powerpath. :rolleyes: ... (2 Replies)
Discussion started by: vxg0wa3
2 Replies

3. AIX

AIX native MPIO

Hi folks, does anybody have a link to a documentation how to implement native MPIO on AIX? We are using EMC PowerPath and Datacore SanSymphony/Cambex for this so far and I wasn't able to find a good description on that topic. All I know so far is that mkpath, chpath and lspath are used to... (3 Replies)
Discussion started by: zaxxon
3 Replies

4. High Performance Computing

High reliability web server - cluster, redundancy, etc

Hi. I am IT manager/developer for a small organization. I have been doing as-needed linux server administration for several years and am by no means an expert. I've built several of my own servers, and our org is currently using hosting services for our servers and I am relatively happy. We... (3 Replies)
Discussion started by: bsaadmin
3 Replies

5. AIX

MPIO Driver

On a particular LPAR, I was running AIX 5.3 TL 3. On Monday I did an update of the LPAR to 5.3 TL 9 SP2. The install was smooth, but then I ran into a problem. The MPIO driver does not work with LSI's StoreAge (SVM4). I did some looking, and looks like 5.3 TL3 = IBM.MPIO 5.3.0.30 5.3... (0 Replies)
Discussion started by: clking
0 Replies

6. Solaris

Reasons for NOT using LDOMs? reliability?

Dear Solaris Experts, We are upgrading from sun4u to T4 systems and one proposal is to use LDOMs and also zones within LDOMs. Someone advised using only zones and not LDOMs because the new machines have fewer chips and if a chip or a core fails then it doesn't impact the zones, but impacts... (3 Replies)
Discussion started by: User121
3 Replies

7. AIX

Need Help with SDD / SDDPCM / MPIO

This is getting very confusing for me, and appreciate if someone can help. Platform: Power VM ( Virtual I/O Server) ioslevel 2.1.3.10-FP23 # oslevel -s 6100-05-00-0000 Storage: IBM DS4300 Two HBAs - Dual Port Fibre Adapter Channels Each card has two ports , so a total of 4 ports going... (3 Replies)
Discussion started by: filosophizer
3 Replies

8. AIX

DISK and MPIO

Hello, I have some concerns over the disk management of my AIX system. For example server1 / > lspv hdisk0 00fa6d1288c820aa rootvg active hdisk1 00fa6d1288c8213c vg_2 active hdisk2 00c1cc14d6de272b ... (6 Replies)
Discussion started by: Phat
6 Replies
volmirror(8)						      System Manager's Manual						      volmirror(8)

NAME
volmirror - Mirrors volumes on a disk or control default mirroring SYNOPSIS
/usr/sbin/volmirror [-g diskgroup] [-d yes|no] medianame [new_medianame...] /usr/sbin/volmirror [-g diskgroup] [-d yes|no] -a [new_medianame...] /usr/sbin/volmirror [-g diskgroup] [-d yes|no] /usr/sbin/volmirror [-g diskgroup] -D OPTIONS
The volmirror command supports the following options: Limits operation of the command to the given disk group, as specified by disk group ID or disk group name. The medianame operands will be evaluated relative to the given disk group. If no disk group is supplied to the volmirror command, rootdg is presumed. Changes the default for subsequent volume creation, depending on the option argument. If the option argument is yes, all subsequent volumes created using the volassist command will automatically be created as mirrored volumes. If the option argument supplied is no, mirroring will be turned off for future volumes by default. Displays current default status for mirroring. Mirrors all existing volumes for the specified disk group. DESCRIPTION
The volmirror command provides a mechanism to mirror all the contents of a specified disk, to mirror all currently unmirrored volumes in the specified disk group, or to change or display the current defaults for mirroring. All volumes that have only a single plex (mirror copy), will be mirrored by adding an additional plex. Volumes containing subdisks that reside on more than one disk will not be mirrored by volmirror. The volmirror command is generally called from the voldiskadm menus. It is not an interactive command and once called, will continue until completion of the operation or until a failure is detected. Note Due to the nature of generating mirror copies of volumes, this command may take a considerable time to complete. In the first listed form of the command, the disk media name is supplied on the command line to volmirror. That name is taken to be the only disk from which volumes should be mirrored. In the case of mirroring volumes from a specified disk, only simple single-subdisk volumes are mirrored. In the first and second listed forms of the command, the new_medianame ... parameter identifies a new disk media name (or set of names). The mirroring operation being performed will use these names as targets on which to allocate the mirrors. An error will result if the same disk is specified for both the source and target disk and if no other viable targets are supplied. EXAMPLES
The following are examples of the use of the volmirror command. The following command mirrors the contents of the disk named disk01 to any available space on any available disk. Subsequent calls to volassist will cause created volumes to be mirrored by default. volmirror -d yes disk01 The following command displays the current status of default mirroring. It prints the string yes if mirroring is currently enabled or no, if not. volmirror -D The following command mirrors any volumes on disk02 onto disk03. volmirror disk02 disk03 FILES
The defaults file for volassist parameters. SEE ALSO
volintro(8), volassist(8), volrootmir(8) volmirror(8)
All times are GMT -4. The time now is 09:58 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy