Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Restore SQL server to another computer with BEWS 2012

Created: 04 Apr 2013 | 17 comments
Nene's picture

Hi support,

I need to confirm if i am restoring an SQL server that was backed up using the SDR on BEWS 2012, will i be required to do any other thing in the SQL?

I would not want to have any issues with the SQL restore since I know only the basics about SQL.

Using SSR is simpler since all I need is the backup, I can restore the image to any other server and it will work like the old one.

A customer wants only BEWS 2012 to use the SDR component. But i was advised getting SSR for complete imaging of the server.

What do you think?

An urgent response will be appreciated.

Operating Systems:

Comments 17 CommentsJump to latest comment

VJware's picture

SDR will restore only the windows server itself, though you will have to run another restore via Backup Exec for an application such as SQL.

Nene's picture

Hi VJware,

I ran a test, I restored the complete server to a similar hardware.

But the IIS and two SQL server services do not start.

Do I need to restore only the C:\ and System State without the partition for the SQL installation? As stated in the document link sent by Donald.

When do I restore the partition for the SQL?

 

Jaydeep S's picture

The only thing that you need to do now is get the SQL Instances up and running. Not sure if they are SQL Server instances or SQL Express. If they are SQL Server instances they will have a Master, Model database backup files siting in the default data folder for the instance example C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data. In this folder locate the $4dr extensions files This is how you rename them -

MASTER$4IDR - MASTER.MDF
MASTLOG$4IDR - MASTLOG.LDF
MODEL$4IDR - MODEL.MDF
MODELLOG$4IDR - MODELLOG.LDF

Now the SQL instance can be started. Following which you can do the SQL restore.

Folr more info refer point 9  in http://www.symantec.com/docs/TECH87893

Nene's picture

Hi Jaydeep,

I will try this and get back to u.

Thank u so much.

Nene's picture

Hi Jaydeep,

The path M:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data has all these files already existing

MASTER$4IDR

MASTER.MDF
MASTLOG$4IDR

MASTLOG.LDF
MODEL$4IDR

MODEL.MDF
MODELLOG$4IDR

MODELLOG.LDF

I tried to copy out the files without the $4IDR and rename the files like u specified but the same issues still exist. The services for IIS and the SQL do not start.

Recall that I said earlier, the SQL is installed on a seperate partition.

If I restore the windows first, how do i restore the SQL partition from the backup exec server?

Is the SQL installed on the C:\ in the scenario u hv?

Jaydeep S's picture

If the path was M:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data I am assuming that would be the default data path for that instance. In my post I had mentioned example of path as C:\ as the SQL is installed on the C Drive

What is the Application log error message that you are getting when you try to start the SQL Service. It would help if you can post it here. As you will not be able to proceed with the database restore while the Instance is down.

Nene's picture

Hi Jaydeep,

I have a 2nd scenario with the SQL installed on C:\ just as u hv yours.

The same application log errors exist.

Below are the errors:

For the SQL services:

Event ID 17120: SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

Event ID 17826: Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.

Event ID 17182: TDSSNIClient initialization failed with error 0x80092004, status code 0x1.

Event ID 26014: Unable to load user-specified certificate (Cert Hash(sha1) The server will not accept any connection. You should verify the certificate is correctly installed........

I already checked these online and the protocol for VIA is disabled.

No other server is using the SQL port.

For IIS, the default Website is not running, specific error code -2146893818

I really need to resolve this ASAP.

Thank you for your support.

 

 

VJware's picture

Did you ensure clearing the "read-only" attribute for the renamed files ?

Secondly, the SQL service should be set to use the local system account.

Nene's picture

Hi VJware,

I was almost thinking u neglected me. just kidding.

Thanx for your support so far.

in one of the last posts, i informed Jaydeep thet the folder already has all of these below. So, if i rename it will give me a 2nd copy. The SQL service was changed to local system but still does not start.

I have attached the SQL screenshot

MASTER$4IDR

MASTER.MDF

MASTLOG$4IDR

MASTLOG.LDF

MODEL$4IDR

MODEL.MDF

MODELLOG$4IDR

MODELLOG.LDF

 

SQL.png
Nene's picture

Hi VJware,

I forgot to inform u. There is no read attribute selected for any of the SQL files.

Thank u.

VJware's picture

Would you post the sql error log from \Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER/MSSQL/Log

Lastly, try the steps listed in these external links... these are the most common reasons for the sql service startup failure -

http://www.sqldbadiaries.com/2013/01/01/service-do...

http://nickstips.wordpress.com/2010/09/08/sql-ssl-...

Alternatively, would recommend you to log a support case.

Nene's picture

Hi Vjware,

Thanx again for your usual support.

Below is the log from the SQL server.

From the links u posted. I do not have the user profile with backup or temporary type, it is only a single one and it is local.

I intend to try the 2nd link for the certificate.

Error Log:

2013-04-10 08:10:33.49 Server      Microsoft SQL Server 2008 R2 (SP2) - 10.50.4000.0 (X64)
    Jun 28 2012 08:36:30
    Copyright (c) Microsoft Corporation
    Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)

2013-04-10 08:10:33.49 Server      (c) Microsoft Corporation.
2013-04-10 08:10:33.49 Server      All rights reserved.
2013-04-10 08:10:33.49 Server      Server process ID is 2712.
2013-04-10 08:10:33.49 Server      System Manufacturer: 'Dell Inc.', System Model: 'OptiPlex 9010'.
2013-04-10 08:10:33.49 Server      Authentication mode is WINDOWS-ONLY.
2013-04-10 08:10:33.49 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2013-04-10 08:10:33.49 Server      This instance of SQL Server last reported using a process ID of 1396 at 4/10/2013 8:09:23 AM (local) 4/10/2013 7:09:23 AM (UTC). This is an informational message only; no user action is required.
2013-04-10 08:10:33.49 Server      Registry startup parameters:
     -d C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf
     -e C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG
     -l C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
     -T 8295
     -T 4199
2013-04-10 08:10:33.53 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2013-04-10 08:10:33.53 Server      Detected 4 CPUs. This is an informational message; no user action is required.
2013-04-10 08:10:33.53 Server      Cannot use Large Page Extensions:  lock memory privilege was not granted.
2013-04-10 08:10:33.63 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
2013-04-10 08:10:33.65 Server      Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2013-04-10 08:10:33.68 spid7s      Starting up database 'master'.
2013-04-10 08:10:34.63 spid7s      Resource governor reconfiguration succeeded.
2013-04-10 08:10:34.63 spid7s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2013-04-10 08:10:34.63 spid7s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
2013-04-10 08:10:34.63 spid7s      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2013-04-10 08:10:34.67 spid7s      SQL Trace ID 1 was started by login "sa".
2013-04-10 08:10:34.67 spid7s      Starting up database 'mssqlsystemresource'.
2013-04-10 08:10:34.77 spid7s      The resource database build version is 10.50.4000. This is an informational message only. No user action is required.
2013-04-10 08:10:35.35 spid10s     Starting up database 'model'.
2013-04-10 08:10:35.35 Server      The server could not load the certificate it needs to initiate an SSL connection. It returned the following error: 0x8009030d. Check certificates to make sure they are valid.
2013-04-10 08:10:35.36 Server      Error: 26014, Severity: 16, State: 1.
2013-04-10 08:10:35.36 Server      Unable to load user-specified certificate [Cert Hash(sha1) "D18EA76CA23FBE0DDE7D8ACD8FB53566C2D43AF2"]. The server will not accept a connection. You should verify that the certificate is correctly installed. See "Configuring Certificate for Use by SSL" in Books Online.
2013-04-10 08:10:35.36 Server      Error: 17182, Severity: 16, State: 1.
2013-04-10 08:10:35.36 Server      TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property.

2013-04-10 08:10:35.36 Server      Error: 17182, Severity: 16, State: 1.
2013-04-10 08:10:35.36 Server      TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property.

2013-04-10 08:10:35.36 Server      Error: 17826, Severity: 18, State: 3.
2013-04-10 08:10:35.36 Server      Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2013-04-10 08:10:35.36 Server      Error: 17120, Severity: 16, State: 1.
2013-04-10 08:10:35.36 Server      SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
 

VJware's picture

Log mentions ~

The server could not load the certificate it needs to initiate an SSL connection. It returned the following error: 0x8009030d. Check certificates to make sure they are valid.

THe 2nd link posted earlier should help...else if not, there used to be a method to disable cert checks..lemme check..

Nene's picture

Hi VJware,

Did you get the method to disable the certificate checks?

I am still stuck on the same issue.

I was wondering, at the beginning of this post u mentioned that SDR would allow restore of the Windows OS only.

But the SQL is installed on the C:\ just as Jaydeep has. How will i restore the SQL using the BEWS?

Will i need to overwrite the master, model and other databases? 

I am really trying to get this to work for this customer.

Using SSR will give a proper image of the server, this i have tested before now. But he does not want to purchase that. He hopes SDR will work for him since it has for others.

I expect your response soon.

Thank you for your continued support.

VJware's picture

Try this KB for deleting & recreating the certs... (i couldn't find the method to disable ssl check :( )

http://support.microsoft.com/kb/309398

Nene's picture

Hi VJware,

Thank you for the response. I will try deleting the certificates.But how do i reinstall it.

Also, what about the process for restoring the OS only using the SDR, then restoring the SQL later? What do u say about that?

Remember, the issue is that I have the SQL restored with the OS from SDR.

Donald Eady's picture

VJware nailed it ... you will be able to restore the server itself but will then need to restore any thing that was being protected by B.E.'s database agentes. SQL,Sharepoint,Exchange Etc... see doc below 

 

http://www.symantec.com/docs/TECH180099

 
 

I hope this posting was helpful