12-08-2006
Hi Andy,
Thanks for the commands. However, I would like to know if this is really the cause for the block size error.
I was not able to encounter this problem when I backup again the tape from JFS to database. Only the next time I started the server and performed a new backup database. Thus, I need further inputs.
Regards
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Following the below info:
----------------------------------------------------------------------------------
# SYNTAX: /dev/rmt/<unit number><density>
· Density: l, m, h, u/c (low, medium, high, ultra/compressed, respectively)
· BSD behavior: (optional) b
· no rewind: (optional) n
· For... (5 Replies)
Discussion started by: guest100
5 Replies
2. Solaris
hi all ,
i have just installed solris 9 on a sun 280R ,and i have appleid the recommended patches .
after the installation i have found that /dev/rmt/ directory is empty , i thought that was normal , so i attached my DDS4 external tape drive and treid :
devfsadm -C
devfsadm -v
reboot --... (1 Reply)
Discussion started by: ppass
1 Replies
3. Solaris
Hi Guys,
I a newbie in Unix environment. I need a help to detect my external SCSI tape drive. I tried with command drvconfig;devlinks;tapes.. but when I go to /dev/rmt/, the directory is still empty.
I also tried with add_drv -v st but I'm getting this message
# add_drv -v st
exit... (8 Replies)
Discussion started by: akuslive
8 Replies
4. AIX
Hi all,
Sometimes, when I reboot my AIX server, my tape drive /dev/rmt# assignments change. This creates some tedious TSM work prior to and after a reboot of the server.
Is there a way to ensure that the /dev/rmt# assignments come up the same every time?
Thanks (5 Replies)
Discussion started by: jwholey
5 Replies
5. Solaris
I have an HP Proliant DL380 with Intel Processors that I recently loaded Solaris 10 with latest patches on it. I'm trying to do a ufsdump to an HP DAT 40 tape drive via SCSI, but I can't get it to do anything because /dev/rmt is empty. I've tried the following with luck:
touch /reconfigure,... (7 Replies)
Discussion started by: cvaughn
7 Replies
6. Hardware
# mt stat
HP DDS-4 DAT (Sun) tape drive:
sense key(0x0)= No Additional Sense residual= 0 retries= 0
file no= 0 block no= 0
mt -f /dev/rmt/0mn erase
/dev/rmt/0mn: write protected or reserved.
Getting error while ufsdump ....
--- Dumping / to /dev/rmt/0mn ---
DUMP: Date... (1 Reply)
Discussion started by: vickyingle5
1 Replies
7. Solaris
# mt stat
HP DDS-4 DAT (Sun) tape drive:
sense key(0x0)= No Additional Sense residual= 0 retries= 0
file no= 0 block no= 0
mt -f /dev/rmt/0mn erase
/dev/rmt/0mn: write protected or reserved.
Getting error while ufsdump ....
--- Dumping / to /dev/rmt/0mn ---
DUMP: Date... (5 Replies)
Discussion started by: vickyingle5
5 Replies
8. AIX
Hello,
I attached a tape drive to one of my partitions but i cannot find the device.
I run the command lsdev|grep rmt but i dont get anything in return.
When i run lsslot -c slot i can see the slot number and the device that belongs to the tape drive but i cannot find any rmt files in /dev.... (6 Replies)
Discussion started by: omonoiatis9
6 Replies
9. Solaris
Hi Peeps,
Got a very wierd problem (not a show stopper, but really annoying).
I've recovered a system for a DR test and by the looks of it every night (between 1030 and 11pm) it's creating a file called 1hbn in /dev/rmt and literally looks like it's utilizing all the remaining space in /... (2 Replies)
Discussion started by: callmebob
2 Replies
10. HP-UX
Hi,
Unable to make tape backup, please help.
/opt/ignite/bin/make_tape_recovery -a /dev/rmt/?mn -I -v -m tar -x inc_entire=vg00
* Creating local directories for configuration files and archive.
======= 04/25/16 16:28:08 IST Started /opt/ignite/bin/make_tape_recovery.
(Mon... (4 Replies)
Discussion started by: anuragr
4 Replies
LEARN ABOUT OSF1
butc_logs
BUTC_LOGS(5) AFS File Reference BUTC_LOGS(5)
NAME
butc_logs - Message logs from the Tape Coordinator process
DESCRIPTION
The Backup System Tape Coordinator (butc) process generates two log files per device, one for error messages and one for actions.
Error Message Log
The TE_device_name file logs error messages generated by the Backup System Tape Coordinator that controls the tape device or backup data
file indicated by device_name.
As the Tape Coordinator initializes, it creates the file in ASCII format in the /var/lib/openafs/backup directory. If there is an existing
file, the Tape Coordinator renames it to TE_device_name.old>, overwriting the existing TE_device_name.old> file if it exists.
For a tape device, the Tape Coordinator derives the variable device_name portion of the filename from the device pathname listed in the
local /var/lib/openafs/backup/tapeconfig file, by stripping off the initial "/dev/" string and replacing any other slashes in the name with
underscores. For example, the filename for a device called /dev/rmt/4m is TE_rmt_4m. Similarly, for a backup data file the Tape Coordinator
strips off the initial slash ("/") and replaces any other slashes in the name with underscores. For example, the filename for a backup data
file called /var/tmp/FILE is TE_var_tmp_FILE.
The messages in the file describe the error and warning conditions the Tape Coordinator encounters as it operates. For instance, a message
can list the volumes that are inaccessible during a dump operation, or warn that the Tape Coordinator is overwriting a tape or backup data
file. The messages also appear in the /var/lib/openafs/backup/TL_device_name file, which traces most of the Tape Coordinator's actions.
Action Log
The TL_device_name file logs the actions performed by the Backup System Tape Coordinator that controls the tape device or backup data file
indicated by device_name. It also records the same error and warning messages written to the TE_device_name file.
As the Tape Coordinator initializes, it creates the file in ASCII format in the /var/lib/openafs/backup directory. If there is an existing
file, the Tape Coordinator renames it to TL_device_name.old, overwriting the existing TL_device_name.old file if it exists.
For a tape device, the Tape Coordinator derives the variable device_name portion of the filename from the device pathname listed in the
local /var/lib/openafs/backup/tapeconfig file, by stripping off the initial "/dev/" string and replacing any other slashes in the name with
underscores. For example, the filename for a device called /dev/rmt/4m is TL_rmt_4m. Similarly, for a backup data file the Tape Coordinator
strips off the initial slash ("/") and replaces any other slashes in the name with underscores. For example, the filename for a backup data
file called /var/tmp/FILE is TL_var_tmp_FILE.
SEE ALSO
tapeconfig(5), butc(8)
COPYRIGHT
IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved.
This documentation is covered by the IBM Public License Version 1.0. It was converted from HTML to POD by software written by Chas
Williams and Russ Allbery, based on work by Alf Wachsmann and Elizabeth Cassell.
OpenAFS 2012-03-26 BUTC_LOGS(5)