Home > Netbackup Error > Operation Requested By An Invalid Server 37 Restore

Operation Requested By An Invalid Server 37 Restore

Contents

If the master server is Windows, stop and then restart the NetBackup Request Manager and NetBackup Database Manager services for the changes to take effect.  This issue has also been observed Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem STATUS CODE 37: When viewing policies in a remote NetBackup Administration Console, the following error Check if services are up. Please look for the following log messages: Client Log Files: Progress log located in /usr/openv/netbackup/logs/user_ops/dbext/logs on client. weblink

Create a SymAccount now!' SQL database restores to a SQL server with a 'backup network' configured are failing with SQL "Error in VxBSAQueryObject: 17." and with "Error in VxBSAGetObject:3" errors. Also, verify that the server or Windows NetBackup Remote Administration Console has a server list entry on the master server. Peername is invalid for restore request Resolution: 1. Thank You! https://www.veritas.com/support/en_US/article.TECH46050

Operation Requested By An Invalid Server 37 Restore

Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Check if services are up." Error Message The list of policies could not be retrieved, status: 37. Showing results for  Search instead for  Do you mean  VOX : Backup and Recovery : NetBackup : Error Code:37 - operation requested by an invalid ... Error ERROR CODE/MESSAGES: -- "Error in VxBSAQueryObject : 17." -- "Error in VxBSAGetObject: 3" -- Status Code 37 - operation requested by an invalid server -- Status Code 46 - server

Below is an explanation of what each switch does:   -pn - The client process on the host connects to the Master Server and asks the question "Who am I?". Terms of use for this information are found in Legal Notices. TECH148211 January 21st, 2011 http://www.symantec.com/docs/TECH148211 Support / SQL database restores to a SQL server with a 'backup network' configured are failing with SQL "Error in VxBSAQueryObject: 17." and with "Error in Checked /etc/hosts files and /etc/resolv.conf files and the entries are available and proper over there. 5.

Also, the activity monitor shows: Not connected.... No Yes How can we make this article more helpful? Stop all NetBackup daemons/services on the master server 2. Symantec is committed to product quality and satisfied customers.

Create/Manage Case QUESTIONS? Symantec's plans are subject to change and any action taken by you based on the above information or your reliance upon the above information is made at your own risk.  Terms It is possible that updates have been made to the original version after this document was translated and published. The Master Server name should be the first SERVER entry in the server list, followed by an entry for whatever other Servers (such as a remote console) will connect to the

Netbackup Error 37 On Client Restore

Opened 'regedit'and browsed to: HKLM\SOFTWARE\Veritas\NetBackup\CurrentVersion\Config\Servers * Checked the server list: - nbmaster01 - nbmedia01 - nbmedia02 Opened remote Java Console * Ran a manual SQL backup of the SQL 2005 test https://vox.veritas.com/t5/NetBackup/Error-Code-37-operation-requested-by-an-invalid-server/td-p/742596 No Yes Did this article save you the trouble of contacting technical support? Operation Requested By An Invalid Server 37 Restore Sorry, we couldn't post your feedback right now, please try again later. Peer Name Is Invalid For Restore Request If a server or Windows NetBackup Remote Administration Console has more than one host name (for example, it has multiple network interfaces), do the following: verify that the master server has

Recreate a new, empty bprd.d directory on the master server 4. On Windows, these daemons are the NetBackup Request Manager and NetBackup database manager services. If you change the server list on a UNIX or Linux master server, for the changes to take effect do the following: stop and restart the NetBackup Request daemon (bprd) and Sorry, we couldn't post your feedback right now, please try again later.

Click OK to exit the Properties screen.Restart NetBackup services on the Master Server when possible.  Ensure that no jobs are running when this is done.   UNIX Master Servers Edit the Veritas does not guarantee the accuracy regarding the completeness of the translation. A: Forward and reverse nslookup can be resolved. http://nodatasource.com/netbackup-error/client-server-handshaking-failed-26-exchange-2010-dag.html Don't have a SymAccount?

Troubleshooting: Please follow all steps within the NetBackup (tm) Troubleshooting Guide or the NetBackup Troubleshooter within the Activity Monitor for this status code before continuing. In the policy, i select, policy type as Standard and On the RHS, i select Foolow NFS. 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

Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem STATUS CODE: 37 "Peername is invalid for restore request" Error Message Peername is invalid for

No Yes Did this article save you the trouble of contacting technical support? No Yes How can we make this article more helpful? CALL US: 1 (866) 837-4827 Solutions Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government Products Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z Services Education Services Business Critical Terms of use for this information are found in Legal Notices.

Related Articles Article Languages x Translated Content Please note that this document is a translation from English, and may

On a UNIX or Linux master server, add a SERVER = media_server_name to the bp.conf file. You may also refer to the English Version of this knowledge base article for up-to-date information. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem Backup of Exchange 2010 Database availability group (DAG) using Fully Qualified Domain Name (FQDN)  gives NBU master needs to resolve media server's IP adress to hostname that appears in Master's Server list.

Not bprd.d. Veritas does not guarantee the accuracy regarding the completeness of the translation. Email Address (Optional) Your feedback has been submitted successfully! Error Message The Backup, Archive, and Restore (BAR) GUI will display this error:   Operation requested by an invalid server - status 37     The bprd debug log shows the

In the host properties of the master server,the media server name is added in Media Servers box. 3. PS : The bprd folder under netbackup/logs on the master should be 'bprd'. No Yes How can we make this article more helpful? NBU MAster: Windows 2008 NBU Version: 7.6.0.1 Media Server: Linux Any leads will be appreciated.

Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Error Code:37 - operation requested by an invalid Operation requested by an invalid serverNot connected.