Forum Discussion

terri_a_wilson's avatar
13 years ago

OpsCenter 7.1 SQL query problem with 1 server with 2 serverid

We are running OpsCenter 7.1 with multiple Netbackup 7.1 master servers.  We have several daily media reports that run for each master server.

When we upgraded the master servers a second server id was created with the same server name.

When media reports are run, the list of media shown is from both the new and the old id.

I don't know how to select a specific server id from nom_NBMedia.

Here is one of the scripts -

select ServerName as Server, MediaID as "Media ID", barcode as "Bar Code", VolumePoolName as Pool from nom_NBMedia
where ServerName='iobackup' and MediaStatus = 'Full' And RobotType !=0
order by 'Expiration Date'
 

Here is the output of a script that searches for serverid.  The problem is with the servers that have two ids but the same friendlyName -

select id as id, networkName as networkName, friendlyName as friendlyName, versionLabel as versionLabel from domain_MasterServer where id > 1

 

id networkName friendlyName versionLabel
59 densv005 densv005 7.1
464 cobackup.na.corp cobackup 6.5.6
760 iobackup.na.corp iobackup 6.5.6
785 jfbackup.na.corp jfbackup 7.1
4237 rhbackup.na.corp rhbackup 7
6686 ssbackup.na.corp ssbackup 6.5.6
6894 wcapps02.na.corp wcapps02 7.1
9709 ssbackup ssbackup 7.1
9778 cobackup cobackup 7.1
14093 iobackup.na.corp iobackup 7.1
10833 jfbackup jfbackup null
30113 tmserver3.na.corp tmserver3.na.corp 7.1

4 Replies

  • Please provide the GUID id from the following output

     

    SELECT * FROM domain_masterserver

    My guess is that the GUID's do not match.

    When upgrading from 6.5.x on the master to 7.1 it may have reregistered itself with OpsCenter, when adding the OpsCenter hostname to the install Wizard.

    I would recommend making a backup copy of your OpsCenter Database, then deleting the duplicate entry.

     

    9709 ssbackup ssbackup 7.1
  • Indeed, the GUID's are different.   How do I delete a duplicate entry from the database?

     

    id networkName friendlyName GUID
    59 densv005 densv005 90A631B9-BC2F-4C85-A554A7C759D4504D
    464 cobackup.na.corp cobackup {5A8F2D53-3733-4941-A115-A31BBE7EA7C0}
    760 iobackup.na.corp iobackup {F08757EA-9BE6-46A3-901F-349936066299}
    785 jfbackup.na.corp jfbackup 2A2E4B68-A133-4D09-ABAA1762ED876015
    4237 rhbackup.na.corp rhbackup {007D6C07-AC80-4EFA-A095-955A5246C130}
    6686 ssbackup.na.corp ssbackup {01661AA0-BDC0-48B3-A70D-592761DE94DB}
    6894 wcapps02.na.corp wcapps02 7859BF39-7FF8-486C-AA61B63F422B41F5
    9709 ssbackup ssbackup F71E71B3-FAED-4228-B9FF222C86BC1A2A
    9778 cobackup cobackup EBB8016C-3AF5-48CB-B7F912527D11DE50
    14093 iobackup.na.corp iobackup A123D52F-305B-48D4-89C4F5FB47665C5F
    10833 jfbackup jfbackup null
    30113 tmserver3.na.corp tmserver3.na.corp BC416499-16B7-4377-BE19DCD86F007C9B
           
  • PLEASE NOTE: This command will remove the master. You should backup your database prior to performing this action. 

    You should be able to execute the following:

    DELETE FROM domain_masterserver WHERE id = <duplicate id>

    In this case, the duplicate id should be 9709.

  • Did the SQL Statement Remove the Duplicate Master?

    If you were able to resolve the issue with the information provided, could you mark the solution?

    --Tom