How to implement big data storage in SharePoint2010 (four-step completion of the RBS solution)

The first step, open the database FileStream support

The actual environment is Sharepoint2010 and SQL Server2008 R2; When the database is installed by default, FileStream may not be turned on, we need to verify that it is turned on. Open SQL Configuration Manager as shown in

After you turn on FileStream, execute the following statements in the database

EXEC sp_configure filestream_access_level, 2
RECONFIGURE

Second, configure the content database and file system mapping

Use [wss_content]
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]
If not exists (select GroupName from sysfilegroups where
Groupname=n ' Rbsfilestreamprovider ') ALTER DATABASE [WSS_Content]
Add Filegroup Rbsfilestreamprovider contains FileStream

Use [WSS_Content]
ALTER DATABASE [wss_content] Add file (name = Rbsfilestreamfile,
filename = ' C:\SharePointData\FileData ') to filegroup Rbsfilestreamprovider

where [WSS_Content] is the name of your SharePoint content database, ' C:\SharePointData\FileData ' is the location where the blob file needs to be stored.

Third, install the RBS provider

Copy the Rbs_x64.msi to each server in the farm (if there are multiple servers), run CMD as an administrator, locate the command prompt line path to the installation file directory, and run the following code.

msiexec/qn/lvx* rbs_install_log.txt/i rbs_x64.msi trustservercertificate=true filegroup=primary DBNAME= "WSS_ Content"dbinstance="sp2010"Filestreamfilegroup=rbsfilestreamprovider filestreamstorename= Filestreamprovider_1

Where wss_content is the content database name and sp2010 is the database instance name.

It is not recommended to run the Install RBS provider (RBS_X64.MSI) directly, because if you run this program directly, the program installs a 30-day execution plan, so it is recommended to install it using the prompt line above.

If only one server is installed, if you have more than one server, you must install this provider on each server, but the installation code is different, as follows:

msiexec/qn/lvx* rbs_install_log.txt/i rbs_x64.msi dbname= "wss_content" dbinstance= "sp2010" DDLOCAL= "Client,Docs, Maintainer,serverscript,filestreamclient,filestreamserver "

After the installation has completed, you can check the content database for more than "mssqlrbs" table, if there is a description of successful installation, if not, you need to uninstall rbs_x64, re-perform the above steps.

Iv. enabling RBS for content databases

Start the SharePoint shell

Run the following code:

(1) $cdb = get-spcontentdatabase "WSS_Content"
Gets the instance of the specified content database (SPContentDatabase) object, the "WSS_Content" marked in green You need to change the actual content database name in your environment.
(2) $RBSS = $cdb. Remoteblobstoragesettings
Gets an instance of the RBS settings (spremoteblobstoragesettings) object for the content database.
(3) $rbss. Installed ()
Checks if RBS is installed on the content database and, if necessary, updates the corresponding property values.
(4) $rbss. The Enable ()
enables RBS on the content database.
(5) $pvdName = $rbss. Getprovidernames () [0]
Gets the name of the first RBS provider registered on the content database.
(6) $rbss. Setactiveprovidername ($pvdName)
Sets the RBS Provider to be activated for the content database.

You can then perform a "$RBSS" to see some of its property values, and if set correctly, its output should look like the following.
If you have a site collection enabled in the content database for RBS FILESTREAM provider, after you enable RBS provider, the documents inside the site collection are not automatically transferred to the NTFS file system immediately via FILESTREAM. Only new documents will be stored on the NTFS file system, and documents previously uploaded within the site collection will still be saved in the content database. If you want to dump all of those old documents into the NTFS file system that we specify, you can continue to execute the following command in the SharePoint Management Shell:
(7) $rbss. Migrate ()
If you want to set a document size threshold that only documents larger than this threshold will be stored on the NTFS file system via RBS FILESTREAM provider, and documents smaller than this threshold are still stored in the content database, you can do so in the SharePoint The following instruction continues in the 2010Management shell (assuming a threshold value of 1048000 bytes, or 1M):
(8) $rbss. Minimumblobstoragesize = 1048000

(9) $rbss. Update ()

After the above steps are successful, you can upload a document in the document library that exceeds 100KB (if a threshold is set, upload a size that exceeds the threshold), and then check to see if there are any newly added files in the C:\SharePointData\FileData.

How to implement big data storage in SharePoint2010 (four-step completion of the RBS solution)