Sponsored Content
Operating Systems HP-UX HP-Unix 64 bit Tape Drive creating problem Post 302389298 by hellozishan on Sunday 24th of January 2010 04:32:18 AM
Old 01-24-2010
HP-Unix 64 bit Tape Drive creating problem

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
HP-UX HPUXSRV B.11.23 U ia64 4122093358 unlimited-user license
#

Any help would be appreciated.

Regards,
Zishan
 

10 More Discussions You Might Find Interesting

1. Cybersecurity

Unix backup to tape drive

does anyone know how I can make an automatic backup of files to a tape drive under UNIX. I have so many commands, I don't know which goes where. I have commands for the task scheduler, Cron and other unix commands. Please help. Very Urgent. Thanks (3 Replies)
Discussion started by: Cute
3 Replies

2. UNIX for Dummies Questions & Answers

Tape Drive on Unix 7.1.1

I am trying to install a tape drive on this system (Unix 7.1.1) where will I start? 1. Do I need to load the driver on the on board scsi? How? 2. Is there a driver for the tape drive itself? Things done: 1. Terminated the device on the controller board. (4 Replies)
Discussion started by: a4tech
4 Replies

3. AIX

Problem reading a 4mm tape drive

I'm attempting to read a tape in a 4mm drive (AIX 4.3) using the following command... tar tvf /dev/rmt0 ...and I keep getting the following error message: tar: 0511-193 An error occurred while reading from the media. There is not enough memory available now. I've googled this error... (2 Replies)
Discussion started by: tdpearson
2 Replies

4. SCO

Tape drive problem

I replaced a HP Superstore Dat 40 with another HP Superstore Dat 40, but my backupedge software keeps putting up error code 1 (device not found) I have tried reinstaling the drive as DAT Alad stp 0 6 0 0. I'm not a computer expert but willing to have a go. I went into Backupedge to try and format a... (2 Replies)
Discussion started by: James Zwecker
2 Replies

5. AIX

Tape Drive Problem.

Dear all, I have ultriam3 tape. It is connected my LPAR. I have that the Sl.Nos. and slot number. but run the cfmgr i am not getting the tape drive. I have fired the command lsdev -Cc tape but no reply. how will i configure the tape in LPAR? Please suggest. It is very urgent. (3 Replies)
Discussion started by: pernasivam
3 Replies

6. Solaris

external tape drive DAT 72 problem

Hi all, I have solaris 10 sparc running and working very well but i have problem with external SCSI tape drive DAT 72 problem it seems to me the tape drive is manufactured by SUN microsystems when i ran ls -l /dev/rmt/0 it reveals the following output bash-3.00# mt -f /dev/rmt/0... (2 Replies)
Discussion started by: h@foorsa.biz
2 Replies

7. UNIX for Dummies Questions & Answers

installing unix tape drive

Hi, i installed a unix tape drive on my alphaserver. when i use a mt command it tells me there is no tape or device. I have used the hardware manager and it shows the tape is present. Can anyone help me understand why it cannot pick up the tape as a default? (1 Reply)
Discussion started by: ryks
1 Replies

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

9. Hardware

Help with scsi tape drive problem

I've had a scsi hard drive, scsi tape drive, and cd rom working off an adaptec 29160 controller. Everything worked great until a few days ago. I begin getting tar format errors (running sco 5.0.6) on the tape drive and occasionally the entire system would hang up while trying to access data on... (0 Replies)
Discussion started by: powwm
0 Replies

10. AIX

AIX 4.2.1 Tape Drive Problem

Hi, The problem I have is I want to restore my AIX machine. I have created a mksysb tape from my tape drive rmt0 and I changed the bootlist using this command "bootlist -m normal rmt0 hdisk0". However, when I display the bootlist "bootlist -om normal", it shows '-' hdisk0. I googled and... (2 Replies)
Discussion started by: AixNoob87
2 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 08:28 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy