Netbackup Error Code 21
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 CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : NetBackup : Error code 21-Socket open failed in NetBackup VOX : Backup and Recovery : NetBackup : Error code 21-Socket open failed in NetBackup Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Solved! Go to Solution Error code 21-Socket open failed in NetBackup Raz_Sam Level 3 ‎10-23-2013 03:26 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hi All, I was facing error code 21- Scoket open failed issue from long back. While trouble shooting, I have restarted NetBackup Client Service. Still am facing same issue. Can any one suggest on this and provide solution for this to fix it. OS: Windows NetBackup version: 6.5 Thanks in Advance, Sam. Solved! Go to Solution. Labels: 7.1.x and Earlier Backing Up Backup and Recovery NetBackup Windows Server (2003-2008) 1 Kudo Reply 1 Solution Accepted Solutions Accepted Solution! Have you confirmed that Marianne Moderator Partner Trusted Advisor Accredited Certified ‎10-23-2013 09:48 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Have you confirmed that Windows firewall is disabled on the client? If there is a company firewall, confirm that vnetd (port 13724) is open in both directions. Status 21 is
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 Backups of the same client using some media servers fail with status 21: socket open failed Article:000006870 Publish: Article URL:http://www.veritas.com/docs/000006870 Support / Article Sign In Remember me Forgot https://vox.veritas.com/t5/NetBackup/Error-code-21-Socket-open-failed-in-NetBackup/td-p/583806 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 Article Languages Subscribe to this Article Manage your Subscriptions Problem Backups of the same client using some media servers fail with https://www.veritas.com/support/en_US/article.000006870 status 21: socket open failed Error Message status 21: socket open failed Solution Overview:This host is a NetBackup client and can be successfully backed up by some remote media servers, but not by other remote media servers and not by itself acting as a NetBackup SAN media server.Troubleshooting:The job details confirms that job went active and that bpbrm encountered a problem connecting to the bpcd process on the client host.4/19/2010 14:23:55 PM - Error bpbrm(pid=9629926) bpcd on myclient exited with status 21: socket open failed  4/19/2010 14:26:00 PM - Error bpbrm(pid=9629926) cannot send mail because BPCD on myclient exited with status 21: socket open failed 4/19/2010 14:26:02 PM - end writing The vnetd debug log on the client host confirms that the media server host can connect to the client host and start the bpcd service.14:20:34.319 [9621694] <2> ProcessRequests: vnetd.c.288: msg: VNETD ACCEPT FROM 2.2.2.2.59499 TO 2.2.2.2.13724 fd = 414:20:34.344 [9621694] <2> ProcessRequests: vnetd.c.349: msg: Request VN_REQUEST_SERVICE_SOCKET(6)14:20:34.344 [9621694] <2> process_service_socket_plus: vnetd.c.1538: service_name: bpcd...snip...14:20:34.344 [9621694] <2> launch_command
190 | 200 210 | 220 | 230 | 240 | 250 | 260 | 1 http://backup.technion.ac.il/codes 2 3 4 5 6 7 8 9 Status Code: 0 Top Message: "the requested operation was successfully completed" Explanation: There were no problems detected with the requested operation. Recommended Action: None, unless this was a database backup performed through a database http://www.sqlserverf1.com/symantec-netbackup-device-management-status-code-21-to-status-code-25/ extension product (for example, NetBackup for Oracle or NetBackup for SQL Server). In those instances, code 0 means the backup script that started the backup ran without error. However, you must check other status as explained in the related NetBackup manual to see if netbackup error the database was successfully backed up. Status Code: 1 Top Message: "the requested operation was partially successful" Explanation: A problem that may require corrective action was detected during the requested operation. Recommended Action: Check the All Log Entries report and also the progress log (if there is one). Some of the problems that can show up under Status Code 1 are: · A file or directory path that is more than 1023 characters long. · Could not open a file. · On a UNIX system, NetBackup could not get netbackup error code the link name of a file. · On a UNIX system, NetBackup could not process a sparse file. · Read error encountered in a file. · File is of an unknown type. · On a UNIX system, the lstat system call fails on a file that is eligible to be backed up. This may be a permission problem. · On UNIX, a file could not be locked that has mandatory locking enabled. Status Code: 2 Top Message: "none of the requested files were backed up" Explanation: A backup or archive could not back up any of the files in the file list. Recommended Action: Verify that the files exist and you have read access to them. · On UNIX clients, check to see if the files or directories would be excluded because of an entry in /usr/openv/netbackup/exclude_list. · On PC clients, check the exclude list per the instructions in the user's guide for the client. · On Windows NT clients, verify that the account used to start the NetBackup Client service has read access to the files. If you are backing up a network drive or a UNC (universal naming convention) path, use the Services application in the Windows NT Control Panel to verify that the NetBackup Client service does not start under the SYSTEM account. The SYSTEM account cannot access network drives. To back up network drives or UNC paths, change the NetBackup Client service startup to log in as a user that has permission to access network drives. Status Code: 3 Top Message: valid archive image produced, but no files deleted
Symantec NetBackup Device management status code 21 to status code 25 January 7, 2015 SQLServerF1 Leave a comment Symantec NetBackup product is a backup and recovery product designed for enterprise users. Symantec NetBackup tool can be used to perform backups of SQL Server databases, Oracle, MySQL, Sybase, PostGres Databases, flat file backups, etc, and provides various other features. These status codes appear in exit status and command output for the ltid, tpclean, tpreq, and tpunmount commands, and in system or debug logs. Programs that call those commands, such as media and device management user interfaces and the vmoprcmd command also presented these codes. Below are some of the NetBackup Device management status code 21 to status code 25 which may be received while using the Symantec NetBackup tool. Device management status code 21 Message: The drive is not ready or inoperable Explanation: A drive was selected for a mount request, but the drive is not ready with loaded media. Recommended Action: Wait until the drive is ready before you manually assign a drive to a pending mount request. Device management status code 22 Message: IPC Error: Daemon may not be running Explanation: A request to ltid cannot be serviced. (ltid is the Media Manager device daemon on UNIX and Linux or the NetBackup Device Manager service on Windows.) ltid is probably not running. If ltid is still running, its process lock file may have been removed. Also, message queues may not function correctly on the system. ¦ If ltid is not running, start ltid and try the operation again. On UNIX and Linux, run /usr/openv/volmgr/bin/ltid, and on Windows, start the NetBackup Device Manager service. ¦ If ltid is already running, check for the existence and permissions of the lock file itself and the lock file directory, which are as follows: /usr/openv/volmgr/misc/.ltipid (UNIX and Li