Sponsored Content
Full Discussion: CPIO Backup End of Media
Operating Systems SCO CPIO Backup End of Media Post 302308655 by systime_nz on Monday 20th of April 2009 01:17:49 AM
Old 04-20-2009
CPIO Backup End of Media

I dont recommend multi tapes with CPIO.

To fit more onto a tape, I would suggest you use 'compress -H' to compress the data. Your initial find command is piped to compress -H which in turn is piped to the destination device

To read the contents of the tape you will need to use 'uncompress' which is piped from 'dd if' command and uncompress is piped to cpio
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

backup listing(cpio)

Hi i am using HPUX and i want to know wht is the command to see the listing from the tape device.. i have taken the backup using cpio -ocvB>/dev/rmt/0m while seeing the listing using cpio -itvB</dev/rmt/0m it is not showing the listing giving message -c option sd be there if i put -c... (1 Reply)
Discussion started by: Prafulla
1 Replies

2. UNIX for Dummies Questions & Answers

cpio backup to a remote device..

Hi, Needing to perform a backup of one system to the tape unit on another system. Why, well because the local tape device is stuffed and I desparately need to have a backup completed successfully sooner rather than not at all. My question is how do I set the below code to allow me to perform... (3 Replies)
Discussion started by: Cameron
3 Replies

3. UNIX for Dummies Questions & Answers

backup with CPIO

Hi All, I have a tape backup(DDS2) with cpio. I want to restore just some directory from this device but I do not know the command ?? other question what is the best cpio command to take more than 8 GB data ? thanks Alice (1 Reply)
Discussion started by: alisevA3
1 Replies

4. UNIX for Advanced & Expert Users

extract cpio backup on tape

Hi, I was wondering, If I take a backup using cpio to tape from UNIX, can I extract data on windows box using cpio for windows? Anybody ever do this? Thanks. (1 Reply)
Discussion started by: yonez
1 Replies

5. SCO

cpio Backup and restore to spare server fails

Our company purchased a spare HP ML350 server - identical to current one in use to act as minimal downtime replacement should the inevitable happen. After install of OS 5.0.7 and restore of cpiobackup I get this message: -: Syntax error: Hostname= $inexpected The SCO licence policy... (4 Replies)
Discussion started by: moondogi
4 Replies

6. Shell Programming and Scripting

rsync backup mode(--backup) Are there any options to remove backup folders on successful deployment?

Hi Everyone, we are running rsync with --backup mode, Are there any rsync options to remove backup folders on successful deployment? Thanks in adv. (0 Replies)
Discussion started by: MVEERA
0 Replies

7. UNIX for Dummies Questions & Answers

Remote Tape Backup Using cpio

Hi all, I've got two HP machines running HP-UX 11.31 and would like to remotely backup one server onto another server's tape unit using the cpio command. The two servers use a secured communication channel, i.e ssh. Kindly help, Koketso (1 Reply)
Discussion started by: Koketso
1 Replies

8. AIX

CPIO restoration from LTO2 tape media on AIX 4.3.3

Hi, AIXers :) Recently i'm playing around with cpio command, when i try to list out content from LTO2 Tape media using command: #cpio -itvc < /dev/rmt1 it's stopped at particular path 100777 root 1042591 Mar 24 10:09:05 2012 /home/uv/bin/usd and there was an error thrown out: ... (2 Replies)
Discussion started by: polar
2 Replies

9. UNIX for Beginners Questions & Answers

Need to end Backup Process SCO Openserver 5

I was attempting to run a backup at our business last Friday evening when I apparently locked up our whole mainframe. Rather than observing the current time and adding a minute or two to that for the backup start time (like I typically would), I accidentally entered the actual current time to the... (11 Replies)
Discussion started by: hometrics
11 Replies

10. UNIX for Advanced & Expert Users

Cpio - input files (from list) are stored in different order inside cpio archive - why?

Due to budget constraints I have to reinvent an Enterprise backup system in a SPARC (sun4v) Solaris estate (10 & 11). (yep - reinvent wheel, fun but time consuming. Is this wise?! :confused: ) For each filesystem of interest, to try to capture a 'catalog' at the front of each cpio archive (for... (1 Reply)
Discussion started by: am115998
1 Replies
COMPRESS(1)						    BSD General Commands Manual 					       COMPRESS(1)

NAME
compress, uncompress -- compress and expand data SYNOPSIS
compress [-fv] [-b bits] [file ...] compress -c [-b bits] [file ...] uncompress [-fv] [file ...] uncompress -c [file ...] DESCRIPTION
The compress utility reduces the size of files using adaptive Lempel-Ziv coding. Each file is renamed to the same name plus the extension .Z. A file argument with a .Z extension will be ignored except it will cause an error exit after other arguments are processed. If compres- sion would not reduce the size of a file, the file is ignored. The uncompress utility restores compressed files to their original form, renaming the files by deleting the .Z extensions. A file specifica- tion need not include the file's .Z extension. If a file's name in its file system does not have a .Z extension, it will not be uncompressed and it will cause an error exit after other arguments are processed. If renaming the files would cause files to be overwritten and the standard input device is a terminal, the user is prompted (on the standard error output) for confirmation. If prompting is not possible or confirmation is not received, the files are not overwritten. As many of the modification time, access time, file flags, file mode, user ID, and group ID as allowed by permissions are retained in the new file. If no files are specified or a file argument is a single dash ('-'), the standard input is compressed or uncompressed to the standard output. If either the input and output files are not regular files, the checks for reduction in size and file overwriting are not performed, the input file is not removed, and the attributes of the input file are not retained in the output file. The options are as follows: -b bits The code size (see below) is limited to bits, which must be in the range 9..16. The default is 16. -c Compressed or uncompressed output is written to the standard output. No files are modified. The -v option is ignored. Compression is attempted even if the results will be larger than the original. -f Files are overwritten without prompting for confirmation. Also, for compress, files are compressed even if they are not actually reduced in size. -v Print the percentage reduction of each file. Ignored by uncompress or if the -c option is also used. The compress utility uses a modified Lempel-Ziv algorithm. Common substrings in the file are first replaced by 9-bit codes 257 and up. When code 512 is reached, the algorithm switches to 10-bit codes and continues to use more bits until the limit specified by the -b option or its default is reached. After the limit is reached, compress periodically checks the compression ratio. If it is increasing, compress continues to use the existing code dictionary. However, if the compression ratio decreases, compress discards the table of substrings and rebuilds it from scratch. This allows the algorithm to adapt to the next "block" of the file. The -b option is unavailable for uncompress since the bits parameter specified during compression is encoded within the output, along with a magic number to ensure that neither decompression of random data nor recompression of compressed data is attempted. The amount of compression obtained depends on the size of the input, the number of bits per code, and the distribution of common substrings. Typically, text such as source code or English is reduced by 50-60%. Compression is generally much better than that achieved by Huffman cod- ing (as used in the historical command pack), or adaptive Huffman coding (as used in the historical command compact), and takes less time to compute. EXIT STATUS
The compress and uncompress utilities exit 0 on success, and >0 if an error occurs. The compress utility exits 2 if attempting to compress a file would not reduce its size and the -f option was not specified and if no other error occurs. SEE ALSO
gunzip(1), gzexe(1), gzip(1), zcat(1), zmore(1), znew(1) Welch, Terry A., "A Technique for High Performance Data Compression", IEEE Computer, 17:6, pp. 8-19, June, 1984. STANDARDS
The compress and uncompress utilities conform to IEEE Std 1003.1-2001 (``POSIX.1''). HISTORY
The compress command appeared in 4.3BSD. BUGS
Some of these might be considered otherwise-undocumented features. compress: If the utility does not compress a file because doing so would not reduce its size, and a file of the same name except with an .Z extension exists, the named file is not really ignored as stated above; it causes a prompt to confirm the overwriting of the file with the extension. If the operation is confirmed, that file is deleted. uncompress: If an empty file is compressed (using -f), the resulting .Z file is also empty. That seems right, but if uncompress is then used on that file, an error will occur. Both utilities: If a '-' argument is used and the utility prompts the user, the standard input is taken as the user's reply to the prompt. Both utilities: If the specified file does not exist, but a similarly-named one with (for compress) or without (for uncompress) a .Z exten- sion does exist, the utility will waste the user's time by not immediately emitting an error message about the missing file and continuing. Instead, it first asks for confirmation to overwrite the existing file and then does not overwrite it. BSD
May 17, 2002 BSD
All times are GMT -4. The time now is 07:04 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy