Unsolved
This post is more than 5 years old
2 Posts
0
2317
February 11th, 2016 05:00
Database 'SomethingSomething' is using FILESTREAM functionality and cannot be backed up.
Hi,
We are using Networker 8.1.1.5. And we have an issue where database on SQL Server is not getting backed up.
The message NW posts is something like:
* Server.Domain:MSSQL:DatabaseName 4690:(pid 14580):SQL Server FILESTREAM support is not enabled for this instance. Database 'DatabaseName' is using FILESTREAM functionality and cannot be backed up.
* Server.Domain:MSSQL:DatabaseName 29211:(pid 14580):At least 1 valid backup target is required
* Server.Domain:MSSQL:DatabaseName 43709:(pid 14580):Stop time: Wed Feb 10 22:03:38 2016
* Server.Domain:MSSQL:DatabaseName
On server we have enabled FS ( http://content.screencast.com/users/R083RT/folders/Jing/media/aeee1558-56b6-4f5f-ace8-e9eab8f427b7/2016-02-11_1434.png )
Is there any other special setting that has to be enabled for this thing to work?
P.S.
I have also checked the user rights and he has SA, so this should also cover it.
Thanks in advance



ble1
4 Operator
•
14.3K Posts
0
February 11th, 2016 14:00
Did you check https://support.emc.com/kb/110952
Justsomeguy2
2 Posts
0
February 11th, 2016 23:00
Is there any cance to get answer from an accessible or any other readable page?
When I click on that link I get "Access Denied"
I hope this is not some kind of an "top secret" issue ...
BR
CarlosRojas
1.7K Posts
0
February 11th, 2016 23:00
Hi Justsomeguy
It is documented as a pre-requisite:
When backing up filestream data, select the Allow Remote Clients Access to Filestream Data option in the Properties page of the SQL Server instance in the SQL Server Configuration Manager. This is a requirement for the backups to be successful. The SQL Server documentation provides details about the SQL Server Configuration Manager.
So please enable it and give it another try.
Thank you,
Carlos
ble1
4 Operator
•
14.3K Posts
0
February 13th, 2016 13:00
It is not. I'm customer and this is customer level KB. Most likely you or your browser cache are broken