Use your system's ps command and monitor CPU utilization to help decide which of these conditions exist. No Yes How can we make this article more helpful? By joining you are opting in to receive e-mail. On UNIX and Linux clients, if both the NIS and the DNS files are used, verify that they match. weblink
Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem STATUS CODE 41: NetBackup Exchange mailbox backups fail with a Status Code 41. Repeat this process for the LOTUS_NOTES_INI value. Previou: How To Fix Brother Machine Error 71 Next: 1305 Erorr Msi Rating for Windows Wiki: 5 out of 5 stars from 75 ratings. This option must be selected. Once this option is selected, saved, and the server rebooted, the problem should be resolved.3.
Add the CLIENT_READ_TIMEOUT values to the master server, media server, and client when a NetBackup database extension product is installed. Go to the Administrator console2. Has anything changed in NBU?
You may also refer to the English Version of this knowledge base article for up-to-date information. Powered by Blogger. This is both a blessing and a curse. The system returned: (22) Invalid argument The remote host or network may be down.
Generated Thu, 01 Dec 2016 15:28:18 GMT by s_ac16 (squid/3.5.20) Netbackup Network Connection Timed Out(41) Template images by molotovcoketail. The default value for this parameter is 5.The retransmission timer is initialized to three seconds when a TCP connection is established; however, it is adjusted on the fly to match the Navigate to SOFTWARE\VERITAS\NetBackup\CurrentVersion\Config4.
To correct it, add CLIENT_READ_TIMEOUT to the /usr/openv/netbackup/bp.conf file and set it to increase the timeout interval. It can also be brought about if the laptop or desktop is contaminated with a trojan or spyware attack or through a poor shutdown of the computer system. How to check the SERIAL NUMBER of a WINDOWS MACHIN... Any one of the preceeding actions can end up in the removal or data corruption of Windows system files.
The curse is obvious but the blessing is that you are about to embark on a journey that provides enlightenment and understanding of how NetBackup actually works.This is because the 41 http://www.tek-tips.com/viewthread.cfm?qid=1027355 Client file system utilizing too many resourcesSteps to try: Disable Veritas Snapshot Provider (VSP) on backup Disable AntiVirus DisableTracker.exe Troubleshooting 1 ) Increase the Network timeout in the client properties default Status 41 Netbackup Labels: 7.5 Backup and Recovery NetBackup Troubleshooting 1 Kudo Reply 8 Replies General Symantec Nicolai Moderator Partner Trusted Advisor 10-20-2012 02:35 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Netbackup Error Code 41 Troubleshooting Status 41 can be Client Connect Timeout or Client Read Timeout.
The last file in the log is the file that causes problems. have a peek at these guys Depending on the number of databases, this value may need to be set to 1800 or higher. To increase the Client Read Timeout by modifying the registry, start Regedit by selecting When you finish the investigation of the problem, delete the /usr/openv/netbackup/logs/bpbkar directory, since the log files can become quite large and are not deleted automatically. The bpbkar client process is not hung. Status Code 41 In Cobol
For this case, use Host Properties on the NetBackup server to change Client connect timeout or Client read timeout. More information on CLIENT_READ_TIMEOUT is available. This can be a cause of long delays for a client to time out on a slow link.For additional information about the latest service pack for Windows 2000, click the article http://nodatasource.com/netbackup-error/netbackup-status-code-239-oracle.html ndd -get /dev/tcp tcp_recv_hiwat ndd -get /dev/tcp tcp_xit_hiwat for windows please see : http://www.symantec.com/docs/TECH60844 Note that any changes will cause a momentary hitch in the network on this box so
During a backup, the NetBackup client agent may not be able to send keepalives to the media server if the read of client data is taking a long time to complete Refer to Microsoft TechArticle 170359 for details on how to change this value. The text of the article is reproduced below for convenience:*Begin Microsoft Article-----------------------------------------------------------------------------------------------------------------------------------------How to Modify the TCP/IP Maximum Retransmission Join UsClose HomeChange ViewPrint NetBackup status code: 41 Message: network connection timed out Explanation: The server did not receive any information from the client for too long a period of
Click Start | Run and type regedt322. This error occurs during incremental backups when directories have thousands of unmodified files. Lotus Notes ID file incorrectly specified in notes.ini:In the Lotus Notes notes.ini file, there are two fields which, if present, may need to be changed. This particular code can be used by the supplier to identify the error made.
See "Using the Host Properties Window" in the Troubleshooting Guide). Make sure all recommended NetBackup patches are installed. The following information applies only to UNIX or Linux clients: The bpbkar client process is hung on a file that has a mandatory locking set. this content Article:000026275 Publish: Article URL:http://www.veritas.com/docs/000026275 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
With database systems, some clients with very large filesystems / active filesystems / lots of small files may need a value of 1800, 3600, 7200, 10800 or higher. This article provides advice that tells you the best way to successfully treat your Microsoft Windows Netbackup Error 41 On Restore error messages both by hand and / or automatically. RE: Status 41: network connection timed out creakyjoe (IS/IT--Management) 24 Mar 05 08:50 pls see comments on http://www.tek-tips.com/viewthread.cfm?qid=1029336&page=1Rich RE: Status 41: network connection timed out 1781 (TechnicalUser) 30 Mar 05 11:46 Resolution:Search the server's notes.ini file for the values KeyFilename and ServerKeyFilename.
On Windows clients: The bpbkar client process is not hung. Select a the host properties tab.3. This occurs most often when either the KeyFilename or the ServerKeyFilename is set to some ID file other than the server.id file. is not the user with the problem.....
Sorry, we couldn't post your feedback right now, please try again later. Join your peers on the Internet's largest technical computer professional community.It's easy to join and it's free. Sometimes it is a busy system trying to backup an active file.I would start with disabling VSP and seeing if that will allow the backup to partially complete and see what