Re: make_tape_recovery just sitting there I tried:
make_tape_recovery -Av -p
and again, it just hangs after the following:
$make_tape_recovery -Av -p
* Creating local directories for configuration files and
archive.
======= 07/09/07 09:05:39 EDT Started make_tape_recovery. (Mon Jul
09
09:05:39 EDT 2007)
@(#) Ignite-UX Revision A.3.7.95
@(#) net_recovery (opt) $Revision: 10.575.1.1 $
* 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
WARNING: Filesystem /bulk/1 is not mounted. It will be ignored.
WARNING: Filesystem /bulk/2 is not mounted. It will be ignored.
It doesn't lock the machine up, and nothing appears in /var/adm/syslog/
syslog.log
On Jul 8, 12:27 pm, "Antonio" <x...@pippo.it> wrote:
> From the log, you make_tape_recovery is not good, same FS are only
> partially saved (1) and other are not saved (such as /opt say 0 >> not
> saved).
> Only FileSystems that have number 2 are saved by make_tape_recovery
> Try to use
> make_tape_recovery -Av -p for preview or make_tape_recovery -Av to backup
> your system and wait to finish command save_config.
> If you want to exclude same FS use -x exclude=/mount_point
>
> Regards
> Antonio
>
> "mohnkern" <mohnk...@gmail.com> ha scritto nel messaggionews:1183755460.926415.110770@m36g2000hse .googlegroups.com...
>
> > We've got an HP-UX 10.20 box that we've been doing recovery tapes for
> > years, every 3 months. However, this month, when we ran
> > make_tape_recover -v -p inc_entire=vg00 to get a preview, the job
> > starts, but then just sits there:
>
> > $make_tape_recovery -v -p inc_entire=vg00
> > * Creating local directories for configuration files and
> > archive.
>
> > ======= 07/06/07 16:17:21 EDT Started make_tape_recovery. (Fri Jul
> > 06
> > 16:17:21 EDT 2007)
> > @(#) Ignite-UX Revision A.3.7.95
> > @(#) net_recovery (opt) $Revision: 10.575.1.1 $
>
> > * 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
>
> > WARNING: Filesystem /bulk/1 is not mounted. It will be ignored.
> > WARNING: Filesystem /bulk/2 is not mounted. It will be ignored.
>
> > In? dsk/vg name minor# Associated
> > disks/mountpoints
> > 1 v /dev/vg00 0x00 /dev/dsk/
> > c3t6d0
> > /dev/vg00/lvol1 /
> > stand 1
> > /dev/vg00/lvol2
> > /dev/vg00/
> > lvol3 / 1
> > /dev/vg00/lvol5 /
> > opt 0
> > /dev/vg00/lvol6 /
> > tmp 0
> > /dev/vg00/lvol7 /
> > usr 1
> > /dev/vg00/lvol8 /
> > var 0
> > 0 v /dev/vg01 0x01 /dev/dsk/
> > c3t4d0 /dev/dsk/c3t3d0
> > /dev/vg01/lvol1 /fs/
> > pestudies 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
> > WARNING: Filesystem /bulk/1 is not mounted. It will be ignored.
> > WARNING: Filesystem /bulk/2 is not mounted. It will be ignored.
> > * Creating System Configuration.
> > WARNING: The volume group /dev/vg00 will be only partially included in
> > the
> > System Recovery Archive. This means that not all files and
> > directories on this volume group will be restored when the
> > archive is
> > installed. This message can be suppressed using the "-P s"
> > option for
> > make_tape_recovery. See make_tape_recovery(1M) for more
> > details.
>
> > * /opt/ignite/bin/save_config -f
> > /var/opt/ignite/recovery/2007-07-06,16:17/system_cfg vg00
>
> > -----------------------------------------------------------------------------------------------------------------------------------------------
>
> > It doesn't lock up (you can ctrl-c out) and there's nothing in /var/
> > adm/syslog/syslog.log indicating a problem. I'm at a loss to figure
> > out what's happening. We let it sit there for two and 1/2 hours, and
> > nothing.
>
> > Am I impatient, or is there some way to figure out why it isn't
> > completing the preview? |