07-17-2002
Creating A Make Recovery Tape
A customer called me and stated that when they created a make recovery tape for their hp-ux 9000/770, it wiped out three of their volume groups from the lvmtab, fstab, /dev directory(all associated files). I didn't believe them until I conducted a tech assist. I restored their system by recreating the volume groups from SAM. After completing our disaster and recovery procedures, all was fine until I created a new make recovery tape. I monitored the entire process, after completion I looked at the file save.log to check for errors from the make recovery but the tape was created successfully. The next morning I came in and to my suprise, the system was back to it's original state when I came for the tech assist. So there is something in the creating of the make recovery tape that is not restoring the volume groups back to normal. I believe it's the import.scr file that's not running. Do anyone have a clue to what could be the problem....
8 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello All
I am need of amke recover tape for solaris.Could anybody tell me how do i create a make recovery tape for solaris.I am on sun-solaris 2.8
regards
Hrishy (2 Replies)
Discussion started by: xiamin
2 Replies
2. Solaris
Hi,
We have some IBM LTO tape drives connect over SAN.
I have the following questions :-
1) Command that can list the tape drive details like who is manufacturer, model number, make etc etc
2) I would like to know what are the key differences between IBM LTO Generation 1 and Generation... (5 Replies)
Discussion started by: new2prog
5 Replies
3. AIX
Hi,
Has anyone please got some advise as to how I can make a CD/DVD on an AIX 5.3 system so that it can be fully recoverd just by inserting the backed up system.
The system that I need to recover has no writable devices, not even a tape drive (it wasn't specified by me btw).
I am trying to... (0 Replies)
Discussion started by: stevek007
0 Replies
4. HP-UX
Hi,
Currently, we are doing make recovery in our servers but dds tape drive of 1 of our servers is not working. I suppose to use external dds tape drive but the problem is that there is no slot from the server for the scsi type external dds device. Is it possible to use drives from other... (5 Replies)
Discussion started by: Tris
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. HP-UX
Hello All,
I have HP Openview storage data protector version 5.5. When I am going to write my backup I have an error message saying "Connot Open Device /dev/rmt/0mn"
Follownig is my output:
# ls -l /dev/rmt/0mn
crw-rw-rw- 2 bin bin 205 0x080140 Jan 17 16:41 /dev/rmt/0mn
# uname -a... (2 Replies)
Discussion started by: hellozishan
2 Replies
7. AIX
Hi all,
Is it possible to boot from SMS menu boot devices into TS3200 FC tape library in case of an mksysb recovery on system p550 - 520 power6.
please note the library is fibre channel (1 Reply)
Discussion started by: h@foorsa.biz
1 Replies
8. 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
LEARN ABOUT CENTOS
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)