How to diagnose an Ignite issue

[Sagar Sirdesai]

Hi
I have a ignite client running hp-ux 11.31 OS.
The ignite image for this client client is taken to ignite server which also runs hpux 11.31.

But I have s issue when I initiated the Ignite backup to Ignite Server .
I can the ignite being initiated but nothing getting copied to the Ignited Server.

Below is the contents of log file

IGNITE/UX: beginning make_net_recovery to server knot0002

** 0 - The Volume Group or Filesystem is Not included in the
System Recovery Archive
** 1 - The Volume Group or Filesystem is Partially included in the
System Recovery Archive
** 2 - The Volume Group or Filesystem is Fully included in the
System Recovery Archive

* Scanning system for IO devices...
* Boot device is: 0/0/8/1/0/4/0.0x5005076305104497.0x5001000000000000

Please advise how can I diagnose what and where the issue could be

Thanks

Sagar

[Tim Nelson]

what log file are you looking at ?

on the ignite server knot0002:/var/opt/ignite/clients//recovery/latest/recovery.log ?

[Steven E. Protter]

Shalom Sagar,

It would appear to be your command line options. You need to include a volume group.

What command line options are you using?

SEP

[Chandrahasa s]

Hi ,

Provide following output
a)ignite command which u fire from client
2)cat /etc/fstab and /etc/sbtab ---server side
3)tail -f /var/opt/ignite/clients//recovery/latest/recovery.log ----server side
4)try to ping client to server and server to client using hostname.


Chandra

[Sagar Sirdesai]

1)The Command used to gt th eignite is
/opt/ignite/bin/make_net_recovery -v -n 2 -P s -s knot0002 -x inc_entire=vg00 -x exclude=/var/adm/crash

2)knot0002> cat /etc/fstab
# System /etc/fstab file. Static information about the file systems
# See fstab(4) and sam(1M) for further details on configuring devices.
# created by auto-ignite postinstallation script Wed Dec 9 13:39:43 GMT 2009
/dev/vg00/lvol3 / vxfs delaylog 0 1
/dev/vg00/lvol1 /stand vxfs tranflush 0 1
/dev/vg00/lvol4 /home vxfs delaylog,nosuid 0 2
/dev/vg00/lvol5 /opt vxfs delaylog 0 2
/dev/vg00/lvol6 /scdhold vxfs delaylog,nosuid 0 2
/dev/vg00/lvol7 /tmp vxfs delaylog,nosuid 0 2
/dev/vg00/lvol8 /usr vxfs delaylog 0 2
/dev/vg00/lvol9 /var vxfs delaylog 0 2
/dev/vg00/lvol11 /wload vxfs delaylog,nosuid 0 2
/dev/vg00/lvol10 /var/adm/crash vxfs delaylog,nosuid 0 2
/dev/vg00/lvol12 /layered_products vxfs delaylog 0 0
/dev/vg00/lvol13 /var/opt/ignite/depots vxfs delaylog 0 0
/dev/vg00/lvol14 /var/opt/ignite/recovery/archives vxfs delaylog 0 0
knot0002>

The /etc/sbtab is empty


3)knot0002> tail -f recovery.log
* /opt/ignite/lbin/make_arch_config -c /var/opt/ignite/recovery/client_m
nt/0x001E0B45781E/recovery/2010-04-14,08:36/archive_cfg -g /var/opt/ig
nite/recovery/client_mnt/0x001E0B45781E/recovery/2010-04-14,08:36/flis
t -n 2010-04-14,08:36 -r ipf -b 64 -d Recovery\ Archive -L
/var/opt/ignite/recovery/arch_mnt -l
knot0002:/var/opt/ignite/recovery/archives/knot0401 -i 1 -m t
* Saving the information about archive to
/var/opt/ignite/recovery/previews
* Creating The Networking Archive


4)The ping from server to client and from client to server is successfull


Sagar

[Torsten.]

>> * Creating The Networking Archive


From now on it takes a while - how long did you wait?

[Sagar Sirdesai]

Hi
I waited for over 10 Hours but nothing happened.

For same client I initiated the Ignite to different Ignite Server (knot0001) and it commplete within 40 Minutes.
So I guess the issue is with the new Ignite Server knot0002

Sagar

[Steven E. Protter]

Shalom Sagar,

See:
http://forums13.itrc.hp.com/service/forums/questionanswer.do?threadId=1421344

My last post.

Make sure:

root@mngp01:/root # showmount -e
export list for mngp01:
/var/opt/ignite/clients (everyone)
/var/opt/ignite/recovery/archives (everyone)

These shares are required for a proper Ignite server.

Do some tests nfs mounts to make sure things work properly.

SEP

[Chandrahasa s]

Hi,

Looks like u r s make_net_recovery syntax is wrong.

Go through attachment you will be able to resolve this issue.

[Sajith P V]

Hi,

This may be an nfs issue. try to take backup without -P s option.

try with -p so that it will give you preview.