tar to tape drive command


 
Thread Tools Search this Thread
Top Forums UNIX for Advanced & Expert Users tar to tape drive command
# 8  
Old 10-12-2010
You might want to use dd option "bs=65536" or the like so you write more than 512 bytes a record.

tar will embed nulls in his output even to a pipe to compress unless you use cpio or maybe find an option for tar to stifle most or all of the nulls.

The compress is faster than gzip but twice as big, generally, so gzip or gzip -9 or bzip2 is a better choice. Tape is usually slower than CPU even with bzip2. Play around with the compression level options (bzip2 has a bewildering set), and see what is fast enough. Usually, there is not much difference between gzip -7 and gzip -9, but your data and CPU may vary. Oh, look, rzip, 7zip, . . .

---------- Post updated at 04:48 PM ---------- Previous update was at 04:45 PM ----------

rzip(1): large-file compression program - Linux man page
gzip vs. bzip2 vs. rzip (by Jeremy Zawodny)

---------- Post updated at 05:05 PM ---------- Previous update was at 04:48 PM ----------

PS: If you sort the files from find by extension or file type, you get even better compression! The rzip site says it must have a flat file in -- worried about 32 bit VM space, I guess.
Login or Register to Ask a Question

Previous Thread | Next Thread

8 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

tar command to explore multiple layers of tar and tar.gz files

Hi all, I have a tar file and inside that tar file is a folder with additional tar.gz files. What I want to do is look inside the first tar file and then find the second tar file I'm looking for, look inside that tar.gz file to find a certain directory. I'm encountering issues by trying to... (1 Reply)
Discussion started by: bashnewbee
1 Replies

2. AIX

savevg/tar/mksysb of server-A on remote tape drive possible ?

Every 3 months we have to do backups (smitth mksysb/lsmksysb + tar) on at least 30 workstations. We have to carry around 2 external tape drives to connect to them. It is a pain to do because it takes at least 3 days to do (evening/night shift) and users sometimes complain that there desk is not put... (1 Reply)
Discussion started by: Browser_ice
1 Replies

3. Solaris

Tar & Tape drive without media

Hi all, I would like to know what would happen if the tape (media) is not placed on the drive and a tar command is executed to backup on the tape. My problem is that tar command hanged for multiple days instead of throwing the error, Is it valid behaviour? I was unable to test the... (4 Replies)
Discussion started by: jmsathish
4 Replies

4. AIX

Tape Drive

I have tape drive in one Lpar. when i saw that time tape is in defined state. After that i deleted the tape drive using the rmdev -R command. Then fired the cfgmgr -v command. But I am not getting the tape drive. Now the drive is even not in defined state also. It is not shown the tape drive. How... (1 Reply)
Discussion started by: pernasivam
1 Replies

5. Solaris

backup through tar command on remote tape

Hello Everybody I have two servers, name A & B. I need to take a backup of one directory(/girish) on serverA. But my tape drive is in serverB through tar command. But when I run the following command it doesn't take the backup. Could any one correct my command to take a backup tar cvf - ... (0 Replies)
Discussion started by: girish.batra
0 Replies

6. Solaris

tar on remote tape drive

hello guys, am trying to save a file file1 to a remote tape drive using tar and i get a permission denied error as shown below: server1%tar cvf - file1 | rsh server2 dd of=/dev/rmt/1m conv=sync a file1 1883905K permission denied since server2 requires login username and password, i see in... (3 Replies)
Discussion started by: nom
3 Replies

7. UNIX for Advanced & Expert Users

Does tar do crc checking on a tape or tar file?

Trying to answer a question about whether tar table-of-contents is a good tool for verifying tape data. (1 Reply)
Discussion started by: tjlst15
1 Replies

8. Solaris

Command to determine Tape Drive model and make

Hi, We have some IBM LTO tape drives connect over SAN. I have the following questions :- 1) Command that can list the tape drive details like who is manufacturer, model number, make etc etc 2) I would like to know what are the key differences between IBM LTO Generation 1 and Generation... (5 Replies)
Discussion started by: new2prog
5 Replies
Login or Register to Ask a Question
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)