07-11-2008
Hi,
I have got the following error when trying to list the content:
# tctl -f /dev/rmt0.1 fsf 3
# restore -tvqf /dev/rmt0
restore: 0511-123 The volume on /dev/rmt0 is not in backup format.
Mount volume 1 on /dev/rmt0.
Press the Enter key to continue.
# tar -tvf /dev/rmt0
tar: 0511-169 A directory checksum error on media; -559038737 not equal to 1726.
Can you please help?
Thanks!!
Victor Cheung
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Whats up guys. I dont ask many questions but this time i need a quick one answerd.
NOS: AIX 4.3.3 and 4.3.2
BOX: RS/6000 F50
i have 12 pv's (mirrored) and 2 vg's and i want them both backed up @ once on one tape drive so i can do it via cron.
I have looked at mksysb and backup. my main... (5 Replies)
Discussion started by: Optimus_P
5 Replies
2. UNIX for Advanced & Expert Users
anybody knows how to recover from a tape in AIX 4.3 from a IBM rs6000 170 system backup done only 97% ? (0 Replies)
Discussion started by: jupiter8
0 Replies
3. AIX
Currently I have a Dell Ultrium LTO 2 Tape Drive. I am going to have a IBM AIX server. Just wonder if it is possibe to connect this tape drive to the aix server? I have Brightstor Arcserver installed on another win 2003 server. Is it possible to install the arcserve agent on the aix and use the... (1 Reply)
Discussion started by: ming413
1 Replies
4. AIX
Hi,
My situation is to write a backup script for AIX server which doesnt have a tape mounted.
They have created a folder on windows so that all AIX backup files can be moved to that windows folder where they will put these AIX backup files on a tape.
Appreciate help.
Regards
dsrules. (7 Replies)
Discussion started by: dsrules
7 Replies
5. AIX
hello,
I am facing this problem when trying to prepare AIX 5.3 for Veritas Backup:
Veritas Software is not able to communicate properly with our tape library
When we tried to run these commands here's the output
# cfgmgr -l fscsi0
# cfgmgr -l fscsi2
# cfgmgr -l fscsi1
cfgmgr:... (3 Replies)
Discussion started by: filosophizer
3 Replies
6. Solaris
Hi,
I want to take backup of files older than 20 days from a directory onto a tape drive on remote machine on Solaris.
The files are of format abc-20100301000000.gz on my local machine.
I know the below commands for searching files older than x days and command for backup procedure.
solar1 #... (7 Replies)
Discussion started by: jyothi_wipro
7 Replies
7. AIX
Hello,
I am trying to install a server from a mksysb made on an other server but whit his proper image.data and bosinst.data, but after selecting boot from DLT tape and starting installation in normal mode with default setting, I get this error message :
error / warning
there is no disk... (2 Replies)
Discussion started by: astjen
2 Replies
8. AIX
Hi,
We have backup on LTO-3 tape it was taken from windows via windows backup utility,
now the issue is that we want to list the content of tape in aix 6.1. Kindly help.
Regards
Salman (3 Replies)
Discussion started by: salmanraza
3 Replies
9. 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
10. AIX
Hello,
Running AIX 7.2 on Power9 bare-metal (no LPAR and no NIM server), in the process of creating a guide on MKSYSB process.
I understand that MKSYSB is a backup of the rootvg and we can exclude stuff via exclude.rootvg file, the rest of the data volumes are mapped to the system as LUNs via... (7 Replies)
Discussion started by: c3rb3rus
7 Replies
HT(4) Kernel Interfaces Manual HT(4)
NAME
ht - RH-11/TU-16 magtape interface
DESCRIPTION
The files mt0, mt1, ... refer to the DEC RH/TM/TU16 magtape. When opened for reading or writing, the tape is not rewound. When closed,
it is rewound (unless the 0200 bit is on, see below). If the tape was open for writing, a double end-of-file is written. If the tape is
not to be rewound the tape is backspaced to just between the two tapemarks.
A standard tape consists of a series of 512 byte records terminated by a double end-of-file. To the extent possible, the system makes it
possible, if inefficient, to treat the tape like any other file. Seeks have their usual meaning and it is possible to read or write a byte
at a time. Writing in very small units is inadvisable, however, because it tends to create monstrous record gaps.
The last octal digit of the minor device number selects the drive. The middle digit selects a controller. The initial digit is even to
select 800 BPI, odd to select 1600 BPI. If the 0200 bit is on (initial digit 2 or 3), the tape is not rewound on close. Note that the
minor device number has no necessary connection with the file name, and in fact tp(1) turns the short name x into `/dev/mtx'.
The mt files discussed above are useful when it is desired to access the tape in a way compatible with ordinary files. When foreign tapes
are to be dealt with, and especially when long records are to be read or written, the `raw' interface is appropriate. The associated files
may be named rmt0, ..., rmt7, but the same minor-device considerations as for the regular files still apply.
Each read or write call reads or writes the next record on the tape. In the write case the record has the same length as the buffer given.
During a read, the record size is passed back as the number of bytes read, provided it is no greater than the buffer size; if the record is
long, an error is indicated. In raw tape I/O, the buffer must begin on a word boundary and the count must be even. Seeks are ignored. A
zero count is returned when a tape mark is read; another read will fetch the first record of the next tape file.
FILES
/dev/mt?, /dev/rmt?
SEE ALSO
tp(1)
BUGS
The magtape system is supposed to be able to take 64 drives. Such addressing has never been tried.
Taking a drive off line, or running off the end of tape, while writing have been known to hang the system.
If any non-data error is encountered, it refuses to do anything more until closed. In raw I/O, there should be a way to perform forward
and backward record and file spacing and to write an EOF mark explicitly.
HT(4)