Sponsored Content
Operating Systems Solaris [SOLVED] How to initialize LTO5 Tape Drive? Post 302753487 by Mack1982 on Wednesday 9th of January 2013 01:11:19 PM
Old 01-09-2013
[SOLVED] How to initialize LTO5 Tape Drive?

Hi,

We replaced one of our tape drives (attached to a SPARC Server) with an LTO5 one (external, attached vi SAS). Manually we check (using tar) that the OS can write data to the Tape Drive, however, the application backup is failing.

Since the application takes its own backup, the apps team opened a case with the vendor. The vendor came back stating that "the tape is not initialized".

Can someone explain what it means and how to do it in Solaris 10.

---------- Post updated at 10:11 PM ---------- Previous update was at 08:53 AM ----------

Got it, it is done by the application.
This User Gave Thanks to Mack1982 For This Post:
 

8 More Discussions You Might Find Interesting

1. Solaris

type of tape drive

Hello Expert, I'm new from unix I just want to ask how to check what particullar tape drive installed on my SUN Ultra 450. thanks (1 Reply)
Discussion started by: eykyn17
1 Replies

2. 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

3. AIX

Writing in a tape drive

Hi all, I need to write on a tape drive with AIX5.3. How to know the name of this tape and what is the procedure to read and write on this tape? Regards, Tovo (2 Replies)
Discussion started by: tovohery
2 Replies

4. 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

5. SCO

How to initialize tape drive

Hi all Just connected a SCSI tape drive to our ScoUnix server running Unixware 7.0.1. The ID assigned to it is 3. When I open ArcServe it is saying that tape drive is not found and I cannot configure it. How can I make the tape drive accessible to the system? Thanks! (4 Replies)
Discussion started by: ramon82
4 Replies

6. 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

7. AIX

Slow listing of LTo5 tape contents

Hi, We are taking our filesystem backup having size of 1.3 TB on LTO5 catridges using the following command find * -print|backup -ivf '/dev/rmt0' '-U' i.e backup byname and it took about 6.5 Hours to complete When we are listing same tape contents using the following command restore... (1 Reply)
Discussion started by: m_raheelahmed
1 Replies

8. 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
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)
All times are GMT -4. The time now is 09:36 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy