Sponsored Content
Full Discussion: frecover
Operating Systems HP-UX frecover Post 53347 by Perderabo on Tuesday 13th of July 2004 11:00:09 AM
Old 07-13-2004
When a restore fails because frecover encountered a problem, it offer you a chance to write recovery information into a file. If you did that, you should be able use the -R option to restart the recover. If not, you will need to start over as far as I know.
 

6 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

frecover

Started an frecover from Sam, with a recovery scope and a different destination. Here is what is happening. Starting file recovery... frecover(5423): incorrect volume mounted; frecover(5424): expected volume 1, and got 2 frecover(5433): Do you wish to continue using this volume? (^/^) y... (5 Replies)
Discussion started by: molonede
5 Replies

2. UNIX for Dummies Questions & Answers

frecover on HP 11.11

Hi, Can someone please explain how I can check whether my files were backed-up to tape. I issued this command and got an error:- # frecover -I /tmp/mth -f /dev/rmt/5m frecover(2105): did not find expected file marker frecover(5409): unable to read volume header frecover(5418): not an... (2 Replies)
Discussion started by: gummysweets
2 Replies

3. HP-UX

HP fbackup/frecover to SUN UNIX format?

Hi All, We have about 7 years worth of data which used the HP fbackup utility. Is there any utility to read these tapes on Solaris? The goal is to create new tapes using Legato. Do we need to download them to a box first using frecover, then copy them from SUN using Legato? Any help in... (0 Replies)
Discussion started by: tinakumar
0 Replies

4. HP-UX

frecover command need help urgent please

Hi, I have a tape fbackup done (fbackup -f /dev/rmt/0m -i / -I index.fullfbackup) and I need to restore 3 filesystems, I would like to know the correct command and options: example: I want to restore the filesystem /data1 under /data1 and /data2 under another filesystem /datatest I tried... (4 Replies)
Discussion started by: touny
4 Replies

5. HP-UX

frecover problem

I had to do a recovery and restore from backup (using ignite & backups from fbackup job) on hpux 10.20. Problem is, all users (except root) receive error 'unknown user' when logging in (during script that checks quotas). They can still successfully log in to the system. However, the files... (9 Replies)
Discussion started by: mrviking
9 Replies

6. Red Hat

frecover counterpart on linux

Hello All, The frecover command on HP UX gives information about the backed up file in the format- Magic Field: Machine Identification: System Identification:HP-UX Release Identification:B.11.11 Node Identification: User Identification: Record Size: Time: Media Use:0 Volume Number:1... (1 Reply)
Discussion started by: shamik
1 Replies
AMRESTORE(8)						      System Manager's Manual						      AMRESTORE(8)

NAME
amrestore - extract backup images from an Amanda tape SYNOPSIS
amrestore [ -r | -c | -C ] [ -b blocksize ] [ -p ] [ -h ] tapedevice | holdingfile [ hostname [ diskname [ datestamp [ hostname [ diskname [ datestamp ... ]]]]]] DESCRIPTION
Amrestore extracts backup images from the tape mounted on tapedevice or from the holding disk file holdingfile that match hostname, diskname and datestamp patterns given on the command line. The tape or holding file must be in a format written by the amdump or amflush program. If diskname is not specified, all backups on the tape for the previous hostname are candidates. If datestamp is not specified, all backups on the tape for the previous hostname and diskname are candidates. If no hostname, diskname or datestamp are specified, every backup on the tape is a candidate. Hostname and diskname are special expression descibe in the "HOST & DISK EXPRESSION" section of amanda(8). Datestamp are special expres- sion describe in the "DATESTAMP EXPRESSION" section of amanda(8). For example, if diskname is "rz[23]a", it would match disks rz2a and rz3a. Datestamp is useful if amflush writes multiple backup runs to a single tape. Unless -p is used, candidate backup images are extracted to files in the current directory named: hostname.diskname.datestamp.dumplevel OPTIONS
-b Set the blocksize used to read the tape or holding file. All holding files must be read with a blocksize of 32 KBytes. Amrestore should normally be able to determine the blocksize for tapes on its own and not need this parameter. The default is 32 KBytes. -p Pipe output. The first matching backup image is sent to standard output, which is normally a pipe to restore or tar, then amrestore quits. It may be run again to continue selecting backups to process. Make sure you specify the no-rewind tapedevice when doing this. Note: restore may report "short read" errors when reading from a pipe. Most versions of restore support a blocking factor option to let you set the read block size, and you should set it to 2. See the example below. -c Compress output using the fastest method the compression program provides. Amrestore normally writes output files in a format understood by restore or tar, even if the backups on the tape are compressed. With the -c or -C option, amrestore writes all files in compressed format, even if the backups on the tape are not compressed. Output file names will have a .Z or .gz extension depend- ing on whether compress or gzip is the preferred compression program. This option is useful when the current directory disk is small. -C Compress output using the best method the compression program provides (may be very CPU intensive). See the notes above about the -c option. -r Raw output. Backup images are output exactly as they are on the tape, including the amdump headers. Output file names will have a .RAW extension. This option is only useful for debugging and other strange circumstances. -h Header output. The tape header block is output at the beginning of each file. This is like -r except -c or -C may also be used to compress the result. Amrecover uses the header to determine the restore program to use. If a header is written (-r or -h), only 32 KBytes are output regardless of the tape blocksize. This makes the resulting image usable as a holding file. EXAMPLES
The following does an interactive restore of disk rz3g from host seine, to restore particular files. Note the use of the b option to restore, which causes it to read in units of two 512-byte blocks (1 Kbyte) at a time. This helps keep it from complaining about short reads. % amrestore -p /dev/nrmt9 seine rz3g | restore -ivbf 2 - The next example extracts all backup images for host seine. This is the usual way to extract all data for a host after a disk crash. % amrestore /dev/nrmt9 seine If the backup datestamp in the above example is 19910125 and seine has level 0 backups of disks rz1a and rz1g on the tape, these files will be created in the current directory: seine.rz1a.19910125.0 seine.rz1g.19910125.0 You may also use amrestore to extract a backup image from a holding disk file that has not yet been flushed to tape: % amrestore -p /amanda/20001119/seine.rz1a.2 | restore -ivbf 2 - Amrestore may be used to generate a listing of images on a tape: % mt -f /dev/nrmt9 rewind % amrestore -p /dev/nrmt9 no-such-host > /dev/null This asks amrestore to find images for host no-such-host. It will not find any entries that match, but along the way will report each image it skips. CAVEATS
GNU tar must be used to restore files from backup images created with the GNUTAR dumptype. Vendor tar programs sometimes fail to read GNU tar images. AUTHOR
James da Silva <jds@cs.umd.edu> University of Maryland, College Park SEE ALSO
amanda(8), amdump(8), amflush(8), tar(1) restore(8) AMRESTORE(8)
All times are GMT -4. The time now is 09:03 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy