make_tape_recovery error

[Mike Holt_1]

root@server1:/var/opt/ignite/recovery/latest>>make_tape_recovery -Av
* Creating local directories for configuration files and archive.

======= 08/25/05 15:26:10 EDT Started make_tape_recovery. (Thu Aug 25
15:26:10 EDT 2005)
@(#) 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 = /dev/rmt/0mn

* Number of Archives to Save = 2

* Pax type = tar

WARNING: Cannot parse mount information for /remote/rfes

** 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
WARNING: Cannot parse mount information for /remote/rfes
ERROR: The list_expander command failed. This could be due to a problem with
the file: "/var/opt/ignite/recovery/latest/archive_content" - see
messages above.

======= 08/25/05 15:26:13 EDT make_tape_recovery completed unsuccessfully

[Devender Khatana]

Hi,

It seems something with /remote/rfes is listed in /etc/fstab but is not currently mounted. Allthough in that case also it should go ahead just by giving a warning.

Could you attach bdf output and /etc/fstab file.

HTH,
Devender

[saju_2]

Hi

The mount point /remote/rfes is not currently mounted in the server

Either hash out the entry from fstab or mount it if u require...

Regards
CS

[Marvin Strong]

since /remote/rfes is not being used. you can also exclude it from the backup.

make_tape_recovery -Av -x exclude=/remote/rfes


also if your just looking for vg00

make_tape_recovery -v -x inc_entire=vg00

[Steven E. Protter]

Ignite make_tape_recovery checks fstab and will fail if all mentioned mounts are properly mounted. Otherwise it fails. Its a good safeguard to make sure the archive will be usable.

SEP

[Sandman!]

Check the /etc/fstab file and make sure that its not an NFS mount point that's offline or not available. Other option is to simply exclude it from the make_tape_recovery command line.

regards!

[Uday_S_Ankolekar]

This error usually due to typo in /etc/fstab file. Check for any syntax error

-USA..

[Bill Hassell]

This is a common error when the box is (or has) running automounter or AutoFS. /remote/rfes may be a symbolic link created by the automounter. Cleanup the automounter configs or just exclude that path from Ignite.

[Mike Holt_1]

I've already tried excluding mount points, still doesn't work.

Seems I've got some directories mounted up that aren't in the fstab... I'm going to fix that problem and try again.

Thanks for all your help

Mike

[HugoAlmeida]

Be carefull.
fstab has the directories that you want to mount at boot.
Check mnttab (mountpoints currently mounted)
for inconsistencies.
Check file system space available in /var or /tmp.I known that's a long shot but i have seen some strange errors in past versions of ignite when there was little space available in /var or /tmp (i think the mountpoint can be configured).