Veeam 9.5 Restore SQL to Another Server

Veeam 9.5 Restore SQL to Another Server

Restoring a DB from a SQL Server 2012 backup to a different SQL server with SQL 2014 Express installed.  Using Veeam 9.5 U1.

I left in the issues you would encounter along the way.  Required destination SQL server firewall ports and SQL server configuration.

 

 

Start an application item recovery

Veeam SQL Explorer - Restore to a different server

 

Select Microsoft SQL Server

2017-09-13_15-32-08

 

Pick the SQL VM.  Next, Next, Finish

2017-09-13_15-32-41

 

Highlight the Database and select Restore to another server

2017-09-13_15-33-51

 

Then choose point in time or restore last image level backup and click next

2017-09-13_15-34-53

 

Enter the Server-name/instance – Make sure user is entitled in the remote SQL instance.  Log in to remote SQL with the user and make user it has permissions.

2017-09-13_16-00-14

 

If you get the error:

2017-09-13_15-41-02

“(3480) Error: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 – Error Locating Server/Instance Specified)”

 

Then on the destination SQL server open SQL Server Configuration Manager and set the SQL Server Browser Service to Automatic and start it.

2017-09-13_15-40-00

 

2017-09-13_15-41-582017-09-13_15-42-23

 

Then from SQL Server Network Configuration Enable “Named Pipes”

2017-09-13_15-44-07

 

Then from the properties of TCP/IP – Select the IP Address tab and under IBAB TCP Port set to 1433

2017-09-13_15-45-52

2017-09-13_15-46-20

Click the Protocol Tab and Set enabled to Yes and Click OK.

2017-09-13_15-47-48

 

Restart the SQL Service.

2017-09-13_15-49-18

 

From Windows firewall right click inbound Rules and “New Rule”

Select port and Next

2017-09-13_15-51-51

Choose TCP and port 1433 and next

2017-09-13_15-52-38

Select the correct network to apply rule. Next

2017-09-13_15-53-56

Next

2017-09-13_15-53-25

Give it a Name and Finish.

2017-09-13_15-54-56

 

Do this again and add one more incoming TCP rule for Port 1434.

 

Click Next Again on Restore Wizard

2017-09-13_16-00-14

 

Brows to Folder on Remote SQL server that has space for the Restored DB and click Select.

2017-09-13_16-01-10

2017-09-13_16-02-44

 

And then on the Restore Wizard Click Restore.

2017-09-13_16-28-43

 

If your wizard is stalled out on connecting to the target SQL server you may find some events in the restore log that indicate you need to open more ports.

2017-09-13_16-29-23

Log directory for Veeam SQL Explorer

C:\ProgramData\Veeam\Backup\SQLExplorer\Logs

Veeam.SQL.Explorer_2017_09_13_15_33_04.log

9/13/2017 4:29:32 PM 11 (8772) Failed to start agent service on port 1025.
9/13/2017 4:29:32 PM 11 (8772) Error: Unable to start service: Veeam.SQL.Service_20170913162909. See logs for more details.
9/13/2017 4:29:32 PM 11 (8772) Starting agent on port 1026…
9/13/2017 4:29:33 PM 11 (8772) Service not started.
9/13/2017 4:29:33 PM 11 (8772) Service type: 16
9/13/2017 4:29:33 PM 11 (8772) Current state: 1
9/13/2017 4:29:33 PM 11 (8772) Exit code: 0
9/13/2017 4:29:33 PM 11 (8772) Check point: 0
9/13/2017 4:29:33 PM 11 (8772) Wait hint: 0
9/13/2017 4:29:33 PM 11 (8772) Service specific exit code: 0
9/13/2017 4:29:33 PM 11 (8772) Service process ID: 0
9/13/2017 4:29:33 PM 11 (8772) Failed to start agent service on port 1026.
9/13/2017 4:29:33 PM 11 (8772) Error: Unable to start service: Veeam.SQL.Service_20170913162909. See logs for more details.
9/13/2017 4:29:33 PM 11 (8772) Starting agent on port 1027
9/13/2017 4:29:34 PM 11 (8772) Service started successfully.
9/13/2017 4:29:34 PM 11 (8772) Agent started on port 1027
9/13/2017 4:29:34 PM 11 (8772) Connecting to agent on server: MIRAWWW01 (port: 1027)…
9/13/2017 4:29:34 PM 11 (8772) Binding to RPC service using service principal name: mirawww01$@MIRA.LAN…
9/13/2017 4:29:55 PM 11 (8772) Error: The RPC server is unavailable
9/13/2017 4:29:55 PM 11 (8772) Stack:
9/13/2017 4:29:55 PM 11 (8772) at Veeam.Core.Test(Void* hBinding)
at Veeam.Core.Rebind(Char* bindstr, Char* spn, UInt32 authType, _SEC_WINNT_AUTH_IDENTITY_W* auth, UInt32 timeout, Void** hBinding)
9/13/2017 4:29:55 PM 11 (8772) Binding to RPC service…
9/13/2017 4:30:16 PM 11 (8772) Error: The RPC server is unavailable
9/13/2017 4:30:16 PM 11 (8772) Stack:
9/13/2017 4:30:16 PM 11 (8772) at Veeam.Core.Test(Void* hBinding)
at Veeam.Core.Rebind(Char* bindstr, Char* spn, UInt32 authType, _SEC_WINNT_AUTH_IDENTITY_W* auth, UInt32 timeout, Void** hBinding)
9/13/2017 4:30:16 PM 11 (8772) Failed to connect to agent on port 1027. Check firewall settings.
9/13/2017 4:30:16 PM 11 (8772) Error: The operation completed successfully

I added another inbound rule on the target SQL machine for TCP inbound on ports 1025-1040 and once that was added the restore proceeded.

The KB for restores only mentions for 1433 and 1434 but from the logs it clearly needs at least one more in the 1025-1040 range.  Seems to start at 1025 and increment up one port at a time looking for one open.

https://helpcenter.veeam.com/backup/howtosql/how2_sql_prep_step1_check_ports.html

 

Once all ports needed are open you you should see progress.

2017-09-13_16-34-01

2017-09-13_16-34-29

2017-09-13_16-34-52

 

DB successful restored to Point-In-Time and attached in SQL Server

2017-09-13_16-39-40

 

 

Leave a Reply