Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- VOX
- Data Protection
- NetBackup
- Have you tried running a
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
SQL Restore Failure
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-15-2009 11:20 AM
Having an issue restoring an SQL db to an alternate client. This is a refresh that occurs every month. Today the DBA is launching this and I'm seeing the following error in the NBU console for the job.
NBU 6.5.3
1 master/media server
Windows 2003
6/15/2009 12:02:28 PM - begin Restore
6/15/2009 12:02:31 PM - restoring image sapbiprd1_1245033018
6/15/2009 12:02:31 PM - requesting resource Fibre Transport
6/15/2009 12:02:31 PM - Info nbjm(pid=8204) NBU status: 800, EMM status: Fibre Transport resources are not available
6/15/2009 12:02:31 PM - Info nbjm(pid=8204) NBU status: 800, EMM status: Fibre Transport resources are not available
6/15/2009 12:02:44 PM - connected
6/15/2009 12:02:44 PM - started process bptm (6388)
6/15/2009 12:02:44 PM - started process bptm (7876)
6/15/2009 12:02:46 PM - begin reading
6/15/2009 12:06:22 PM - Critical bptm(pid=6388) sts_read_image failed: error 2060017 system call failed
6/15/2009 12:06:22 PM - Critical bptm(pid=6388) image read failed: error 2060017: system call failed
6/15/2009 12:06:22 PM - Error bptm(pid=6388) cannot read image from disk, Invalid argument
6/15/2009 12:06:24 PM - Error bptm(pid=7876) The following files/folders were not restored:
6/15/2009 12:06:24 PM - Error bptm(pid=7876) UTF - /sapbiprd1.MSSQL7.SAPBIPRD1.db.BIP.~.7.004of007.20090614203003..C
6/15/2009 12:06:24 PM - Error bptm(pid=7876) UTF - /sapbiprd1.MSSQL7.SAPBIPRD1.db.BIP.~.7.004of007.20090614203003..C
6/15/2009 12:06:25 PM - restored image sapbiprd1_1245033018 - (media read error(85)); restore time 00:03:54
6/15/2009 12:06:28 PM - end Restore; elapsed time: 00:04:00
the restore failed to recover the requested files(5)
6/15/2009 12:06:29 PM - Error bpbrm(pid=1432) client restore EXIT STATUS 85: media read error
Output below from the client
OPERATION RESTORE
OBJECTTYPE DATABASE
RESTORETYPE MOVE
#
DATABASE "BIT"
#
MOVE "BIPDATA1"
TO "H:\BIT\BITDATA1\BITDATA1.mdf"
#
MOVE "BIPDATA2"
TO "H:\BIT\BITDATA2\BITDATA2.ndf"
#
MOVE "BIPDATA3"
TO "H:\BIT\BITDATA3\BITDATA3.ndf"
#
MOVE "BIPDATA4"
TO "H:\BIT\BITDATA4\BITDATA4.ndf"
#
MOVE "BIPLOG1"
TO "S:\BITLOG1\BITLOG1.ldf"
#
# The following image is type: Full
NBIMAGE "sapbiprd1.MSSQL7.SAPBIPRD1.db.BIP.~.7.001of007.20090614203003..C"
#
SQLHOST "alabwsap5"
SQLINSTANCE "BIT"
#
NBSERVER "ALABBK3"
STRIPES 007
BROWSECLIENT "sapbiprd1"
MAXTRANSFERSIZE 6
BLOCKSIZE 7
RESTOREOPTION REPLACE
RECOVEREDSTATE RECOVERED
NUMBUFS 2
ENDOPER TRUE
INF - RESTORE STARTED USING
Microsoft SQL Server 2005 - 9.00.3077.00 (X64)
Dec 17 2008 20:40:08
Copyright (c) 1988-2005 Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 1)
Batch = C:\Program Files\Veritas\NetBackup\DbExt\MsSql\Restore_BIT_from_BIP_20090615.bch, Op# = 1.
INF - Restoring from <7> images. The first is <sapbiprd1.MSSQL7.SAPBIPRD1.db.BIP.~.7.001of007.20090614203003..C>.
INF - restore database "BIT" from VIRTUAL_DEVICE='VNBU0-1672-6784-1245075338', VIRTUAL_DEVICE='VNBU1-1672-6784-1245075338', VIRTUAL_DEVICE='VNBU2-1672-6784-1245075338', VIRTUAL_DEVICE='VNBU3-1672-6784-1245075338', VIRTUAL_DEVICE='VNBU4-1672-6784-1245075338', VIRTUAL_DEVICE='VNBU5-1672-6784-1245075338', VIRTUAL_DEVICE='VNBU6-1672-6784-1245075338' with stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 14, replace , norecovery, move 'BIPDATA1' to 'H:\BIT\BITDATA1\BITDATA1.mdf', move 'BIPDATA2' to 'H:\BIT\BITDATA2\BITDATA2.ndf', move 'BIPDATA3' to 'H:\BIT\BITDATA3\BITDATA3.ndf', move 'BIPDATA4' to 'H:\BIT\BITDATA4\BITDATA4.ndf', move 'BIPLOG1' to 'S:\BITLOG1\BITLOG1.ldf', replace
INF - Number of stripes: 7, Number of buffers per stripe 2.
INF - Created VDI object for SQL Server instance <BIT>. Connection timeout is <300> seconds.
Restore started Mon Jun 15 08:15:42 2009
INF - ODBC return code <2>, SQL State <01000>, SQL Message <3211><[Microsoft][SQL Native Client][SQL Server]10 percent processed.>.
INF - ODBC return code <2>, SQL State <01000>, SQL Message <3211><[Microsoft][SQL Native Client][SQL Server]20 percent processed.>.
INF - ODBC return code <2>, SQL State <01000>, SQL Message <3211><[Microsoft][SQL Native Client][SQL Server]30 percent processed.>.
INF - ODBC return code <2>, SQL State <01000>, SQL Message <3211><[Microsoft][SQL Native Client][SQL Server]40 percent processed.>.
ERR - Error in VxBSAGetData: 3.
CONTINUATION: - System detected error, operation aborted.
ERR - Error in VxBSAGetData: 3.
CONTINUATION: - System detected error, operation aborted.
ERR - Error in DBthreads::dbclient: 6.
CONTINUATION: - The system cannot find the file specified.
ERR - Error in VxBSAEndData: 6.
CONTINUATION: - The handle used to associate this call with a previous VxBSAInit() call is invalid.
ERR - Error in DBthreads::dbclient: 6.
CONTINUATION: - The system cannot find the file specified.
ERR - Error in VxBSAEndData: 6.
CONTINUATION: - The handle used to associate this call with a previous VxBSAInit() call is invalid.
ERR - Error in VxBSAGetData: 3.
CONTINUATION: - System detected error, operation aborted.
ERR - Error in VxBSAEndData: 3.
CONTINUATION: - System detected error, operation aborted.
ERR - Error in VxBSAGetData: 3.
CONTINUATION: - System detected error, operation aborted.
ERR - Error in VxBSAEndData: 3.
CONTINUATION: - System detected error, operation aborted.
ERR - Error in VxBSAGetData: 3.
ERR - Error in VxBSAGetData: 3.
CONTINUATION: - System detected error, operation aborted.
CONTINUATION: - System detected error, operation aborted.
ERR - Error in VxBSAEndData: 3.
ERR - Error in VxBSAEndData: 3.
CONTINUATION: - System detected error, operation aborted.
CONTINUATION: - System detected error, operation aborted.
ERR - Error in VxBSAGetData: 3.
CONTINUATION: - System detected error, operation aborted.
ERR - Error in VxBSAEndData: 3.
CONTINUATION: - System detected error, operation aborted.
ERR - Error in VDS->Close: 0x80770004.
CONTINUATION: - An abort request is preventing anything except termination actions.
INF - OPERATION #1 of batch C:\Program Files\Veritas\NetBackup\DbExt\MsSql\Restore_BIT_from_BIP_20090615.bch FAILED with STATUS 1 (0 is normal). Elapsed time = 2014(2014) seconds.
INF - Results of executing <C:\Program Files\Veritas\NetBackup\DbExt\MsSql\Restore_BIT_from_BIP_20090615.bch>:
<0> operations succeeded. <1> operations failed.
Labels:
6 REPLIES 6
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-15-2009 11:30 AM
http://seer.entsupport.symantec.com/docs/295563.htm
talks about duplication though maybe applicable to restore
On the Windows 2003 server in question, 2 Registry Keys (PoolUsageMaximum, PagedPoolSize) may be created to fine-tune how the operating system manages Paged Pool Memory. For complete details on creating and configuring these registry keys, review Microsoft Knowledge Base Article below:
http://support.microsoft.com/kb/304101/en-us
Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.
talks about duplication though maybe applicable to restore
On the Windows 2003 server in question, 2 Registry Keys (PoolUsageMaximum, PagedPoolSize) may be created to fine-tune how the operating system manages Paged Pool Memory. For complete details on creating and configuring these registry keys, review Microsoft Knowledge Base Article below:
http://support.microsoft.com/kb/304101/en-us
Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-15-2009 05:44 PM
It might be that the bptm process is trying to read backup image off disk storage unit while it's already open for previous stripe's restore.
Ask your DBA to set STRIPES to 1 and test restore again - this will also help memory/buffer allocation for the restore, you might not even need to touch registry.
http://support.veritas.com/docs/285209
Cheers,
Abe
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-15-2009 10:28 PM
From the master server log it seems that backup has failed with status code 85
6/15/2009 12:06:25 PM - restored image sapbiprd1_1245033018 - (media read error(85)); restore time 00:03:54
6/15/2009 12:06:28 PM - end Restore; elapsed time: 00:04:00
the restore failed to recover the requested files(5)
6/15/2009 12:06:29 PM - Error bpbrm(pid=1432) client restore EXIT STATUS 85: media read error
As per Symantec jobs failing with status code 84 - media write , 85 - media read and 86 media position, there could be potential hardware issues that can cause these errors.
There are several tools available from the hardware vendors that can be used to help diagnose these hardware issues.
6/15/2009 12:06:25 PM - restored image sapbiprd1_1245033018 - (media read error(85)); restore time 00:03:54
6/15/2009 12:06:28 PM - end Restore; elapsed time: 00:04:00
the restore failed to recover the requested files(5)
6/15/2009 12:06:29 PM - Error bpbrm(pid=1432) client restore EXIT STATUS 85: media read error
As per Symantec jobs failing with status code 84 - media write , 85 - media read and 86 media position, there could be potential hardware issues that can cause these errors.
There are several tools available from the hardware vendors that can be used to help diagnose these hardware issues.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-16-2009 01:20 AM
Have you tried running a verify from the catalog on this image to make sure it is readable?
Also do you have another copy of this image? If so i would try and restore from this image as well
Are you running this from Disk or Tape?
Also do you have another copy of this image? If so i would try and restore from this image as well
Are you running this from Disk or Tape?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-29-2010 09:21 AM
Hello Giroevolver...
I have this problem with all sql images from this server.
But in other server i dont have any problem.
I´m running this from tape.
I have this problem with all sql images from this server.
But in other server i dont have any problem.
I´m running this from tape.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-29-2010 11:36 AM
Related Content
- Drive Address 1 is already occupied by drive in NetBackup
- 10 years old netbackup appliance database service down, ssl certification out date in NetBackup
- Best way to upgrade redhat 7,9 to 8.x on both netbackup master and media servers in NetBackup
- Get-BEBackupDefinition not showing all results in Backup Exec
- Alta Recovery Vault Pre-Install Checklist - Hot of The Press!! in NetBackup
