1) AIX version is: 6100-08-00-0000 is the DVD release. You should update to a SP.
2) Get the SP files using smit suma or FixCentral, download.
3) Once you have the downloads, smitty update_all.
Lastly, why are you using backup (i.e., backup by inode) rather than backupbyfilename.
Usually backups are by filename and/or made for a whole volume group. # savevg -i -f /dev/rmt0 vgName
or # cd /some/directory; find . | backup -if /dev/rmt0
In your case it looks like the last option would be:
Note also, if doing backup by inode - as your example - you should unmount /backup first
Example (where I write to a file, not a tape)
If you continue to have these lseek errors, file a call with IBM or your BP for support and diagnosis.
This User Gave Thanks to MichaelFelt For This Post:
Hi folks,
I'm trying to organize functions in my ksh program into libraries.
If I run my program as any ksh user it will succeed.
Only when I run my program as tcsh user (i.e oracle) I failed.
Example
=======
The ksh code:
tornado:/tmp # cat nir.ksh
#! /bin/ksh
cdromPath=`pwd`... (1 Reply)
I'm getting following message at my EOD backup script:sh: line1: /dev/rct0: cannot create What could be the possible causes for this error and how could I resolve it? (10 Replies)
I am having difficulty in doing ontape -s -L 0. At first it was giving a message Archive failed - function to write to tape failed code -l errno 5.
After about 24 hours it says "could not write archive tape. What do I do?
Can anyone please advise on what the problem is and what I can do?
... (0 Replies)
In AIX 5.1, a daily run script that backing up oracle data failed yesterday with following errors:
The Tivoli backup of DBPROD failed.
What could be the issue, OS, backup or Oracle? (3 Replies)
Hi Experts,
I have a code like this.
=====
#include....
int main()
{
int count = 0;
while(1){
printf("\n Interation number is: %d \n ",count);
rv = system(" test.sh > log.txt " );
if (-1 == rv)
{
printf("Could not generate static log: error... (12 Replies)
I tried to use lseek system call to determine the number of bytes in a file. To do so, I used open system call with O_APPEND flag to open a file. As lseek returns the current offset so I called lseek for opened file with offset as zero and whence as SEEK_CUR. So I guess it must return the number of... (3 Replies)
Hello I am trying to run rpc program to query an entry from a file at the server side that is in the form of <mm> <dd> <event>. I get the proper result at the server. I have verified it by printf statements just before return statement of the result at server side. But somehow I am unable to... (0 Replies)
Discussion started by: mvikramreddy92
0 Replies
LEARN ABOUT DEBIAN
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)