learn unix and linux commands

Evaluating Tape Drive Performance

 
Thread Tools Search this Thread
# 1  
Old 02-07-2011
Evaluating Tape Drive Performance

This paper discusses the importance of key specifications typically used to evaluate tape drive performance.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

7 More Discussions You Might Find Interesting

1. HP-UX

TAPE drive

I have used ioscan -fnC tape and the system identified the tape drive. what is the command to show a listing of what is on the tape? I have used ls /dev/rmt/rmt0 to no avail. can anyone help? Thanks in advance (10 Replies)
Discussion started by: Randydog
10 Replies

2. SCO

Tape Drive Logs?

I've recently been tasked with "refurbishing" an HP Proliant ML370 running SCO 5.0...something. This is primarily used for legacy support and is kept on a shelf for safe keeping. The scope of work includes hardware diagnostics and blowing the dust out. I have run HP diagnostics on the array,... (1 Reply)
Discussion started by: v1corp
1 Replies

3. Solaris

Help with tape drive

Hey folks, Linux admin here, forced to use Opensolaris to try to use ufsdump/ufsrestore to get some data of some old tapes. I've got Opensolaris 2009.06 on x86 and a Sony SDX-700V. As a "control" experiment, I booted the system with a Linux live CD and the tape drive worked perfectly. ... (2 Replies)
Discussion started by: eddy_sysad
2 Replies

4. AIX

Tape Drive problem

Hi, I'm at AIX 5.3. My EOD program is giving following error while writing to tape: Can't write output cpio: Media Surface error Failed on Shell-script cd /; cpio -ocB 2 >> /autoline/misc/logs/bk.CopyToTape < /autoline/work/BACKUP.01022 1>/dev/rm0 I have tried with several new tapes,... (2 Replies)
Discussion started by: tayyabq8
2 Replies

5. AIX

Tape Drive

I have tape drive in one Lpar. when i saw that time tape is in defined state. After that i deleted the tape drive using the rmdev -R command. Then fired the cfgmgr -v command. But I am not getting the tape drive. Now the drive is even not in defined state also. It is not shown the tape drive. How... (1 Reply)
Discussion started by: pernasivam
1 Replies

6. SCO

Tape drive cleaning

Hello everyone, First, thank you anyone who might be able to help : ) !! here it is, I am using SCO at my business, and I back up everything to a tape drive. I want to do my cleaning of the drive, and i put in the cartridge to the drive, it recognizes it yet it will not engage the... (5 Replies)
Discussion started by: RichardHeadd
5 Replies

7. UNIX for Dummies Questions & Answers

tape drive

Hi, I need to restore my tape backup, when I type "tape status" it gives; status : ready beginning-of-tape write-protected soft errors : 0 hard errors : 0 underruns : 3 but... (4 Replies)
Discussion started by: alisevA3
4 Replies
Login or Register to Ask a Question
BACKUP_STATUS(8)					       AFS Command Reference						  BACKUP_STATUS(8)

NAME
backup_status - Reports a Tape Coordinator's status SYNOPSIS
backup status [-portoffset <TC port offset>] [-localauth] [-cell <cell name>] [-help] backup st [-p <TC port offset>] [-l] [-c <cell name>] [-h] DESCRIPTION
The backup status command displays which operation, if any, the indicated Tape Coordinator is currently executing. OPTIONS
-portoffset <TC port offset> Specifies the port offset number of the Tape Coordinator for which to report the status. -localauth Constructs a server ticket using a key from the local /etc/openafs/server/KeyFile file. The backup command interpreter presents it to the Backup Server, Volume Server and VL Server during mutual authentication. Do not combine this flag with the -cell argument. For more details, see backup(8). -cell <cell name> Names the cell in which to run the command. Do not combine this argument with the -localauth flag. For more details, see backup(8). -help Prints the online help for this command. All other valid options are ignored. OUTPUT
The following message indicates that the Tape Coordinator is not currently performing an operation: Tape coordinator is idle Otherwise, the output includes a message of the following format for each running or pending operation: Task <task_ID>: <operation>: <status> where <task_ID> Is a task identification number assigned by the Tape Coordinator. It begins with the Tape Coordinator's port offset number. <operation> Identifies the operation the Tape Coordinator is performing, which is initiated by the indicated command: Dump The backup dump command. Restore The backup diskrestore, backup volrestore, or backup volsetrestore commands. Labeltape The backup labeltape command. Scantape The backup scantape command. SaveDb The backup savedb command. RestoreDb The backup restoredb command. <status> Indicates the job's current status in one of the following messages. number Kbytes transferred, volume volume_name For a running dump operation, indicates the number of kilobytes copied to tape or a backup data file so far, and the volume currently being dumped. number Kbytes, restore.volume For a running restore operation, indicates the number of kilobytes copied into AFS from a tape or a backup data file so far. [abort requested] The backup kill command was issued, but the termination signal has yet to reach the Tape Coordinator. [abort sent] The operation is canceled by the backup kill command. Once the Backup System removes an operation from the queue or stops it from running, it no longer appears at all in the output from the command. [butc contact lost] The backup command interpreter cannot reach the Tape Coordinator. The message can mean either that the Tape Coordinator handling the operation was terminated or failed while the operation was running, or that the connection to the Tape Coordinator timed out. [done] The Tape Coordinator has finished the operation. [drive wait] The operation is waiting for the specified tape drive to become free. [operator wait] The Tape Coordinator is waiting for the backup operator to insert a tape in the drive. If the Tape Coordinator is communicating with an XBSA server (a third-party backup utility that implements the Open Group's Backup Service API [XBSA]), the following message appears last in the output: <XBSA_program> Tape coordinator where <XBSA_program> is the name of the XBSA-compliant program. EXAMPLES
The following example shows that the Tape Coordinator with port offset 4 has so far dumped about 1.5 MB of data for the current dump operation, and is currently dumping the volume named "user.pat.backup": % backup status -portoffset 4 Task 4001: Dump: 1520 Kbytes transferred, volume user.pat.backup PRIVILEGE REQUIRED
The issuer must be listed in the /etc/openafs/server/UserList file on every machine where the Backup Server is running, or must be logged onto a server machine as the local superuser "root" if the -localauth flag is included. SEE ALSO
backup(8), 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 BACKUP_STATUS(8)