Netbackup Tld Control Daemon Error
Contents |
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Sign In
Robot Inventory Failed: Unable To Sense Robotic Device (202)
CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow robot inventory failed: unable to open robotic path (201) down your search results by suggesting possible matches as you type. Showing results for Search instead for Do you mean
Auto Empty Media Access Port Request Rejected By Tldcd, Unable To Sense Robotic Device
VOX : Backup and Recovery : NetBackup : NetBackup TLD Control Daemon Event Detail: TLD(1) ... VOX : Backup and Recovery : NetBackup : NetBackup TLD Control Daemon Event Detail: TLD(1) ... Subscribe netbackup robtest to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page NetBackup TLD Control Daemon Event Detail: TLD(1) Mode_sense error NevilleW Level 2 01-02-2009 12:05 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content 1 Netbackup 6.5.2a Master/Media server running on Windows 2003 robotic library is down on server Std SP2.1 Quantum Tape library.Hi, every several months we have an issue with respect to our staging disk to tape duplications andour tape library.What we notice after the issue happens is, all 4 of our tape drives in our library are down.To get out of this situation, we shut down the library, shut down the netbackup master/media server(in our case it is 1 server) and then turn on the library and then the netbackup server.Usually at this point, we can bring up the drives (although sometimes a second set of reboots is needed).As well, there is 1 or more tapes in the tape drives which we need to move via the library console.In the windows application log, we see the following error entries:------------------------------------------Log: APPLICATION (#11271)Event ID: 13943Event Time: Tue Dec 30 04:00:16 AMEvent Category: NoneSeverity: ErrorEvent User: N/AEvent Source: NetBackup TLD Control Daemon Event Detail: TLD(1) Mode_sense error------------------------------------------Log: APPLICATION (#11270)Event ID: 13942Event Time: Tue Dec 30 04:00:16 AMEvent Category: NoneSeverity: ErrorEvent User: N/AEvent Source: NetBackup TLD Control Daemon Event Detail: TLD(1) key = 0x4, asc = 0x44, ascq = 0x0, INTERNAL TARGET FAILURE------------------------------------------Log: APPLICATION (#11271)Event ID: 13943Event Time: Tue Dec 30 04:00:16 AMEvent Category: NoneSe
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Troubleshooting Robot or Drive Issues in NetBackup Article:000013667 Publish: https://vox.veritas.com/t5/NetBackup/NetBackup-TLD-Control-Daemon-Event-Detail-TLD-1-Mode-sense-error/td-p/214942 Article URL:http://www.veritas.com/docs/000013667 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 to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Related https://www.veritas.com/support/en_US/article.TECH169477 Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem Troubleshooting Drive/Library Issues in NetBackup This document provides information on, and how to resolve, various tape drive issues that may be encountered whilst using NetBackup. Solution It is important to understand that NetBackup does not write data directly to a tape drive. For example: when using Solaris, NetBackup relies on the operating system to write the data to the tape using the st tape driver. The only slight involvement with NetBackup is that it specifies the block size to use - but this is still passed to the operating system. Other operating systems work in a similar manner. The SCSI pass-through driver (sg driver on Solaris) - allows SCSI commands to be passed directly to the drive. For example, the 'test-unit-ready' SCSI command is used, for example, when mounti
of this problem is most often a result of communication problems. There are two NetBackup daemons for robotic control, one runs on the machine with robotic control, the other runs on the machine that has drives in the robot. http://kb.eventtracker.com/evtpass/evtpages/EventId_14242_NetBackupTLD_48815.asp For example, if the robot is a TLD robot the two daemons https://mykb4ref.wordpress.com/category/netbackup/ are tldcd ( runs on the server with robotic control) and tldd (runs on server with drives on the robot). In this commonly occurring problem, the drives will change from TLD control to AVR control. This is so the jobs will go into a pending mount state, rather than unable to failing. That happens so that if network communications were to fail between two server for a short time, then there would be no need to fail the jobs and they could wait until the connection comes back up. However, at times this can be caused by more severe problems.The above error is what will cause drives in a robot to go robot inventory failed: into an AVR control mode. It is not possible to give a single cause or a single solution. This is because these two daemons are unable to communicate.Some common causes are:1. Network connectivity has just plain failed. In this case, the network must be restored.2. There are multiple interfaces on one or both of the machines that cannot route to or resolve each other. In this case, either routing needs to be changed so that a request going will be able to reach its destination. Also, adding the proper host names to the /etc/hosts file has been shown to work in some situations.3. The tldcd daemon has enters an uninterruptible state or is hung, thus making it unable for it to reply to tldd. In this case, shutdown the media management daemons by running /usr/openv/volmgr/bin/stopltid.4. The /etc/services file is missing the correct entries on one or both the servers.------------------------------------------------------------------Reference LinksVeritas Information Did this information help you to resolve the problem? Yes: My problem was resolved. No: The information was not helpful / Partially helpful. Comments: Captcha Refresh
in question has a downwards pointing red arrow. 2. One or more paths for the drive appears to be down – On the graphical representation of the backup device, the drive in question has a downwards pointing red arrow. 3. Application event log shows the following events: Event Type: Error Event Source: NetBackup TLD Control Daemon Event Category: None Event ID: 13945 Description: TLD(0) cannot dismount drive 7, slot 103 already is full Event Type: Error Event Source: NetBackup Device Manager Event Category: None Event ID: 2636 Description: Operator /EMM server has DOWN’ed drive HP. ULTRIUM2-SCSI.006 (device 6) RESOLUTION: 1. Manually dismount the tape inside drive 7 (as indicated in the event log). 2. Load the dismounted tape back to the tape library via MAP. 3. Perform a tape inventory 4. Up those paths which appear to be down. The red arrows should disappear. Leave a Comment August 6, 2009 MISSING_DRIVE:HUL5B06126 Filed under: Netbackup -- kb4ref @ 9:06 am SYMPTOMS: 1. Two of the tape drives appears to be down - On the graphical representation of the backup device, the drive in question has a downwards pointing red arrow. 2. In the ‘Drive Path' for the drives, it states: ‘MISSING_DRIVE:HULxxxxxxx' RESOLUTION: 1. Stop all Hosts Start NBU Admin Console and expand ‘Media and Device Management'. Expand ‘Devices' and click ‘Hosts'. Click on the first Host, do a right-click and select ‘Stop/Restart Device Manager Service…'. Select ‘Stop' for Action and click ‘OK'. Repeat the above step for all Hosts. The status for all hosts should change to ‘Active for Tape'. 2. Shutdown Netbackup by issuing ‘bpdown -v'. 3. Shutdown the Master Server. 4. Power-off all routers and the tape library. 5. Power-on the tape library and wait for the initialization process to complete. 6. Power-on the routers. 7. Start-up the Master Server. 8. Check that all Hosts are running. The status for all hosts should be ‘Active for Tape and Disk'. 9. Check that all the drives are up. 10. Rerun all jobs which failed. Leave a Comment Blogroll WordPress.com WordPress.org Categories: Certificate Netbackup Scrabble Search: Archives: September 2009 August 2009 Meta: Register Log in RSS Comments RSS XFN WordPress.com Blog at WordPress.com.