Sponsored Content
Full Discussion: Backup and restore using tar
Operating Systems Linux Red Hat Backup and restore using tar Post 302759053 by hicksd8 on Monday 21st of January 2013 09:56:09 AM
Old 01-21-2013
The /dev directory holds the device nodes for the hardware. It is the connection between the O/S and the actual hardware (eg, /dev/sda being a disk drive).

When you restore a backup to different hardware, these devices will be wrong for that hardware and will need to be rebuilt/reset to suit. I'm not a RedHat expert so I don't know exactly how that would be achieved. Perhaps RedHat experts on this forum can tell us how to restore to different hardware.

Anyway, the point is you need to backup all hard disk directories and ignore the directories which are really pseudo memory (eg, /proc). You need to distinguish between the two.

Work on the principle that it is better to have a backup containing stuff that is unnecessary and/or needs modification to suit new hardware rather than not have a copy of it at all.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Cannot restore a TAR backup

I backed up a unix database using "tar -cvf /dev/rmt1 -N 800 /*" Normally I would restore this using "tar -xvf /dev/rmt1 -N 800" This is reporting an error about "not enough memory" I have done a new test backup and restore using the same commands and they work. ANY IDEAS ? (2 Replies)
Discussion started by: Ross.Goodman
2 Replies

2. Solaris

tar - restore a file

We use tar for backing up a server. I need to restore just one file from this backup. Anyone know the syntax? (2 Replies)
Discussion started by: frustrated1
2 Replies

3. UNIX for Dummies Questions & Answers

Question regarding tar restore

I created a relative backup of my home directory using tar into a file named backup.tar. No problem there. I checked it out using the table of contents command to list the contents of the backup.tar file, and there is no problem there either. But, when I tried restoring backup.tar into a... (2 Replies)
Discussion started by: Relykk
2 Replies

4. Solaris

Backup / restore

Hi.... everyone could help me to understand how to do a backup of my servers .. operating systems is sun solaris 8 . I have some question about .... 1) Is better backup phisical disk or partition ??? i sow the command is ufsdump 0cfu /expbck/bcksunver/c0t0d0s5 dev/dsk/c0t0d0s5 to... (4 Replies)
Discussion started by: tt155
4 Replies

5. AIX

Backup and restore

I have several H80 machines, all with AIX 4.3.3. On these machines I have mksysb running for rootvg backups and savevg for non-rootvg backups. I'm trying to get a list of files on the tapes, but I can't seem to do it with tar for the mksysb images. I keep getting the directory checksum errors?... (3 Replies)
Discussion started by: uXion
3 Replies

6. HP-UX

F-Backup restore

Hello! i have a blank harddrive and a complete tape backup of the workstation. the backup is made with F-Backup. Now my question is: how can i restore my workstation? thanks for every idea! paul tittel hup-si (3 Replies)
Discussion started by: paultittel
3 Replies

7. UNIX for Dummies Questions & Answers

Restore files with TAR -- Help

Hi, Can anyone tell me the right TAR command to restore all the files dirs/subdirs/files etc. to a given directory on my hdd from a TAPE drive? I already used the list function to see that there is data on it with this commando: # tar tf /dev/st0 Now I need to copy all the data to a... (1 Reply)
Discussion started by: severt
1 Replies

8. Shell Programming and Scripting

Backup/restore scripts

hi people i am in need of some assistance here hoping to star a linux course in january to wanted to get some experiance before starting so got a hold of some old assessments from a mate at college so just working through them in my spare time for the past 8 weeks or so and this is the final ? that... (2 Replies)
Discussion started by: boabbyrab
2 Replies

9. AIX

Backup and restore

Hi experts, i got a question. i have a production server with two Volume Group(VG) which are rootvg and datavg. Both of these VGs are 256 PP SIZE. On Disaster Recovery Server (DR server) contains two empty hardisks for restoring rootvg and datavg from production server. This two hardisks are... (7 Replies)
Discussion started by: polar
7 Replies

10. Red Hat

Backup / Restore

Hi, I need to back up a RH file system (96G). The files are oracle .dbf format some of which are 5G in size. I know that tar has got a size restriction of 2G so I cannot use this. Can anyone recommend an alternative way of backuping up this FS? I have been looking at dump but this... (6 Replies)
Discussion started by: Duffs22
6 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 01:02 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy