Redirect SQL restore fail with status 5 and 2850

[eddynfs]

Hello folks,

I try to do a redirect SQL restore from one SQL Server to Another, but all restore jobs finish with status 5 and 2850. Beyond this, a detect a strange message in the LOG of Netbackup Database Extension like this

"DBMS MSG - ODBC return code <-1>, SQL State <37000>, SQL Message <5591><[Microsoft][ODBC SQL Server Driver][SQL Server]FILESTREAM feature is disabled.>."

Here are the settings of the environment where I am trying to restore:

Netbackup Server: Netbackup 7.6.0.4 in a Windows Server 2008 R2

The SQL Production Server: SQL Server 2012 hostend in a Windows Server 2008 R2 Enterprise

The SQL Destinantion Server: SQL Server 2012 hostend in a Windows Server 2008 R2 Enterprise

Do any of you understand it. Your help is much appreciated.

[P_Kesavan]

Hello ,

can you please check on the following things .

1. The restore script on the destination SQL Host and triggered from there ?

2. Have you created the No.restrictions file master server as you are doing the altertnate restore ?

No.Restriction file path --> \Program Files\Veritas\Netbackup\db\altnames\

[eddynfs]

Hi @P_Kesavan,

1. The restore script on the destination SQL Host and triggered from there ? Yes. 

2. Have you created the No.restrictions file master server as you are doing the altertnate restore ?

No.Restriction file path --> \Program Files\Veritas\Netbackup\db\altnames\

Yes.

Follow the restore script on destionation SQL Server that I using:

#
# This is a template for the database MOVE command.
#
OPERATION RESTORE
OBJECTTYPE DATABASE
RESTORETYPE MOVE
#
# Replace the database name in the following line with the name of the database that you
# want to move to. Also remove the hash mark <#> which precedes the keyword <DATABASE>.
#
DATABASE "Sharepoint_Portal_CMT1109"
#
# Replace the file path <E:\MSSQL11.MSSQLSERVER\MSSQL\DATA\Sharepoint_Portal_CMT.mdf>
# with a new file path. Also remove the hash mark <#> which precedes the keyword <TO>.
# The target of the MOVE keyword must be "Sharepoint_Portal_CMT".
MOVE "Sharepoint_Portal_CMT"
TO "C:\TEMP\netbackup_sql\Sharepoint_Portal_CMT1109.mdf"
#
#
# Replace the file path <F:\Rbs_CMT>
# with a new file path. Also remove the hash mark <#> which precedes the keyword <TO>.
# The target of the MOVE keyword must be "RBSFilestreamFile".
MOVEFILESTREAMDIR "RBSFilestreamFile"
TO "C:\TEMP\netbackup_sql\Rbs_CMT"
#
#
# Replace the file path <F:\Log\Sharepoint_Portal_CMT_log.ldf>
# with a new file path. Also remove the hash mark <#> which precedes the keyword <TO>.
# The target of the MOVE keyword must be "Sharepoint_Portal_CMT_log".
MOVE "Sharepoint_Portal_CMT_log"
TO "C:\TEMP\netbackup_sql\Sharepoint_Portal_CMT_log1109.ldf"
#
# The following image is type: Full
NBIMAGE "elnbsbsrv42.MSSQL7.ELNBSBSRV42.db.Sharepoint_Portal_CMT.~.7.001of002.20170911204939..C"
SQLHOST "ELNBSBSRV42T"
NBSERVER "ELNBSBSRV83"
BROWSECLIENT "ELNBSBSRV42"
MAXTRANSFERSIZE 6
BLOCKSIZE 7
RECOVEREDSTATE NOTRECOVERED
NUMBUFS 2
ENDOPER TRUE

note: I was tried RECOVEREDSTATE with both RECOVERED ou NOTRECOVERED

Thanks man.

[P_Kesavan · Accepted solution]

The only error ,could see from the logs attached is FILESTREAM disabled.

Could you check on the source host from where the backups happened for Filestreaming option . 

If the source is enabled with FILESTREAM option , please speak to your SQL DBA about enabling this option on the target host .

Then you may try the restore.

[rk1074]

does  the path C:\TEMP\netbackup_sql physically exist on server?

also chk the below discussion:

https://vox.veritas.com/t5/NetBackup/SQL-restore-issue/td-p/688244

[Mike_Gavrilov]

Could you share your C:\Program files\VERITAS\NetBackup\logs\dbclient\<log files> from the destination client, please? If the folder wasn't created create it, set logging on the destination client to max ( Start>Backup, Archive and restore >File>Netbackup Client Properties>Troubleshooting>  Set Verbose to 5, General to 2, database to 9) and re-run restore. 

[eddynfs]

@P_Kesavan thanks for you advice.

I was able to execute the restore now.

When you told me about the FILESTREAM option on the Target Host, I asked for DBA to verify this option in the TARGET HOST. The FILESTREAM was disabled.

When the DBA enable this option, I tray again the restore and the restore job finished with status 0.

Once again, a Thank you for your assistance.

And thank for everyone. This case can be closed now.