make_sys_image cannot proceed with the archive creation while the legacy device support has been

[juanjojulian]

Hello, Im trying to make an ignite copy and I´m getting this error:

/opt/ignite/bin/make_net_recovery -s Ignite-server -n 1 -x inc_entire=vg00
ERROR: make_sys_image cannot proceed with the archive creation while the legacy device support has been disabled on the system. Enable the legacy devices using the command insf -L and re-create the recovery archive.

Ignite-UX version is:
swlist -l product | grep -i ignite

Ignite-UX C.7.12.519 HP-UX System Installation Services

HP-UX version is:

uname -a
HP-UX esdcux03 B.11.31 U ia64 2049830978 unlimited-user license

Legacy device support is in fact disable in this system, I have two questions:

- ¿Is it impossible to make a Ignite copy without legacy support?
- ¿Is it dangerous to activate back legacy support in a production system?

Thank you.

[Viktor Balogh]

> - ¿Is it impossible to make a Ignite copy without legacy support?

I don't know a way to do it without legacy support, but that does not mean it's impossible.

> - ¿Is it dangerous to activate back legacy support in a production system?

I don't think it's dangerous, but you will have a risk that in the future somebody will use the legacy devices and this way the active/active multipassing will be bypassed.

[bubunis]

I too am getting the same error

"
ERROR:   make_sys_image cannot proceed with the archive creation while the
legacy device support has been disabled on the system. Enable the
legacy devices using the command insf -L and re-create the "

Any help in this regard will be highly appreciated.

I am using HP UX 11.31.

Client's IGNITE Version : C.7.13.259

Master's IGNITE Version :  C.7.13.259

Thanks....

[Bart Voet_1]

Recently a check has been introduced when running make_sys_image to ensure that legacy device files are enabled. So there is indeed no other workaround than to enable them (insf -L). An enhancement request has been logged for make_sys_image to allow it to run even if legacy device files are removed. At this point in time there is no solution implemented yet, so the insf -L workaround is the only solution now.