Operating System - HP-UX
1748027 Members
3649 Online
108757 Solutions
New Discussion юеВ

Re: How to create an OS Core DVD with special Ignite version

 

How to create an OS Core DVD with special Ignite version

Hi all,

I have a problem in restoring a system using an OS-Core DVD with Ignite 7.5.142. The tape Ignite version is 7.6.100 and when trying to restore the machine, I got an error like the one below:
ERROR: The version of Ignite-UX on your tape (C.7.6.100) is different than
the version of Ignite-UX on the media that the client booted
(C.7.5.142). The versions must match in order to ensure correct behavior.

Continuing the installation with a tape version mismatch is likely
to cause indeterminate problems.
Do you want to continue anyway? (y/[n]):

Any idea what I could do? Could I create an OS-CORE DVD with the Ignite version 7.6.100??

Any help would be nice!
Thanks, Juergen
2 REPLIES 2
nightwich
Valued Contributor

Re: How to create an OS Core DVD with special Ignite version

Hi Juergen


I think you create your ignite backup with version C.7.5.142 and the upgrade the ignite client in the server.

Just a thought ...
chris huys_4
Honored Contributor

Re: How to create an OS Core DVD with special Ignite version

Hi Juergen,

I think the -s option was used with the make_tape_recovery, to create the initial ignite backup tape. Correct ?

If this is the case, try the following procedure. (the procedure was made originally by wtec ;) to solve a similar problem, i.e. in that case, we needed a ignite version that dealt with a "certain problem" and that ignite version was a "higher ignite version" then the one with which the ignite backup was taken )

NOTE: the procedure was made for a pa-risc environment. With integrity some small adjustments could be needed.

BEGIN Procedure
Here are the exact steps I followed for my test. For the purpose of this discussion, the following systems were used:

bali2 ignite client to be recovered
bali1 original ignite server
bali3 new ignite server

1) On the ignite server (bali1), create a tarball of the client directory, using the name
represented by the MAC address of the client, bali2:

# cd /var/opt/ignite/clients
# tar cvf /tmp/tar.out 0x0060B07E857D

2) On the new ignite server, which is running Ignite-UX C.7.6.100 or greater,
ftp the tarball over, and untar it in the /var/opt/ignite/clients directory:

# pwd
/var/opt/ignite/clients
# tar xvf tar.out
x 0x0060B07E857D/client_status, 0 bytes, 0 tape blocks x 0x0060B07E857D/config.sys, 565 bytes, 2 tape blocks x 0x0060B07E857D/client_name, 8 bytes, 1 tape blocks x 0x0060B07E857D/install.log, 1199 bytes, 3 tape blocks x 0x0060B07E857D/hw.info, 1052 bytes, 3 tape blocks x 0x0060B07E857D/host.info, 695 bytes, 2 tape blocks x 0x0060B07E857D/recovery/client_status, 338 bytes, 1 tape blocks x 0x0060B07E857D/recovery/2006-11-13,19:54/recovery.log, 4419 bytes, 9 tape bloc ks x 0x0060B07E857D/recovery/2006-11-13,19:54/archive_content, 273 bytes, 1 tape bl ocks x 0x0060B07E857D/recovery/2006-11-13,19:54/system_cfg, 6930 bytes, 14 tape block s x 0x0060B07E857D/recovery/2006-11-13,19:54/control_cfg, 472 bytes, 1 tape blocks

x 0x0060B07E857D/recovery/2006-11-13,19:54/flist, 7545591 bytes, 14738 tape bloc ks x 0x0060B07E857D/recovery/2006-11-13,19:54/archive_cfg, 3215 bytes, 7 tape block s x 0x0060B07E857D/recovery/2006-11-13,19:54/manifest, 9379 bytes, 19 tape blocks x 0x0060B07E857D/recovery/latest symbolic link to 2006-11-13,19:54 x 0x0060B07E857D/recovery/defaults, 436 bytes, 1 tape blocks x 0x0060B07E857D/recovery/archive_content, 273 bytes, 1 tape blocks x 0x0060B07E857D/server.state, 1573 bytes, 4 tape blocks x 0x0060B07E857D/lockfile, 0 bytes, 0 tape blocks x 0x0060B07E857D/CINDEX, 987 bytes, 2 tape blocks x 0x0060B07E857D/env.vars, 223 bytes, 1 tape blocks x 0x0060B07E857D/config, 1754 bytes, 4 tape blocks x 0x0060B07E857D/manifest/manifest, 7486 bytes, 15 tape blocks x 0x0060B07E857D/manifest/manifest.info, 5144 bytes, 11 tape blocks x 0x0060B07E857D/manifest/manifest.oinfo, 4663 bytes, 10 tape blocks x 0x0060B07E857D/manifest/manifest.orig, 7486 bytes, 15 tape blocks x 0x0060B07E857D/manifest/manifest.seed, 60 bytes, 1 tape blocks x 0x0060B07E857D/manifest/template.def, 14257 bytes, 28 tape blocks x 0x0060B07E857D/install.log.prev, 1544 bytes, 4 tape blocks x 0x0060B07E857D/config.full, 8887 bytes, 18 tape blocks

3) Create a symlink to the client name:

# ln -s 0x0060B07E857D bali2
# ll bali2
lrwxr-xr-x 1 bin bin 14 Nov 13 22:01 bali2 -> 0x0060B07E8
57D

4) Add the IP and MAC address information to the /etc/opt/ignite/instl_boottab
file on the new server:

16.113.10.17:0x0060B07E857D::reserve # bali2

5) From the client console, initiate a network boot:

Main Menu: Enter command > bo lan.16.113.86.12 install
END Procedure.

Greetz,
Chris