Sponsored Content
Operating Systems AIX Rebooting redundant VIOs and mirroring of PVs they serve to client LPARs Post 302968033 by maraixadm on Thursday 3rd of March 2016 11:08:21 AM
Old 03-03-2016
Rebooting redundant VIOs and mirroring of PVs they serve to client LPARs

need to confirm:
we have a system with two VIOs each serving a partition on a local disk to a client LPAR. That client LPAR has them both in a VG which is mirrored (exact). So each disk has a copy of the client LV that the client VG supports. This is the setup that was bequeathed to us by the vendors who set up the system originally, and which we've replicated to further systems.

I'm doing an upgrade cycle on the VIOs. If I reboot one of them after installing the upgrade, I would like
  1. the other VIO to continue serving its instance of the mirrored LV - don't see a reason to anticipate trouble with this
  2. when the rebooted VIO comes back, I expect the client LVM to deal with incongruities between the two copies of the mirrored LV appropriately.

#2 is my concern. What I read about mirror write consistency is that active MWC records writes in the MWC log and reaps that when the VG is varied back on, while passive MWC records that an LV has been opened, and forces a syncvg.

I'm trying to dig up how that applies when I shut down one VIO and thus make one of the client PVs supporting the mirrored client LV disappear for a while, then turn it back on and have it reappear in the mirrored VG. MWC is set to on/active for the mirrored LV.

Should I not worry because this is the correct configuration and this is what it was designed to support ?

Conversely, should I save myself the concern and drive risk to 0 by shutting down the client LPAR ? We have a maintenance window to work with; on the other hand it seems to me this is the kind of scenario that VIO redundancy was meant to address, so I shouldn't have to shut down client LPARs.

TIA...

---------- Post updated 03-03-16 at 11:08 ---------- Previous update was 03-02-16 at 18:09 ----------

well, it worked fine - no bobbles in the filesys

still interested in any views you may have of the above, tx
 

10 More Discussions You Might Find Interesting

1. IP Networking

to serve or be served??

I have two machines on my network - one OSX mac and one linux box. The mac is my main workhorse, and the linux box does occasional chores and webserving. Currently the mac shares (via NFS) files with the Liinux box. Would it be less demanding on the mac if I made it a client, and moved my files... (2 Replies)
Discussion started by: mistafeesh
2 Replies

2. AIX

rebooting vio client

Hi, I would like to reboot vio client but I am not able to access vio client(I am not able to get putty) , I am able to get putty of vio server, is there any command by using which from vio server I can reboot vio client? (3 Replies)
Discussion started by: manoj.solaris
3 Replies

3. AIX

DUAL VIOS & Client LPAR hangs at 25b3

I have a DUAL VIO ( IBM Virtual I/O ) setup on p 570. Two Vio server ( VIOS ) and many LPAR clients. VIO ( latest version + service pack + applied the fix ) and AIX 6.1 ML2 When both VIOs are running, and if I turn on a Client LPAR, the LPAR hangs at LED 25b3 for more than 1 hour then it... (2 Replies)
Discussion started by: filosophizer
2 Replies

4. HP-UX

How to Mirror LV and umirror after to change PVs...

Greetings Im running HP UX B 11.11 and Im not sure on how to do this request to "mirror current 5 LVs on vgSPAN to the new LUNs assigned to the VG and unmirror the LVs and finally return the 12 LUNs to SAN storage" The existing LVs were extended to accommodate a user request to extend 2 FS on... (3 Replies)
Discussion started by: hedkandi
3 Replies

5. AIX

VIOS IP address - separate vlan for vios servers ?

Hello, Lets say for simplicity that I do not use any vlan config inside my server - one lpar group use hea physical port1, another group hea physical port2. Physical port1 configured as vlan1 on external switch, physical port2 as vlan2. What is the common practice - should I isolate my vios... (0 Replies)
Discussion started by: vilius
0 Replies

6. AIX

Shared Disk in VIOS between two LPARs ?

is there any way to create shared virtual disk between two LPARs like how you can do it using Storage through Fiber on two servers ? Trying to stimulate HACMP between two LPARs (1 Reply)
Discussion started by: filosophizer
1 Replies

7. HP-UX

PVS command in HP-UX

Dear Engineer, Is there any command in HP-UX work similiar to PVS command in Linux? With Best Regards, Md. Abdullah-Al Kauser (4 Replies)
Discussion started by: makauser
4 Replies

8. UNIX for Advanced & Expert Users

Unable to install client AIX LPAR to vscsi hdisk provided from VIOS

Hi everybody, I have Power5 server with 4 internal hdisks each of 70Gb. VIOS server was installed via Virtual I/O Server Image Repository on the HMC. HMC release - 7.7.0 VIOS rootvg installed on 2 disk(these disks merged to one storage pool during VIOS install process),and 2 others hdisks... (2 Replies)
Discussion started by: Ravil Khalilov
2 Replies

9. AIX

Chef client on VIOs? How do you manage your VIO configs?

I know the VIOs are generally to be treated as an appliance and one should never drop down to oem_setup_env. In reality however, oem is a very useful tool to get the job done. So that leads me into the question of using the Chef client on a VIO. Currently a big push to manage all our *nix... (4 Replies)
Discussion started by: RecoveryOne
4 Replies

10. AIX

Need to replace a broken PV in a VIO VG used for client LPARs (and it won't release the old one)

I have a broken PV in a VIO VG that's used to support client LPARs using LVs. On the client LPAR, I reduced all PVs from the relevant client VG and thus deleted it. I.e. there is no client LPAR using the VIO VG. Yet when I try to reducevg the VIO VG, it complains that the LV hosted on the PV is... (2 Replies)
Discussion started by: maraixadm
2 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 07:44 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy