cancel
Showing results for 
Search instead for 
Did you mean: 

Redirected restore of MS SQL database.

NBU35
Level 6

Hi 

it is just for a clearity:

In case of redirected restore of any SQL database from NBU for MSSQL:

1) can I restore to aleternate client having different version of SQL.
2) Is it possible to restore to other client with same diffrent version of Windows & SQL.
3) what if version of NBU client is also diffrent.

1 ACCEPTED SOLUTION

Accepted Solutions

Marianne
Level 6
Partner    VIP    Accredited Certified
SQL server 2014 is only supported as from NBU 7.6.0.3. Restore should work if target is on correct, supported NBU version. Just double check that Microsoft supports restores from version 2012 to 2014.

View solution in original post

11 REPLIES 11

inn_kam
Level 6
Partner Accredited
 

NetBackup for Microsoft SQL Server: Performing a database move to the same SQLHOST or to an alternate SQLHOST

Article:TECH35995  |  Created: 2004-01-09  |  Updated: 2013-10-24  | 

Article URL http://www.symantec.com/docs/TECH35995

 

 

https://www-secure.symantec.com/connect/forums/restoration-msql-db-instance-servera-serverb

 

 

DOCUMENTATION: Step-by-step procedure for using NetBackup to restore a Microsoft SQL Full Backup using a MOVE script

Article:TECH51062  |  Created: 2007-01-08  |  Updated: 2010-01-02  | 

Article URL http://www.symantec.com/docs/TECH51062

 

 

DOCUMENTATION: Step-by-step procedure for using NetBackup to restore a Microsoft SQL Full Backup using a MOVE script

Article:TECH51062  |  Created: 2007-01-08  |  Updated: 2010-01-02  |  Article URL http://www.symantec.com/docs/TECH51062

 

 

 

inn_kam
Level 6
Partner Accredited

1.

https://www-secure.symantec.com/connect/forums/restore-sql-transaction-log-along-database-different-sql-server#comment-10317631.

Where did you try to start the restore?

It must be done on the destination client where you want to restore to.

You first have to authorize redirected restore on the master by creating altnames files or else No.Restrictions touch file.

See 'Redirecting a restore to a different host'  in NetBackup for Microsoft SQL Server Administrator's Guide:  http://www.symantec.com/docs/DOC5173 

Please also ensure that you have NBU 7.5.0.5 or later installed on the SQL servers - there were bugs/issues with erlier 7.5 patch levels.

 

https://www-secure.symantec.com/connect/forums/netbackup-sql-restore-different-hostpath-and-instance#comment-9697891

Log on to the server where you want to restore (SAOS00506006) and run it from there.

BROWSECLIENT   'Restores images from a host other than the local host.'

so it must point to the original server 

also change

TO  "F:\MSSQL\DataATLAS_log.ldf"

to

TO  "F:\MSSQL\Data\ATLAS_log.ldf"

(missing backslash)

and make sure the path F:\MSSQL\Data\ exists on SAOS00506006

Will Restore -- where there is a Will there is a way

2.https://www-secure.symantec.com/connect/forums/regarding-sql-restore#comment-9162871

...my Source SQL server is on 2008 version and Destination SQL Server is on 2005 version .....

I cannot imagine that this will be supported by Microsoft. Probably the reason for the error we see in above output:

 

https://www-secure.symantec.com/connect/forums/netbackup-cannot-browse-or-restore-sql-client-backups#comment-9687851

When you browse for restores, the SQL server will send its local hostname as Source Client to the master.

When you modify the hostname in the SQL Client GUI to the Virtual name, it sends the following to the master server:
Client ETCCSPCLDB2 is requesting backup images for Client ETCCSPCLDB.

The master treats these names as totally different Client names (i.e. redirected restore).
Now, in NBU, client restore of a different client name is not allowed by default. 
You need to add altnames files to allow client to perform redirected restore.

All of this is documented in NBU for SQL Admin Guide: http://www.symantec.com/docs/DOC5173 

See Redirecting a restore to a different host 
and Performing a restore on a virtual SQL Server instance

Hope this helps.

Supporting Storage 

 

inn_kam
Level 6
Partner Accredited

3. NBU Client which version to which version

and SQL which version to which version

u have to check the compaitibility 

NetBackup 7.x Database Agent Compatibility List

Article:TECH126904  |  Created: 2010-01-13  |  Updated: 2014-11-19  |  Article URL http://www.symantec.com/docs/TECH126904
 

NBU35
Level 6

Hi Inn_Kam

Thanks for your replies, but I am still struggling to get an concrete answer.

As per my understanding from last technote (DB ACL)

1) can I restore to aleternate client having different version of SQL.

It is only possible to restore to other client with different SQL version (provided target SQL server has more latest version of SQL server in comparison to source SQL server).
 

2) Is it possible to restore to other client with same diffrent version of Windows & SQL.

It is possible to restore provided that windows & SQL server version is supported & keeping 1st point in mind.

 
3) what if version of NBU client is also diffrent.

It is possible.

kindly suggest if there is anything which is wrong as per my assumption in this case .

inn_kam
Level 6
Partner Accredited

Hi champ

as per concrete answer ,one must clear the versions of SQL and NB 

NBU35
Level 6

Source : NBU client is 7.5.0.6 & SQL Server 2012

Target : NBU 76.0.2 & SQL server 2014.

inn_kam
Level 6
Partner Accredited

restore and check

(Taking from Admin guide of Netbackup SQL 7.5)

Redirecting a restore to a different host
Multiple NetBackup database clients can be configured to use a single NetBackup
master server for backing up SQL Server databases. With this configuration, you
can back up SQL Server database objects from one client and restore them to
another. In the following procedure, HostA is the client that was originally backed
up and HostB is the other client to which the restore is redirected.
To redirect a restore to a different host
1 Establish permission settings on the master server.
Do one of the following:
■ Create a install_path\NetBackup\db\altnames\No.Restrictions file
to allow unrestricted redirected restore privileges.
■ Create a install_path\NetBackup\db\altnames\HostB file to allow HostB
to restore HostA's data. The client named HostB can then access HostA's
data on the master as well as any other client's data that was backed up
on the master.
2 Select File > Set SQL Server connection properties.
3 Log onto the target instance on HostB.
Performing backups and restores of SQL Server
Redirecting a restore to a different host
98
4 Select File > Set NetBackup client properties and select the current master
server to be a master server that is common to both HostA and HostB.
5 Select File > Restore SQL Server objects.
6 From the Backup History Options dialog box, select HostA as the SQL host
from which the target objects were backed up.
When the restore window appears it contains a history of objects that were
backed up from HostA. Select those objects and restore them to HostB

Marianne
Level 6
Partner    VIP    Accredited Certified
SQL server 2014 is only supported as from NBU 7.6.0.3. Restore should work if target is on correct, supported NBU version. Just double check that Microsoft supports restores from version 2012 to 2014.

NBU35
Level 6

I checked restore from SQL version 2012 (Source) to (target) SQL version 2014 is possible, but vice versa is not possible.

So if I am correct then same is possible from netbackup for MSSQL, but we need to ensure minimum supported of version of NBU client agent is installed on source/ target(as per DB ACL).

inn_kam
Level 6
Partner Accredited

yes as already posted that we have to care about Data base compaitibility

if problem is clear , mark the solution which solves your problem

thanks

Marianne
Level 6
Partner    VIP    Accredited Certified
Lower version to higher version restore is normally supported by any kind of application and database but not the other way round. It makes sense as the newer version always comes with new features that is not understood by the lower version. This is true for NBU, OS, MS-SQL, Oracle, Exchange, etc... etc...