Can I get rid of tftp server created by ignite?

[TwoProc]

I've got some servers here which are regularly backed up via ignite to an ignite server (separate machine). In an effort to continuously lock down systems by questioning the validity of services running on servers - I need to know if I need the tftp services that the ignite install put on the ignite client machines (in /etc/inetd.conf).

Question: On all machines except the ignite server(s) - can I get rid of the two tftp entries and still do network based backup/restore of these servers to and from the separate ignite server machine?

We did some testing and backup seems just fine without the tftp services - but not sure about recovery. Can anyone enlighten us on this?

[RAC_1]

If you want a client to get ignited from ignite server, you need that entry. Which you can do at the time of igniting it. Else you can get rid of it. Only ignite server needs to have it as you prepare ignites recoveries on it.

[TwoProc]

RAC, thanks for the reply. I do need more information to make a decision.

If my client server is "down" and I'm using my ignite bootable tape to boot up and then point the recovery tool to the ignite server ... what do I need this entry for? Does it come into play during the recovery process after a sort of "boot-strap" operation in which I partially come up under ignite?

Or, would this be for a use in which I'm not restoring a whole system but just a part? If so, I use Data Protector for that...

More information please.

[RAC_1]

If you are doing tape recovery it wont be needed. But you point to ignite server then it is defintely required.

Anil

[TwoProc]

RAC,

Well, it's not a tape recovery - it's a network based recovery off an ignite server that I would be starting from an ignite-bootable tape.

Can you explain further?

[TwoProc]

Can anyone else add to this?
It would be much appreciated.
Thanks.

[Robert-Jan Goossens_1 · Accepted solution]

Hi John,

Check this doc.

Europe
http://www4.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000075211553

US
http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000075211553

Document description: Disabling tftp on servers for Ignite-UX (IUX) make_net_recovery
Document id: KBRC00015311

[TwoProc]

Thanks Robert,
It is exactly what I needed. Wish I had a rabbit to give... :-)

For anyone interested - I cut out the good part of the document and am posting...


Thanks very much!

John
--------EXCERPT FROM HP DOC ------

Servers are not required to have tftp enabled when creating a
make_net_recovery as of version B.5.4.x.

But, tftp is still required on the IUX server when recovering a
client.

In summary, when you are creating a network archive, tftp is not required as
of B.5.4 version of IUX. Portions that did use tftp were easily modified to
change this. However, when you are recovering a client, the IUX server needs
tftp to download the mini-kernel/OS, this needs tftp and we cannot modify how
to get the client up and then get nfs working to get the full archive.

Hence, the best solution is to add to your disaster recovery procedures that
when recovering a client, you need to first enable tftp on the IUX server that
the client will be booting off.

[TwoProc]

Thanks Robert