topic Re: fbackup command in Operating System - HP-UX

fbackup command

Son dam bi — Mon, 19 Oct 2009 06:12:06 GMT

I have a old tape which used HP fbackup to backup , can advise if I want to know what files is in the tape , can advise how can I list it out ? thx

Re: fbackup command

Suraj K Sankari — Mon, 19 Oct 2009 06:47:57 GMT

Hi,
Restore your backup into any tmp area
with frestore command.

Suraj

Re: fbackup command

SoorajCleris — Mon, 19 Oct 2009 08:14:30 GMT

Hi,

Create a temporory mount point with enough spcae and restore the backup there. Use "frecover" command to restore the back up.

Regards,
Sooraj

Re: fbackup command

Dennis Handly — Mon, 19 Oct 2009 10:42:51 GMT

Just use frecover with "-I path" to get a list into "path".

Re: fbackup command

OldSchool — Tue, 20 Oct 2009 15:02:26 GMT

Dennis has it...if you want to know what's on the tape, extract the index from the tape to a file and examine that.

btw: there is no "frestore", and it why would you restore the entire tape to disk merely to find out what's on it???

Re: fbackup command

Julián Aimar — Tue, 20 Oct 2009 15:50:49 GMT

Hi

generate the index in disk through the syntax:

#frecover -I // -f /dev/rmt/

after this you can verify the archives on the index file.

Index file contains the list of all files backed up by fbackup in that archive

Example,

#frecover -I /tmp/Index -f /dev/rmt/0m

#more /tmp/Index

Buena suerte !!

Re: fbackup command

Bill Hassell — Wed, 21 Oct 2009 00:46:22 GMT

You can use two methods to identify the tape:

frecover -V - -f /dev/rmt/

frecover -I - -f /dev/rmt/

The first (-V -) will show you the header on the tape (date/time when the tape was made, etc). The second (-I -) shows you the table of contents. While you can specify a file to contain the contents (-I /tmp/files.index) you can immediately se the results using - to specify standard output.

Re: fbackup command

Michael Steele_2 — Wed, 21 Oct 2009 01:48:52 GMT

Hi

Actually, you want to use frecover to verify the contents of a fbackup tape. The 'N' arguement is 'no recover'

frecover -rNv -f /dev/rmt/0m 2> /tmp/file
-or- just
frecover -rNv -f /dev/rmt/0m | more