Netbackup Error 37
Contents |
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community netbackup error 37 restore MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate
Peer Name Is Invalid For Restore Request
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 STATUS CODE 37: Known causes for a NetBackup Status Code 37 "Operation requested by an invalid server" Article:000030824 Publish: Article URL:http://www.veritas.com/docs/000030824 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 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 STATUS CODE 37: Known causes for a NetBackup Status Code 37 "Operation requested by an invalid server" Error Message Operation requested by an invalid server Solution Overview: Known causes for a NetBackup Status Code 37 "Operation requested by an invalid server"Troubleshooting: Review the Activity Monitor or the All Log Entries report for the backup which failed with a Status Code 37 and determine what server name is not considered valid by the master serverLog files: N/A Resolution: Most commonly, a Status Code 37 is the result of not adding a new media server's name to the servers list on the master server. - For UNIX master servers, add the line SERVER =
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 STATUS CODE 37: SQL restore attempts fail with NetBackup Status Code 37 (operation requested by an invalid server). Article:000095126 https://www.veritas.com/support/en_US/article.TECH46050 Publish: Article URL:http://www.veritas.com/docs/000095126 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 to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Related Articles Article Languages Subscribe https://www.veritas.com/support/en_US/article.TECH51332 to this Article Manage your Subscriptions Problem STATUS CODE 37: SQL restore attempts fail with NetBackup Status Code 37 (operation requested by an invalid server). Error Message operation requested by an invalid server Solution Overview: When attempting to restore a Microsoft SQL server database, the restore fails with a NetBackup Status Code 37 (operation requested by an invalid server). Troubleshooting: On the Windows master server, look to see if there is a directory with the same name as the SQL server in the
by Zhang Yunlong at 21:29 Email This BlogThis! Share to Twitter Share to Facebook Share to Pinterest Labels: Symantec NetBackup No comments : Post a Comment Newer Post Older Post Home Subscribe to: Post Comments ( Atom ) Category Active Directory ( 4 ) Admin Script http://ylnotes.blogspot.com/2014/04/NetBackupError37.html ( 17 ) Android ( 1 ) Audit Reports ( 1 ) Backup ( https://adsm.org/lists/html/Veritas-bu/2002-11/msg00462.html 4 ) CleanUp to Free Space ( 4 ) Clone ID Reset Script ( 2 ) Exchange Server ( 2 ) Gallery ( 2 ) Hyper-V ( 2 ) IE ( 2 ) Linux Application Server ( 1 ) Mac OS ( 1 ) Office 101 ( 1 ) Password Reset for Windows Account ( 3 ) netbackup error Quick Reference ( 1 ) Sample Admin Script ( 2 ) Slipstream Script ( 1 ) Software Router ( 1 ) SQL Server ( 3 ) Symantec NetBackup ( 2 ) Symantec NetBackup 101 ( 1 ) System Update Readiness Tool ( 3 ) TMG 2010 ( 1 ) USB Boot ( 3 ) vHypervisor ( 1 ) Windows Activation ( 3 ) Windows Troubleshooting ( 4 ) XenServer ( netbackup error 37 1 ) Blog Archive ▼ 2014 ( 36 ) ► October ( 2 ) ▼ April ( 6 ) [Move to blog.ylnotes.com] Express Script: Referen... [Move to blog.ylnotes.com] Setup Hyper-V Remote IS... [YLN] WinFix: Failover Cluster - Add Cluster Node ... [Move to blog.ylnotes.com] Validate Windows Cluste... [Move to blog.ylnotes.com] Symantec NetBackup Erro... [Move to blog.ylnotes.com] Admin Scripts: Create F... ► March ( 16 ) ► February ( 10 ) ► January ( 2 ) ► 2013 ( 41 ) ► December ( 3 ) ► November ( 1 ) ► October ( 4 ) ► September ( 5 ) ► August ( 5 ) ► July ( 12 ) ► June ( 11 ) Search This Blog Popular Posts Recently Android Page [YLN] Microsoft iSCSI Target Server (WS2012/R2) - Error: Unable to import the virtual disk. A Virtual disk with that file path already exists [Move to blog.ylnotes.com] System Update Readiness Tool - Windows 8/8.1 & Windows Server 2012/2012 R2 [Move to blog.ylnotes.com] Active Directory: Domain Name Rename - Single DC for Windows Server 2012 [Move to blog.ylnotes.com] TMG 2010 - The easiest way to import URL Sets Admin Script: Backup SQL Server Databases with Week Of Month Timestamp Express Setup: IE 11 for Windows 7/Server 2008 R2 Vyat
(Michael G Andersen) Date: Wed, 27 Nov 2002 09:46:35 +0100 Hi Gerrit I have had this error when the client sent another name than the one used by Netbackup, the bprd log on the master server was where I found our bug using verbose = 99 in bp.conf Regards Michael Gerrit Bos