cancel
Showing results for 
Search instead for 
Did you mean: 

Storage Server has two named in NBDB EMM

h-mazeh
Level 3
Partner Certified

Hello All,

 

It happened that EMM DB holds two names for same datadomain storage server. one is FQDN SSDD01.domain.com (which is the orginal) while other is shortname one SSDD01.

SSD01 is stopping any action to backup, if it is cleared or avaialbe none of my backups run to the LAN ddboost, the error showing is:

Error nbjm (pid=11001) NBU status: 2074, EMM status: Disk volume is down
Disk volume is down (2074)

Now what is needed is to clear the shortname one from EMM, how can we do so?

 

Regards,

2 ACCEPTED SOLUTIONS

Accepted Solutions

mph999
Level 6
Employee Accredited

You could try deleting it :

nbemmcmd -deletehost -machinename SSD01 -storage_server <type>
 
where type = PureDisk, DataDomain or whatever it is
 
 

View solution in original post

Anshu_Pathak
Level 5

@h-mazeh @mph999

You need to contact Veritas technical support and ask them to involve Veritas NetBackup engineering.

Veritas NetBackup engineering will provide a SQL script to remove incorrect storage server entry. Another reason to involve engineering is that they will take care of all the references (backup image, disk pool, disk volume, image expiration and configuration) to storage server and can map/move (relevant entires) it to the correct storage server.

Another quick solution is to stop using other name for storage server and remove its entry from DNS and Host files. This may or may not work and also it is not a reliable solution, I would only recommend it for issue isolation or temporary fix.

 

View solution in original post

2 REPLIES 2

mph999
Level 6
Employee Accredited

You could try deleting it :

nbemmcmd -deletehost -machinename SSD01 -storage_server <type>
 
where type = PureDisk, DataDomain or whatever it is
 
 

Anshu_Pathak
Level 5

@h-mazeh @mph999

You need to contact Veritas technical support and ask them to involve Veritas NetBackup engineering.

Veritas NetBackup engineering will provide a SQL script to remove incorrect storage server entry. Another reason to involve engineering is that they will take care of all the references (backup image, disk pool, disk volume, image expiration and configuration) to storage server and can map/move (relevant entires) it to the correct storage server.

Another quick solution is to stop using other name for storage server and remove its entry from DNS and Host files. This may or may not work and also it is not a reliable solution, I would only recommend it for issue isolation or temporary fix.