Ignite backup problem - make_net_recovery

[Narendra Uttekar]

Hi,
I am getting error while taking ignite backup through make_net_recovery as below on Ignite UX server,
testdr:[/]# make_net_recovery -x inc_entire=vg00 -s test07 -a test07:/archive/hpuxclient/testdr
* Creating NFS mount directories for configuration files.

======= 02/28/11 00:27:26 PST Started make_net_recovery. (Mon Feb 28 00:27:26 PST 2011)
@(#)Ignite-UX Revision C.7.11.444
@(#)ignite/net_recovery (opt) Revision: /branches/IUX_RA1009/ignite/src@81712 Last Modified: 2010-07-23 02:35:40 -0600 (Fri, 23 Jul 2010)

* Checking Versions of Recovery Tools
* Scanning system for IO devices...
* Boot device is: 0/0/2/0.6.0
* Creating System Configuration.
* /opt/ignite/bin/save_config -f /var/opt/ignite/recovery/client_mnt/0x001083FEF4AC/recovery/2011-02-28,00:27/system_cfg vg00
* Backing Up Volume Group /dev/vg00
* /usr/sbin/vgcfgbackup /dev/vg00
* Creating Map Files for Volume Group /dev/vg00
* /usr/sbin/vgexport -s -p -m /etc/lvmconf/vg00.mapfile /dev/vg00

* Backing Up Volume Group /dev/vgmaxdb
* /usr/sbin/vgcfgbackup /dev/vgmaxdb
* Creating Map Files for Volume Group /dev/vgmaxdb
* /usr/sbin/vgexport -s -p -m /etc/lvmconf/vgmaxdb.mapfile /dev/vgmaxdb

* Backing Up Volume Group /dev/vgmindb
* /usr/sbin/vgcfgbackup /dev/vgmindb
* Creating Map Files for Volume Group /dev/vgmindb
* /usr/sbin/vgexport -s -p -m /etc/lvmconf/vgmindb.mapfile /dev/vgmindb

* Backing Up Volume Group /dev/vgtctdb
* /usr/sbin/vgcfgbackup /dev/vgtctdb
* Creating Map Files for Volume Group /dev/vgtctdb
* /usr/sbin/vgexport -s -p -m /etc/lvmconf/vgtctdb.mapfile /dev/vgtctdb

* Creating Control Configuration.
* Creating Archive File List
* Creating Archive Configuration

* /opt/ignite/lbin/make_arch_config -c /var/opt/ignite/recovery/client_mnt/0x001083FEF4AC/recovery/2011-02-28,00:27/archive_cfg -g
/var/opt/ignite/recovery/client_mnt/0x001083FEF4AC/recovery/2011-02-28,00:27/flist -n 2011-02-28,00:27 -r pa -b 64 -d Recovery\ Archive -L
/var/opt/ignite/recovery/arch_mnt -l test07:/archive/hpuxclient/testdr -i 1 -m t
* Saving the information about archive to /var/opt/ignite/recovery/previews
* Creating The Networking Archive

* /opt/ignite/data/scripts/make_sys_image -d /var/opt/ignite/recovery/arch_mnt -t n -s local -n 2011-02-28,00:27 -m t -w
/var/opt/ignite/recovery/client_mnt/0x001083FEF4AC/recovery/2011-02-28,00:27/recovery.log -u -R -g
/var/opt/ignite/recovery/client_mnt/0x001083FEF4AC/recovery/2011-02-28,00:27/flist -a 12802140

* Preparing to create a system archive.
* The archive is estimated to reach 6401070 kbytes.
* Free space on /var/opt/ignite/recovery/arch_mnt
after archive should be about 14517146 kbytes.

* Archiving contents of ttcmaxdr via tar to
/var/opt/ignite/recovery/arch_mnt/2011-02-28,00:27.
pax: stand/dlkm.vmunix.prev/symtab : I/O error
pax: stand/dlkm.vmunix.prev/symtab : An unexpected end-of-file has occurred.
pax: stand/vmunix.prev : I/O error
pax: stand/vmunix.prev : An unexpected end-of-file has occurred.
pax: usr/bin/rcs : I/O error
pax: usr/bin/rcs : An unexpected end-of-file has occurred.
WARNING: The pax command returned a non-zero exit status (exit status 1).
* Creation of system archive complete.
NOTE: The following files are in the list of files that were on the
system, but they are no longer present. These files are not
included in the backup:
/var/tmp/ign_configure/make_sys_image.log
/var/opt/ignite/tmp/AAAa25287
/var/opt/ignite/tmp/BAAa25287

* Creating CINDEX Configuration File

* /opt/ignite/bin/manage_index -q -c 2011-02-28,00:27\ Recovery\ Archive -i /var/opt/ignite/recovery/client_mnt/0x001083FEF4AC/CINDEX -u Recovery\
Archive


======= 02/28/11 01:33:03 PST make_net_recovery completed with warnings

Thanks,
Narendra

[Dennis Handly]

pax: stand/dlkm.vmunix.prev/symtab : I/O error
pax: stand/dlkm.vmunix.prev/symtab : An unexpected end-of-file has occurred.
pax: stand/vmunix.prev : I/O error
pax: usr/bin/rcs : I/O error

These look serious. Can you do the following:
ll /stand/dlkm.vmunix.prev/symtab /stand/vmunix.prev /usr/bin/rcs

If the size isn't 0, try: cksum /usr/bin/rcs

[Narendra Uttekar]

Hi Dennis,
I have checked the files and the size is not zero. So i have run the cksum /usr/bin/rcs as you said. But no luck same error.

Please let me know what could be the problem thats why i am getting this error.

Thanks,
Narendra

[Dennis Handly · Accepted solution]

>So I have run the cksum /usr/bin/rcs as you said. But no luck same error.

I wanted to see if I could duplicate the error outside ignite. It proves your disk is bad and nothing wrong with ignite.

[Jim Walls]

If you have a known good backup of the affected files you could try restoring them. Alternatively copy them in from a similar system.

If you suspect the media is dodgy then try doing a dd of the raw disk:

dd if=/dev/rdsk/cxtxdx of=/dev/null bs=65536

...and see if any errors are reported.

If you get no errors it will suggest that the file systems may be corrupt in some way, which seems unlikely since /stand and /usr are different fs types.