topic Re: Make_net_recovery error in Operating System - HP-UX

Make_net_recovery error

Redhat — Sun, 14 Oct 2007 23:34:12 GMT

Hi Gurus,

Ignite backup is failing with the following error: It's due to the map FS .ignite is failing as there is mismatch between entry in fstab and mnttab .How to get rid of it ?
Need to take ignite for vg00 only .Why ignite is checking other filesystem (not to be backed up) ?

# /opt/ignite/bin/make_net_recovery -v -s qhus014adm -x inc_entire=vg00 -x exclude=/tmp
* Creating NFS mount directories for configuration files.
* Recovery Archive Name = 2007-10-14,18:28

* Lanic Id = 0x0014C2105237

* Ignite-UX Server = qhus014adm

======= 10/14/07 18:28:34 HST Started /opt/ignite/bin/make_net_recovery. (Sun
Oct 14 18:28:34 HST 2007)
@(#) Ignite-UX Revision C.6.1.44
@(#) net_recovery (opt) $Revision: 10.672 $

* Testing for necessary pax patch.
* Passed pax tests.
* Recovery Archive Description = Recovery Archive

* Recovery Archive Location =
qhus014adm:/var/opt/ignite/recovery/archives/qhus034

* Number of Archives to Save = 2

* Pax type = tar

WARNING: Filesystem /HT_CC is not mounted. It will be ignored.
WARNING: Filesystem /view is not mounted. It will be ignored.
WARNING: Filesystem /HT_ClearCase/vobs/HT_Kenan is not mounted. It will be
ignored.
WARNING: Filesystem /HT_ClearCase/vobs/HT_Kansys is not mounted. It will be
ignored.
WARNING: Filesystem /HT_ClearCase/vobs/HT_Mediation is not mounted. It will be
ignored.
WARNING: Filesystem /HT_ClearCase/vobs/HT_AAIS_BB is not mounted. It will be
ignored.
WARNING: Filesystem /HT_ClearCase/vobs/HT_CRM is not mounted. It will be
ignored.
WARNING: Filesystem /HT_ClearCase/vobs/HT_PUBCOMM is not mounted. It will be
ignored.
WARNING: Filesystem /HT_ClearCase/vobs/HT_Eportal is not mounted. It will be
ignored.
WARNING: Filesystem /HT_ClearCase/vobs/HT_WS_Dispatcher is not mounted. It
will be ignored.
WARNING: Filesystem /HT_ClearCase/vobs/MGSV is not mounted. It will be
ignored.
WARNING: Filesystem /HT_ClearCase/vobs/HT_FSCM is not mounted. It will be
ignored.
WARNING: Filesystem /HT_ClearCase/vobs/HT_HCM is not mounted. It will be
ignored.
WARNING: Filesystem /HT_ClearCase/vobs/HT_EPM is not mounted. It will be
ignored.
WARNING: Cannot parse mount information for /

** 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 Recovery Tools
WARNING: Filesystem /HT_CC is not mounted. It will be ignored.
WARNING: Filesystem /view is not mounted. It will be ignored.
WARNING: Filesystem /HT_ClearCase/vobs/HT_Kenan is not mounted. It will be
ignored.
WARNING: Filesystem /HT_ClearCase/vobs/HT_Kansys is not mounted. It will be
ignored.
WARNING: Filesystem /HT_ClearCase/vobs/HT_Mediation is not mounted. It will be
ignored.
WARNING: Filesystem /HT_ClearCase/vobs/HT_AAIS_BB is not mounted. It will be
ignored.
WARNING: Filesystem /HT_ClearCase/vobs/HT_CRM is not mounted. It will be
ignored.
WARNING: Filesystem /HT_ClearCase/vobs/HT_PUBCOMM is not mounted. It will be
ignored.
WARNING: Filesystem /HT_ClearCase/vobs/HT_Eportal is not mounted. It will be
ignored.
WARNING: Filesystem /HT_ClearCase/vobs/HT_WS_Dispatcher is not mounted. It
will be ignored.
WARNING: Filesystem /HT_ClearCase/vobs/MGSV is not mounted. It will be
ignored.
WARNING: Filesystem /HT_ClearCase/vobs/HT_FSCM is not mounted. It will be
ignored.
WARNING: Filesystem /HT_ClearCase/vobs/HT_HCM is not mounted. It will be
ignored.
WARNING: Filesystem /HT_ClearCase/vobs/HT_EPM is not mounted. It will be
ignored.
WARNING: Cannot parse mount information for /
ERROR: The list_expander command failed. This could be due to a problem with
the -x options specified - see messages above.

Re: Make_net_recovery error

Ludovic Derlyn — Mon, 15 Oct 2007 02:20:33 GMT

hi,

Have you an entruy in /etc/fstab for /HT_ClearCase/vobs/HT_EPM ?

if Yes, it's must be mounted or ignored by -x exclude

Regards

L-DERLYN

Re: Make_net_recovery error

Redhat — Mon, 15 Oct 2007 02:43:57 GMT

The fstab contains:
/dev/vg00/lvol3 / vxfs delaylog 0 1
/dev/vg00/lvol1 /stand hfs defaults 0 1
/dev/vg00/lvol4 /opt vxfs delaylog 0 2
/dev/vg00/lvol5 /tmp vxfs delaylog 0 2
/dev/vg00/lvol6 /usr vxfs delaylog 0 2
/dev/vg00/lvol7 /var vxfs delaylog 0 2
/dev/vg00/lvol8 /home vxfs delaylog 0 2
qnas002:/qhus034_apps /apps nfs bg,hard,intr 0 0
nas002:/qwss052_vobs /vobs nfs bg,hard,intr 0 0
#qnas002:/qwss052_apps /apps_1 nfs bg,hard,intr 0 0
qnas002:/qwss052_HT_CC /HT_CC nfs bg,hard,intr 0 0
qnas002:/qwss052_var_adm_rational /var/adm/rational nfs bg,hard,intr 0 0
qnas002:/qwss052_storage_vob /storage_vob nfs bg,hard,intr 0 0
#qnas002:/qwss052_storage_view /storage_view nfs bg,hard,intr 0 0
qnas002:/qwss052_opt_rational /opt/rational nfs bg,hard,intr 0 0
/dev/vg10_qhus034/lvol1 /HT_ClearCase vxfs rw,suid,largefiles,delaylog,datainlog 0 2
/dev/vg00/lvol13 ... swap pri=0 0 0
====
shall I need to exclude all the map entry ..

Re: Make_net_recovery error

Robert-Jan Goossens — Mon, 15 Oct 2007 02:52:54 GMT

Hi,

I think it would be easier to create a ignite_fstab.

# cp /etc/fstab /etc/ignite_fstab

remove all umounted filesystem including the nfs filesystems from the ignite_fstab.

# mv /etc/fstab /etc/fstab.ORG
# mv /etc/ignite_fstab /etc/fstab
restart your make_net_recovery, and sfater it has finished mv teh fstab.ORG back to the fstab.

Robert-Jan

Re: Make_net_recovery error

Redhat — Mon, 15 Oct 2007 02:53:10 GMT

Anyway excluding anything is not solving the issue..

Re: Make_net_recovery error

Ludovic Derlyn — Mon, 15 Oct 2007 03:13:10 GMT

hi

this mountpoint dev/vg10_qhus034/lvol1 /HT_ClearCase vxfs rw,suid,largefiles,delaylog,datainlog 0 2
it is mounted ?
For mountpoint in nas, Exclude this from ignite

solution given by RJG seems clean to resolve your problem

regards
L-DERLYN

Re: Make_net_recovery error

Redhat — Mon, 15 Oct 2007 04:06:41 GMT

The problem remains even after replacing /etc/fstab for time being.

If I replace /etc/mnttab in the same way does it afftect the NFS mount points?
Current bdf is as below:
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 2048000 1558728 485480 76% /
/dev/vg00/lvol1 1001729 60103 841453 7% /stand
/dev/vg00/lvol7 4300800 3151736 1141056 73% /var
/dev/vg00/lvol6 4096000 3606544 489456 88% /usr
/dev/vg00/lvol5 2048000 1713976 332112 84% /tmp
/dev/vg00/lvol4 4096000 1559000 2517328 38% /opt
/dev/vg00/lvol8 4096000 2961256 1127056 72% /home
/dev/vg10_qhus034/lvol1
571277312 396514504 173397480 70% /HT_ClearCase
qnas002:/qwss052_var_adm_rational
8790216 901736 7888480 10% /var/adm/rational
qnas002:/qhus034_apps
193402088 15622976 177779112 8% /apps
/view 2048000 1558728 485480 76% /view
/HT_ClearCase/vobstore/HT_Kenan.vbs
571277312 396514504 173397480 70% /HT_ClearCase/vobs/HT_Kenan
/HT_ClearCase/vobstore/HT_Kansys.vbs
571277312 396514504 173397480 70% /HT_ClearCase/vobs/HT_Kansys
/HT_ClearCase/vobstore/HT_Mediation.vbs
571277312 396514504 173397480 70% /HT_ClearCase/vobs/HT_Mediation
/HT_ClearCase/vobstore/HT_AAIS_BB.vbs
571277312 396514504 173397480 70% /HT_ClearCase/vobs/HT_AAIS_BB
/HT_ClearCase/vobstore/HT_CRM.vbs
571277312 396514504 173397480 70% /HT_ClearCase/vobs/HT_CRM
/HT_ClearCase/vobstore/HT_PUBCOMM.vbs
571277312 396514504 173397480 70% /HT_ClearCase/vobs/HT_PUBCOMM
/HT_ClearCase/vobstore/HT_Eportal.vbs
571277312 396514504 173397480 70% /HT_ClearCase/vobs/HT_Eportal
/HT_ClearCase/vobstore/HT_WS_Dispatcher.vbs
571277312 396514504 173397480 70% /HT_ClearCase/vobs/HT_WS_Dispatcher
/HT_ClearCase/vobstore/MGSV.vbs
571277312 396514504 173397480 70% /HT_ClearCase/vobs/MGSV
/net/qhus034/HT_ClearCase/vobstore/HT_GCOMMF.vbs
571277312 396514504 173397480 70% /HT_ClearCase/vobs/HT_GCOMMF
/net/qhus034/HT_ClearCase/vobstore/HT_CFG_MGMT.vbs
571277312 396514504 173397480 70% /HT_ClearCase/vobs/HT_CFG_MGMT
/net/qhus034/HT_ClearCase/vobstore/HT_IVR.vbs
571277312 396514504 173397480 70% /HT_ClearCase/vobs/HT_IVR
/HT_ClearCase/vobstore/HT_FSCM.vbs
571277312 396514504 173397480 70% /HT_ClearCase/vobs/HT_FSCM
/HT_ClearCase/vobstore/HT_HCM.vbs
571277312 396514504 173397480 70% /HT_ClearCase/vobs/HT_HCM
/HT_ClearCase/vobstore/HT_EPM.vbs
571277312 396514504 173397480 70% /HT_ClearCase/vobs/HT_EPM
/net/qhus034/HT_ClearCase/vobstore/HT_Interfaces.vbs
571277312 396514504 173397480 70% /HT_ClearCase/vobs/HT_Interfaces
/net/qhus034/HT_ClearCase/vobstore/HT_POS.vbs
571277312 396514504 173397480 70% /HT_ClearCase/vobs/HT_POS
/net/qhus034/HT_ClearCase/vobstore/HT_ACN_Utils.vbs
571277312 396514504 173397480 70% /HT_ClearCase/vobs/HT_ACN_Utils
/net/qhus034/HT_ClearCase/vobstore/HT_AdvancedConfigurator.vbs
571277312 396514504 173397480 70% /HT_ClearCase/vobs/HT_AdvancedConfigurator
/net/qhus034/HT_ClearCase/vobstore/HT_KP.vbs
571277312 396514504 173397480 70% /HT_ClearCase/vobs/HT_KP
/net/qhus034/HT_ClearCase/vobstore/HT_PVOB.vbs
571277312 396514504 173397480 70% /HT_ClearCase/vobs/HT_PVOB
/net/qhus034/HT_ClearCase/vobstore/HT_NG-LQP.vbs
571277312 396514504 173397480 70% /HT_ClearCase/vobs/HT_NG-LQP
/net/qhus034/HT_ClearCase/vobstore/HT_PMO.vbs
571277312 396514504 173397480 70% /HT_ClearCase/vobs/HT_PMO
/net/qhus034/HT_ClearCase/vobstore/HT_NRMS.vbs
571277312 396514504 173397480 70% /HT_ClearCase/vobs/HT_NRMS
/net/qhus034/HT_ClearCase/vobstore/HT_Remedy.vbs
571277312 396514504 173397480 70% /HT_ClearCase/vobs/HT_Remedy
/net/qhus034/HT_ClearCase/vobstore/HT_ASAP.vbs
571277312 396514504 173397480 70% /HT_ClearCase/vobs/HT_ASAP
/net/qhus034/HT_ClearCase/vobstore/HT_TIBCO.vbs
571277312 396514504 173397480 70% /HT_ClearCase/vobs/HT_TIBCO
/net/qhus034/HT_ClearCase/vobstore/HT_Indus.vbs
571277312 396514504 173397480 70% /HT_ClearCase/vobs/HT_Indus
qnas002:/qwss052_opt_rational
8790216 4075304 4714912 46% /opt/rational
qnas002:/qwss052_storage_vob
8790216 808 8789408 0% /storage_vob
/ 2048000 1558728 485480 76% /net/qhus034

Re: Make_net_recovery error

Robert-Jan Goossens — Mon, 15 Oct 2007 05:40:45 GMT

Hi,

Could you run following command.

# /opt/ignite/lbin/list_expander > /tmp/list_expander.log

and post the resuls of the log file?

Regards,
Robert-Jan

Re: Make_net_recovery error

Redhat — Mon, 15 Oct 2007 22:42:30 GMT

It is creating a 0 bin file:
-rw-r--r-- 1 root sys 0 Oct 15 17:38 /tmp/list_expander.log

with the following error in console
WARNING: statvfs failed. '/vobs' in /etc/fstab or /etc/mnttab not found: No
such file or directory (errno = 2)
WARNING: Filesystem /HT_CC is not mounted. It will be ignored.
WARNING: Filesystem /view is not mounted. It will be ignored.
WARNING: Filesystem /HT_ClearCase/vobs/HT_Kenan is not mounted. It will be
ignored.
WARNING: Filesystem /HT_ClearCase/vobs/HT_Kansys is not mounted. It will be
ignored.
WARNING: Filesystem /HT_ClearCase/vobs/HT_Mediation is not mounted. It will be
ignored.
WARNING: Filesystem /HT_ClearCase/vobs/HT_AAIS_BB is not mounted. It will be
ignored.
WARNING: Filesystem /HT_ClearCase/vobs/HT_CRM is not mounted. It will be
ignored.
WARNING: Filesystem /HT_ClearCase/vobs/HT_PUBCOMM is not mounted. It will be
ignored.
WARNING: Filesystem /HT_ClearCase/vobs/HT_Eportal is not mounted. It will be
ignored.
WARNING: Filesystem /HT_ClearCase/vobs/HT_WS_Dispatcher is not mounted. It
will be ignored.
WARNING: Filesystem /HT_ClearCase/vobs/MGSV is not mounted. It will be
ignored.
WARNING: Filesystem /HT_ClearCase/vobs/HT_FSCM is not mounted. It will be
ignored.
WARNING: Filesystem /HT_ClearCase/vobs/HT_HCM is not mounted. It will be
ignored.
WARNING: Filesystem /HT_ClearCase/vobs/HT_EPM is not mounted. It will be
ignored.
WARNING: Cannot parse mount information for /
====
Looking for some solution ..points ahead

Re: Make_net_recovery error

Ludovic Derlyn — Tue, 16 Oct 2007 02:39:18 GMT

hi

just an remark , when i look your /etc/fstab
all mount points NFs begin to qnas , not for vobs

it's normal ?

qnas002:/qhus034_apps /apps nfs bg,hard,intr 0 0
nas002:/qwss052_vobs /vobs nfs bg,hard,intr 0 0
#qnas002:/qwss052_apps /apps_1 nfs bg,hard,intr 0 0

Re: Make_net_recovery error

Redhat — Tue, 16 Oct 2007 02:59:58 GMT

Good finding ..But I am interested in for some kind of solution only ..That was a copy/paste error.

Re: Make_net_recovery error

Ludovic Derlyn — Tue, 16 Oct 2007 04:24:08 GMT

hi,

yes but the message error console is :

WARNING: statvfs failed. '/vobs' in /etc/fstab or /etc/mnttab not found: No
such file or directory (errno = 2)

You are on 11iV3 ?

largefiles are set to vobs ?

Regards
L-DERLYN

====================================================
VERITAS Enterprise Administrator File System Provider Fixed Incidents
====================================================

104705 Add localization packaging to fspro
104715 Incorrect statvfs field is being used for normalization of fs size

Re: Make_net_recovery error

Redhat — Wed, 17 Oct 2007 04:23:01 GMT

The server is HPUX 11.11.

Yes large file is enable for the FS

Re: Make_net_recovery error

Redhat — Sat, 27 Oct 2007 10:50:25 GMT

Putting it on top.Need expert's light..

Re: Make_net_recovery error

Bill Hassell — Sat, 27 Oct 2007 18:15:55 GMT

The errors are very clear. Your /etc /fstab file has filesystems listed that are not there. Copy your fstab file, then put # in front of every line that matches an error message. Ignite always verifies that the current system is 'normal' and in your case, the list of filesystems that are supposed to be mounted does not match the state ofr your system.

You can try mount -a and if everything mounts OK without an error, then make_tape_recovery will work OK. You do not want a backup of a system that has problems.