Sponsored Content
Full Discussion: How to restore from disk?
Operating Systems HP-UX How to restore from disk? Post 303012584 by jduehmig on Tuesday 6th of February 2018 10:18:16 AM
Old 02-06-2018
How to restore from disk?

Our new rx2800 server is running HP-UX 11iV3. We have a cron script to perform an fbackup to a file on disk nightly. Now I'm trying to do a test restore, but I can't seem to find the correct way to specify the backup file as the source in frecover. Can anyone point me in the right direction?
Thanks,
Joe

Last edited by rbatte1; 02-07-2018 at 01:31 PM.. Reason: Emboldened commands for clarity
 

6 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

Restore to disk from tape

I have been restoring from tape some old data. I have done quite a few tapes and have had no problems until now. The command I am running is "dd if=/dev/rmt/1hbn bs=1024 | tar -pBxF - ". This is the second tape have have come up with the error "Not enough space". This tape has a couple of... (1 Reply)
Discussion started by: mtoombs
1 Replies

2. UNIX for Dummies Questions & Answers

How to restore a dump file on the disk

Hi all, i am a real dummy to unix and in need of help.My platform is Sun solaris(5.9) I have a dump file, an oracle cold backup taken with ufsdump command. This dump file resides on the disk, not the tape. I want to extract this dump file to a directory. But i cant, i read about ufsrestore... (1 Reply)
Discussion started by: merope
1 Replies

3. Solaris

after ZFS can not restore VTOC of disk..

I tried to use zfs .. only for test ..so when I take my test disks into zfs pool their VTOC changed .. and 7th slice does not appear now. How can I restore default VTOC to my disks. my machine is x86 .. SunFire X4200 .. so this disks do not have slices like sparc machines .. they have... (6 Replies)
Discussion started by: samar
6 Replies

4. AIX

mksysb restore - Wrong OS level for restore

Hi all, I am still working on my mksysb restore. My latest issue is during an alt_disk_install from tape I got the following error after all the data had been restored. 0505-143 alt_disk_install: Unable to match mksysb level 5.2.0 with any available boot images. Please correct this... (0 Replies)
Discussion started by: pobman
0 Replies

5. AIX

Dd of disk contains vg and restore on another m/c

Hello gurus, I have a requirement of backup of a vg containing a file system. vg1 contains 3 LV each of 50G size. They are coming out from ~350G harddisk. and only 150G is being used. Now, i want to dd this hdisk and restore to another machine. I am not sure how to go about this. Can some... (3 Replies)
Discussion started by: abhishekdave
3 Replies

6. UNIX for Advanced & Expert Users

LVM - restore metadata on other disk

Hi guys, I would like to ask your opinion about my theory, how to fix my broken LVM without risking any data loss. I use Archlinux at home. I just love this distro, even it gives me a lots of work (particularly after system updates). Basic system spec: AMD FX(tm)-6100 Six-Core Processor... (1 Reply)
Discussion started by: lyynxxx
1 Replies
rmt(1M) 																   rmt(1M)

NAME
rmt - remote magnetic-tape protocol module SYNOPSIS
DESCRIPTION
is a program used by the remote dump and restore programs for manipulating a magnetic tape drive through an interprocess communication (IPC) connection. The and commands also use to achieve remote backup capability (see fbackup(1M) and frecover(1M)). is normally started up with an or call (see rexec(3N) and rcmd(3N)). accepts requests specific to the manipulation of magnetic tapes, performs the commands, then responds with a status indication. DDS devices that emulate magnetic tapes are also supported. All responses are in ASCII and in one of two forms. Successful commands have responses of where number is an ASCII representation of a decimal number. Unsuccessful commands are responded to with where error-number is one of the possible error numbers described in errno(2) and error-message is the corresponding error string as printed from a call to (see perror(3C)). The protocol is comprised of the following commands: Open the specified device using the indicated mode. device is a full pathname and mode is an ASCII representation of a decimal number suitable for passing to (see open(2)). If a device is already open, it is closed before a new open is performed. Open the specified device using the indicated mode. device is a full pathname and mode is an ASCII representation of an octal number suitable for passing to If a device is already open, it is closed before a new open is performed. Close the currently open device. The device specified is ignored. Perform an operation using the specified parameters (see lseek(2)). The response value is that returned from by Write data onto the open device. reads count bytes from the connection, aborting if a premature end-of-file is encountered. The response value is that returned from by (see write(2)). Read count bytes of data from the open device. If count exceeds the size of the data buffer (10 Kbytes), it is truncated to the data buffer size. then performs the requested and responds with if the read was successful. Otherwise an error is returned in the standard format. If the read was successful, the data read is then sent. Perform a command using the specified parameters. Parameters are interpreted as ASCII representations of the decimal values to be placed in the and fields of the structure used in the call. The return value is the count parame- ter when the operation is successful. Return the status of the open device, as obtained with a call. If the operation was successful, an ACK is sent with the size of the status buffer, then the status buf- fer is sent (in binary). Return the status of the open device, as obtained with a call. If the operation was successful, an ACK is sent with the size of the status buffer, then the status buf- fer is sent (in binary). Return the status of the open device, as obtained with a call. If the operation was successful, an ACK is sent with the size of the status buffer, then the status buffer is sent in the following ASCII format: machine<blank>value<newline> stat_struct_member_name<blank>value<newline> The end of the data is indicated by an ASCII NULL character. See for the definition. In addition to the struct stat information, there is an entry in the buffer describing the machine type as returned from a call (see uname(2)). In the above format ``machine'' is a key word. All fields except of the are returned. Return the status of the open device, as obtained with a call. If the operation was successful, an is sent with the size of the status buffer, then the status buffer is sent in the following ASCII format: machine<blank>value<newline> mtget_struct_member_name<blank>value<newline> The end of the data is indicated by an ASCII NULL character. See for the definition. In addition to the struct mtget information there is an entry in the buffer describing the machine type as returned from a call. In the above format "machine" is a keyword. Any other command causes to exit. RETURN VALUE
Device status is returned in the field contains defined macros for checking the status bits. DIAGNOSTICS
All responses are of the form described above. WARNINGS
Use of this command for remote file access protocol is discouraged. AUTHOR
was developed by the University of California, Berkeley. SEE ALSO
ftio(1), fbackup(1M), frecover(1M), dump(1M), restore(1M), rcmd(3N), rexec(3N). rmt(1M)
All times are GMT -4. The time now is 05:13 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy