SharePoint environments in either datacenter can access storage containers in both Azure regions. Since version integrity protection is built into SharePoint's architecture, previous versions of the file contents can be retrieved, depending on individual administrator settings. This process ensures that files can't be changed or corrupted after an initial save, protecting against attackers that try to corrupt old versions. ![]() This means that Microsoft can only add new blobs and can never change old ones until they're permanently deleted. See the Azure Storage redundancy article for details. ![]() Within each region, Azure Locally Redundant Storage (LRS) provides a high level of reliability. This same technique is used in all workflows to prevent propagation of any corruption that should occur. After the contents are written into Azure Storage, checksums are stored separately with metadata, and are used to ensure that the committed write is identical to the original file sent to SharePoint during all future reads. If writes to either Azure region fail, the file save will fail. Every file is simultaneously written into both a primary and a secondary datacenter region. SharePoint has a custom-built solution for storage of customer data in Azure Storage. The complete set of controls to ensure data resiliency is explained in further sections. SharePoint has built a custom resiliency plan on top of Azure Storage to ensure near real-time duplication of user content and a truly active/active system. ![]()
0 Comments
Leave a Reply. |