bash-3.2# /usr/openv/volmgr/bin/tpconfig -l Device Robot Drive Robot Drive Device Second Type Num Index Type DrNum Status Comment Name Path Device Path robot 0 - ACS - - - - backup drive - 0 hcart2 - UP - HP.ULTRIUM5-SCSI.000 /dev/rmt/1cbn ACS=-1, LSM=-1, PANEL=-1, DRIVE=-1 drive - 1 hcart2 - UP - HP.ULTRIUM5-SCSI.001 /dev/rmt/0cbn ACS=-1, LSM=-1, PANEL=-1, DRIVE=-1 drive - 2 hcart2 - UP - HP.ULTRIUM5-SCSI.002 /dev/rmt/2cbn ACS=-1, LSM=-1, PANEL=-1, DRIVE=-1 drive - 3 hcart2 - UP - HP.ULTRIUM5-SCSI.003 /dev/rmt/3cbn ACS=-1, LSM=-1, PANEL=-1, DRIVE=-1 drive - 4 hcart2 - UP - HP.ULTRIUM5-SCSI.004 /dev/rmt/4cbn ACS=-1, LSM=-1, PANEL=-1, DRIVE=-1 drive - 5 hcart2 - UP - HP.ULTRIUM5-SCSI.005 /dev/rmt/5cbn ACS=-1, LSM=-1, PANEL=-1, DRIVE=-1 bash-3.2# 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 AVR - No - 0 1 hcart2 AVR - No - 0 2 hcart2 AVR - No - 0 3 hcart2 AVR - No - 0 4 hcart2 AVR - No - 0 5 hcart2 AVR - No - 0 ADDITIONAL DRIVE STATUS Drv DriveName Shared Assigned Comment 0 HP.ULTRIUM5-SCSI.000 No - 1 HP.ULTRIUM5-SCSI.001 No - 2 HP.ULTRIUM5-SCSI.002 No - 3 HP.ULTRIUM5-SCSI.003 No - 4 HP.ULTRIUM5-SCSI.004 No - 5 HP.ULTRIUM5-SCSI.005 No - bash-3.2# bash-3.2# /usr/openv/netbackup/bin/admincmd/bpstulist -U Label: backup-hcart2-robot-acs-0 Storage Unit Type: Media Manager Host Connection: backup Number of Drives: 6 On Demand Only: no Max MPX/drive: 1 Density: hcart2 - 1/2 Inch Cartridge 2 Robot Type/Number: ACS / 0 Max Fragment Size: 1048576 MB bash-3.2# Please help me to solve this problem Thank you ndt

Why did you add ACS type robot if you don't have an ACSLS server? If your drives are SAN attached, please delete all drives and robot in NBU config, then run NBU device config wizard to re-add devices. Robot should be added as TLD with drives under TLD control.

ndt

Level 4

12 years ago

Solved

robot inventory failed: Unable to initialize robot (204)

bash-3.2# /usr/openv/volmgr/bin/tpconfig -l
Device Robot Drive       Robot                    Drive                 Device         Second
Type     Num Index  Type DrNum Status  Comment    Name                  Path           Device Path
robot      0    -    ACS    -       -  -          -                     backup
  drive    -    0 hcart2    -      UP  -          HP.ULTRIUM5-SCSI.000  /dev/rmt/1cbn  ACS=-1, LSM=-1, PANEL=-1, DRIVE=-1
  drive    -    1 hcart2    -      UP  -          HP.ULTRIUM5-SCSI.001  /dev/rmt/0cbn  ACS=-1, LSM=-1, PANEL=-1, DRIVE=-1
  drive    -    2 hcart2    -      UP  -          HP.ULTRIUM5-SCSI.002  /dev/rmt/2cbn  ACS=-1, LSM=-1, PANEL=-1, DRIVE=-1
  drive    -    3 hcart2    -      UP  -          HP.ULTRIUM5-SCSI.003  /dev/rmt/3cbn  ACS=-1, LSM=-1, PANEL=-1, DRIVE=-1
  drive    -    4 hcart2    -      UP  -          HP.ULTRIUM5-SCSI.004  /dev/rmt/4cbn  ACS=-1, LSM=-1, PANEL=-1, DRIVE=-1
  drive    -    5 hcart2    -      UP  -          HP.ULTRIUM5-SCSI.005  /dev/rmt/5cbn  ACS=-1, LSM=-1, PANEL=-1, DRIVE=-1
bash-3.2#

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   AVR                -                     No       -         0
  1 hcart2   AVR                -                     No       -         0
  2 hcart2   AVR                -                     No       -         0
  3 hcart2   AVR                -                     No       -         0
  4 hcart2   AVR                -                     No       -         0
  5 hcart2   AVR                -                     No       -         0

                             ADDITIONAL DRIVE STATUS

Drv DriveName            Shared    Assigned        Comment
  0 HP.ULTRIUM5-SCSI.000  No       -
  1 HP.ULTRIUM5-SCSI.001  No       -
  2 HP.ULTRIUM5-SCSI.002  No       -
  3 HP.ULTRIUM5-SCSI.003  No       -
  4 HP.ULTRIUM5-SCSI.004  No       -
  5 HP.ULTRIUM5-SCSI.005  No       -
bash-3.2#
bash-3.2# /usr/openv/netbackup/bin/admincmd/bpstulist -U

Label:                backup-hcart2-robot-acs-0
Storage Unit Type:    Media Manager
Host Connection:      backup
Number of Drives:     6
On Demand Only:       no
Max MPX/drive:        1
Density:              hcart2 - 1/2 Inch Cartridge 2
Robot Type/Number:    ACS / 0
Max Fragment Size:    1048576 MB
bash-3.2#

Please help me to solve this problem

Thank you

ndt

Marianne
12 years ago
Why did you add ACS type robot if you don't have an ACSLS server?

If your drives are SAN attached, please delete all drives and robot in NBU config, then run NBU device config wizard to re-add devices.

Robot should be added as TLD with drives under TLD control.

10 Replies

Marianne
Level 6
12 years ago
Drives in AVR means that NBU cannot communicate with ACSLS server.

First step is to check if all necessary NBU processes are running:

bpps -x.

If not, stop NBU, add VERBOSE entry to /usr/openv/volmgr/vm.conf, then start NBU again.

Check if all MM processes are starting correctly.

If not, check /var/adm/messages for errors.
Will_Restore
Level 6
12 years ago
See this technote for possible solution

http://www.symantec.com/business/support/index?page=content&id=TECH67982&actp=search&viewlocale=en_US&searchid=1379962346629

ACS library, Inventory Failed: Unable to initialize robot status code 204

...

also when drives are not in use appear as AVR
mph999
Level 6
12 years ago

rpcinfo -t {acsls_host name} 300031 2

rpcinfo -t {acsls_host name} 300031 1

rpcinfo -u {acsls_host name} 300031 2

rpcinfo -u {acsls_host name} 300031 1

At least one of them, should return output like this

program 300031 version 2 ready and waiting

If not, then you have a comms issue between the media server and the ACS server

I would be follow this TN http://www.symantec.com/docs/TECH20783

And set the comms to use TCP as opposed to UDP (TCP is more reliable)

If the above commands do show the message "program 300031 version 2 ready and waiting" I would consider deleting and reconfiguring the drives, having forst confirmed the drives are correctly visbible from the OS.

You coud use scan and tpconfig -dl to check the config of each drive, but to be honest, it's quicker to just reconfigure.

However, a reconfig should be last restort, the usual cause of AVR is communcation to the robot, or in this case, ACS server.
mph999
Level 6
12 years ago
Just spotted something. In the tpconfig -d output, all the drives show the same Drive number, and all are -1 , not sure that is correct. Could you explain the histpory of the issue : Has this every worked Is it a new config If it did work, what changed to make it not work Have you already re-run the device config

ndt

Level 4

12 years ago

bash-3.2# /usr/openv/netbackup/bin/bpps -x
NB Processes
------------
    root  1859  1834   0 17:57:27 ?           0:00 /usr/openv/netbackup/bin/bpjava-susvc root -1 -1 C /usr/openv/java/auth.conf 1
    root   760     1   0 17:55:25 ?           0:15 /usr/openv/netbackup/bin/nbemm
    root   811     1   0 17:55:30 ?           0:15 /usr/openv/netbackup/bin/nbim
    root   819     1   0 17:55:31 ?           0:07 /usr/openv/netbackup/bin/nbrmms
    root   631     1   0 17:55:18 ?           0:00 /usr/openv/netbackup/bin/vnetd -standalone
    root  1836  1834   0 17:57:16 ?           0:00 /usr/openv/netbackup/bin/bpjava-susvc root -1 -1 C /usr/openv/java/auth.conf 1
    root   763     1   0 17:55:25 ?           0:06 /usr/openv/netbackup/bin/nbrb
    root   799     1   0 17:55:28 ?           0:01 /usr/openv/netbackup/bin/bpdbm
    root   757     1   0 17:55:24 ?           0:07 /usr/openv/netbackup/bin/nbaudit
    root   754     1   0 17:55:23 ?           0:02 /usr/openv/netbackup/bin/nbevtmgr
    root   634     1   0 17:55:19 ?           0:00 /usr/openv/netbackup/bin/bpcd -standalone
    root   702     1   0 17:55:21 ?           1:15 /usr/openv/db//bin/NB_dbsrv @/usr/openv/var/global/server.conf @/usr/openv/var/
    root   777     1   0 17:55:27 ?           0:07 /usr/openv/netbackup/bin/bprd
    root   800   799   0 17:55:28 ?           0:17 /usr/openv/netbackup/bin/bpjobd
    root   783     1   0 17:55:27 ?           0:00 /usr/openv/netbackup/bin/bpcompatd
    root   806     1   0 17:55:29 ?           0:07 /usr/openv/netbackup/bin/nbstserv
    root   803     1   0 17:55:29 ?           0:02 /usr/openv/netbackup/bin/nbpem
    root   796     1   0 17:55:28 ?           0:03 /usr/openv/netbackup/bin/nbjm
    root   842     1   0 17:55:33 ?           0:05 /usr/openv/netbackup/bin/nbars
    root   875     1   0 17:55:34 ?           0:02 /usr/openv/netbackup/bin/nbsvcmon
    root   839     1   0 17:55:32 ?           0:00 /usr/openv/netbackup/bin/nbsl
    root  1039   803   0 17:55:36 ?           0:00 /usr/openv/netbackup/bin/nbproxy dblib nbpem
    root  1828  1793   0 17:57:08 pts/3       0:36 /opt/openv/java/jre/bin/amd64/java -Dvrts.NBJAVA_CONF=/usr/openv/java/nbj.conf
    root  1834     1   0 17:57:16 ?           0:00 /usr/openv/netbackup/bin/bpjava-susvc root -1 -1 C /usr/openv/java/auth.conf 1
    root  1839  1834   0 17:57:17 ?           0:00 /usr/openv/netbackup/bin/bpjava-susvc root -1 -1 C /usr/openv/java/auth.conf 1
    root  2730   803   0 18:15:37 ?           0:00 /usr/openv/netbackup/bin/nbproxy dblib nbpem_cleanup
    root  1900   796   0 17:57:39 ?           0:00 /usr/openv/netbackup/bin/nbproxy dblib nbjm
    root  2564   839   0 18:11:04 ?           0:00 sh -c "/usr/openv/netbackup/bin/nbproxy" dblib -mgrIORFile -PolicyManager-1.ior
    root  2565  2564   0 18:11:04 ?           0:00 /usr/openv/netbackup/bin/nbproxy dblib -mgrIORFile -PolicyManager-1.ior.mgr -pr


MM Processes
------------
    root  2498  2482   0 18:09:57 ?           0:01 acsd
    root  2499  2482   0 18:09:59 ?           0:03 avrd
    root   775     1   0 17:55:26 ?           0:03 vmd
    root  1036     1   0 17:55:36 ?           0:15 acsssi 13741
    root   821     1   0 17:55:31 ?           0:00 acssel -s 13740
    root  2482     1   0 18:09:51 ?           0:02 /usr/openv/volmgr/bin/ltid


Shared Symantec Processes
-------------------------
    root   343     1   0 17:55:10 ?           0:00 /opt/VRTSpbx/bin/pbx_exchange
bash-3.2#

ndt
Level 4
12 years ago
Do I have to install Sun StorageTek ACSLS software?

Thank you.

ndt
mph999
Level 6
12 years ago
No, the ACS software is for the ACS server.

It looks to me like the drives aren't correctly set up on the ACS side of things, not NetBackup.
ndt
Level 4
12 years ago
What can I do next?

Please let me know if you need more information.

I dont have ACS server, just only have a zone include the library and media server HBA.

Thank you.

ndt.

ndt

Level 4

12 years ago

bash-3.2# cat /usr/openv/volmgr/vm.conf
MM_SERVER_NAME = backup

Marianne
Level 6
12 years ago
Why did you add ACS type robot if you don't have an ACSLS server?

If your drives are SAN attached, please delete all drives and robot in NBU config, then run NBU device config wizard to re-add devices.

Robot should be added as TLD with drives under TLD control.

Forum Discussion

robot inventory failed: Unable to initialize robot (204)

10 Replies

Related Content

Unable to inventory robot: Inventory failed: Unable to initialize robot (204)

Failed to initialize EMM connection.

Tape inventory

Getting error as ->inventory failed :unable to initialize robot 204

Inventory fails. media id not unique database.