System Administration
cancel
Showing results for 
Search instead for 
Did you mean: 

Backup into Alpha servers (Digital server)

SOLVED
Go to solution
Manuales
Super Advisor

Backup into Alpha servers (Digital server)

Good afernoon...
could you tell me how can i rewind a tape into Alpha server?

i know that in hp-ux is "mt rewind" but in Alpha servers i do not know ..

and .. could you tell me why appears the following error when i'm running a backup script:

BR051I BRBACKUP 4.5B (71)
BR189W Expiration period equal 0 - backup volumes could be immediately overwritten
BR055I Start of database backup: bdszfvhx.tib 2006-07-05 17.32.57

BR205I Backup volume initialization
BR058I BRBACKUP action ID: bdszfvhx
BR059I BRBACKUP function ID: tib
BR102I Following backup devices will be used:
/dev/nrmt0h,/dev/nrmt1h
BR144I Following backup volume names will be used:
SP1DB01,SP1DB02
BR129I Force option set - no label checking during initialization
BR126I Unattended mode active - no operator confirmation required

BR207I Volumes in devices: /dev/nrmt0h,/dev/nrmt1h
will be initialized with names: SP1DB01,SP1DB02

BR280I Time stamp 2006-07-05 17.32.57
BR226I Rewinding tape volume in device /dev/rmt0h ...
BR278E Command output of 'LANG=C mt -f /dev/rmt0h rew':

Error on device named /dev/rmt0h - Place TZ89 tape drive unit #34 ONLINE
BR280I Time stamp 2006-07-05 17.32.59
BR279E Return code from 'LANG=C mt -f /dev/rmt0h rew': 1
BR213E Winding tape volume in device /dev/nrmt0h failed
BR219E Initialization of volume SP1DB01 in device /dev/nrmt0h failed

BR206I End of backup volume initialization
BR280I Time stamp 2006-07-05 17.32.59
BR054I BRBACKUP terminated with errors
10 REPLIES
Manuales
Super Advisor

Re: Backup into Alpha servers (Digital server)

Also appears:

mt -f /dev/rmt0h rew

Error on device named /dev/rmt0h - Place TZ89 tape drive unit #34 ONLINE


What must i do?
Manuales
Super Advisor

Re: Backup into Alpha servers (Digital server)

I saw about date when was installed these devices and all of them have date 2002 and devices mentioned above have:
crw-rw-rw- 1 root system 9, 104451 Apr 21 06:45 nrmt1h
crw-rw-rw- 1 root system 9, 103427 Apr 21 06:56 nrmt0h

there were any problem with devices?

Mark Poeschl_2
Honored Contributor
Solution

Re: Backup into Alpha servers (Digital server)

I'll assume that give your tape device names you're on Tru64 4.0. That message normally means that the driver is not detecting that a cartridge is in the tape drive. Are you sure your system can actually see the devices in question.

The full command to do the rewind in Tru64 is given in one of the error messages from your output:
mt -f /dev/rmt0h rewind

Can you see the tape devices from the SRM console (>>>) prompt?

Your device special files are set up for tape devices on SCSI bus 6, target IDs 5 and 6. What does this 'scu' utility sequence show you:

# scu
scu> sbtl 6 5 0
scu> show device
Manuales
Super Advisor

Re: Backup into Alpha servers (Digital server)

Here is the output, what is the meaning of that? i mean, is correct the device?

The output is with:
"sbtl 6 5 0" and "sbtl 6 5 0"

prdsvr3:root:> scu
scu> sbtl 6 5 0
Device: TZ89, Bus: 6, Target: 5, Lun: 0, Type: Sequential Access
scu> show device

Inquiry Information:

SCSI Bus ID: 6
SCSI Target ID: 5
SCSI Target LUN: 0
Peripheral Device Type: 0x1 (Sequential Access)
Peripheral Qualifier: 0 (Peripheral Device Connected)
Device Type Modifier: 0
Removable Media: Yes
ANSI Version: 2 (Complies to ANSI X3.131-1994, SCS
I-2)
ECMA Version: 0
ISO Version: 0
Response Data Format: 2 (SCSI-2)
Terminate I/O Process: No
Additional Length: 51
Soft Reset Support: No
Command Queuing Support: No
Target Transfer Disable: No
Linked Command Support: Yes
Synchronous Data Transfers: Yes
Support for 16 Bit Transfers: Yes
Support for 32 Bit Transfers: No
Relative Addressing Support: No
Vendor Identification: DEC
Product Identification: TZ89 (C) DEC
Firmware Revision Level: 2561

scu> sbtl 6 5 6
Device: TZ89, Bus: 6, Target: 5, Lun: 6, Type: not present
scu> show device

Inquiry Information:

SCSI Bus ID: 6
SCSI Target ID: 5
SCSI Target LUN: 6
Peripheral Device Type: 0x1f (not present)
Peripheral Qualifier: 0x3 (No Physical Device Support)
Device Type Modifier: 0
Removable Media: Yes
ANSI Version: 2 (Complies to ANSI X3.131-1994, SCS
I-2)
ECMA Version: 0
ISO Version: 0
Response Data Format: 2 (SCSI-2)
Terminate I/O Process: No
Additional Length: 51
Soft Reset Support: No
Command Queuing Support: No
Target Transfer Disable: No
Linked Command Support: Yes
Synchronous Data Transfers: Yes
Support for 16 Bit Transfers: Yes
Support for 32 Bit Transfers: No
Relative Addressing Support: No
Vendor Identification: DEC
Product Identification: TZ89 (C) DEC
Firmware Revision Level: 2561

scu> exit
Manuales
Super Advisor

Re: Backup into Alpha servers (Digital server)

and ...

how could you obtain this information: "Your device special files are set up for tape devices on SCSI bus 6, target IDs 5 and 6."

Thanks a lot !!!

Mark Poeschl_2
Honored Contributor

Re: Backup into Alpha servers (Digital server)

The text at the bottom of this post is taken from the "SCSI" man page for Tru64 4.0G. It shows how I figured out that your tape devices are at SCSI bus 6, Targets 5 and 6.

The 'sbtl 6 5 0' shows that you are able to communicate with the first drive so as I said your original error points to the cartridge not being in the drive or the drive not detecting that it's been loaded.

sbtl '6 5 6' shows a non-existant LUN (hence the 'not present' notation. To show status for the second tape drive use 'sbtl 6 6 0'.


Start of text taken from Tru64 man page:

To add a tape device, you must use the following equation:

(LUN x 64)+(target ID x 1024)+(bus no. x 16384)+(density x 2)+no_rewind

The following example uses the previous formula to add a SCSI tape device
with bus number 2, target ID 4, and LUN 3:

Perform the calculations for the rewind device files:

Density
low: (3x64) + (4x1024) + (2x16384) + (0x2) + 0 = 37056
high: (3x64) + (4x1024) + (2x16384) + (1x2) + 0 = 37058
med: (3x64) + (4x1024) + (2x16384) + (2x2) + 0 = 37060
aux: (3x64) + (4x1024) + (2x16384) + (3x2) + 0 = 37062

Perform the calculations for the no rewind device files:

Density
low: (3x64) + (4x1024) + (2x16384) + (0x2) + 1 = 37057
high: (3x64) + (4x1024) + (2x16384) + (1x2) + 1 = 37059
med: (3x64) + (4x1024) + (2x16384) + (2x2) + 1 = 37061
aux: (3x64) + (4x1024) + (2x16384) + (3x2) + 1 = 37063

Create the tape rewind device special files:

# mknod /dev/rmt?l c 9 37056
# mknod /dev/rmt?h c 9 37058
# mknod /dev/rmt?m c 9 37060
# mknod /dev/rmt?a c 9 37062

Create the tape no rewind device special files:

# mknod /dev/nrmt?l c 9 37057
# mknod /dev/nrmt?h c 9 37059
# mknod /dev/nrmt?m c 9 37061
# mknod /dev/nrmt?a c 9 37063

Manuales
Super Advisor

Re: Backup into Alpha servers (Digital server)

My friend, thanks for taking time and answer the question ....

and ...

why do you think this one happened:
"sbtl '6 5 6' shows a non-existant LUN (hence the 'not present' notation. To show status for the second tape drive use 'sbtl 6 6 0'."

Thanks a lot. :)
Mark Poeschl_2
Honored Contributor

Re: Backup into Alpha servers (Digital server)

As for why the 'sbtl 6 5 6' showed up as a "not present" tape device I really couldn't say for certain. It would be very unlikely that you actually have hardware connected at '6 5 6' so the "not present" part of the 'scu show device' output makes sense. Perhaps the TZ89 and other device type information was just residual from your previous successful 'scu show device' at '6 5 0'. Just guessing though...
Manuales
Super Advisor

Re: Backup into Alpha servers (Digital server)

Sorry, this server in other place where i'm working and a person in the other side told me that was not present the tape, the tape was put and work o.k. ...

thanks, any way.

Manuales.
Manish PATHAK_2
Regular Advisor

Re: Backup into Alpha servers (Digital server)

HI,

Good to see that your problem is solved.
please close the thread and also rate the replies.

Regards
Manish Pathak