Warnings during make_net_recovery

[Vreriks Marcel]

Hello,

I have two brand new Itanium HP-UX 11.23 machines with Ignite-UX Revision C.6.10.97.
When I want to make a make_net_recovery between this two systems I get warnings in my recovery.log such as:

* /opt/ignite/bin/save_config -f /var/opt/ignite/recovery/client_mnt/0x0
01A4B061E82/recovery/2007-10-09,12:25/system_cfg rootdg
/opt/ignite/bin/save_config[116]: pathCnt > 1 : The specified number is not valid for this command.
/usr/lib/hpux32/dld.so: Unable to find library '/usr/lib/libsmapi.so.2'.
ERROR: smapi_initiate_connection failed.
ERROR: smapi_initiate_connection failed.
save_config: warning - The public size string is NULL.
/usr/lib/hpux32/dld.so: Unable to find library '/usr/lib/libsmapi.so.2'.
ERROR: smapi_initiate_connection failed.
ERROR: smapi_initiate_connection failed.
save_config: warning - The public size string is NULL.

and I get two note's:

NOTE: diskinfo failed for device at: /dev/dsk/c3t1d0s2
NOTE: diskinfo failed for device at: /dev/dsk/c3t0d0s2

The warnings say that the library /usr/lib/libsmapi.so.2 is not on the system which is correct. A find command didn't libsmapi.so.2.

What does it mean and what can I do on these warnings?

Greeting Marcel

[Steven E. Protter]

Shalom Marcel,

The diskinfo issue is probably due to disks present in the source system but not the target system.

The missing library is a hpux 32 bit library, probably for compatability. That should have transferred like anything else. If the system boots and works normally you may be able to take these libraries off another working system.

Overall it does concern me that the image may be missing parts.

SEP

[Robert-Jan Goossens_1 · Accepted solution]

Hi Marcel,

Veritas volume manager?

Try the latest ignite software version C.7.3.148.

http://h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=IGNITEUXB

Regards,
Robert-Jan

[Saurav_1]

Here is a small step by step procedure.

Run command "ignite" on system A. Go to actions and add the client as system B. It should show the system as ignite clients.

export /var/opt/ignite/clients anon=-2
export /var/opt/ignite/recovery/archives anon=-2
mkdir /var/opt/ignite/recovery/archives/
chown bin:bin /var/opt/ignite/recovery/archives/

run command given below as it is on system B

make_net_recovery -P s -s -i

If command runs successfully and you see the ignite GUI. select Next. it will show the space availabe for ignite. Select next. This shows that your configuration is correct.

Select cancel to come out of Ignite. Now you can run the command using crontab and your ignite backup should not report any errors.

/opt/ignite/bin/make_net_recovery -A -P s -s "System B" >/tmp/recovery.last

Cheers

[Vreriks Marcel]

Hello Robert-Jan,

I installed the latest ignite version and the problem disappears.

Thx everybody for the response.

Marcel

[Vreriks Marcel]

Install latest ignite version