03-05-2016
What was not clear to me is whether the storage was physically located.
It sounds like it was using local storage (local, i.e., physical, not from a SAN) and the LPAR (aka virtual machine) was using LVM mirroring.
This was the preferred (read almost only) solution in 2005 before SAN storage was common. HOWEVER, if you have SAN backed storage what is 'common' when you have local (i.e., in the CEC aka Compute node) storage is to use the local storage for rootvg, dvd repositories, secure logs, etc. and SAN and MPIO for hosting VM (or client LPAR) storage.
re: active/passive LVM mirroring: the consistency check was to help 'guess' which mirror was last written when recovering from a crash. In your case, while the VIOS was down, one path was down and it is clear which disk is stale and needs to be synced.
Over time, the disks will sync automatically - but you can speed the process by running syncvg (lsvg vgName will tell you if there are stale disks and if so, how many stale PP)
This User Gave Thanks to MichaelFelt For This Post:
10 More Discussions You Might Find Interesting
1. IP Networking
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
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
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
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
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
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
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
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
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
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
LEARN ABOUT HPUX
vxvmconvert
vxvmconvert(1M) vxvmconvert(1M)
NAME
vxvmconvert - convert LVM volume groups to VxVM disk groups
SYNOPSIS
vxvmconvert
DESCRIPTION
vxvmconvert is a menu-driven program to convert an HP Logical Volume Manger (LVM) configuration to a Veritas Volume Manager configuration.
This man page is a brief overview of vxvmconvert. Refer to the Veritas Volume Manager Migration Guide for a detailed description before
using the conversion procedure.
The vxvmconvert script is interactive and prompts you for responses, supplying defaults where appropriate. There is a Help facility at
every prompt. Enter a question mark (?) at a prompt to display a context-sensitive help message.
With vxvmconvert you can identify LVM volume groups, list disks, analyze volume groups for conversion and complete the conversion of LVM
volume groups to VxVM disk groups.
LVM configurations are converted at the volume group level. All disks used in a volume group are converted together. You cannot use vxvm-
convert to convert unused LVM disks (those not part of an LVM volume group) to VxVM disks. To convert unused LVM disks, use pvremove to
take the disk out of LVM control, then initialize the disk for VxVM use by using vxdiskadm (see pvremove(1M) and vxdiskadm(1M) for more
information).
vxvmconvert changes disks within LVM volume groups to VxVM disks by replacing the areas of the disks used for LVM configuration information
and with the equivalent VxVM volume configuration information. Portions of the disks used for user data, such as file systems and data-
bases, are not affected by the conversion.
The conversion process changes the names by which your system refers to the logical storage, so must be done offline. No applications can
access data in the volume groups undergoing conversion. You must unmount file systems using those volumes and shut down any applications,
such as databases, that might use the volumes directly.
OPERATIONS
Analyze LVM Volume Groups for Conversion
Use this operation to analyze one or more LVM volume groups for conversion to use by VxVM. The analysis checks for problems that
can prevent the conversion from completing successfully. It calculates the space required to add volume group disks to a Volume
Manager disk group. More than one volume group may be entered at the prompt. A grep-like pattern may be used to select multiple
volume groups.
See the ``Limitations in Conversion'' section in the Volume Manager Migration Guide for more information.
Convert LVM Volume Groups to VxVM
Converts one or more LVM volume groups to one or more VxVM disk groups. This adds the disks to a VxVM disk group and replaces
existing LVM volumes with VxVM volumes.
vxvmconvert prompts you to name the VxVM disk group that replaces the LVM volume group being converted. A default is suggested
at the prompt. For example, if you are converting a volume group vg08, vxvmconvert renames it as dg08.
See to the sections ``Dealing with New Logical Volume Names'' and ``Tailoring your VxVM Configuration'' in the Volume Manager
Migration Guide for more information.
Rollback from VxVM to LVM
Rollback reverts VxVM disk groups to LVM volume groups. vxvmconvert provides a limited snapshot capability for the LVM metadata
in a converted volume group. A snapshot is a simple protection method to use during conversion.
Caution! Do not use this operation if the VxVM disk group was modified since the conversion.
See to the section ``Restoring LVM Volume Groups and Disaster Recovery'' in the Volume Manager Migration Guide for more informa-
tion.
List Disk Information
Displays information about the disks on a system. You can obtain detailed information about a disk by entering a specific disk
device address.
List LVM Volume Group Information
Listvg displays a list of LVM volume groups. You can obtain detailed information about an LVM volume group at a specific disk
device address.
SEE ALSO
pvremove(1M), vgcfgbackup(1M), vgrestore(1M), vxdisk(1M), vxdiskadd(1M), vxdiskadm(1M), vxintro(1M)
Veritas Volume Manager Migration Guide
VxVM 5.0.31.1 24 Mar 2008 vxvmconvert(1M)