Ignite backup hangs in IO scanning

[Redhat]

Hi ,
I have facing issue with ignite backup in rp7420.
The ignite version is
C.7.5.142

The backup is hanging after following steps:
* Pax type = tar


In? dsk/vg name minor# Associated disks/mountpoints
1 v /dev/vg00 0x00 /dev/dsk/c0t5d0 /dev/dsk/c7t6d0
/dev/vg00/lvol1 /stand 2
/dev/vg00/lvol2
/dev/vg00/lvol3 / 2
/dev/vg00/lvol4 /home 2
/dev/vg00/lvol5 /tmp 0
/dev/vg00/lvol6 /opt 2
/dev/vg00/lvol7 /usr 2
/dev/vg00/lvol8 /var 2
/dev/vg00/lvol9 /var/adm/crash 2
/dev/vg00/lvol10 /var/usr/local 2
/dev/vg00/lvol11 /var/opt/perf/datafiles 2
0 v /dev/vg01 0x01 /dev/dsk/c0t6d0 /dev/dsk/c4t6d0
/dev/vg01/lvol1 /var/opt/OV 0
/dev/vg01/lvol2 /var/opt/HPO 0

** 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

* Checking Versions of Ignite-UX filesets
* Scanning system for IO devices...

Any resulation will be appreciated and add points

[Patrick Wallek · Accepted solution]

I would do an 'ioscan' and make sure that all of your devices attached to the system are responding and that you don't have any with NO_HW.

[Steven E. Protter]

Shalom,

It would be helpful to see the command you used.

My guess and thats all it is now is that there is a NFS share, possibly stale included in the archive.

Suggested syntax:
#!/usr/bin/sh
/opt/ignite/bin/make_tape_recovery -Av -x inc_entire=vg00 -x exclude=/home -d "description"
# /usr/contrib/bin/eject.tape


SEP

[Redhat]

Is there any way to bypass the device IO checking i.e any -x exclude string ?

Currently there is a disk which has failed in vg01

[Bill Hassell]

This is a feature (ioscan) in Ignite/UX. It will not proceed until every physical disk has been scanned and matched to a volume group or defined as unused. There can be no disk failures, out of sync lvmtab, or other disk config errors. This has been asked for in the past (ie, skip selected volume groups and/or disks) but currently, Ignite is one of the best system health checks you can run. You'll have to fix the bad disk or get rid of it.

[Redhat]

If there is no solution towards the issue other than correcting the hardware problem ,I 'm closing the thread .thanks all for your response.