10 More Discussions You Might Find Interesting
1. UNIX for Beginners Questions & Answers
Hi,
I have an mksysb backup which consists of 2 Volume, how do I combine it into a single Volume or tape ?
Appreciate it (1 Reply)
Discussion started by: AIXBlueCat
1 Replies
2. AIX
Hello,
We need to make a copy of a backup tape, using the 2 tape recorders in IBM 3582 Tape Library
We tried tu use "tcopy", it seems to work fine (no error messages) but we aren't sure if we can rely on it.
my question is how to check if the copy succeded or not, but i also want to know... (3 Replies)
Discussion started by: fastlane3000
3 Replies
3. UNIX for Dummies Questions & Answers
I have several files that I need to get off of a backup tape. I'm using AIX 4.3 (I know this is old) and our backups are done using the bru command. I need to copy these files to a specific location, and not restore them to the original location. Can anyone tell me what command I should use to do... (4 Replies)
Discussion started by: troy
4 Replies
4. UNIX for Dummies Questions & Answers
Dear sir/madam
Could you tell me how to copy or get data from tape to any folder in unix?
Thanks, (2 Replies)
Discussion started by: seyha_moth
2 Replies
5. AIX
I am new to AIX. I want to make a duplicate tape. How can I do that ? (1 Reply)
Discussion started by: Anonno
1 Replies
6. Solaris
Hello, I am trying to copy a boot tape DDS-01 with miniroot, but i donīt get this copy. i have already used the command dd, but donīt work. There are other way to get it. (0 Replies)
Discussion started by: carelias
0 Replies
7. UNIX Desktop Questions & Answers
Hi,
How to copy a file (online.exp031204.tar.Z) from the tape drive /dev/rStp0 (2 Replies)
Discussion started by: rahmanm
2 Replies
8. Solaris
I have two tape drives attached to my system , and i am trying to copy one tape to another using both tape drives and using the following command :
dd if=/dev/rmt/1 of=/dev/rmt/2
but unfortunitly i am getting the following error :
read: Not enough space
0+0 records in
0+0 records... (2 Replies)
Discussion started by: itsgeorge
2 Replies
9. Shell Programming and Scripting
I have a file called feed_file. Every week, I would like to copy this file
to tape. I would not like the file on this tape to be over written with
the previous weeks file. So what I would prefer to do is to add time stamp
at the end of each weeks file on the tape in order for the files to look... (1 Reply)
Discussion started by: ted
1 Replies
10. Shell Programming and Scripting
I am copying a file to tape but it keeps failing, can any body help?
I tried the tar,cp, mv commands and not seems to be working
#!/bin/ksh
#
# Return Codes
# 0 - success
# 1 - failure
#
#
#
dat=`date +%y%m%d`
cp /u07/work/theo_test.log /dev/rmt0/exp_dump.${dat}.$$
if (( ${?}... (1 Reply)
Discussion started by: ted
1 Replies
TAR(5) File Formats Manual TAR(5)
NAME
tar - tape archive file format
DESCRIPTION
Tar, (the tape archive command) dumps several files into one, in a medium suitable for transportation.
A ``tar tape'' or file is a series of blocks. Each block is of size TBLOCK. A file on the tape is represented by a header block which
describes the file, followed by zero or more blocks which give the contents of the file. At the end of the tape are two blocks filled with
binary zeros, as an end-of-file indicator.
The blocks are grouped for physical I/O operations. Each group of n blocks (where n is set by the b keyletter on the tar(1) command line
-- default is 20 blocks) is written with a single system call; on nine-track tapes, the result of this write is a single tape record. The
last group is always written at the full size, so blocks after the two zero blocks contain random data. On reading, the specified or
default group size is used for the first read, but if that read returns less than a full tape block, the reduced block size is used for
further reads.
The header block looks like:
#define TBLOCK 512
#define NAMSIZ 100
union hblock {
char dummy[TBLOCK];
struct header {
char name[NAMSIZ];
char mode[8];
char uid[8];
char gid[8];
char size[12];
char mtime[12];
char chksum[8];
char linkflag;
char linkname[NAMSIZ];
} dbuf;
};
Name is a null-terminated string. The other fields are zero-filled octal numbers in ASCII. Each field (of width w) contains w-2 digits, a
space, and a null, except size and mtime, which do not contain the trailing null and chksum which has a null followed by a space. Name is
the name of the file, as specified on the tar command line. Files dumped because they were in a directory which was named in the command
line have the directory name as prefix and /filename as suffix. Mode is the file mode, with the top bit masked off. Uid and gid are the
user and group numbers which own the file. Size is the size of the file in bytes. Links and symbolic links are dumped with this field
specified as zero. Mtime is the modification time of the file at the time it was dumped. Chksum is an octal ASCII value which represents
the sum of all the bytes in the header block. When calculating the checksum, the chksum field is treated as if it were all blanks. Link-
flag is NULL if the file is ``normal'' or a special file, ASCII `1' if it is an hard link, and ASCII `2' if it is a symbolic link. The
name linked-to, if any, is in linkname, with a trailing null. Unused fields of the header are binary zeros (and are included in the check-
sum).
The first time a given i-node number is dumped, it is dumped as a regular file. The second and subsequent times, it is dumped as a link
instead. Upon retrieval, if a link entry is retrieved, but not the file it was linked to, an error message is printed and the tape must be
manually re-scanned to retrieve the linked-to file.
The encoding of the header is designed to be portable across machines.
SEE ALSO
tar(1)
BUGS
Names or linknames longer than NAMSIZ produce error reports and cannot be dumped.
4.2 Berkeley Distribution November 7, 1985 TAR(5)