OK, there are several switches for the mt command. In reality all you want is the tape to be some way from the beginning of the tape.
You could try;
Code:
mt -f /dev/rmt/1n eom
Or you could try;
Code:
mt -f /dev/rmt/1n eod
It has been some time since I used tapes this way, one switch is the "end of media" and the other is "end of data" - normally you would use when you wanted to append data to a tape set.
Then run the retention command, as to using the disaster recovery guide for legato - you are getting into an area where you need to have the backup procedures documented to know how to recover them.
Has anyone ever used Networker to backups a SunSolaris 5.4 system. I have all the my other OS on the network being backup except for the 5.4 systems. It's has to do with a daemon. So help me out this doesn't make any since> (3 Replies)
Hello,
Firstable I am new on hp-ux (well long time ago) I am more aix admin....
Legato networker is the tool backup use on the hp-ux. I don't know this tool and would like to know where to find some docs or training.
My first question will be : when a system (hp-ux B.11.0) is backuped on a... (8 Replies)
Hi Fellas/Ladies
I havent dont any restore unix systemsand recently issue has come up that I need to restore to fridays copy.
I want to restore everything to last fridays for the directory /usr/local/projects.
Anyone done legato restores?
Would it keep acl/permissions, symlinks etc.
... (0 Replies)
hi all,
I have just installed networker 7.3 on my HPUX machine, licenced and ready to go, however, when I try to load/inventory/label a type using the autochanger I am getting the following error:
Cannot find attribute 'operation instance' for resource 'NSR jukebox'.
When I check to see what... (1 Reply)
I am running legato 7.3.2.
Here is my issue. I have taken over the backup duties from an employee who left the company. He was running Legato as the backup server/client of choice (I don't know much about Legato, but i am learning on the job). He has it setup to run the admin qui from the backup... (3 Replies)
I am having an issue with Sun EBS Networker 7.3, (64 bit) (Sun Hardware, Solaris 9) where it expects an Oracle DB (11.5.10 with 10g Database (10.2.0.2)) size of 4294967295 bytes. The DB's get backed up anyway, but it's only happening to certain DB's. The warning messages occur at random intervals... (4 Replies)
Hi ALl
I have recently installed networker 7.6 on my solaris 10 host(V240). My bosses requirement was that the GUI was still availible (nwadmin). However on 7.6 there is no GUI and nwadmin does not exist. I have copied nwadmin over from the previous version of legato i had installed (6.2), and... (5 Replies)
Hi Guys,
we are currently upgrading our networker to a newer version on newere hardware.
We are currently running networker 6.1.2 adn are upgrading to Networker 7.6sp2.
I was wondering if there was a way to migrate our indexes (so that from the old version(on E450) to the new version of... (0 Replies)
Hi.
AIX 7.1, Networker 7.6.3.
My system detect all drives, but a jbconfig sent me this message :
"You must install the LUS SCSI passthrough driver"
I have Atape driver 12.3.9 on my AIX.
Tks (0 Replies)
Discussion started by: stephnane
0 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)