While you don't need to configure anything else in your binarystore.xml, this is what the cluster-azure-blob-storage template looks like under the hood:
<config version="2"> <chain template="cluster-azure-blob-storage"/> <provider id="cache-fs-eventual-azure-blob-storage" type="cache-fs"> <provider id="sharding-cluster-eventual-azure-blob-storage" type="sharding-cluster"> <sub-provider id="eventual-cluster-azure-blob-storage" type="eventual-cluster"> <provider id="retry-azure-blob-storage" type="retry"> <provider id="azure-blob-storage" type="azure-blob-storage"/> </provider> </sub-provider> <dynamic-provider id="remote-azure-blob-storage" type="remote"/> </provider> </provider> <!-- cluster eventual Azure Blob Storage Service default chain --> <provider id="sharding-cluster-eventual-azure-blob-storage" type="sharding-cluster"> <readBehavior>crossNetworkStrategy</readBehavior> <writeBehavior>crossNetworkStrategy</writeBehavior> <redundancy>2</redundancy> <lenientLimit>1</lenientLimit> <property name="zones" value="local,remote"/> </provider> <provider id="remote-azure-blob-storage" type="remote"> <zone>remote</zone> </provider> <provider id="eventual-cluster-azure-blob-storage" type="eventual-cluster"> <zone>local</zone> </provider> <!--cluster eventual template--> <provider id="azure-blob-storage" type="azure-blob-storage"> <accountName>XXXXXX</accountName> <accountKey>XXXXXX</accountKey> <endpoint>https://<ACCOUNT_NAME>.blob.core.windows.net/</endpoint> <containerName><NAME></containerName> </provider> </config>
For details about the cache-fs provider, see Cached Filesystem Binary Provider.
For details about the eventual provider, see Eventual Binary Provider.
For details about the retry provider, see Retry Binary Provider.
For details about the remote binary provider, see Remote Binary Provider.
For details about the sharding-cluster, see Sharding-Cluster Binary Provider.