cancel
Showing results for 
Search instead for 
Did you mean: 

Drive issue

dixit47
Level 4

 

Master server : NBU 7.6.0.3, OS : Solaris
Media server : NBU 7.0.1, OS : Linux


Drive is not showing in vmoprcmd o/p, however we are able to see drives in tpconfig and tpautoconf o/p


@abc: vmoprcmd -d

                                PENDING REQUESTS

                                     <NONE>

                                  DRIVE STATUS

Drv Type   Control  User      Label  RecMID  ExtMID  Ready   Wr.Enbl.  ReqId

                             ADDITIONAL DRIVE STATUS

Drv DriveName            Shared    Assigned        Comment

 

 

@abc: tpconfig -d
Id  DriveName           Type   Residence
      Drive Path                                                       Status
****************************************************************************
0   J_0_0_1_5_LTO3       hcart3 ACS(0)  ACS=0, LSM=0, PANEL=1, DRIVE=5
      /dev/nst5                                                        UP
1   J_0_0_1_8_LTO3       hcart3 ACS(0)  ACS=0, LSM=0, PANEL=1, DRIVE=9
      /dev/nst4                                                        UP
2   J_0_0_1_9_LTO3       hcart3 ACS(0)  ACS=0, LSM=0, PANEL=1, DRIVE=8
      /dev/nst3                                                        UP
3   J_0_0_1_0_LTO3       hcart3 ACS(0)  ACS=0, LSM=0, PANEL=1, DRIVE=0
      /dev/nst2                                                        UP
4   J_0_0_1_4_LTO3       hcart3 ACS(0)  ACS=0, LSM=0, PANEL=1, DRIVE=4
      /dev/nst1                                                        UP
5   J_0_0_1_1_LTO3       hcart3 ACS(0)  ACS=0, LSM=0, PANEL=1, DRIVE=1
      /dev/nst0                                                        UP

Currently defined robotics are:
  ACS(0)     ACSLS server = abc.com

EMM Server = bbc.com

 


@abc: tpautoconf -t
TPAC60 HP      Ultrium 3-SCSI  L6HS HU10538DF2 -1 -1 -1 -1 /dev/nst0 - -
TPAC60 HP      Ultrium 3-SCSI  L6HS HU10609TYT -1 -1 -1 -1 /dev/nst3 - -
TPAC60 HP      Ultrium 3-SCSI  L6HS HU10635L9K -1 -1 -1 -1 /dev/nst4 - -
TPAC60 HP      Ultrium 3-SCSI  L6HS HU10601P86 -1 -1 -1 -1 /dev/nst5 - -
TPAC60 HP      Ultrium 3-SCSI  L6HS HU10711FDD -1 -1 -1 -1 /dev/nst2 - -
TPAC60 HP      Ultrium 3-SCSI  L6HS HU106229WW -1 -1 -1 -1 /dev/nst1 - -


Please suggest !

 

1 ACCEPTED SOLUTION

Accepted Solutions

dixit47
Level 4

No Marianee, media server is not ACSLS server, ACSLS server is different.. its typo mistake :)

no reason, but in our env. most of the media server version is 7.0.1.

 

bpps o/p :

root     39863     1  0 Nov13 ?        00:00:03 /usr/openv/volmgr/bin/ltid
root     39872     1  0 Nov13 ?        00:00:03 vmd -v
root     40020 39863  0 Nov13 ?        00:00:00 acsd -v
root     40025 39863  0 Nov13 ?        00:00:00 avrd -v
root     40028 40020  0 Nov13 ?        00:00:00 acssel -s 13740
root     40089 40020  0 Nov13 ?        00:00:01 acsssi 13741
 

 

yeah, there is issue with routes as in nbemmcmd -listhosts cmd o/p : showing

        LocalDriveSeed = ""
        MachineDescription = ""
        MachineFlags = 0x75
        MachineNbuType = media (1)
        MachineState = not reachable by master (6)
 

Actually Primary interface is pinging and issue is with backup interface of media server

Checking with SA team to add routes. hope it will resolve the issue.. :)

Thanks Marianne :)

 

 

 

 

View solution in original post

5 REPLIES 5

dixit47
Level 4

Bounced and reset the media server andbut no luck :( .. kindly suggest

Yasuhisa_Ishika
Level 6
Partner Accredited Certified

How about on bbc.com?  I suppose that bbc.com is master server of your NetBackup domain.

dixit47
Level 4

yes, bbc is master server.. still drives are not showing in vmoprcmd -d output !!

Marianne
Level 6
Partner    VIP    Accredited Certified

I am surprised to see that the media server is also acsls server? Is that right?
ACSLS server is normally a standalone server that only controls the robot.

Any reason why media server is not running 7.6.x like the master server?

I assume that this media server has worked fine in the past.
Did anything happen recently?
Anything in /var/log/messages?

Which processes are running on the media server?
Check bpps -x output.

Suggestion: 
Stop NBU on media server.
Stop PBX on media server.
Add VERBOSE entry to /usr/openv/volmgr/vm.conf
Start PBX on media server
Start NBU on media server

Check running processes with 'bpps -x'
Run vmoprcmd -d
Check /var/log/messages for errors.

To verify master <-> media server comms, run these commands on the master:

nbemmcmd -listhosts -verbose

nbemmcmd -getemmserver

dixit47
Level 4

No Marianee, media server is not ACSLS server, ACSLS server is different.. its typo mistake :)

no reason, but in our env. most of the media server version is 7.0.1.

 

bpps o/p :

root     39863     1  0 Nov13 ?        00:00:03 /usr/openv/volmgr/bin/ltid
root     39872     1  0 Nov13 ?        00:00:03 vmd -v
root     40020 39863  0 Nov13 ?        00:00:00 acsd -v
root     40025 39863  0 Nov13 ?        00:00:00 avrd -v
root     40028 40020  0 Nov13 ?        00:00:00 acssel -s 13740
root     40089 40020  0 Nov13 ?        00:00:01 acsssi 13741
 

 

yeah, there is issue with routes as in nbemmcmd -listhosts cmd o/p : showing

        LocalDriveSeed = ""
        MachineDescription = ""
        MachineFlags = 0x75
        MachineNbuType = media (1)
        MachineState = not reachable by master (6)
 

Actually Primary interface is pinging and issue is with backup interface of media server

Checking with SA team to add routes. hope it will resolve the issue.. :)

Thanks Marianne :)