Operation Requested By An Invalid Server 37 Restore
On a UNIX or Windows NT client, create the bpbkar activity log directory on the client. Also, verify that the NetBackup Client Service Port Number and NetBackup Request Service Port Number on the Network tab in the NetBackup Configuration dialog box match the settings in the services This can be caused by a network problem or a problem with the process reading from the socket. 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.
For detailed troubleshooting information, create an activity log directory for the process that returned this status code, retry the operation, and check the resulting activity log. Examine other activity logs or the progress log on the client. Recommended Action: Verify that the requested volume is available and an appropriate drive is ready and in the UP state. If the backup involves a slave server, verify that these entries are correct on both the master and slave server. https://www.veritas.com/support/en_US/article.TECH46050
Operation Requested By An Invalid Server 37 Restore
On Windows NT clients, verify that the account used to start the NetBackup services has read access to the files. Explanation: The tape manager, bptm reported that the media did not load and position within the allotted time. To increase the amount of information that appears in the logs, see the logging topics in Chapter 3, "Using the Logs and Reports." Retry the operation and check the resulting activity Status Code: 65 Message: client timed out waiting for the continue message from the media manager.
- Recommended Action: Verify that the NetBackup Database Manager daemon (service on Windows NT) is running.
- Correct problems and retry the archive.
- Email Address (Optional) Your feedback has been submitted successfully!
On Windows NT clients, verify that the account used to start the NetBackup Client service has read access to the files. This error can be caused by the system not having enough semaphores allocated. On Windows, these daemons are the NetBackup Request Manager and NetBackup database manager services. If you are using an AIX token ring adapter and the routed daemon is running, the timeout can occur because the token ring adapter creates dynamic routes, causing the routed daemon
On Windows NT clients, verify that the account used to start the NetBackup Client service has read access to the files. Check the bpbkar and tar messages in the bpcd log file. Recommended Action: Verify that the class type attribute for the class is correct. https://www.veritas.com/support/en_US/article.TECH51332 On NetWare target and OS/2 clients the master server name is the first SERVER entry in the bp.ini file.
Check the level of network activity. Status Code: 70 Message: an entry in the file list expanded to too many characters Explanation: The wildcards used in one of the file list entries caused too many files to On a UNIX system, NetBackup could not get the link name of a file. To verify which files were backed up, use the NetBackup client-user interface in restore mode and browse the files in the archive.
Netbackup Restore Error 37
If necessary, update the server list. http://systemmanager.ru/nbadmin.en/nbu_37.htm No Yes How can we make this article more helpful? Operation Requested By An Invalid Server 37 Restore Status Code: 58 Message: can't connect to client Explanation: The server was unable to connect to the client. Netbackup Error 37 On Client Restore On Sun Solaris, verify that all operating system patches are installed (see the Operating Notes section of the NetBackup Release Notes - UNIX).
Status Code: 54 Message: timed out connecting to client Explanation: The server could not complet e the connection to the client. e.g.NetBackup\bin\bpclntcmd -pnexpecting response from server mastermedia.domain.com media 10.10.10.10 4380In the example above, I ran the command on media and master (The master server) returned the IP etc of media, which made Recommended Action: Check the NetBackup Problems report for clues on why the failure occurred. Read of an incomplete or corrupt file. Peer Name Is Invalid For Restore Request
On an SCO system, code 60 can occur because the mount-point path name exceeds 31 characters, which is the maximum allowed on an SCO system. Join Us! *Tek-Tips's functionality depends on members receiving e-mail. Then, retry the operation and check the resulting activity log. If a backup on a Windows NT NetBackup client fails with status code 11 and the client is using Open Transaction Manager (OTM) for open file management, it is possible that
Then, retry the operation and check the resulting activity logs. Recommended Action: If the server is a valid server, verify that it is in the server list on the client. Status Code: 10 Message: allocation failed Explanation: Allocation of system memory failed because there is insufficient system memory available.
Recommended Action: Verify that the server did not crash.
You may also refer to the English Version of this knowledge base article for up-to-date information. Check the Problems report for clues. Solution Overview:When viewing policies in a remote NetBackup Administration Console, the following error is seen: "The list of policies could not be retrieved, status 37, operation requested by an invalid server." This problem can also occur if a NetBackup process was terminated through Task Manager or another utility.
Information for: Enterprise Small Business Consumer (Norton) Partners Our Offerings: Products Products A-Z Services Solutions Connect with us: Support Connect Communities Security Center Find a Partner Events Webcasts Contact Us About If NetBackup is under another type of account, reinstall it under an administrator account. Submit a False Positive Report a suspected erroneous detection (false positive). This could be caused by the system being overloaded with too many processes and not enough physical or virtual memory.
Status Code: 6 Message: the backup failed to back up the requested files Explanation: Errors caused the user backup to fail. 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). Recommended Action: Try the backup again. Then, retry the operation and check the resulting activity logs.
For detailed troubleshooting information, create an activity log directory for the process that you suspect of returning this status code. Recommended Action: Verify that the server software has been installed correctly on the master server and all slave servers. On a Windows NT NetBackup server, set the Verbose option on the Troubleshooting tab in the NetBackup Configuration dialog box. If you change the server list on a UNIX master server, you must stop and then restart the NetBackup Request daemon (bprd) and NetBackup Database Manager daemon (bpdbm) for the changes
Check the progress log on the client for messages on why the archive failed. On UNIX and Windows NT clients, create a bpbkar activity log directory. Status Code: 9 Message: an extension package is needed but was not installed Explanation: A NetBackup extension product is required in order to perform the requested operation. Recommended Action: Check the NetBackup Problems report.
media_server_name is the host name of the media server. If the error occurs when executing a command on the command line, verify that the parameters are valid. When the robot is controlled by an Automated Cartridge System, verify that the ACSLS system is up.