Forum Discussion

Arshad_Khateeb's avatar
Arshad_Khateeb
Level 5
5 years ago

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 ...
7.1.x and Earlier
windows server 2012
  • Marianne's avatar
    Marianne
    5 years ago

    Arshad_Khateeb 

    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)

Marianne's avatar
Marianne
Level 6
5 years ago

Arshad_Khateeb 

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)

  • Arshad_Khateeb's avatar
    Arshad_Khateeb
    Level 5
    5 years ago
    Thanks Marrianne for the quick response. Hope you are good with family in this pandemic.
     
    Size of the database is 1539 MB.
    On media server> client connect/read timeout-14400, backup start/end notify timeout-300
    on client> dbcilent created and global loggin on it is set to 3, client read timeout set to 14400 from 300,
    on media server> global logging set to 3 from minimum, bpbrm and bptm created,
    on master> bprd exists,
    I can't restart nbu at the moment, does bprdreq -rereadconfig on master will do instead?
    Is there anything else you want me to do before i ask the SQL guys to kick off the restore?
    Thanks again!
    • Marianne's avatar
      Marianne
      Level 6
      5 years ago

      Not 100% sure, but bprdreq -rereadconfig probably worth a try.
      dbclient will be the most useful log if the restore should fail again.

      Other than increasing timeouts, can you ask the SQL dba to look into Instant data file initialization ?

      If anything goes wrong and you want to upload logs, please copy to .txt files (e.g. dbclient.txt) and upload as attachment.
      (Seems VOX spam filter does not 'like' log output as part of a post.)

       

      *** Thanks for good wishes with pandemic.... We are healthy, thanks! Just tired of staying home during lockdown... *** 

      • Arshad_Khateeb's avatar
        Arshad_Khateeb
        Level 5
        5 years ago

        finally it was found that the guy who was restoring from database side was doing wrong. he was by mistake doing restoring from different server which just has a small difference in its name. we are done with the restore today and glad it worked. i will revert the changes i have done and by the way bprdreq -rereadconfig worked instead of restarting the NetBackup daemons.

        thanks Marrianne for your real quick help on this issue!