Please help us by completing this surveyGo to survey
By default sensenet stores binaries (files) in its SQL database. If you want to store binaries in an external Blob provider instead of the main Content Repository database, we offer a feature for our Enterprise customers that can store binaries in Azure Blob Storage so that operators have more flexibility when installing and maintaining sensenet. We deliver our Enterprise customer an Enterprise Azure Blob Package that contains all the binaries needed to make it work.
Azure Blob Storage is a great choice for Enterprise solutions as binary storage. It is reliable and easy to adapt to.
You should follow the instructions below to install and maintain this enterprise feature.
We tested this component with Microsoft’s WindowsAzure.Storage v8.1.1 client library. You can learn more of Azure Blob Storage at the Azure Blob Storage home page.
You need to change the configuration file for your content repository and for tools as well in order to use Azure for blob storage.
For a first step, check the components. The following files must be copied from your Enterprise Azure Blob package into [yourwebsite]\bin and [yourwebsite]\tools:
It is important that you keep all the configurations in sync for the different components in sensenet - otherwise you won’t be able to save or read binaries correctly.
The following file is affected: web.config To configure the Repository, you must do: Configure the connectionstring.
<connectionStrings> <add name="SenseNet.AzureBlobStorage" connectionString="DefaultEndpointsProtocol=https;AccountName=[azure account name];AccountKey=[azure account key];EndpointSuffix=core.windows.net" /> ...
Configure the blob provider:
<sensenet> <blobStorage> <add key="BlobProvider" value="SenseNet.AzureBlobStorage.AzureBlobProvider" /> <add key="MinimumSizeForBlobProviderKB" value="1" /> </blobStorage> ...
Configure the tools if you use them. Modify all relevant configurations in the tools directory. The tool is relevant if the it reads or writes any repository content. The following files are affected: Import.exe.config, Export.exe.config, SyncPortal2AD.exe.config, SnAdminRuntime.exe.config. On each tool configuration file you must do as it was bid in the previous section.
If you intend to implement a backup policy, you can do it easily with the use of asynchronous copy blob, that is a built-in feature of Azure:
Currently there is no migration tool that moves existing binaries from the SQL database to Azure Blob Storage. However after you install this provider, the system will save new files to it and old files will also be moved as you save them.
Is something missing? See something that needs fixing? Propose a change here.