Operating System - HP-UX
1752781 Members
6694 Online
108789 Solutions
New Discussion юеВ

Re: Ignite restoration problem

 
M.sureshkumar
Regular Advisor

Ignite restoration problem

Hi All,

When i tried to restore the ignite bakup from tape, i am getting the following error.

Error:

WARNING: Command: "/sbin/ioinit -f /tmp/ioinit.in" failed. Instance number
assignments for devices of class "ext_bus" may not be assigned
correctly.te/data/scripts/os_arch_post_c".
* Run all specified post-configure scripts..
* Executing user specified script: .post_c).
"/opt/ignite/data/scripts/os_arch_post_c".
* Running in recovery mode (os_arch_post_c).the volume group
* Executing user specified commands.disk in the volume group
Couldn't open physical volume "/dev/rdsk/c2t0d1":v/vgswap".
Verification of unique LVM disk id on each disk in the volume groupmtab" file.
/dev/vgswap failed.uration for /dev/vg00 has been saved in /etc/lvmconf/vg00.con
Beginning the import process on Volume Group "/dev/vgswa
vgchange: Volume group "/dev/vgswap" does not exist in the "/etc/lvmtab" file.
Volume Group configuration for /dev/vg00 has been saved in /etc/lvmconf/vg00.con
/vgswap".
fvgswap".Executing the commands "
vgcfgbackup: Couldn't access the list of physical volumes for volume group "/dev
/usr/sbin/vgimport -v -m /etc/lvmconf/vgswap.mapfile /dev/vgswap
/vgswap". /dev/dsk/c2t0d1 \
ERROR: Executing the commands "\
/usr/sbin/vgimport -v -m /etc/lvmconf/vgswap.mapfile /dev/vgswap

\

/dev/dsk/c2t0d1 \
/dev/dsk/c11t0d1 \
/dev/dsk/c13t0d1 \
/dev/dsk/c15t0d1 \
/dev/dsk/c17t0d1 \
/dev/dsk/c4t0d1 \
/dev/dsk/c6t0d1 \
/dev/dsk/c8t0d1
/usr/sbin/vgchange -a r vgswap

test -d /dev/vg00 && /usr/sbin/vgcfgbackup /dev/vg00
test -d /dev/vgswap && /usr/sbin/vgcfgbackup /dev/vgswap
" produced a failure.


* Run_Postconfigure_Scripts: Error


======= 04/06/09 16:06:06 IST Installation complete: Failure


Note: /dev/vgswap is sitting in EVA.

Pls guide me to resolve this issue.


Regards,
Suresh
7 REPLIES 7
Frank de Vries
Respected Contributor

Re: Ignite restoration problem

Looks like you are trying to restore a backup that was made for a different hardware ??

It is not the Ignite , but the contents complaints about incompatibility and initialization
Look before you leap
Prashanth Waugh
Esteemed Contributor

Re: Ignite restoration problem

Hi,

it seems that there is a problem related to importing vg.
check the man pages for vgimport.
i think the command should be like that.
eg. vgimport -v -s -m /tmp/vg02.mymap /dev/vg02

Reagrds
Prashant
For success, attitude is equally as important as ability
RUET
Regular Advisor

Re: Ignite restoration problem

Did you interrupt the ignite procedure to have ignite screen in order to check what disks are seen by the server ..
it seems that disks set in the configuration files are wrong (not the same path ..)

So rerun your restore
interrupt ignite process in order to have the ignite screen consoel
check disks and LVM architecture.
You can modify in this screen LVM config, by example, associate vgswap to a disk you select in the list of seen disks ..

If you don't see any eva disks, may be it's a zoning problem ..
pat
smatador
Honored Contributor

Re: Ignite restoration problem

Hi,
With ignite, you could restore your image to a different hardware but if the source image have the driver for the new hardware target, if not you will go to some trouble. You could also merge the cloning with an update which are on a depot, like that the clone could have the driver.
To clone to a different model, you have to set _HP_CLONING to true.
When you are on the ignite recovery screen you should answer for it.

I agree with P R, it seem like a problem to access to your EVA. Perhaps, you could first recover the system without vgswap, check for the EVA disk and after recreate the vgswap.

Hope it helps
M.sureshkumar
Regular Advisor

Re: Ignite restoration problem

Hi All,

I restored in standby server.This server is not connected in network.

How to recover without vgswap in standby server.
Pls find the production server swap output ..

prd#swapinfo -tam
Mb Mb Mb PCT START/ Mb
TYPE AVAIL USED FREE USED LIMIT RESERVE PRI NAME
dev 24000 0 24000 0% 0 - 1 /dev/vg00/lvol2
dev 61312 219 61093 0% 0 - 0 /dev/vgswap/lvswap
reserve - 34148 -34148
memory 18412 3581 14831 19%
total 103724 37948 65776 37% - 0 -


Note:i have taken ignite image from production server.

Regards,
Suresh
smatador
Honored Contributor

Re: Ignite restoration problem

Hi,
Go on the console, boot to your ignite tape. After, you have to interact with the ignite process, go to the screen LVM, remove the vgswap. Do the recover. Boot on single mode, modify /etc/fstab and comment the vgswap. Boot normally.
M.sureshkumar
Regular Advisor

Re: Ignite restoration problem

Hi smatador,

Pls give me the step by step procedure.

Regards,
Suresh