recovery

[himacs]

Hi Admins,

I am going to reboot B.11.23 server as the part of patch deployment.

The server is with mirrored disks and has no ignite backup.
As the recovery option what i am planning is to remove secondary disk from the server before reboot and insert again if server does not come up with primary disk after reboot.

Please tell me is that feasible? and if yes,what are the steps i have to follow.

Regards
himacs

[Horia Chirculescu]

Hello,

Would be great if you would have in handy a spare disk to make first a mirror image on it (in order to boot up the server with both mirrored disks on-line)

Horia.

[Prasanth Thomas]

Hi,

I think better you have to take the backup before doing any upgradation actovty on production server. Its very easy to install and configure the ignite on hp-ux server.
Please find the below links.

http://docs.hp.com/en/5992-5037/5992-5037.pdf

http://forums13.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1265181350697+28353475&threadId=1283820

Regards,
Prasanth Thomas.

[R.K. #]

Hi Himacs,

You can also go with DRD.

[Michal Kapalka (mikap)]

hi,

i think you don't need to do it, because if the system is mirrored, and you already patched it, so the applied patches are on both disk.

and if you remove the disk, when the OS is runneing, you could make the second disk incostintent, so maybe the system will be not able boot form this disk.

sorry but patching of the system without ingnite backup is for me not understable.

mikap

[Johnson Punniyalingam]

Please tell me is that feasible? and if yes,<<<

feasible for your case, tells how confident you are and How critical is the Server, if you don't have Ignite Backup ?

"precaution is Better than Cure."

Ok when you talk about feasible? Yes it can be done

Make sure you can boot your server Using your secondary mirror disk, before you proceed to patching.

Break mirror of your secondary disk

1) Remove lvol mirrors:(lvol 1 ,2,3,4 ..etc)
# lvreduce -m 0 /dev/vg00/lvol2 /dev/dsk/c2t6d0

2) # vgreduce /dev/vg00 /dev/dsk/c2t6d0 -> Sec disk

de-attach your "Sec-disk" and boot from your primary disk

[R.K. #]

Hi again,

Have you already patched the system or yet to do it?
If yes and your server already rebooted then everythign is fine.

Else, use DRD as you do not have ignite.

[himacs]

Hi All,

Thanks for the responses.

i am planning to follow below steps.

1.Remove sec disk while server is up
2.reboot the server
3.apply patch
4.reboot the server with pri disk
5.If server is not coming up,shutdown the server ,inert sec disk and boot with sec
6.If everything is fine with primary,insert sec disk later
7.And pri will syc with sec automatically,so all the changes done in pri will apply in sec.

About the backup ,i can only take network ignite backup - make_net_recovery

I cant think abt DRD


So please ur suggestions on above points

Regards
himacs

[Johnson Punniyalingam]

Once "Your Patching Activity" completed.

you can refer to "Good Disk Gone Bad" PDF file and remirror you "Secondary Disk"

[Johnson Punniyalingam]

>>About the backup ,i can only take network ignite backup - make_net_recovery<<<

YES, At least you should do that, before patching Your Server

[himacs]

Hi Johnson,

m going to remove the sec without breaking the mirror.

I want to know while booting which options we have to select in efi boot manager to boot using sec disk



regards
himacs

[Johnson Punniyalingam · Accepted solution]

>>>m going to remove the sec without breaking the mirror.>>>>

Why ??? -> Hope Server will complaint

I want to know while booting which options we have to select in efi boot manager to boot using sec disk

Check below Thread for more information
http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1252838

[R.K. #]

Hi..

>> m going to remove the sec without breaking the mirror.
>> [..] to boot using sec disk [..]

How can boot from Sec if you are removing it?


To find boot disks:
Shell> map â r â fs â b

To boot from fs0:
Shell> fs0:
fs0:>hpux -lq

[R.K. #]

Sorry for junk chars...

To find boot disks:
Shell> map -Â Â r -Â Â fs -Â Â b

[R.K. #]

Ooh...my fault.

It is:
Shell> map -r -fs -b

[Johnson Punniyalingam]

>>>m going to remove the sec without breaking the mirror.>>>>

You need to properly remove "Secndory Disk" information from the OS level" by "lvextend -m 0" and vgreduce I believe later you cannot put back the disk,

[himacs]

Hi R.K,

Shell> map -r -fs -b >>

will it display sec disk path like fs1: ?

regards
himacs

[Prasanth Thomas]

HI,

i think better you can split the lvs instead of lvreduce. So it wont make any impact on second disk. If anything goes wrong we can rebulid it by lvmerge command.
Please let me know why did not you plan for ignite recvoery image, as i mentioned earlier its very easy and wont take more than 2 hours. Its very neccessary to rebulid the system when the server got crash.

Regards,
Prasanth Thomas.

[Prasanth Thomas]

Shell> map -r will show the mapped devices from there you can identify the sec boot disk by using H/W path.

for make_net_recovery you have to verify the lan card whether it is lan boot supported. You can verify it by using server user guide or let me know the server model number.

regards,
Prasanth Thomas.

[himacs]

Hi Prashanth,

Thanks for your concerns.Please find the server details

ia64 hp server rx3600
DEH40200047


Regards
Pavan

[R.K. #]

Hi Again,

Shell> map -r -fs -b

Suppose you find fs1 (this might be your secondary disk).
Shell>fs1:
fs1:> dir
fs1:> ls
You should see "EFI"
fs1:> cd efi
fs1\efi> dir
You should see "HPUX.EFI"

Now, to boot from this disk:
fs1\efi> hpux.efi

So, if you find hpux.efi, that means this is a boot disk.

[himacs]

HI All,

Wish me luck .. m going to do it today


Regards
himacs

[Prasanth Thomas]

HI Himacs,

I think this server is lan boot supported and for more conformation please send me the o/p of
1. #ioscan -fnC lan
2. #lanscan

Regards,
Prasanth Thomas.

[johnsonpk]

>>>i am planning to follow below steps.

1.Remove sec disk while server is up ###(Are yo sure that ur sec disk is bootable)
2.reboot the server
3.apply patch
4.reboot the server with pri disk
5.If server is not coming up,shutdown the server ,inert sec disk and boot with sec ###( what if the sec hdd is also not bootable ?have you checked the sec hdd by booting server from that hdd ?)
6.If everything is fine with primary,insert sec disk later
7.And pri will syc with sec automatically,so all the changes done in pri will apply in sec.


I would follow the below steps

1) Check the vg is in sync or not
#vgsync vg00
2)verify quarum disabled
# efi_cp -d /dev/rdsk/c1t0d0s1 -u /EFI/HPUX/AUTO . ;cat AUTO (check it for both disk in vg00)
it should be " boot vmunix -lq "
3) check from which disk the server is booted currently ( you check in syslog )
4)shutdown server and remove the disk that you got from step 3 (the disk from whcih server booted succesfully last time)
5)boot server,Apply patch and reboot
6)if everything is fine insert the other disk ,ioscan ,insf-eC disk, vgchange -a y vg00, vgsync vg00,

[johnsonpk]

Johnson>> You need to properly remove "Secndory Disk" information from the OS level" by "lvextend -m 0" and vgreduce I believe later you cannot put back the disk,

Johnson will it be same as running vg00 without mirror, what will happen if the current disk /os is corrupted ?? you will end up having one corrupted os disk and a free disk :-(