https://community.hpe.com/t5/operating-system-hp-ux/query-on-ignite/m-p/4726352#M498767 If you check your /var/opt/ignite/clients directory with ls -l, you will see that the hostname is used as a link another directory which corresponds to the MAC address of the NIC.<BR /><BR />You see, the ignite restore uses bootp to retrieve the stored image.<BR /><BR />As such, the MAC address should identify the correct image to use.<BR /><BR />p.s.<BR />This is also why you might setup a bootp-helper if you're ignite server is not on the same subnet as your host :)<BR /><BR />Regards<BR />Tor-Arne Tue, 14 Dec 2010 23:29:24 GMT Tor-Arne Nostdal 2010-12-14T23:29:24Z https://community.hpe.com/t5/operating-system-hp-ux/query-on-ignite/m-p/4726351#M498766 There are 2 ignite clients with same hostname. we have taken the ignite backup of both nodes by including -a option for spcifying the exact archive path. <BR />eg: <BR />hostname1 abc archive path /var/opt/ignite/recovery/archives/abc<BR /><BR />hostname2 abc archive path /var/opt/ignite/recovery/archives/abc1<BR /><BR />Do we need to take any extra precaution while restoring these archives. Tue, 14 Dec 2010 16:37:36 GMT https://community.hpe.com/t5/operating-system-hp-ux/query-on-ignite/m-p/4726351#M498766 Team_of_5 2010-12-14T16:37:36Z https://community.hpe.com/t5/operating-system-hp-ux/query-on-ignite/m-p/4726352#M498767 If you check your /var/opt/ignite/clients directory with ls -l, you will see that the hostname is used as a link another directory which corresponds to the MAC address of the NIC.<BR /><BR />You see, the ignite restore uses bootp to retrieve the stored image.<BR /><BR />As such, the MAC address should identify the correct image to use.<BR /><BR />p.s.<BR />This is also why you might setup a bootp-helper if you're ignite server is not on the same subnet as your host :)<BR /><BR />Regards<BR />Tor-Arne Tue, 14 Dec 2010 23:29:24 GMT https://community.hpe.com/t5/operating-system-hp-ux/query-on-ignite/m-p/4726352#M498767 Tor-Arne Nostdal 2010-12-14T23:29:24Z