Oh yea, controllers changed. Ummm, the attached output seems to be fine bro.. But, not practically.
It shows up 482 out of which 2 are root/rootmir.. So, remaining 480. Actual Disks should be 120 as each disk has 4 paths. Per your earlier post, 4 storages with 30 each. So, 30*4=120. Path's appear to be fine ENABLED. However, if we see it clearly, there are few disks only with 2 paths..
Let's do like this.. Proceed checking the controllers..
Make sure that all the controllers are showing up and fine. Get the controller name and status...
Check if the controllers are enabled and active. (It also depends on the DMP layout/algorithm you are using)
Find the controllers which are disabled, perhaps, this could give us some information.. I would also give priority to the controllers which were changed recently.
Hello everybody,
My job is to load the data from Oracle table to flat file and from flat file to oracle table using ETL tool Informatica. My flat files are fixed width. In the first phase, it is loading 66351 records into data file through tool. When I checked through wc -l <data filename> it is... (1 Reply)
Hello everybody,
I am working on ETL side. My job is to load the data from Oracle table to flat file and from flat file to oracle table using ETL tool Informatica. My flat files are fixed width. In the first phase, it is loading 66351 records into data file through tool. When I checked through... (1 Reply)
Hi ,
I am trying to execute the following script.
#!/bin/sh
find . -name "common.log.diff"
if ; then
cp common.log common.log.diff
diff common.log common.log.diff > DIFFERENCE.log
cp common.log common.log.diff
grep "ERROR" DIFFERENCE.log
if ; then
echo "1"
else
echo "0"
fi... (5 Replies)
I have a new SAN (Fujitsu Eternus 2000) and am trying to setup a veritas cluster on it, however veritas does not see all of the vluns I have exposed to the box. The OS does see them though. I have seen a lot of post about this, but it seems they are about people having just the opposite problem... (0 Replies)
I am running a sql session within a shell script. Later I am performing some validations on the value coming from the sql session.
The problem is that, the value I am getting from sql session have an extra white space at the begining(I am actually, assigning the outcome of the sql session to a... (5 Replies)
Hi,
I have a sun 440, it already has LUN's configured with MPXIO.
I just had more LUNS added, I did devfsadm and cfgadm -al, and they're showing up twice in "Format". :confused:
There are no new fiber cables or HBA's involved, same physical setup, just adding LUNS.
Aren't they... (0 Replies)
Hi,
I've noticed that mpathadm states that one of our luns has no active paths:
/dev/rdsk/c6t60000970000298700009533031324333d0s2
Total Path Count: 4
Operational Path Count: 4
/dev/rdsk/c6t60000970000298700009533031333037d0s2
... (3 Replies)
Hello
I am working on one script where I am trying to display all the directories which is inside the workspace but somehow it is giving me weird output and this is occurring only with one directory other also having the result.html file inside the directory.
for i in `ls -1 | egrep -iv... (2 Replies)
Hi All
I am trying to perform the below operation -count=`cat abc.txt | wc -l`
echo$count
5
Head=Start"$DATE"00000"$count"File
echo $HEAD
START15020300000 5File
There is a space coming before 5 which is not needed . How to ignore that . (4 Replies)
Gents,
I did a small scritp called make_file
It read file1.txt file and generate an output as attached.. But the script is showing more extra information not needed.
I have attached the output file as desired.
Could you please help to fix this scrip to get the correct output
Thanks... (4 Replies)
Discussion started by: jiam912
4 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)