Home > Cannot Start > Cannot Start Netbackup Device Manager

Cannot Start Netbackup Device Manager

You may also refer to the English Version of this knowledge base article for up-to-date information. CALL US: 1 (866) 837-4827 Solutions Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government Products Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z Services Education Services Business Critical Server Type Host Version Host Name EMM Server MEDIA 6.5 Thanks NetBackup Support! his comment is here

[email protected] 22:01:14 /usr/openv/netbackup/bin/admincmd # !521 nbemmcmd -deletehost -machinename mfp01-2.hs.azdhs.gov -machinetype media NBEMMCMD, Version:7.1.0.2 Command completed successfully. Fist of all - you have two separate media server entries for this server - one with shortname and another with FQDN (instead of one entry with emm alias for alternate Veritas does not guarantee the accuracy regarding the completeness of the translation. Checking with the host "mfp01-2.hs.azdhs.gov"... https://vox.veritas.com/t5/NetBackup/device-manager-service-fails-to-start/td-p/722839

Go to Solution. Try to inspect your admin-logs on master server to check when this record was created. 2. So, my suggestion is to first of all get rid of FQDN for media server to avoid attempts to communicate with it: UNKNOWN RELEASE (-2)mfp01-2.hs.azdhs.gov You should have one entry only - not both (like with other workin media servers).

The NetBackup Device Manager service will display this error in the Application Event Log:Event Type: ErrorEvent Source: NetBackup Device ManagerEvent Category: NoneEvent ID: 0Date: 2/10/2006Time: 1:50:48 PMUser: N/AComputer: xxxxxxxxxDescription:EMM interface initialization Go to Solution Device Manager won't stay started Switcho Level 4 ‎12-06-2010 09:41 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Checking with the host "hsprod14"... Sorry, we couldn't post your feedback right now, please try again later.

Once I reapplied the patches, everything started working again. Showing results for  Search instead for  Do you mean  VOX : Backup and Recovery : NetBackup : Device Manager won't stay started VOX : Backup and Recovery : NetBackup : Device Terms of use for this information are found in Legal Notices.

Related Articles Article Languages x Translated Content Please note that this document is a translation from English, and may https://vox.veritas.com/t5/NetBackup/Device-Manager-won-t-stay-started/td-p/356422 There were problems getting information on one or more hosts.

nmedina Level 3 ‎07-01-2009 11:38 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Do u have the tape drives This client has been working fine for months and hasn't even had a reboot.No changes that anyone is admitting to. Any chance you were running demo license which has now expired? Labels: 7.5 Agents Backup and Recovery Enterprise Backup and Recovery Error messages Monitoring NetBackup Windows 8 2 Kudos Reply 1 Solution Accepted Solutions Accepted Solution!

  • Now i'm suspecting a license issue, because when using NetBackup Configuration Wizard to Configure Storage Devices for a second media server, the drives are detected with a limitation.
  • Labels: 7.1.x and Earlier Backup and Recovery NetBackup SAN Shared Storage Option 3 Kudos Reply 1 Solution Accepted Solutions Accepted Solution!
  • The log \\VERITAS\NetBackup\logs\admin  records this error after the failed nbdb_ping:14:03:37.687 [3612.540] <16> nbdb_ping: ODBC connection failed.14:03:37.687 [3612.540] <16> nbdb_ping: ErrMsg Specified driver could not be loaded due to system error  126
  • Go to Solution NetBackup 7.1 Media (Device) Manager Won't stay started AlanTLR Level 5 ‎08-07-2012 12:16 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to
  • Command did not complete successfully. 0 Kudos Reply Accepted Solution!
  • Error 1053: The service did not respond to the start or control request in a timely fashion." Does anyone have any idea how to resolve this?
  • Here you RiaanBadenhorst Moderator Partner Trusted Advisor Accredited Certified ‎12-07-2010 06:52 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content
  • Also, returned emtries failed for FQDN and shortname returned FQDN for EMM server where other media servers returned shortname.
  • The open database connectivity (ODBC) Data Source Administrator, under Administrative Tools > Data Sources (ODBC), shows VERITAS NB Adaptive Server Anywhere 9.0.1 as "Not marked" in the Version and Company fields

Labels: 7.1.x and Earlier Backup and Recovery NetBackup 0 Kudos Reply 1 Solution Accepted Solutions Accepted Solution! More Bonuses Lets see the output of: bpminlicense -verbose If you are sharing drives, but do not have SSO license on all the servers, then you will have problems with drives, and hence Seems like a comms issue Marianne Moderator Partner Trusted Advisor Accredited Certified ‎08-07-2012 10:43 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Solved!

we havetwo media servers, bck02 (controlerof therobot ) and bck03, we installed the correct pilotes and drivers of the hardware with the latest firmwares, theOSof all the servers can correctly see this content No Yes Did this article save you the trouble of contacting technical support? Do Houssam Level 2 Partner ‎06-16-2015 04:30 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content >NetBackup Device Manager? Article:000009269 Publish: Article URL:http://www.veritas.com/docs/000009269 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in

Showing results for  Search instead for  Do you mean  VOX : Backup and Recovery : NetBackup : device manager service fails to start VOX : Backup and Recovery : NetBackup : View solution in original post 0 Kudos Reply 5 Replies > of all the servers can revarooo Level 6 Employee ‎06-16-2015 03:31 AM Options Mark as New Bookmark Subscribe Subscribe to [email protected] 22:04:44 /usr/openv/netbackup/bin/admincmd # 0 Kudos Reply 1. http://optimisersonpc.com/cannot-start/cannot-start-svchost-exe.html client hostname could not be found(48) Try 'nbemmcmd -deletehost .....' Hopefully this will work without issues.

I agree with Marianne that hostname resolution needs to be sorted out first. Scott 0 Kudos Reply Resolved Will_Restore Level 6 ‎07-01-2009 12:15 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content aha! That error was a revarooo Level 6 Employee ‎06-16-2015 06:56 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Good

Go to Solution.

Checking with the host "wayback"... thanks for your efforts. 0 Kudos Reply bpminlicense Marianne Moderator Partner Trusted Advisor Accredited Certified ‎12-07-2010 12:25 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email The NetBackup Device Manager service only needs to run when devices are configured. Someone (Marianne, mph999?), please help!

mfp01-2 is the one in question. It is possible that updates have been made to the original version after this document was translated and published. Checking with the host "hsprod14"... http://optimisersonpc.com/cannot-start/cannot-start-administrative-tools.html Resolved Scott_Killam Level 3 ‎07-01-2009 12:05 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Thanks for the assistance...the issue

client hostname could not be found(48) Try 'nbemmcmd -deletehost .....' Hopefully this will work without issues. Any suggestions? It findsand configureseverything as it always has.The NetBackup Device Manager does not start...this service manages this process I believe.

Back to Top