Well, they probably have such plan for future I would assume. Most of the customers that I know are currently running 9.40. I guess move to 10 will come this year somewhere. What product management has told you abour support plan in future? Usually they have schedule when each version would be tested (and if everything ok added to compatibility matrix or new module would be released with support for it).

well, Legato told me, there is an RFE LGTpa75042 "NMI support for IDS 10".

The comment from legato on this:

The current state of LGTpa75042 is : unevaluated.
That means that this RFE have been assigned to an engineer but we don't know yet if it will be accepted ( and then what the planned release is refused.

As this statement is very dissatisfying, I am looking for people who are or might be affected by this

Regards
Rainer

well I tried to use NMI 2.0 with IDS 10 and it fails.

the onbar loops somewhere in the XBSA library and netver contacts the networker server.

Just out of curiosity, what happens when you try to backup Informix 10 with existing current version of module? Sometime, even the version is not on the compatibility list (as it is not tested yet) module is perfectly capable of doing backups (and restores of course). Did you try to see if it runs?

This leads me to an idea I did once - ask them to send you list of tests to be performed for verification of the module (if existing module is capable to handle IDS 10) and if all is fine it should be added to compatibility matrix. However, such thing usually works with LGTO/EMC partners. For end users I'm not sure... perhaps if big enough... Give it a try - test first existing module and if it seems to work approach Legato support with this idea (unless they will test it themselves before).

To be honest, this forum is rather new thing and I'm not sure how many customer are following this forum for now (potential is here, now we just need some time). There is also NetWorker mailing list which is used (and run) by users where you have some Legato partners, consultants, end customer and people from Legato as well (even they are keeping low profile mostly). You may wish to post your query there as well to get more feedback or get in touch with people directly. To get more information check:
http://listserv.temple.edu/archives/networker.html

I am using hp-ux 11.11 with NMI 2.0 and IDS 10.00.FC4

Networker server is a WIN 2000 box.

Doing an onbar -b -L 0
with BAR_DEBUG=5
logs the following:

2006-01-27 10:10:48 4908 4906 do_args: return 0 (0x00)
2006-01-27 10:10:48 4908 4906 bar_siginit: enter
2006-01-27 10:10:48 4908 4906 bar_siginit: return
2006-01-27 10:10:48 4908 4906 bar_alarm: enter
2006-01-27 10:10:48 4908 4906 bar_alarm: return 0 (0x00)
2006-01-27 10:10:48 4908 4906 bar_exec: enter
2006-01-27 10:10:48 4908 4906 BSAQueryApi: enter
2006-01-27 10:10:48 4908 4906 bar_loadXBSA: enter
2006-01-27 10:10:48 4908 4906 bar_loadXBSA: return 0 (0x00)
2006-01-27 10:10:48 4908 4906 BSAQueryApiVersion: enter
2006-01-27 10:10:48 4908 4906 BSAQueryApiVersion: return
2006-01-27 10:10:48 4908 4906 bar_alarm: enter
2006-01-27 10:10:48 4908 4906 bar_alarm: return 240 (0xf0)
2006-01-27 10:10:48 4908 4906 BSAGetLastError: enter
2006-01-27 10:10:48 4908 4906 BSAGetLastError: return 132 (0x84)
2006-01-27 10:10:48 4908 4906 barQueryApi: return 0 (0x00)
2006-01-27 10:10:48 4908 4906 get_a_connection: enter
2006-01-27 10:10:48 4908 4906 bar_api_connect: enter
2006-01-27 10:10:48 4908 4906 bar_srv_status: enter
2006-01-27 10:10:48 4908 4906 bar_srv_status: return 5 (0x05)
2006-01-27 10:10:48 4908 4906 bar_alarm: enter
2006-01-27 10:10:48 4908 4906 bar_alarm: return 240 (0xf0)
2006-01-27 10:10:48 4908 4906 bar_api_connect: return 0 (0x00)
2006-01-27 10:10:48 4908 4906 get_a_connection: return 0 (0x00)
2006-01-27 10:10:48 4908 4906 bar_db_connect: enter
2006-01-27 10:10:48 4908 4906 bar_srv_status: enter
2006-01-27 10:10:48 4908 4906 bar_srv_status: return 5 (0x05)
2006-01-27 10:10:48 4908 4906 bar_db_connect: return 0 (0x00)
2006-01-27 10:10:48 4908 4906 bar_full_logs: enter


and onbar never leaves this state

Tracing the onbar_d with tusc shows the loop it takes:

send(7, "\001\001\0Y s e l e c t i s ".., 142, 0)
recv(7, "\0\b\002\0\0\0\0\0\0\0\f\003\0\0".., 4096, 0)
send(7, "\001\001\0Y s e l e c t i s ".., 142, 0)
recv(7, "\0\b\002\0\0\0\0\0\0\0\f\003\0\0".., 4096, 0)
send(7, "\001\001\0Y s e l e c t i s ".., 142, 0)
.
.
.
.

Can you let me know what OS did you use? My colleague just did a test with IDS 10 on Solaris 9 with current Informix module by Legato and it works without any problems. After that we corrupted the dbs and with onbar -r we were able to bring back whole thing back to its feet as expected. In our case both IDS server and NW server were same machine (it was test setup).

Perhaps one more thing - Informix used to come with bandled version of NW in the past and so is with 10... The limitation is that you need tape drive on the Informix box and etc, but you could use that for a test of your backup (just to see if it runs). I believe problem at your side is related to something else rather than NetWorker itself - at least this is how it looks from the error so far.

No idea, but it seems like core issue here is related to error pointed out in line "BSAGetLastError: return 132". If you look for this string it will point to IBM site and issue with sm_vesions (mine on Solarix box used 1|1.0.1|nwbsa|1).