Ms Sql Server Policy Restore Error 2809
Contents |
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 error in getcommand: 0x80770004 Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体)
Netbackup Restore Sql Database To Different Server
English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Redirected restore of SQL netbackup sql alternate client restore database to a different client failing with MS-SQL-Server policy restore error (2809) Article:000018133 Publish: Article URL:http://www.veritas.com/docs/000018133 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 Redirected restore of SQL database to a different client failing with MS-SQL-Server policy restore error (2809) Error Message From Job Activity Monitor parent job :06/04/2013 20:17:07 - Error bpbrm (pid=2205) socket read failed: errno = 104 - Connection reset by peer06/04/2013 20:17:07 - Error bptm (pid=2210) cannot write data to socket, Connection reset by peer06/04/2013 20:17:07 - Error bptm (pid=2210) The following files/folders were not restored:.....06/04/2013 20:17:08 - Error bpbrm (pid=2205) client restore EXIT STATUS 13: file read failed06/04/2013 20:17:08 - restored from image sql01_1369627752; restore time: 0:00:3906/04/2013 20:17:09 - end Restore; elapsed time 0:00:42MS-SQL-Server policy restore error (2809)From Job Activity Monitor child job :06/04/2013 20:16:22 - begin Restore06/04/2013 20:16:24 - Info dbclient (pid=5216) INF - RESTORE STARTED USING06/04/2013 20:16:24 - Info dbclient (pid=5216) Microsoft SQL Server 2008 (SP2) - 10.0.3798.0 (X64) 06/04/2013 20:16:24 - Info dbclient (pid=5216) Jun 18 2010 16:37:39 06/04/2013 20:16:24 - Info dbclient (pid=5216) Copyright (c) 1988-2008 Microsoft Corporation06/04/2013 20:16:24 - Info dbclient (pid=5216) Standard Edition (64-bit) on Windows NT 6.1
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Sign In CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : NetBackup https://www.veritas.com/support/en_US/article.TECH206956 : full-diff restores of ms-sql database fails with 2... VOX : Backup and Recovery : NetBackup : full-diff restores of ms-sql database fails with 2... Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page full-diff restores of ms-sql database https://vox.veritas.com/t5/NetBackup/full-diff-restores-of-ms-sql-database-fails-with-2809-status/td-p/590269 fails with 2809 status code DavidE31 Level 4 12-27-2013 12:50 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hello, we are facing a problem with full-diff restores of ms-sql database using MOVE scripts Master Server is W2008 R2 with NBU 7.5.0.6, media servers as well MS-SQL server : sql server 2008 on Windows 2003 R2 64bit SP2 with NBU 7.5.0.6, netbackup MS-SQL client installed Here are the steps to backup and restore databases : - source and dest clients are the same - in the MOVE script, database is renamed and restored to another volume disk of the same source server - the backup script is placed in a MS-SQL policy with "Perform snapshot backups" activated (snapshot method "auto") What happens : - full + diff backups are OK - the full restore job is OK, but the diff restore fails with 2809 status
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER https://www.veritas.com/support/en_US/article.000024200 Customer Center Support Community MyVeritas Customer Success Licensing Programs https://www.veritas.com/support/en_US/article.000110101 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 SQL restore ms sql fails due to a file name mis-match. Article:000024200 Publish: Article URL:http://www.veritas.com/docs/000024200 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 ms sql server to set up your subscription. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem Attempts to perform a SQL restore fail due to a failed filename mis-match comparing the file referenced in NBIMAGE found in the restore BCH file against the filename returned by bpbrm. Error Message The error can be observed from the dbclient log: 19:40:53.270 [344.4520] <16> readTarHeader: ERR - requested filename does not match returned filename With the corresponding parent informational job details: Detailed Status: 9/23/2014 7:40:47 PM - begin Restore 9/23/2014 7:40:48 PM - Info dbclient(pid=344) INF - RESTORE STARTED USING 9/23/2014 7:40:48 PM - Info dbclient(pid=344) Microsoft SQL Server 2014 - 12.0.2000.8 (X64) 9/2
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 NetBackup status code: 2809 Article:000110101 Publish: Article URL:http://www.veritas.com/docs/000110101 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 Description Message: MS-SQL-Server policy restore errorExplanation: An error caused the restore of the SQL Server data to fail.Recommended Action: Try the following possible solutions in the order presented:Ensure that the client server list contains entries for the master server and any media servers that can be used during a backup or restore.Examine the status or the progress log on the client for messages on why the restore failed. Also, check the All Log Entries report on the server.Check ownership and permission on directories where files are restored and on the SQL instance that you are restoring.Check ownership and permission on the SQL Server instance and on the directories where files are restored.Check the following logs for additional failure information on the client side:install_path\NetBackup\logs\dbclient install_path\NetBackup\logs\bpbkar (Snapshot Client) install_path\NetBackup\logs\bpfis (Snapshot Client) install_path\NetBackup\logs\bppfi (instant recovery) Check the SQL server Event Viewers (application and system) for any errors or messages that are related to the restore operation.Increase restore verbose levels.See the NetBackup for SQL Server Administrator's Guide.Review this guide to verify that you launched the restore correctly.Connect to the server where SQL is running and launch the restore from that server using the Backup, Archive, and Restore GUI.Correct the problems that you find and retry the restore.Click here to view technical notes and