RSINFOMINDS: 04/01/2012

About Us

RSInfoMinds, a web based IT Training and Consultancy firm. It is established with high dreams in training people in IT Infrastructure Field. We provide Online and Class Room training in various fields of IT Infrastructure Management.

Join Us: http://www.facebook.com/RSInfoMinds

Mail Us: rsinfominds@gmail.com

Twitter: @RSInfoMinds

We are specialized in the below courses:

Redhat Linux Admin Redhat Linux Cluster

Redhat Virutualization IBM AIX Admin

IBM AIX Virtualization IBM AIX Cluster

HP Unix Admin HP Unix Cluster

HP Unix Virtualization Shell Scripting

Veritas Volume Manager Veritas Cluster

Oracle Core DBA VMWare

We provide training in such a way, So that you get in depth knowledge on the Courses you look for.

And we ensure you are very confident from each and every Techincal aspect that the IT Industry needs and expects from you.

We also conduct Workshops on the latest technology and the real time faculties sharing their work experiences to make you the best.

Sunday 22 April 2012

VG Configuration and Restore in HP UX

This posts shows how to take backup of a volume group configuration and restoring.

# cd /etc/lvmconf/<vgname> : The directory by default holds the backup of all the volume group configurations.

The volume group configuration is taken whenever LVM commands are applied on the volume group.

The configuration files are always stored with the ".conf" extension.

# vgcfgbackup -f <filename.conf> <volume_group> : Command to take back up of the volume group.

# vgcfgrestore -f <filename.conf> </dev/rdsk/c#t#d#> : Command to restore the volume group configuration on a physical volume.

The above process is applied, during a disk replacement activity. When a faulty disk is replaced in a volume group, instead of mirroring the data on a new disk we simply apply the configuration file and execute "# vgsync" command. This applies the configuration on the new disk.

Thursday 19 April 2012

Hi All, Its Time To Navigate Veritas Volume Manager.

Monday 16 April 2012

Software Management in HPUX

The software management in HP UX is divided as Depot, Bundle, Product and Fileset.

# swlist -l depot : Command shows the depots on the machine.

# swlist -l bundle : Command shows the bundle on the machine.

# swlist -l prodcut : Command shows the product on the machine.

# swlist -l fileset : Command shows the fileset on the machine.

# swlist -l patch : Command shows the patches on the machine.

# swlist -l bundle/product/fileset -a revision : Command to view the revision on the bundle/product/fileset

# swlist -l depot/bundle/product/fileset -a software_spec : Command to view the version, revision, arch, vendor details.

# cd /var/adm/sw : Location of all the software logs on the machine.

Thursday 12 April 2012

LUN Information in HPUX

SCSIMGR: SCSI Manager is an utility to get the LUN information from the server.

# scsimgr -h get_attr : Command to get basic attributes of all SCSI Devices.

# scsimgr -v get_stat : Command to get global statistics.

# scsimgr get_stat -D /dev/rdisk/disk0 : Command to get statistics of a particular disk.

# scsimgr get_stat -D /dev/rdisk/disk0 all_lpt : Command to get all the LUN path for a disk.

# scsimgr -v get_stat -H 0/4/1/0.0x60060b000014f45a0001000000000011 : Command to get statistics for a Hardware path.

Monday 2 April 2012

Unmirrorvg Cont...

Original Copy : hdisk4
1nd Copy : hdisk3
2nd Copy : hdisk5

Now I unmirror the 2nd copy of the volume group "data".

bash-3.2# lsvg -p data
data:
PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION
hdisk4 active 1084 1019 217..152..216..217..217
hdisk3 active 1084 1019 217..152..216..217..217
hdisk5 active 542 477 109..43..108..108..109
bash-3.2# unmirrorvg -c 2 data
bash-3.2# lsvg -p data
data:
PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION
hdisk4 active 1084 1019 217..152..216..217..217
hdisk3 active 1084 1019 217..152..216..217..217
hdisk5 active 542 542 109..108..108..108..109

Unmirrorvg Cont...

Now, we discuss the mirroring using 3 disks.

bash-3.2# lsvg -p data
data:
PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION
hdisk4 active 1084 1019 217..152..216..217..217
hdisk3 active 1084 1084 217..217..216..217..217
hdisk5 active 542 542 109..108..108..108..109

hdisk4 : Original Copy.

bash-3.2# mirrorvg -c 3 data hdisk3 hdisk5

0516-1125 mirrorvg: Quorum requirement turned off, varyoff and varyon

volume group for this to take effect.

bash-3.2# lsvg -p data

data:

PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION

hdisk4 active 1084 1019 217..152..216..217..217

hdisk3 active 1084 1019 217..152..216..217..217

hdisk5 active 542 477 109..43..108..108..109

bash-3.2# lsvg -l data

data:

LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINT

loglv01 jfs2log 1 3 3 open/syncd N/A

fslv01 jfs2 64 192 3 open/syncd /data

bash-3.2#

So, as per the command executed. I can say,

hdisk4: Original.

hdisk3: 1st mirror.

hdisk5: 2nd mirror.

Now, will try this.

bash-3.2# lsvg -p data

data:

PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION

hdisk4 active 1084 1019 217..152..216..217..217

hdisk3 active 1084 1019 217..152..216..217..217

hdisk5 active 542 477 109..43..108..108..109

bash-3.2# unmirrorvg -c 2 data

bash-3.2# lsvg -p data

data:

PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION

hdisk4 active 1084 1019 217..152..216..217..217

hdisk3 active 1084 1019 217..152..216..217..217

hdisk5 active 542 542 109..108..108..108..109

bash-3.2#

The above command proves that the 2nd copy was in hdisk5 and its removed.

Now we will mirror it back.

bash-3.2# mirrorvg data hdisk5

0516-1118 mirrorvg: No logical volumes in volume group to mirror.

0516-1200 mirrorvg: Failed to mirror the volume group.

bash-3.2# lsvg -l data

data:

LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINT

loglv01 jfs2log 1 2 2 open/syncd N/A

fslv01 jfs2 64 128 2 open/syncd /data

The above command failed to mirror. But the command is correct.

But it worked when I executed like this,

bash-3.2# mirrorvg -c 3 data hdisk5

bash-3.2# lsvg -l data

data:

LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINT

loglv01 jfs2log 1 3 3 open/syncd N/A

fslv01 jfs2 64 192 3 open/syncd /data

bash-3.2# lsvg -p data

data:

PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION

hdisk4 active 1084 1019 217..152..216..217..217

hdisk3 active 1084 1019 217..152..216..217..217

hdisk5 active 542 477 109..43..108..108..109

This needs an explanation...

Umirrorvg Command

This post shows what really the unmirrorvg command does:

bash-3.2# lsvg -p data

data:
PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION
hdisk4 active 1084 1084 217..217..216..217..217
hdisk3 active 1084 1019 217..152..216..217..217
hdisk5 active 542 542 109..108..108..108..109

bash-3.2# lspv -l hdisk5
bash-3.2# lspv -l hdisk4
bash-3.2# lspv -l hdisk3
hdisk3:
LV NAME LPs PPs DISTRIBUTION MOUNT POINT
loglv01 1 1 00..01..00..00..00 N/A
fslv01 64 64 00..64..00..00..00 /data

The above output shows that I have a volume group called "data" which belongs to the physical volume "hdisk3" that hold some data in it across the mount point "/data"

bash-3.2# mirrorvg data hdisk4 /* Mirrored Data VG on hdisk4"

0516-1125 mirrorvg: Quorum requirement turned off, varyoff and varyon

volume group for this to take effect.

bash-3.2# lsvg -p data

data:

PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION

hdisk4 active 1084 1019 217..152..216..217..217

hdisk3 active 1084 1019 217..152..216..217..217

hdisk5 active 542 542 109..108..108..108..109

bash-3.2#

Now,

hdisk3 holds Original Copy.

hdisk4 holds 1st mirror Copy.

Now I go ahead to remove the Original copy from hdisk3.

bash-3.2# unmirrorvg data hdisk3

0516-1133 unmirrorvg: Quorum requirement turned on, varyoff and varyon

volume group for this to take effect.

bash-3.2# lsvg -l data

data:

LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINT

loglv01 jfs2log 1 1 1 open/syncd N/A

fslv01 jfs2 64 64 1 open/syncd /data

bash-3.2# lsvg -p data

data:

PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION

hdisk4 active 1084 1019 217..152..216..217..217

hdisk3 active 1084 1084 217..217..216..217..217

hdisk5 active 542 542 109..108..108..108..109

bash-3.2#

Now I again do mirroring on hdisk5.

So,

hdisk4 holds Original Copy (former 1st mirror copy).

hdisk4 holds mirror copy.

bash-3.2# lsvg -l data

data:

LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINT

loglv01 jfs2log 1 2 2 open/syncd N/A

fslv01 jfs2 64 128 2 open/syncd /data

bash-3.2# lsvg -p data

data:

PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION

hdisk4 active 1084 1019 217..152..216..217..217

hdisk3 active 1084 1084 217..217..216..217..217

hdisk5 active 542 477 109..43..108..108..109

bash-3.2# lspv -l hdisk5

hdisk5:

LV NAME LPs PPs DISTRIBUTION MOUNT POINT

loglv01 1 1 00..01..00..00..00 N/A

fslv01 64 64 00..64..00..00..00 /data

bash-3.2# lspv -l hdisk4

hdisk4:

LV NAME LPs PPs DISTRIBUTION MOUNT POINT

loglv01 1 1 00..01..00..00..00 N/A

fslv01 64 64 00..64..00..00..00 /data

bash-3.2# lspv -l hdisk3

bash-3.2#

So, we I have only one mirror copy on "hdisk5".

So, I unmirror the volume group.

bash-3.2# unmirrorvg data

0516-1133 unmirrorvg: Quorum requirement turned on, varyoff and varyon

volume group for this to take effect.

bash-3.2# lsvg -l data

data:

LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINT

loglv01 jfs2log 1 1 1 open/syncd N/A

fslv01 jfs2 64 64 1 open/syncd /data

bash-3.2# lsvg -p data

data:

PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION

hdisk4 active 1084 1019 217..152..216..217..217

hdisk3 active 1084 1084 217..217..216..217..217

hdisk5 active 542 542 109..108..108..108..109

bash-3.2#

So, the data on the hdisk5 has been removed.