topic Re: make_tape_recovery failed in Operating System - HP-UX

make_tape_recovery failed

dennischen — Fri, 08 Dec 2017 07:20:12 GMT

Hi,

I have a question, when I execute the bellow make_tape_recovery command. The errors come up.... How can I fix it.. The make_tape_recovery is relying on the /etc/fstab? Thanks.

backupdr[/etc]#make_tape_recovery -Av
* Creating local directories for configuration files and archive.

======= 12/08/17 15:16:24 EAT Started make_tape_recovery. (Fri Dec 08
15:16:24 EAT 2017)
@(#) Ignite-UX Revision B.4.3.94
@(#) net_recovery (opt) $Revision: 10.609 $

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

* Recovery Archive Location = /dev/rmt/0mn

* Number of Archives to Save = 2

* Pax type = tar

ERROR: Cannot stat device file: /dev/vgarchive1/lvol_archive: No such file or
directory (errno = 2). Check /etc/fstab for a bad entry.

** 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
ERROR: Cannot stat device file: /dev/vgarchive1/lvol_archive: No such file or
directory (errno = 2). Check /etc/fstab for a bad entry.
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.

backupdr[/etc]#ll /etc/fstab
-rw-r--r-- 1 oracle dba 1632 Mar 31 2016 /etc/fstab
backupdr[/etc]#\
> 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.
/dev/vg00/lvol_photo070109 /test vxfs delaylog 0 2
/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/lvol_fuo /home/fuo vxfs delaylog 0 2
/dev/vg00/deploy /var/Deploy vxfs delaylog 0 2
/dev/vg48-11/lvol_archive /insure_archive vxfs delaylog 0 2
/dev/vg48-11/lvol_backarch2 /hisarch2 vxfs delaylog,nodatainlog,largefiles,rw,suid 0 2
/dev/vgextdb03/lvol_arch /opt/oracle/archive_web vxfs delaylog 0 2
/dev/vgextdb01/lvol_arch2 /opt/oracle/archive_web2 vxfs delaylog 0 2
/dev/vgarchive1/lvol_archive /opt/oracle/OPS/archive vxfs delaylog 0 2
/dev/vgarchive2/lvol_archive /opt/oracle/OPS/archive2 vxfs delaylog 0 2
#/dev/vg48-10/photo /photo vxfs delaylog 0 2
#/dev/vg48-11/lvol_archive /insure_archive vxfs delaylog 0 2
#/dev/vg48-11/lvol_backarch2 /hisarch2 vxfs delaylog,nodatainlog,largefiles,rw,suid 0 2
/dev/vg00/lvol8 /home vxfs delaylog 0 2
/dev/vg00/lvol2b ... swap pri=1 0 0
/dev/vg00/lvol_swap01 ... swap pri=1 0 0
/dev/vg00/lvol_swap02 ... swap pri=1 0 0
/dev/vg00/lvol_swap03 ... swap pri=1 0 0
/dev/vg00/lvol_swap04 ... swap pri=1 0 0
#/dev/vg00/lvol2b / dump defaults 0 0
#/dev/vg00/lvol_swap01 / dump defaults 0 0
#/dev/vg00/lvol_swap02 / dump defaults 0 0
#/dev/vg00/lvol_swap03 / dump defaults 0 0
#/dev/vg00/lvol_swap04 / dump defaults 0 0
/dev/vgdmp/lvdmp /dmp vxfs delaylog 0 2

Re: make_tape_recovery failed

Torsten. — Fri, 08 Dec 2017 07:57:02 GMT

You could try something like this:

/opt/ignite/bin/make_tape_recovery -x inc_entire=vg00 -I -v -a /dev/rmt/0mn

Re: make_tape_recovery failed

Patrick Wallek — Fri, 08 Dec 2017 14:08:24 GMT

Here's the line it is complaining about in /etc/fstab:

/dev/vgarchive1/lvol_archive /opt/oracle/OPS/archive vxfs delaylog 0 2

Do the /dev/vgarchive1/lvol_archive volume group and logical volume exist (check with 'vgdisplay -v vgarchive1')? Does the /opt/oracle/OPS/archive exist (check with 'bdf')?

If not, then you may want to remove, or comment, that line in /etc/fstab and try again.

Re: make_tape_recovery failed

Bill Hassell — Fri, 08 Dec 2017 18:33:32 GMT

The command line suggested by Torsten is definitely recommended. The Ignite program make_tape_recovery is designed for vg00 only. It is used to restore a boot disk when it has failed (and no mirroring). Without the option -x inc_entire=vg00, all the mountpoints will be included which will likely exceed your tape capacity. Your backup strategy should be make_tape_recovery for failed boot disk recovery, and fbackup for all the mountpoints (including vg00). fbackup knows how to use multiple tapes and is the fastest backup method for tape.

For fbackup, first create a config file like this:

# cat /etc/fbackup.conf
blocksperrecord 4096
records 64
checkpointfreq 8192
readerprocesses 6
maxretries 5
retrylimit 5000000
maxvoluses 200
filesperfsm 5000

Then you can backup your entire system like this:

fbackup -i / -v -c /etc/fbackup.conf -f /dev/rmt/0m > /tmp/fbackup.log 2>&1

All the progress and error messages will be recorded in the logfile /tmp/fbackup.log
Look at this file for the results of the backup.

Re: make_tape_recovery failed

Amiteshjsk — Wed, 27 Dec 2017 07:54:13 GMT

Hi,

Actuallly I think your mount point path is not corrected. Please check library again and mount point mn should be corrected then you select your tape path like /dev/rmt/4mn.

or you can check your tape is proper or not by using below commands...

#mt -f path stat

in output-

Status :BOT online compression immediate-report-mode

thanks,

#amiteshjsk