UMA question

[Starrynight_1]

Hello people

I am new with UMA and I have a little question.
I have a Omniback II backup failed with this message:
Can not load exchanger medium (Target drive is busy.)

I went to investigate and found this in UMA, with stat d:
1030 D1 Full "" ""
1031 D2 Full "" ""
1032 D3 Empty "" ""
1033 D4 Empty "" ""
1034 D5 Empty "" ""
1035 D6 Empty "" ""
1036 D7 Empty "" ""
1037 D8 Empty "" ""
1038 D9 Empty "" ""
1039 D10 Empty "" ""
As I went to check the robot and saw no tapes in drives I pressumed I had to change drivers D1 an D2 state to Empty.
That??s when the problem begins.
I try to make offl D1 and I get the message:
offl: No drive(s) specified

I think I got to know the "identification" of the tape drive to issue this command. I just don??t know how to find it...there are other systems making backups with this robot. But I pressume this is an easy task for you UMA's experts guys...

Any sugestion?
Thanks in advance...

SN

[Corthouts Carlo]

Hi,

You could also use the 'mt' command to put the drives offline. This command is not
used from withing uma but from the commandline.

> mt -t offl

Note : only specify the raw, no rewind berkeley type device. fe : /dev/rmt/0mnb

[Alexander M. Ermes]

Hi there.
To address the drive you can either use the number ( 1030 ) or the shortcut D1.
If you want to empty the drive, just do

move D1 S1
move 1030 9
.
for setting offline use

offl D1
or
offl 1030

That should do it.
Rgds
Alexander M. Ermes

[Starrynight_1]

Dear Carlo:

I don??t know what to put in when I do mt -t offl

this system manages the robot but have only one dds tape drive.

Dear Erme:

I also thought that??s what I should do, but here??s the output:

> offl 1030
offl: No drive(s) specified
> offl D1
offl: No drive(s) specified

....... :-(

"See" you

[Corthouts Carlo]

Hi,

How are the drives connected to the machine?

Through Fiber Channel/Direct SCSI?

Are there device files available on the system from where you try to use uma?

Every drive if configured on that system should have a device file available.

Check with "ioscan -fnC tape"
Then you need to know which device file belongs to which tape device on the robot.

Once you know you use the raw, no rewind, berkeley device file for that drive.

Every drive normally has multiple device files like :

/dev/rmt/1m
/dev/rmt/1mb
/dev/rmt/1mn
/dev/rmt/1mnb

these are all device files with different options for the same drive (1)
You should in this case you need to use the one with mnb

[Rita C Workman]

Hi Starrynight,

Alexander has spoken well.
When you run UMA to check what is in drives (stat d), you might want to also see what slots are open (stat s).
Now as he mentions move the tapes (move d1 s_ _) from the drive to an open slot.
Then go back into OBII and update your library by running Devices/Media
Edit
Barcode Scan
....this will refresh the library so it 'KNOWS' for certain where everything is. Just in case your not checking the library before you start a backup.
Often I find that folks manually do something with tapes-don't run a check before they do a backup-and then run into problems because tapes are left in drives or are not where OBII thought they were.

Just a thought,
Rita

[James George_1]

Hi

try these mc commands.

mc -p /dev/picker -rD to see the status of your drives.


mt -t /dev/rmt/??m offl

( To see the etnry for ??m , go to devices and media screen ( hope you are using Omniback !)
and take the device name for the drive)

Rgds / James

[Ian Dennison_1]

I agree with James, you have got to map out the relationship between these 3 things,...

The drive index # you know the drive as
The drive specified in OmniBack Devices
The drive specified in the 'uma' command line

All 3 of these should be in line with each other, otherwise things get interesting.

Share and Enjoy! Ian

[A. Clay Stephenson]

Hi:

I suspect that you specicied the -robot argument to uma correctly but did not specify the the -device argument(s) correctly.

ROBOT=/dev/robot/c2t3d0 (or whatever)
D1=/dev/rmt/1mnb (or whatever)
D2=/dev/rmt/3mnb (or whatever)
D3=/dev/rmt/4mnb (or whatever)

then
uma like this:
uma -ioctl ${ROBOT} -barcode -device ${D1} ${D2} ${D3} < cmd_file

It is important, that you specify the drives in the correct order (lowest drive to highest).

If this still does work, I would do an omnisv.sh stop and then do a ps -ef | grep omni and kill any other processes found. If these drives are actually physically connected to other hosts then the uma method is going to fail unless you run the command on that host.

[Starrynight_1]

Thank you very much everybody.

I just found wich were the drives I wanted and made a reset to them in the robot.
The problem is solved.

Bye