This can occur because there is no process listening on the bpcd port or there are more connections to the bpcd port than the network subsystem can handle with the listen() Note: If you are using bpstart_notify scripts on UNIX or Windows NT clients, verify that messages are not being written to stdout or stderr. Status Code: 49 Message: client did not start Explanation: The client failed to start up correctly. Details: start Control Panel -> Network Connections -> Local Area Connection -> Properties / Settings -> Advanced tab -> (now you'll see the checkbox for "Protect my computer..." (the firewall)) -> Source
This can be caused by a network problem or a problem with the process reading from the socket. Recommended Action: Free up memory by terminating unneeded processes that consume memory. Status Code: 39 Message: client name mismatch Explanation: The name that the client used in a request to the NetBackup server did not match the client name configured in the Your cache administrator is webmaster.
o The bp.conf file on UNIX and Macintosh clients. Possible causes include: I/O error reading from the file system. Inserting a DBNull value in database TreePlot does not give a "binary-looking" tree for a binary tree What is the definition of function in ZF/ZFC?
o Create a bpcd activity log directory (this log is created automatically on Macintosh clients. On a UNIX system, the lstat system call fails on a file that is eligible to be backed up. A Riddle of Feelings Heathrow to Gatwick and traffic jam Why is the TIE fighter tethered in Force Awakens? Select Custom for the Installation mode and click Next.
This has been seen to occur during backups when directories have thousands of unmodified files; it has also been seen when backing up file systems or directories that reside on optical 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. Like you said, the program must be 32 bits. Recommended Action: Check the NetBackup Problems report for clues on why the error occurred.
o The bp.ini file on OS/2 and NetWare target clients. 2. On clients and servers, verify that the name service is set up to correctly resolve the NetBackup client names. On Recommended Action: 1. Check the Problems report for information about the error. 2. Verify that the client and servers are operational and connected to the network. 3. Create an activity log To display this dialog box, start the Backup, Archive, and Restore interface on the server and click Configure on the Actions menu (also see "Using the Configure - NetBackup Window" on Any unauthorized review, use, disclosure or distribution is prohibited.
Examine the resulting activity log file for detailed troubleshooting information. 4. Perform "Resolving Network Communication Problems" on page 21. Also check hosts file (and if you have DNS temporarily rename the hosts file on the Master server torun a quick test backup)E:\Program Files\VERITAS\NetBackup\bin>bpclntcmd -?bpclntcmd: unrecognized option -?bpclntcmd: -svbpclntcmd: -pnbpclntcmd: -selfbpclntcmd: Use your system's ps command and monitor CPU utilization to help decide which of the above conditions exist. NetBackup executes client processes as the requesting user.
CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information or otherwise protected by law. this contact form Try to determine the file and why the error occurred. If so, kill it and try again. 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.
Status Code: 15 Message: file close failed Explanation: A close of a file or socket failed. Status Code: 11 Message: system call failed Explanation: A system call failed. NOTE: Your ESET security product will automatically start after you log in to the system in all supported Linux distributions. have a peek here Status Code: 2 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.
RESOLUTION Enable telnet client on your computer and restart the debug session. Then, retry the operation and check the resulting activity logs. 2. On Sun Solaris, verify that all operating system patches are installed (see the Operating Notes section of the NetBackup Release Recommended Action: Save all error information and call customer support.
The symptoms of the problem vary. So, the question, I believe, is why sometimes 32bits cmd.exe is called, and why 32bits cmd.exe appears as having the path system32\cmd.exe, on the console window –Sampaio Jun 9 '13 at Recommended Action: None, unless this was a database backup performed through a database extension product (for example, NetBackup for Oracle or NetBackup for SQL Server). If you cannot determine the cause from the Problems report, create activity log directories for the processes that could have returned this status code.
Recommended Action: Check the NetBackup Problems report. 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 On a UNIX system, NetBackup could not process a sparse file. Check This Out Since the backup was successful, you can delete the files that were backed up (or have the system administrator delete the files if you do not have the necessary permissions).
I checked, and there is indeed *32 next to the process. If rbak does not exit with a status message, NetBackup cannot determine whether the restore worked or not. Then retry the operation and check the resulting activity logs. 2. A possible cause could be a high network load. share|improve this answer answered Aug 8 '15 at 2:43 Nguyen Dang Tung 1 Please read the question again carefully.
If this is not possible, check for loose connections or other network problems. 2. Verify that the server list settings are correct on both the client and the server. No 32-bit version was to be found in Windows\SysWOW64. Can Klingons swim? If these logs do not provide a clue, create a bpbrm activity log on the server, retry the operation again, and check the resulting activity log.