Full backup lasts only 15 minutes!!!

[JUAN_91]

Ignite-UX B.2.2.161.
HP-UX B.11.00.
Model: N4000-44
Main Memory: 2048 MB
Processors: 4
OS mode: 64 bit
LVM Device file mount point size fs type
/dev/vg00:
/dev/vg00/lvol1 /stand 100 hfs
/dev/vg00/lvol2 swap 1408
/dev/vg00/lvol3 / 200 vxfs
/dev/vg00/lvol4 /opt 1600 vxfs
/dev/vg00/lvol5 /tmp 500 vxfs
/dev/vg00/lvol6 /users 700 vxfs
/dev/vg00/lvol7 /usr 1200 vxfs
/dev/vg00/lvol8 /var 600 vxfs
/dev/vg00/lvol9 swap 2200
/dev/vg00/lvol10 /alcatel 17528 vxfs
/dev/vg00 unallocated 0

./make_recovery -C -v
shutdown -r now
boot pri (interact YES)
ISL hpux -is
vgchange -a y
mountall -l
fbackup -0i / -f /dev/rmt/0m

[Mahesh Kumar Malik]

Hi

Since you are not seeing any errors, believe backup is perfect. Since backup is being taken in single user mode, throughput is better.

You may verify the backup to by listing files backed up on tape

Regards
Mahesh

[JUAN_91]

Do you think that a HP-UX + applications are backed up in least than 15' ?

Thanks for your response and regards,

Juan.

[melvyn burnard]

well you do not state what type of device is used, nor what interface it is on.
Have you also checked the backup tape contents by using frecover and either checking the Index file listing, or a test recovery using the -N option to disable writes to disc?

[Florian Heigl (new acc)]

You might want to try make_tape_recovery -A -C -v for a change.

See the man page on the difference, in short it means 'include_entire_vg00', so maybe Your /alcatel really wasn't included.

[Gavin Clarke]

Florian is right, make_recovery really isn't a good command to use. There are many links that will give you good suggestions about make_tape_recovery here is an example:

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=939864

[Gavin Clarke]

And here is another link to the forum which 'sort of' explains why make_recovery isn't used, it is obsolete.

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=866167

[Steven E. Protter]

WEll, we're four major releases behind on Ignite and using obsolete make_recovery instead of make_tape_recovery.

Try make_tape_recovery and see how long it takes.

Try Ignite version 6.x as well.

The final test, where the rubber meets the road is how the Ignite recvoery goes. I would not rely on it at all under these circumstances.

SEP

[Alessandro Pilati]

Juan,
I did a full system backup with make_tape_recovery in 23 minutes, so I think it's normal...

[Florian Heigl (new acc)]

Allessandro - did you also have a 18GB data volume in Your vg00? I could image a DDS5 being that fast, don't get me wrong :)


Oh, yeah, btw...: Juan, production data has no reason at all to reside in vg00.
(about 10 reasons for it going from data loss to longer downtimes)

Florian