Configuring remote blob storage with SharePoint 2010

I have taken this article from the below URL
 
With Sharepoint 2010, the Remote Blob Storage (RBS) functionality, which allows putting documents into the database filesystem instead of the database itself, came into focus again. To make that happen each content database is located in a specific section of the file system where all the documents are stored. This documents are none the less managed by Sharepoint, a database is mandatory even if the documents are stored as BLOB because metadata is written exclusively into databases.
The following installation routines and steps to activate RBS are based on Technet and the blogs of Jie Li and ToddKlindts.
All the following installations have been done on Microsoft Windows Server 2008 R2 and Microsoft SQL Server 2008 R2 as there is no support for RBS on Microsoft SQL Server 2005.
First of all we have to activate FILESTREAM on the SQL instance that you want to put to the BLOB. 
  1. Connect to SQL Server 
    Start –> All Programs –> Microsoft SQL Server 2008 R2 –> Configuration Tools –> SQL Server Configurations Manager
  2. In the Services list, click “SQL Server Services”
  3. Choose your SQL instance (here “SQL Server (MSSQLSERVER)”) and right click Properties.
  4. Switch to the FILESTREAM tab and check all the available checkboxes
  5. Click Apply –> OK 
    clip_image002
  6. Now start SQL Server Management Studio 
    Start –> All Programs –> Microsoft SQL Server 2008 R2 –>SQL Server Management Studio
  7. Open a query windows and start the following SQL statement clip_image004 
    For easier reference, just copy the text below
    EXEC sp_configure filestream_access_level, 2 
    RECONFIGURE 
This was the first step, FILESTREAM is now successfully activated.
All further steps requires SharePoint to be installed properly and that a WebApplication has already been created. The Content Database in this case I created by Powershell: 
  1. Connect to a Front End Server Start –> Microsoft SharePoint 2010 Products –> SharePoint 2010 Management Shell Create a Content Database clip_image006 
    For easier reference, just copy the text below
    New-SPContentDatabase –name WSS_Content_Blob_001 –WebApplication     http://sp2010 –MaxSiteCount 1 –WarningSiteCount 0
Now the new content database (in this case “WSS_Content_Blob_001”) has to be prepared for use with FILESTREAM.
  1. Connect to your SQL Server 
    Start –> All Programs –> Microsoft SQL Server 2008 R2 –>SQL Server Management Studio
Open a query and execute the statement below. Replace “C:\Blobstore“ by your storage-path. The directory must not exist when executing the statement, otherwise an error will be given. clip_image008 For easier reference, just copy the text below 


use [WSS_Content_Blob_001]

 

if not exists (select * from sys.symmetric_keys where name = N'##MS_DatabaseMasterKey##')create master key encryption by password = N'Admin Key Password !2#4'






 

 
use [WSS_Content_Blob_001] 
if not exists (select groupname from sysfilegroups where groupname=N'RBSFilestreamProvider')alter database [WSS_Content_Blob_001]  add filegroup RBSFilestreamProvider contains filestream


use [WSS_Content_Blob_001] 
alter database [WSS_Content_Blob_001] add file (name = RBSFilestreamFile, filename = 'c:\Blob_001') to filegroup RBSFilestreamProvider


Now the direcory for the Blobstore has been created in “C:\Blob_001”
Next you have to download the EXE for RBS, and it has to be copied to each Web Frontend Server. During all the following steps mind checking the log files for errors. 
  1. Connect to the Web Front End hosting the Central Admin Console
  2. Open a Command Prompt (IMPORTANT -> run with elevated permissions) 
    clip_image010
  3. Change to the directory containing the previously downloaded RBS_X64.exe
  4. Delete or rename a already existing „rbs_install_log.txt“ if applicable.
  5. Run the follwoing command, replace DBNAME with your content database and DBINSTANCE with your SQL instance. Mind that this command only works once, if you want to configure a second database, chose the option “Configure additional database” (see below).
    msiexec /qn /lvx* rbs_install_log.txt /i RBS_X64.msi TRUSTSERVERCERTIFICATE=true FILEGROUP=PRIMARY DBNAME="WSS_Content_Blob_001" DBINSTANCE="DC" FILESTREAMFILEGROUP=RBSFilestreamProvider FILESTREAMSTORENAME=FilestreamProvider_1
  6. After this process has completed (it may take a minute or two, the log reads “Verbose Logging stopped”), check the “rbs_install_log.txt” if it contains the following line of text (it should be approximately 21 lines before the end of the file: 
    "Product: SQL Remote Blob Storage -- Configuration completed successfully" 

    If that is not the case you have an issue. Check the following: 
    - Are you in the right directory 
    - Did you make a typo 
    - Did you run the prompt with elevated privileges
  7. If you have more than one WFE in your farm, you now have to change to the other servers and run the following command: clip_image012 
    For easier reference, just copy the text below 
    msiexec /qn /lvx* rbs_install_log.txt /i RBS_X64.msi DBNAME="WSS_Content_Blob_001" DBINSTANCE="DC" ADDLOCAL="Client,Docs,Maintainer, ,FilestreamClient,FilestreamServer" 
  8. Check the “rbs_install_log.txt” if it contains the following line of text (it should be approximately 21 lines before the end of the file: 
    "Product: SQL Remote Blob Storage -- Configuration completed successfully" 
  9. Execute all steps from step 7 on every additional WFE. This is mandatory, otherwise problems might occur.
The script has created a few tables in the database, check if they are existing: 
  1. Connect to SQL Server 
    Start –> All Programs –> Microsoft SQL Server 2008 R2 –>SQL Server Management Studio
  2. Execute the following query clip_image014 
    For easier reference, just copy the text below 
    use WSS_Content_Blob_001 
    select * from dbo.sysobjects 
    where name like ‘rbs%’     
The result should show the RBS tables. This may take a while.
As one last step you have to tell Sharepoint that the content database uses RBS. To do that you have to execute the following command: 
  1. Connect to WFE 
    Start –> Microsoft SharePoint 2010 Products –> SharePoint 2010 Management Shell
  2. Execute the following commands in sequence: clip_image016
    For easier reference, just copy the text below 
    $cdb = Get-SPContentDatabase WSS_Content_Blob_001 

    $rbss = $cdb.RemoteBlobStorageSettings

    $rbss.Installed()

    $rbss.Enable() 

    $rbss.SetActiveProviderName($rbss.GetProviderNames()[0]) 
    $rbss     
Since all has been prepared we can check the functionality. Just create a site collection and make sure the content database used is “WSS_Content_Blob_001”. (or whatever you chose during install). 
  1. Connect to WFE 
    Start –> Microsoft SharePoint 2010 Products –> SharePoint 2010 Central Administration
  2. Application Management – Manage Content Databases
  3. Choose the applicable Web Application
  4. Configure the Content Database to put the next site collection to “WSS_Content_Blob_001” 
    – If you have multiple databases, set “Maximum Number of Site Collections” to the current value 
    – “WSS_Content_Blob_001” should not contain any site collections
  5. Go back to the main site of  Central Administration
  6. Application Management – Create Site Collection 
    - Enter all the required data 
    - OK
  7. As soon as the site collection creation is finished, all newly uploaded documents should be created in the filesystem.

Notice:

Documents below 100 kB will not be put to the file system but will be stored in the database.

Configure additional content databases:

If you want to configure more than one content database for RBS, all the steps above have to be executed. The only difference is the command in step 5. This one dies not work, and no RBS tables are created. Therefore use the command below:


 
msiexec /qn /i rbs.msi REMOTEBLOBENABLE=1 FILESTREAMPROVIDERENABLE=1 DBNAME=WSS_Content_Blob_002 FILESTREAMSTORENAME=FilestreamProvider_1 ADDLOCAL=EnableRBS,FilestreamRunScript DBINSTANCE=CD 

Comments

Post a Comment

Popular posts from this blog

SharePoint 2016 and 2019 Ports

http://sharepoint2016server.blogspot.com/2016/10/sharepoint-2016-ports-list.html SharePoint 2019: Distributed Cache : TCP Port 22233, 22236 : UDP Port N/A : Protocols ICMP Type 0 (ping) People Picker : TCP Port 53, 88, 135, 137–139, 389, 445, 636, 749, 750, 3268, 3269 : UDP Port N/A 53, 88, 137–139, 389, 445, 749 : UDP Port N/A : Protocols N/A Sandbox Service : TCP Port 32846 : UDP Port N/A : protocols N/A Search Crawler : TCP Port Web Application Ports Used (e.g., 80, 443) : UDP Port N/A : Protocols N/A Search Index : TCP Ports 16500–16519 : UDP Port N/A : Protocols N/A Service Applications : TCP Port 32843, 32844 : UDP Port N/A : Protocols N/A SQL Server : TCP Port 1433 (default) : UDP Port 1434 (default) : Protocols N/A WCF Services : TCP Port 808 : UDP Port N/A : Protocols N/A User Profile Service : TCP Port 53, 88, 389, 5725, 1025–5000, 49152–65536 : UDP Port 53, 88, 389, 464 : Protocols N/A SMTP : TCP Port 25 (default), 587 (TLS default) : UDP Port N/A : Protocols ...
Read more

Clear fields based on drop-down values in PowerApps

Clear current selection from drop down when another drop down value changes 1) Parent drop-down is States 2) Child drop-down is City We can hide and show the City drop-down based on States Value changes NOTE: Please use your DataCardValues and  lv_dpclear is local variable Select City data card and go to the Advanced properties for DataCard Look for the Visible property and write the below code If(DataCardValue3.Selected.Value="VA",true,false) For clearing the City dropdown selected value based state changes. Select the State drop-down (first drop-down) and go to Advanced use the below code in OnChange  UpdateContext({lv_dpclear: true}); UpdateContext({lv_dpclear: false})  In the Reset property of the second dropdown(City), add the below code       lv_dpclear -------------------------------------------------------------------- Clearing text box and Date Control values based on dropdown selection: Add belo...
Read more

Hide a SharePoint list field based on user group using JQuery Webservice in 2010

A field in a SharePoint list form like NewForm.aspx or EditForm.aspx can be easily hidden by using the following Jquery statements. Assume that we have an input field named Feedback var feedbackField = $("input[title=Feedback]"); feedbackField.parent().parent().parent().hide();    But what if we want to hide the field for a particular SharePoint user group only. Let's say we have a user group named "Test Group" and we don't want to show the Feedback field to the users of this group. In order to achieve this we need to know whether the current logged in user belongs to the "Test Group" or not.This can be done by using   SPServices , a Jquery library for SharePoint web services. Grab the latest version of SPServices Jquery library from codeple x and Jquery from here . Once you have both .js files, upload them to a SharePoint document library. In my case I created a folder named JS inside Shared Documents Document library and uploaded both files...
Read more