> Cannot Start
> Cannot Start Netbackup Device Manager
Cannot Start Netbackup Device Manager
If the NBDB does start and nbdb_ping responds correctly then the DB is probably ok - in these cases I usually pick on a process that isn;t running and enable its Application Log says:There are no entries in the drive database. Checking with the host "mfp01-2.hs.azdhs.gov"... Thanks NetBackup Support! http://haywirerobotics.com/cannot-start/cannot-start-apache-2-0.html
NetBackup Device Manager? when I do bpps * WDRBKUPMSTR2 10/08/14 01:47:36.995 COMMAND You may also refer to the English Version of this knowledge base article for up-to-date information. Checking with the host "mexmb01"... https://vox.veritas.com/t5/NetBackup/device-manager-service-fails-to-start/td-p/722839
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 Checking with the host "mfp01-2"... Go to Solution. Command did not complete successfully.
- There were problems getting information on one or more hosts.
- Any other thoughts are welcome... 0 Kudos Reply worrisome Will_Restore Level 6 07-01-2009 10:59 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend
- Checking with the host "wayback"...
- 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
Solution Adding a temporary evaluation license key will allow the Netbackup Device Manager service to be restarted. Showing results for Search instead for Do you mean VOX : Backup and Recovery : NetBackup : Netbackup Services not Starting up VOX : Backup and Recovery : NetBackup : Netbackup Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem Netbackup Device manager ( ltid process ) will not start when attempting to configure drives The NetBackup Device Manager service only needs to run when devices are configured.
Here are the highlights: 1. It is possible that updates have been made to the original version after this document was translated and published. Do you have these log directories created? over here I then tried adding the devices through the Admin Console (from the master) wizard, and got the error that it couldn't start the "media manager device daemon", after I've verified that
It findsand configureseverything as it always has.The NetBackup Device Manager does not start...this service manages this process I believe. No Yes Did this article save you the trouble of contacting technical support? Thanks, Scott Solved! 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
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 If not, follow this TN http://www.symantec.com/docs/TECH72780 If you are not running BMR, skip any step that metions BMR After this, the NBDB should start so at that point NBU services can 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 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
Checking with the host "hsprod14"... http://haywirerobotics.com/cannot-start/cannot-start-safe-mode-mup-sys.html Create/Manage Case QUESTIONS? Handy NetBackup Links 0 Kudos Reply that media server (FQDN) watsons Level 6 08-08-2012 04:53 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a 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?
Following the troubleshooting guides and this thread, I found that I get the following in the Event Viewer after trying to start the Device Manager manually: "There are no entries in Checking with the host "wayback"... 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. this content This client has been working fine for months and hasn't even had a reboot.No changes that anyone is admitting to.
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 Unfortunately now I cannot inventory any of my robots. No Yes Menu Close Search SOLUTIONS Solutions Overview Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government PRODUCTS Product Overview Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z SERVICES
MEDIA 7.1 mfp01-1 wayback MEDIA
Checking with the host "mfp01-2"... Checking with the host "mdd01"... I have also seen that media servers that cannot be contacted cause all sorts of issues with resource broker on the master server - like jobs queing for long times and 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
If your master can't resolve mfp01-2.hs.azdhs.gov and if mfp01-2.hs.azdhs.gov and mfp01-2 are the same try to add record into /etc/hosts at master-server. 3. It is possible that updates have been made to the original version after this document was translated and published. The command line process \\VERITAS\NetBackup\bin>nbdb_ping fails with, "Database [NBDB] is not available."5. have a peek at these guys Solution Edited the vm.conf file found in the \veritas\volmgr\ directory. The entry MM_SERVER_NAME= was incorrect, this entry is unique to the server that it resides. Correct the entry
[email protected] 13:42:36 /usr/openv/netbackup/bin/admincmd # nbemmcmd -getemmserver NBEMMCMD, Version:126.96.36.199 These hosts were found in this domain: fearless, mdd01, mexmb01, mfp01-1, mfp01-2, mfp01-2.hs.azdhs.gov, hsprod14, wayback Checking with the host "fearless"... Checking with the host "mexmb01"... Application Log RiaanBadenhorst Moderator Partner Trusted Advisor Accredited Certified 12-06-2010 10:51 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content VOX : Backup and Recovery : NetBackup : Can't inventory rebotic tape library - Can not sta...
Solved! Email Address (Optional) Your feedback has been submitted successfully! Labels: 7.6 Backup and Recovery Configuring NetBackup 0 Kudos Reply 1 Solution Accepted Solutions Accepted Solution! \veritas\volmgr revarooo Level 6 Employee 06-16-2015 04:46 AM Options Mark as New Bookmark Subscribe Subscribe but when i execute bpminlicense -verbose it shows shared storage license with license type = 1 Permanent 0 Kudos Reply Accepted Solution! \veritas\volmgr revarooo Level 6 Employee 06-16-2015 04:46 AM Options