cancel
Showing results for 
Search instead for 
Did you mean: 

Mirroring in HP-UX 11.11

SOLVED
Go to solution
Gordana
Occasional Advisor

Mirroring in HP-UX 11.11

Hello,

Happy New Year to you all!

I am new to HP-UX and this is my first question on this forum so I hope I will not sound silly.

I need to increase size of two filesystems:

/relay from 600 to 800 GB
/cucc2 from 80 to 130 GB

Our environment includes the following:
1. Server HP RP4440 with HP-UX 11.11
2. disks on EVA4000 (Command View 5)

That pretty much means that I could not dynamically increase size of my LVs.
This is the plan that I have so far:
1. add more disks (we borroved 8 146GB disks) to VG
2. mirror original small LVs to borrowed disks
3. unmirror original LVs
4. remove original LVs
5. recreate LV’s with bigger space
6. mirror LVs again
7. unmirror LVs on borroved disks
8. remove LVs from borrowed disks
9. remove borrowed disks

(I included more detailed plan in here as well for your review.)
The thing that is confusing to me is in regards of output of insf command and the way how server is seeing those disks/paths. If I understand correctly I am seeing all 4 paths for each disk (considering that 2 disks are assign to my server)?

Could you please check my list and respond to me with your findings.

Thank you all for your time.


Here are some information about our server:

# ioscan -fnC disk
Class I H/W Path Driver S/W State H/W Type Description
==========================================================================
disk 0 0/0/3/0.0.0.0 sdisk CLAIMED DEVICE _NEC DVD+-RW ND-6650A
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0
disk 1 0/1/1/0.1.0 sdisk CLAIMED DEVICE HP 36.4GST336754LC
/dev/dsk/c2t1d0 /dev/rdsk/c2t1d0
disk 2 0/1/1/1.0.0 sdisk CLAIMED DEVICE HP 36.4GST336754LC
/dev/dsk/c3t0d0 /dev/rdsk/c3t0d0
disk 4 0/4/2/0.1.6.0.0.0.1 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c8t0d1 /dev/rdsk/c8t0d1
disk 7 0/4/2/0.1.6.0.0.0.2 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c8t0d2 /dev/rdsk/c8t0d2
disk 11 0/4/2/0.1.6.0.0.0.3 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c8t0d3 /dev/rdsk/c8t0d3
disk 15 0/4/2/0.1.6.0.0.0.4 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c8t0d4 /dev/rdsk/c8t0d4
disk 20 0/4/2/0.1.6.0.0.0.5 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c8t0d5 /dev/rdsk/c8t0d5
disk 24 0/4/2/0.1.6.0.0.0.6 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c8t0d6 /dev/rdsk/c8t0d6
disk 27 0/4/2/0.1.6.0.0.0.7 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c8t0d7 /dev/rdsk/c8t0d7
disk 31 0/4/2/0.1.6.0.0.1.0 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c8t1d0 /dev/rdsk/c8t1d0
disk 35 0/4/2/0.1.6.0.0.1.1 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c8t1d1 /dev/rdsk/c8t1d1
disk 39 0/4/2/0.1.6.0.0.1.2 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c8t1d2 /dev/rdsk/c8t1d2
disk 43 0/4/2/0.1.6.0.0.1.3 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c8t1d3 /dev/rdsk/c8t1d3
disk 5 0/4/2/0.1.7.0.0.0.1 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c9t0d1 /dev/rdsk/c9t0d1
disk 10 0/4/2/0.1.7.0.0.0.2 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c9t0d2 /dev/rdsk/c9t0d2
disk 14 0/4/2/0.1.7.0.0.0.3 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c9t0d3 /dev/rdsk/c9t0d3
disk 18 0/4/2/0.1.7.0.0.0.4 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c9t0d4 /dev/rdsk/c9t0d4
disk 22 0/4/2/0.1.7.0.0.0.5 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c9t0d5 /dev/rdsk/c9t0d5
disk 26 0/4/2/0.1.7.0.0.0.6 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c9t0d6 /dev/rdsk/c9t0d6
disk 30 0/4/2/0.1.7.0.0.0.7 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c9t0d7 /dev/rdsk/c9t0d7
disk 33 0/4/2/0.1.7.0.0.1.0 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c9t1d0 /dev/rdsk/c9t1d0
disk 38 0/4/2/0.1.7.0.0.1.1 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c9t1d1 /dev/rdsk/c9t1d1
disk 42 0/4/2/0.1.7.0.0.1.2 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c9t1d2 /dev/rdsk/c9t1d2
disk 46 0/4/2/0.1.7.0.0.1.3 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c9t1d3 /dev/rdsk/c9t1d3
disk 3 0/5/2/0.1.6.0.0.0.1 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c10t0d1 /dev/rdsk/c10t0d1
disk 8 0/5/2/0.1.6.0.0.0.2 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c10t0d2 /dev/rdsk/c10t0d2
disk 12 0/5/2/0.1.6.0.0.0.3 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c10t0d3 /dev/rdsk/c10t0d3
disk 16 0/5/2/0.1.6.0.0.0.4 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c10t0d4 /dev/rdsk/c10t0d4
disk 19 0/5/2/0.1.6.0.0.0.5 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c10t0d5 /dev/rdsk/c10t0d5
disk 23 0/5/2/0.1.6.0.0.0.6 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c10t0d6 /dev/rdsk/c10t0d6
disk 28 0/5/2/0.1.6.0.0.0.7 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c10t0d7 /dev/rdsk/c10t0d7
disk 32 0/5/2/0.1.6.0.0.1.0 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c10t1d0 /dev/rdsk/c10t1d0
disk 36 0/5/2/0.1.6.0.0.1.1 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c10t1d1 /dev/rdsk/c10t1d1
disk 41 0/5/2/0.1.6.0.0.1.2 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c10t1d2 /dev/rdsk/c10t1d2
disk 45 0/5/2/0.1.6.0.0.1.3 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c10t1d3 /dev/rdsk/c10t1d3
disk 6 0/5/2/0.1.7.0.0.0.1 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c11t0d1 /dev/rdsk/c11t0d1
disk 9 0/5/2/0.1.7.0.0.0.2 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c11t0d2 /dev/rdsk/c11t0d2
disk 13 0/5/2/0.1.7.0.0.0.3 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c11t0d3 /dev/rdsk/c11t0d3
disk 17 0/5/2/0.1.7.0.0.0.4 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c11t0d4 /dev/rdsk/c11t0d4
disk 21 0/5/2/0.1.7.0.0.0.5 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c11t0d5 /dev/rdsk/c11t0d5
disk 25 0/5/2/0.1.7.0.0.0.6 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c11t0d6 /dev/rdsk/c11t0d6
disk 29 0/5/2/0.1.7.0.0.0.7 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c11t0d7 /dev/rdsk/c11t0d7
disk 34 0/5/2/0.1.7.0.0.1.0 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c11t1d0 /dev/rdsk/c11t1d0
disk 37 0/5/2/0.1.7.0.0.1.1 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c11t1d1 /dev/rdsk/c11t1d1
disk 40 0/5/2/0.1.7.0.0.1.2 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c11t1d2 /dev/rdsk/c11t1d2
disk 44 0/5/2/0.1.7.0.0.1.3 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c11t1d3 /dev/rdsk/c11t1d3

# strings /etc/lvmtab
/dev/vg00
/dev/dsk/c2t1d0
/dev/dsk/c3t0d0
/dev/vg01
/dev/dsk/c8t0d4
/dev/dsk/c8t0d3
/dev/dsk/c8t0d1
/dev/dsk/c8t0d6
/dev/vg03
/dev/dsk/c8t0d7
/dev/vg02
/dev/dsk/c8t0d5
/dev/dsk/c8t0d2
/dev/vg04
D= x
/dev/dsk/c8t1d0
/dev/dsk/c8t1d1


# lvdisplay -v /dev/vg02/lvol1
--- Logical volumes ---
LV Name /dev/vg02/lvol1
VG Name /dev/vg02
LV Permission read/write
LV Status available/syncd
Mirror copies 0
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 600000
Current LE 37500
Allocated PE 37500
Stripes 0
Stripe Size (Kbytes) 0
Bad block on
Allocation strict
IO Timeout (Seconds) default

--- Distribution of logical volume ---
PV Name LE on PV PE on PV
/dev/dsk/c8t0d5 37500 37500

# lvdisplay -v /dev/vg02/lvol2
--- Logical volumes ---
LV Name /dev/vg02/lvol2
VG Name /dev/vg02
LV Permission read/write
LV Status available/syncd
Mirror copies 0
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 80000
Current LE 5000
Allocated PE 5000
Stripes 0
Stripe Size (Kbytes) 0
Bad block on
Allocation strict
IO Timeout (Seconds) default

--- Distribution of logical volume ---
PV Name LE on PV PE on PV
/dev/dsk/c8t0d5 895 895
/dev/dsk/c8t0d2 4105 4105

# diskinfo /dev/rdsk/c8t1d2
SCSI describe of /dev/rdsk/c8t1d2:
vendor: HP
product id: HSV200
type: direct access
size: 838860800 Kbytes
bytes per sector: 512

# diskinfo /dev/rdsk/c8t1d3
SCSI describe of /dev/rdsk/c8t1d3:
vendor: HP
product id: HSV200
type: direct access
size: 136314880 Kbytes
bytes per sector: 512

# diskinfo /dev/rdsk/c9t1d2
SCSI describe of /dev/rdsk/c9t1d2:
vendor: HP
product id: HSV200
type: direct access
size: 838860800 Kbytes
bytes per sector: 512

# diskinfo /dev/rdsk/c9t1d3
SCSI describe of /dev/rdsk/c9t1d3:
vendor: HP
product id: HSV200
type: direct access
size: 136314880 Kbytes
bytes per sector: 512

# diskinfo /dev/rdsk/c10t1d2
SCSI describe of /dev/rdsk/c10t1d2:
vendor: HP
product id: HSV200
type: direct access
size: 838860800 Kbytes
bytes per sector: 512
# diskinfo /dev/rdsk/c10t1d3
SCSI describe of /dev/rdsk/c10t1d3:
vendor: HP
product id: HSV200
type: direct access
size: 136314880 Kbytes
bytes per sector: 512

# diskinfo /dev/rdsk/c11t1d2
SCSI describe of /dev/rdsk/c11t1d2:
vendor: HP
product id: HSV200
type: direct access
size: 838860800 Kbytes
bytes per sector: 512

# diskinfo /dev/rdsk/c11t1d3
SCSI describe of /dev/rdsk/c11t1d3:
vendor: HP
product id: HSV200
type: direct access
size: 136314880 Kbytes
bytes per sector: 512

# vgdisplay -v /dev/vg02|egrep 'LV Name|Used PV'
LV Name /dev/vg02/lvol1
Used PV 1
LV Name /dev/vg02/lvol2
Used PV 2


REQUIRED STEPS :

New disks (1168 GB) assigned on EVA4000 for HP-UX server:

# insf
insf: Installing special files for sdisk instance 39 address 0/4/2/0.1.6.0.0.1.2
insf: Installing special files for sdisk instance 43 address 0/4/2/0.1.6.0.0.1.3
insf: Installing special files for sdisk instance 42 address 0/4/2/0.1.7.0.0.1.2
insf: Installing special files for sdisk instance 46 address 0/4/2/0.1.7.0.0.1.3
insf: Installing special files for sdisk instance 41 address 0/5/2/0.1.6.0.0.1.2
insf: Installing special files for sdisk instance 45 address 0/5/2/0.1.6.0.0.1.3
insf: Installing special files for sdisk instance 40 address 0/5/2/0.1.7.0.0.1.2
insf: Installing special files for sdisk instance 44 address 0/5/2/0.1.7.0.0.1.3

*** CROSSREFERENCING NOTE for me ***

sdisk instance 39 address 0/4/2/0.1.6.0.0.1.2 /dev/dsk/c8t1d2
sdisk instance 43 address 0/4/2/0.1.6.0.0.1.3 /dev/dsk/c8t1d3
sdisk instance 42 address 0/4/2/0.1.7.0.0.1.2 /dev/dsk/c9t1d2
sdisk instance 46 address 0/4/2/0.1.7.0.0.1.3 /dev/dsk/c9t1d3
sdisk instance 41 address 0/5/2/0.1.6.0.0.1.2 /dev/dsk/c10t1d2
sdisk instance 45 address 0/5/2/0.1.6.0.0.1.3 /dev/dsk/c10t1d3
sdisk instance 40 address 0/5/2/0.1.7.0.0.1.2 /dev/dsk/c11t1d2
sdisk instance 44 address 0/5/2/0.1.7.0.0.1.3 /dev/dsk/c11t1d3


*********** MAKE SURE WE HAVE A VALID BACKUP! ****************

1. Initialize disks for use with LVM:

# pvcreate –f /dev/dsk/c8t1d2

# pvcreate –f /dev/dsk/c8t1d3

2. Add new disks to volume group vg02:


# vgextend vg02 /dev/dsk/c8t1d2

# vgextend vg02 /dev/dsk/c8t1d3

Check if everything is Ok:

# vgdisplay –v /dev/vg02 | grep “PV name”

It should return output like this:

PV Name /dev/dsk/c8t0d5
PV Name /dev/dsk/c8t0d2
PV Name /dev/dsk/c8t1d2
PV Name /dev/dsk/c8t1d3

3. Create mirror copy of logical volumes in VG02 (the one that contains /cucc2 and /relay filesystems)

# lvextend –m 1 /dev/vg02/lvol1 /dev/dsk/c8t1d2

# lvextend –m 1 /dev/vg02/lv0l2 /dev/dsk/c8t1d3
Use pvdisplay -v to the order of the logical volumes on the mirror disk to insure they are in the correct order.
# pvdisplay -v
Display volume group vg02:
# vgdisplay -v vg02
Before mirroring it was like this:

# vgdisplay -v /dev/vg02|egrep 'LV Name|Used PV'
LV Name /dev/vg02/lvol1
Used PV 1
LV Name /dev/vg02/lvol2
Used PV 2

After mirroring numbers of ‘Used PV’s should be increased by 1:

# vgdisplay -v /dev/vg02|egrep 'LV Name|Used PV'


4. Break the mirror of VG02 (from 2 original disks)

# lvreduce -m 0 /dev/vg02/lvol1 /dev/dsk/c8t0d5
# lvreduce -m 0 /dev/vg02/lvol2 /dev/dsk/c8t0d2
# lvreduce –m 0 /dev/vg02/lvol2 /dev/dsk/c8t0d5

Then check Volume Group:
# vgdisplay -v vg02

5. Reduce borrowed disks from VG02 (execute command for 2 original disks).

# vgreduce /dev/vg02 /dev/dsk/c8t0d5

# vgreduce /dev/vg02 /dev/dsk/c8t0d2

Then check Volume Group vg02 to see the updated g02 volume group information:
# vgdisplay -v vg02

Remove original disks:

# pvremove /dev/rdsk/c8t0d5

# pvremove /dev/rdsk/c8t0d2

Now production data are stored on borrowed disks - we need to move data again on our disks by doing following steps:

**** 2 Newly empty disks should be presented from EVA4000 to our Production server: one 800GB and one 130GB. ****

7. Add new disks
# pvcreate –f /dev/dsk/

# pvcreate –f /dev/dsk/

8. Add new disks to volume group vg02:

# vgextend vg02 /dev/dsk/c8t1d2

# vgextend vg02 /dev/dsk/c8t1d3

Check if everything is Ok:

# vgdisplay –v /dev/vg02 | grep “PV name”

Output should return 4 disks.

9. Mirror VG02

# lvextend –m 1 /dev/vg02/lvol1 /dev/dsk/

# lvextend –m 1 /dev/vg02/lv0l2 /dev/dsk/

Use pvdisplay -v to the order of the logical volumes on the mirror disk to insure they are in the correct order.

# pvdisplay –v /dev/dsk/

Display volume group vg02:

# vgdisplay -v vg02
# vgdisplay -v /dev/vg02|egrep 'LV Name|Used PV'

10. Break the mirror and release borrowed disks from VG02:

# lvreduce -m 0 /dev/vg02/lvol1 /dev/dsk/

# lvreduce -m 0 /dev/vg02/lvol2 /dev/dsk/

Then check Volume Group vg02 to see the updated g02 volume group information:

# vgdisplay -v vg02

# pvremove /dev/rdsk/

# pvremove /dev/rdsk/




7 REPLIES
sujit kumar singh
Honored Contributor

Re: Mirroring in HP-UX 11.11

Hi Gordana,

the 8 files that insf installs is one for exac path of the 2 disks. there are therefore 8 device files that are installed for the disks, u r correct and these device files are
/dev/dsk/c8t1d2
/dev/dsk/c9t1d2
/dev/dsk/c10t1d2
/dev/dsk/c11t1d2

and the corresponding raw dev files that is rdsk for one disk and

/dev/dsk/c8t1d3
/dev/dsk/c9t1d3
/dev/dsk/c10t1d3
/dev/dsk/c11t1d3

with the corresponding raw dev files fpr the other disk.

i have few questions to ask:

1)do u have online JFS on the system this u can check using the command #swlist -l product -l bundle | grep -i onlinejfs just let me know if u have that installed.


if u have OnlineJFS installed u can do within few minutes and that also u do not require the applications to be down or filesystems to be unmounted.


2)why r u twice mirroring the disks that is i if u have got enough amountof space given from the EVA here? u require (200 + 50 =250 GB Space from the Storage that is u shall need 2 *146 GB LUNs from the storage that u already have.So that is sufficient.
3)have u not got the enough downtime that u think that u have twice to perform the mirroring / because if u do not havve onlineJFS u will need to do this by unmounting the filesystems.

with the ONline JFS this can be done without a downtime and online.

u can do as following :: i am detailing the steps if u have do not have ONline JFS installed and what to so if OnlineJFS is there

a) Initialize disks for use with LVM:

# pvcreate â f /dev/dsk/c8t1d2

# pvcreate â f /dev/dsk/c8t1d3

Add new disks to volume group vg02:


b) # vgextend vg02 /dev/dsk/c8t1d2

# vgextend vg02 /dev/dsk/c8t1d3

c) #lvextend â L 819200 /dev/vg02/lvol1
This extends the lvol1 to 800 GB
d) # lvextend â L 133120 /dev/vg02/lvol2
This extends lvol2 to 130 GB

If u donâ t have Online JFS
e) #umount /relay
f) #umount /cucc2


Extend the Filesystems:

g) #extendfs /dev/vg02/lvol1
h) #extendfs /dev/vg02/lvol2

i) #mount /dev/vg02/lvol2 /cucc2
j) #mount /dev/vg02/lvol1 /relay


U R done. This will take a much smaller time but u need to unmount the file system after extending the LV because then only u can execute the extendfs to extend the filesystem.

Even if u dont have OnlineJFS lvextend, umount and extendfs shall take only minutes tp get the things done.


to be always on the safe side, u must have always have the backup of the Filesystems available with u .



Regards


Sujit




sujit kumar singh
Honored Contributor

Re: Mirroring in HP-UX 11.11

Actually i could not understand the purpose of mirroring twice ... can u Elaborate please


Sujit
Gordana
Occasional Advisor

Re: Mirroring in HP-UX 11.11

Hi Sujit,

Thank you for your time and responses. Yes, we have OnlineJFS - the reason for mirroring twice is because first mirror will be on borrowed disks (we have to return them after this). So by mirroring to borrowed disks I will save data, but then I need to recreate bigger LVs on our disks and mirror data back.

Otherwise your solution would be right option.

Thank you very much!

Gordana
Gordana
Occasional Advisor

Re: Mirroring in HP-UX 11.11

One more thing - maybe that will clear all confusion about double mirroring:

At this point we have only 400BG free space on OUR EVA disks. Although at first we tried to increase space from EVA4000, that space is not visible on server side. HP explained to us that the reason is our level of HP-UX. So we ended up with 250 GB of lost space (space can not be released on EVA side - again because of our Command View version). To release that space we need to remove LVs and recreate them. The only way for us was to borrow disk and mirror twice - at least that we were told.

Any simplier and possible idea would be appreciated.

Thanks again.
sujit kumar singh
Honored Contributor

Re: Mirroring in HP-UX 11.11

hi

then in that case ur plan of action seems to be OK.
BUt remember that using lvextend for mirroring that is using #lvextend -m 1 only creates the Mirror of that LV but does not increase the size of the same.
if u wish to increase the Size u will again need to do an lvextend -L and do a subsequent #fsadm -b

Its nice that u have ONlineJFS installed on ur system which helps u doing without disruption in work.


Sujit
sujit kumar singh
Honored Contributor
Solution

Re: Mirroring in HP-UX 11.11

one more note:


1)for pvcreate u need to use the raw device files instead of the Block device files
that means

pvcreate -f /dev/rdsk/c8t1d3 needs to be done.

for a PV that has multiple paths u need to do pvcreate on only one of the paths.

Accidently if u run a pvcreate -f on any of the Alternate paths ur data will be gone, so be careful dealing with multipathed Devices.



2)lvextemd -m 1 to mirror is surely going to take a long time for this 600 GB sized LV.

3)be careful of the device paths that ur HP system Sees for the LUNs from the EVAs as assigned and deassigned, make sure that u run diskinfo and ur basic tools to identify the LUNs properly.
4)why do not u take advantage of the Alternate Path Feature that provides redundancy of the paths?


for example when u have created a VG using the two disks say /dev/dsk/c8t1d2 /dev/dsk/c8t1d3
#vgextend /dev/vg02 /dev/dsk/c8t1d2 /dev/dsk/c8t1d3

To add the remaining PV paths as Alternate Links to the VG /dev/vg02 u need
#vgextend /dev/vg02 /dev/dsk/c9t1d2 /dev/dsk/c10t1d2 /dev/dsk/c11t1d2 /dev/dsk/c9t1d2 /dev/dsk/c10t1d2 /dev/dsk/c11t1d2

or u can use some multipathing S/W like Securepath in this case to take care of Multipathing as wellas Load Balancing.


Sujit
Gordana
Occasional Advisor

Re: Mirroring in HP-UX 11.11

Sujit,

You were great help to me today. I inherited that server without any documentation. As usual?

As I said I am new to HP and not familiar how it is handling multipaths. You explained to me what I need to know at this point. After this I will add alternate paths to vg02 for sure.


Thank you very much for all your time and responses.