sql restore failed from client
Master
| serverA | Linux(2.6.32-754.25.1.el6.x86_64) | UNIX | Master Server | 8.1 | Connected | Off |
Client
| usseccmpsqce110.ey.net | Windows2012(6) | Windows | Client | 7.7.3 | Connected | Off |
Error
Microsoft SQL Server 2012 (SP4-GDR) (KB4057116) - 11.0.7462.6 (X64)
Jan 5 2018 22:11:56
Copyright (c) Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: )
Batch = C:\Program Files\VERITAS\NetBackup\DbExt\MsSql\Statestics.bch, Op# = 1.
INF - Using backup image USSECBMPSQCE210.MSSQL7.USSECCMPSQCE210\INST2.db.Statistics_DB.~.7.001of001.20200201010322..C
INF - restore database "Statistics_DB_feb" from VIRTUAL_DEVICE='VNBU0-7840-17592-1586278024' with stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2, replace , norecovery, move 'Statistics_DB' to 'G:\G_SQLDATA_1\SQLDATA\Statistics_DB_feb.mdf', move 'Statistics_DB_log' to 'G:\G_SQLLOG_1\SQLLOG\Statistics_DB_Feblog.ldf'
INF - Number of stripes: 1, Number of buffers per stripe 2.
INF - Created VDI object for SQL Server instance <INST2>. Connection timeout is <900> seconds.
ERR - Error in GetConfiguration: 0x80770003.
CONTINUATION: - The api was waiting and the timeout interval had elapsed.
DBMS MSG - ODBC return code <-1>, SQL State <37000>, SQL Message <3201><[Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open backup device 'VNBU0-7840-17592-1586278024'. Operating system error 0x80070002(The system cannot find the file specified.).>.
DBMS MSG - SQL Message <3013><[Microsoft][SQL Server Native Client 11.0][SQL Server]RESTORE DATABASE is terminating abnormally.>
ERR - Error found executing <restore database "Statistics_DB_feb" from VIRTUAL_DEVICE='VNBU0-7840-17592-1586278024' with stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2, replace , norecovery, move 'Statistics_DB' to 'G:\G_SQLDATA_1\SQLDATA\Statistics_DB_feb.mdf', move 'Statistics_DB_log' to 'G:\G_SQLLOG_1\SQLLOG\Statistics_DB_Feblog.ldf'>.
INF - OPERATION #1 of batch C:\Program Files\VERITAS\NetBackup\DbExt\MsSql\Statestics.bch FAILED with STATUS 1 (0 is normal). Elapsed time = 906(906) seconds.
INF - Results of executing <C:\Program Files\VERITAS\NetBackup\DbExt\MsSql\Statestics.bch>:
<0> operations succeeded. <2> operations failed.
What is the size of the database?
Always good to increase Client Read timeout on media server before a restore is attempted (the manual says the value must be changed on the client) :
About minimizing timeout failures on large SQL Server database restores
A large SQL Server restore may fail with a Client Read Timeout error before any
data has been read from the NetBackup media. This error occurs because the SQL
Server may need to pre-write the database files before the restore operation begins.
The time that is required for this process is a function of certain factors: the size of
the database files and the speed at which your host machine can write to disk. For
example, consider that your system can perform disk writes at the rate of 60
megabytes per second and you have a 2.4 terabyte database. Then it takes at least
12 hours for SQL Server to prep the disk before the actual restore can begin. In
reality, the delay may be even longer than what you calculate by as much as 20%
to 40%.
The timeout problem can be resolved by increasing the NetBackup Client Read
Timeout setting. Use the NetBackup Administration Console on the server to change
the properties of each client that contains a database you may need to restore.You may also want to look at this section in the manual:
Instant data file initialization
When you restore a database, filegroup, or database file, SQL Server zeroes the
file space before it begins the restore operation. This action can slow the total
recovery time by as much as a factor of 2. To eliminate file initialization, run the
MSSQLSERVER service under a Windows account that has been assigned the
SE_MANAGE_VOLUME_NAME. For more information, see the SQL Server and
the Windows documentation.For further troubleshooting, please ensure that the following log folders exist:
On client - dbclient (Set logging level to 3. )
On media server: bpbrm and bptm
On master: bprd (NBU needs to be restarted after this folder is created)
