10 More Discussions You Might Find Interesting
1. AIX
i connect an ibm ultrium lto 5 (sas) to an 8204-e8a (v6.1 TL5 SP 1)
then i do an cfgmgr and get message about missing filesets
devices.pciex.1410ca03
devices.pciex.pciexclass.00107
devices.pciex.00107200
devices.pciex.pciex100.72.3
and a few others
i try to find the filesets on the two OS... (1 Reply)
Discussion started by: AIXBlueCat
1 Replies
2. Solaris
Hi guys,
I've changed the LTO3 device, but the OS (Solaris10) doesn't feel it.
From the ok> prompt i've launched the probe-scsi-all command and it worked fine because i could see the new device; the from the ok> i booted the system (normal boot, probably a boot -r could be better..) and from... (11 Replies)
Discussion started by: cecco16
11 Replies
3. AIX
I have a p570 running AIX 5.2 ml 10. We just got in a IBM 3582 library. The library is connected directly to the lpar via fibre cable.
I've installed:
Atape.driver 11.7.7.0
atldd.driver 6.8.4.0
After a reboot, I can see the one tape drive:
... (2 Replies)
Discussion started by: BobSmith
2 Replies
4. Solaris
Can I do this live? Or, do I need to do a probe-scsi-all after doing a stop/A? (10 Replies)
Discussion started by: jgordon
10 Replies
5. HP-UX
Is any one told me that LTO3 tape Cartridge is compatible with LTO2 Tape Drive. (2 Replies)
Discussion started by: Shawn Paul
2 Replies
6. AIX
Hey anyone have the hot news on where to find out if This tape will work with my AIX 5.3?
a Dell PV110T ~ AIX
Base Unit:
PV110T,LTO-3,400/800GB,EXT PowerVault 110T, LTO-3 400/800GB, External Drive-R (222-2100)
Hard Drive Controller:
External 4M SCSI Cable VHDCI/68 pin for Tape... (0 Replies)
Discussion started by: Keith Johnson
0 Replies
7. Solaris
i have 2 hardisk. Hardisk A and Hardisk B.
i have backup the oracle folder from hardisk A to hardisk B c0t0d0s4/oracle.
If i want to restore , what is the command and
what do i need to do ?
urgent help needed.
Thanks for your quick reply . (1 Reply)
Discussion started by: Farbegas
1 Replies
8. UNIX for Dummies Questions & Answers
hi guys,
I have a rp7400 running on 11i and i would like to attach LTO3 certance OEM quantum to this box using an ultra 2 scsi lvd/se-A5149A PCI adapter.Once i attached this card and try to detect it in boot handler running the io command,i can't see the card but once i attach it to the internal... (0 Replies)
Discussion started by: giriplug
0 Replies
9. UNIX for Dummies Questions & Answers
Hi Gurus,
I would like to clarify some doubts regarding a backup strategy.
I have been working on various *NIX as AIX,Solaris and Linux.
I would like to design a backup procedure.WOuld it be possible for me to use a single LTO tape device to backup all the different server with different... (2 Replies)
Discussion started by: mickykt
2 Replies
10. Filesystems, Disks and Memory
HI there,
I need to backup some files from other pcs.
I want to do it from my backupserver.
I am using Unicon (developed from icon) for programming a backupscript, my BS is Mandrake Linux.
The problem I have is:
I cannot use tar multivolume with dd
the command looks something like... (6 Replies)
Discussion started by: mysth
6 Replies
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)