SSO on HP-UX

[toichubek]

Dear all,

i have a netbackup master server on RedHat, and using SSO. installing media server and configuring on Solaris servers are ok. everything is backuping. i've installed on HP-UX, everything seems ok but when i'm trying to start backup, it waits for mount of media.

please help me asap,

thanks in advance,

[Mark_Solutions]

Did you install the SSO license on each Media Server when you installed them - it is one of the few keys that you actually need on a Media Server itself

Hope this helps

[toichubek]

Hi,

yes, otherwise it will not create STU, etc. i think the problem with HP-UX...

thanks,

[Mark_Solutions]

OK, what version and patch level of NetBackup and how are you using them  - Storage Unit Groups, Storage Lifecycle Policies etc.

What does the job "State" say when it is waiting

Thanks

[toichubek]

version 7.1

by using device storage wizard. robot control host:nbumaster, Drives device host -multiple:paths of every server.

state -active, without any status.   waiting for mount of media id #

PS:for solaris servers its ok.

thanks,

[Marianne]

Did you follow all the steps for device config on HP-UX?

e.g. Disabling SPC-2 SCSI reserve in HP-UX and Disabling the HP-UX EMS Tape Device Monitor?

See the HP-UX chapter in NBU Device Configuration Guide http://www.symantec.com/docs/DOC3656

Please also ensure that you have the following in place on the HP-UX media server for further troubleshooting:

VERBOSE entry in /usr/openv/volmgr/vm.conf
Restart NBU after adding the entry. Device-type errors will be logged in syslog.

bptm log folder in /usr/openv/netbackup/logs.

[toichubek]

Mark,

7.1,  by using device storage wizard, robot control host- nbumaster and with multiple device host drives, multiple paths...

state -active,  waiting for mount of media id #

Marianne,

Disabling SPC-2 SCSI reserve in HP-UX needs reboot. i didn't do this steps, i hope this help me.

thanks,

[toichubek]

Hi,

there is no st_ats_enabled kernel parameter to disable SPC-2 SCSI reserve on new HP-UX versions. is it very important? because system and netbackup see the robot and drives.  when backup starts, it seems ok but waiting for mount media...((

thanks in advance,

[Marianne]

Seems I have not worked on HP-UX recently... Last time I did it was there... It is still documented in the Device config guide.

Have you checked and disabled HP-UX EMS Tape Device Monitor?

Have you created bptm log folder? Tape mount requests will be logged in the log file in this folder.

Have you added VERBOSE entry to vm.conf and restarted NBU? Additional info will be logged in syslog.

Please also check that tape drives are under TLD control on the media server. Please post output of the following on HP-UX media server:

/usr/openv/volmgr/bin/scan
/usr/openv/volmgr/bin/tpconfig -l
/usr/openv/volmgr/bin/vmoprcmd -d

[toichubek]

Yes, i disabled Monitor,

i'm junior on Netbackup, i didn't create bptm folder but added VERBOSE entry to vm.conf and restarted, but i didn't find any logs, in syslogs there is no message...

bash-3.2# /usr/openv/volmgr/bin/tpconfig -l
Device Robot Drive       Robot                    Drive                Device
Type     Num Index  Type DrNum Status  Comment    Name                 Path
robot      4    -    TLD    -       -  -          -                    nbumedia
  drive    -    8 hcart2    2      UP  -          hcart2222            /dev/rtape/tape16_BESTnb
  drive    -    9 hcart2    1      UP  -          hcart2223            /dev/rtape/tape18_BESTnb
robot      5    -    TLD    -       -  -          -                    /dev/rchgr/autoch1
  drive    -    0 hcart2    1    DOWN  -          IBM.ULTRIUM-TD5.024  /dev/rtape/tape7_BESTnb
  drive    -    1 hcart2    7    DOWN  -          IBM.ULTRIUM-TD5.025  /dev/rtape/tape8_BESTnb
  drive    -    2 hcart2    5      UP  -          IBM.ULTRIUM-TD5.026  /dev/rtape/tape9_BESTnb
  drive    -    3 hcart2    8    DOWN  -          IBM.ULTRIUM-TD5.027  /dev/rtape/tape10_BESTnb
  drive    -    4 hcart2    4      UP  -          IBM.ULTRIUM-TD5.028  /dev/rtape/tape11_BESTnb
  drive    -    5 hcart2    6    DOWN  -          IBM.ULTRIUM-TD5.029  /dev/rtape/tape12_BESTnb
  drive    -    6 hcart2    2      UP  -          IBM.ULTRIUM-TD5.030  /dev/rtape/tape13_BESTnb
  drive    -    7 hcart2    3    DOWN  -          IBM.ULTRIUM-TD5.038  /dev/rtape/tape14_BESTnb
bash-3.2# /usr/openv/volmgr/bin/vmoprcmd -d

                                PENDING REQUESTS

                                     <NONE>

                                  DRIVE STATUS

Drv Type   Control  User      Label  RecMID  ExtMID  Ready   Wr.Enbl.  ReqId
  0 hcart2 DOWN-TLD             -                     No       -         0
  1 hcart2 DOWN-TLD             -                     No       -         0
  2 hcart2   TLD                -                     No       -         0
  3 hcart2 DOWN-TLD             -                     No       -         0
  4 hcart2   TLD                -                     No       -         0
  5 hcart2 DOWN-TLD             -                     No       -         0
  6 hcart2   TLD                -                     No       -         0
  7 hcart2 DOWN-TLD             -                     No       -         0
  8 hcart2   TLD                -                     No       -         0
  9 hcart2   TLD                -                     No       -         0

                             ADDITIONAL DRIVE STATUS

Drv DriveName            Shared    Assigned        Comment
  0 IBM.ULTRIUM-TD5.024   No       -
  1 IBM.ULTRIUM-TD5.025   No       -
  2 IBM.ULTRIUM-TD5.026   No       -
  3 IBM.ULTRIUM-TD5.027   No       -
  4 IBM.ULTRIUM-TD5.028   No       -
  5 IBM.ULTRIUM-TD5.029   No       -
  6 IBM.ULTRIUM-TD5.030   No       -
  7 IBM.ULTRIUM-TD5.038   No       -
  8 hcart2222             Yes      -
  9 hcart2223             Yes      -

Device Name  : "/dev/rtape/tape16_BESTnb"
Passthru Name: "/dev/pt/pt_tape16"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : "HP      Ultrium 5-SCSI  Y36B"
Vendor ID  : "HP      "
Product ID : "Ultrium 5-SCSI  "
Product Rev: "Y36B"
Serial Number: "HU1126H6UV"
WWN          : ""
WWN Id Type  : 0
Device Identifier: ""
Device Type    : SDT_TAPE
NetBackup Drive Type: 10
Removable      : Yes
Device Supports: SCSI-6
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name  : "/dev/rtape/tape18_BESTnb"
Passthru Name: "/dev/pt/pt_tape18"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : "HP      Ultrium 5-SCSI  Y36B"
Vendor ID  : "HP      "
Product ID : "Ultrium 5-SCSI  "
Product Rev: "Y36B"
Serial Number: "HU1126H6V3"
WWN          : ""
WWN Id Type  : 0
Device Identifier: ""
Device Type    : SDT_TAPE
NetBackup Drive Type: 10
Removable      : Yes
Device Supports: SCSI-6
Flags : 0x0
Reason: 0x0

Device Name  : "/dev/rchgr/autoch3"
Passthru Name: "/dev/rchgr/autoch3"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : "FUJITSU ETERNUS LT S2   4.60"
Vendor ID  : "FUJITSU "
Product ID : "ETERNUS LT S2   "
Product Rev: "4.60"
Serial Number: "LTDE65417238_LL0"
WWN          : ""
WWN Id Type  : 0
Device Identifier: "FUJITSU ETERNUS LT S2   00LTDE654172_LL0"
Device Type    : SDT_CHANGER
NetBackup Robot Type: Not Found(5)
Removable      : Yes
Device Supports: SCSI-5
Number of Drives : 2
Number of Slots  : 48
Number of Media Access Ports: 0
Flags : 0x0
Reason: 0x0

thanks,

[Marianne]

Are those the ONLY entries returned by 'scan'? a lot less devices than in the NBU config?

You really need syslog and bptm for troubleshooting... Please create bptm folder. No need to restart NBU to enable log.

If you run bpps -x on the media server, can you see that Media Manager processes are running with '-v'?

If so, VERBOSE entry in vm.conf was enabled and reason for DOWN drives will be logged in /var/adm/syslog/syslog.log.  'UP' all the DOWN drives and try another backup.

Check syslog.log and bptm log for errors.

[mph999]

For VERBOSE in bp.conf, you need a number:

eg.

VERBOSE = 5  (with the spaces)

Martin

[Marianne]

Just to ensure that we're all on the same page - Martin is correct:VERBOSE in /usr/openv/netbackup/bp.conf  needs a number. This will increase logging level for ALL legacy NBU processes (including bptm).
You can also increase logging level for bptm only with BPTM_VERBOSE = 5 in bp.conf.

VERBOSE in /usr/openv/volmgr/vm.conf does not need a number and will increase Media Manager logging in syslog (including reason for DOWN drives).

[toichubek]

Hi,

i've created bptm folder, and written VERBOSE entry on both files. here are logs:

bptm log on media server:

create_tpreq_file: symlink to path /dev/rtape/tape18_BESTnb
13:15:14.158 [15475] <2> manage_drive_before_load: SCSI RESERVE
13:15:14.161 [15475] <2> manage_drive_before_load: report_attr, fl1 0x00000001, fl2 0x00000000
13:15:14.161 [15475] <4> expandpath: /usr/openv/netbackup/db/media/tpreq/drive_hcart2223
13:15:14.736 [15475] <2> tapelib: wait_for_ltid, Mount, timeout 0
13:17:49.830 [15556] <2> bptm: INITIATING (VERBOSE = 5): -rptdrv -jobid -1321433845 -jm
13:17:49.831 [15556] <2> bptm: PORT_STATUS = 0x00000000
13:17:49.839 [15556] <2> drivename_open: Called with Create 0, file hcart2223
13:17:49.840 [15556] <2> drivename_checklock: Called
13:17:49.840 [15556] <2> drivename_checklock: PID 15475 has lock
13:17:49.840 [15556] <2> report_drives: DRIVE = hcart2223 LOCK = TRUE CURTIME = 1321435069
13:17:49.840 [15556] <2> report_drives: MODE = 0
13:17:49.840 [15556] <2> report_drives: TIME = 1321434914
13:17:49.840 [15556] <2> report_drives: MASTER = nbumedia
13:17:49.840 [15556] <2> report_drives: SR_KEY = 0 1
13:17:49.840 [15556] <2> report_drives: PATH = /dev/rtape/tape18_BESTnb
13:17:49.840 [15556] <2> report_drives: MEDIA = E898L5
13:17:49.840 [15556] <2> report_drives: REQID = -1321433840
13:17:49.840 [15556] <2> report_drives: ALOCID = 526
13:17:49.840 [15556] <2> report_drives: RBID = {74253AF6-1033-11E1-85EA-2B5FF47C73CA}
13:17:49.840 [15556] <2> report_drives: PID = 15475
13:17:49.840 [15556] <2> report_drives: FILE = /usr/openv/netbackup/db/media/tpreq/drive_hcart2223
13:17:49.865 [15556] <2> main: Sending [EXIT STATUS 0] to NBJM
13:17:49.865 [15556] <2> bptm: EXITING with status 0 <----------

/var/adm/syslog/syslog.log:

LTID - Sent ROBOTIC request, Type=1, Param2=0
Nov 16 13:15:14 gcrmdb01 tldd[15335]: TLD(4) MountTape E898L5 on drive 1, from slot 9

on master server:

/var/adm/messages:

TLD(4) opening robotic path /dev/sg2
Nov 16 13:13:04 nbumedia tldcd[17220]: inquiry() function processing library FUJITSU  ETERNUS LT S2    4.60:
Nov 16 13:13:04 nbumedia tldcd[17220]: TLD(4) NumDrives = 2, FirstDriveAddr = 1
Nov 16 13:13:04 nbumedia tldcd[17220]: TLD(4) NumSlots = 48, FirstSlotAddr = 1001
Nov 16 13:13:04 nbumedia tldcd[17220]: TLD(4) NumTransports = 1, TransportAddr = 0, PtmAddr = 101
Nov 16 13:15:06 nbumedia tldcd[17220]: inquiry() function processing library FSC      CS-TL            100A:
Nov 16 13:15:06 nbumedia tldcd[17220]: inquiry() function processing library FUJITSU  ETERNUS LT S2    4.60:
Nov 16 13:15:06 nbumedia tldcd[17220]: tldcd.c.3017, process_request(), received command=1, from peername=gcrmdb01, version 50
Nov 16 13:15:06 nbumedia tldcd[17220]: Processing MOUNT, TLD(4) drive 1, slot 9, barcode AAE898L5        , vsn E898L5
Nov 16 13:15:06 nbumedia tldcd[18716]: TLD(4) opening robotic path /dev/sg2
Nov 16 13:15:06 nbumedia tldcd[18716]: inquiry() function processing library FUJITSU  ETERNUS LT S2    4.60:
Nov 16 13:15:07 nbumedia tldcd[18716]: TLD(4) initiating MOVE_MEDIUM from addr 1009 to addr 1
Nov 16 13:16:01 nbumedia tldcd[18716]: TLD(4) closing/unlocking robotic path
Nov 16 13:16:01 nbumedia tldcd[17220]: inquiry() function processing library FSC      CS-TL            100A:
Nov 16 13:16:01 nbumedia tldcd[17220]: inquiry() function processing library FUJITSU  ETERNUS LT S2    4.60:

It still waits for mount of media.... in media server there are 2 robotics, first one is for VTL - there is no problem with this one, and the problems occured with second one, so i write here only these tapes(/usr/openv/volmgr/bin/scan)...

thanks,

[Marianne]

Seems the request was sent to the robot, the robot performed the mount.

NetBackup is now waiting for the OS to confirm that the mount has taken place. As long as the OS does not confirm the tape mount, NBU cannot proceed.

You need to confirm that tape drive is usable at OS level (without NBU).

Try and manually mount a scratch tape in the drive (/dev/rtape/tape18_BESTnb), then use tar or cpio to write to the tape. You will need assistance from your HP-UX sysadmin.

[toichubek]

Dear all especially  Marianne,

thanks very much for everything. patches for OS fixed this problem.

br,

[Marianne]

You agree that I was right in this post https://www-secure.symantec.com/connect/forums/sso-hp-ux#comment-6324741  about the OS not reporting the tape mount?