Forum Discussion

Spartacus81's avatar
10 years ago

MSDP unable to inventory the diskpool

Friends,

NBU Master & Media SuSe Linux 10 SP2

NB?U 7.6.0.3

Really strange problem. I can't seem to inventory the diskpool, unable to see the storage server properties and replication properties

getting error invalid command parameter (20) RDSM the server was not found getDiskVolumeInfo (status 20)

--dsstat, --getmode, diskpool status all shows okay. but can't seem to run backup and unable to do the inventory.

no much info pdde-config.log, storaged.log and spoold.log arent reporting any error.. any suggessions?

gssuanbmed02:/dedup_data/log # /usr/openv/pdde/pdcr/bin/crcontrol --dsstat
 
************ Data Store statistics ************
Data storage      Raw    Size   Used   Avail  Use%
                  19.1T  18.3T   9.1T   9.2T  50%
 
Number of containers             : 53336
Average container size           : 185889755 bytes (177.28MB)
Space allocated for containers   : 9914615973430 bytes (9.02TB)
Reserved space                   : 841215623168 bytes (783.44GB)
Reserved space percentage        : 4.0%
 
Use "--dsstat 1" to get more accurate statistics
 
gssuanbmed02:/dedup_data/log # /usr/openv/pdde/pdcr/bin/crcontrol --getmode
Mode : GET=Yes PUT=Yes DEREF=Yes SYSTEM=Yes STORAGED=Yes REROUTE=No COMPACTD=Yes
 
gssuanbmed02:/dedup_data/log # /usr/openv/netbackup/bin/admincmd/nbdevquery -listdv -stype PureDisk -dp gssuanbmed02_Pool2 -U
Disk Pool Name      : gssuanbmed02_Pool2
Disk Type           : PureDisk
Disk Volume Name    : PureDiskVolume
Disk Media ID       : @aaaad
Total Capacity (GB) : 18777.63
Free Space (GB)     : 9455.78
Use%                : 49
Status              : UP
Flag                : ReadOnWrite
Flag                : AdminUp
Flag                : InternalUp
Flag                : ReplicationSource
Flag                : ReplicationTarget
Num Read Mounts     : 0
Num Write Mounts    : 1
Cur Read Streams    : 0
Cur Write Streams   : 0
Num Repl Sources    : 1
Num Repl Targets    : 1
Replication Source  : gsgs2nbmed02:PureDiskVolume
Replication Target  : gsgs2nbmed02:PureDiskVolume
 
  • Fixed the issue overnight... it was extremely strange as apparently the diskpool, dsstat and mode all were coming up just fine. anyway, found the following error in nbrmms (/usr/openv/logs/nbrmms) logs after making the logs readable by running the following command 

    vxlogview -i 222 -d all -t 00:30:00 > output.txt

    ERR: failed, unable to open tagfile (9:Bad file descriptor)

    Found this technote and it did the magic. 

    https://support.symantec.com/en_US/article.TECH225907.html

     

7 Replies

  • Are you executing commands on a new server which you haven't before used for administration purposes?

  • nop its the same old media server (vm) driving me mental as diskpool is up, dsstat coming up, getmode returnning YES .. but i cant write nothing into it.. 

  • What's in the EMMSERVER entry for this node?

    It should be the master server name.

    # bpgetconfig -M mediasrvname EMMSERVER

  • Fixed the issue overnight... it was extremely strange as apparently the diskpool, dsstat and mode all were coming up just fine. anyway, found the following error in nbrmms (/usr/openv/logs/nbrmms) logs after making the logs readable by running the following command 

    vxlogview -i 222 -d all -t 00:30:00 > output.txt

    ERR: failed, unable to open tagfile (9:Bad file descriptor)

    Found this technote and it did the magic. 

    https://support.symantec.com/en_US/article.TECH225907.html

     

  • Any ideas how it got changed to a bad value?

  • Same media server that kept on rebooting?
    That could be the reason....

  • sorry got confused with my other post.. no it wasn't the same media server that kept on rebooting.. 

    it's the vm and i have no idea how this value got changed as backup stopped working yesterday early morning around 1ish and all jobs started to fail since.. 

    I was kept on looking logs under /usr/openv/netbackup/logs & /dedup_data/logs/spoold.. didnt give me no clue.. Finally looked into /usr/openv/logs and found the problem..