Abstract: Implementations are provided herein for establishing multi-protocol redirection links that are associated with an object, a file, a set of files, directories, etc. The multi-protocol redirection link can transparently redirect a client to a different part of the namespace or even to a different storage cluster to access data. For example, using multi-protocol redirection links, a single namespace in a cluster of nodes can be scaled up with multiple secondary storage clusters being the eventual redirect path. A multi-protocol redirection table can be established as a basis for the multi-protocol redirection link. The file system can be aware of discriminative information associated the client, for example, the network protocol the client is using, the access zone the client is connecting to, user identification of the client, group identification of the client, geography of the client, etc.

Abstract: Systems and methods that enable removal of data from an endpoint, while not propagating such removal to other endpoints when synchronizing data sources associated therewith. A designation component can indicate items as forgotten items, wherein such items are being known to an endpoint and deleted therefrom—yet, reintroduced therein and reappearing (e.g., as a create) upon re-synchronizing with the replica over again. Moreover, the forgotten items can employ additional metadata such as in from of an additional bit that indicates whether an item is a forgotten item.

Abstract: Implementations for communicating network configuration and IP changes to protocol heads. An in-memory cache of currently available IP addresses and locations can be maintained via a registration and callback method. The registered protocol head will have its cache updated when the network configuration changes. The protocol head will also receive events indicating specific changes as they occur, and a callback can be registered to act upon certain configuration events. An additional event can be sent to the protocol head indicating intent to move IP addresses from one node to another. The provided information allows the protocol head to make quicker, more informed decisions about IP address states when interacting with its protocol clients. It also allows the protocol head to anticipate IP movement so that it can provide improved availability and fewer disruptions for its protocol clients, improving the continuous availability experience.

Abstract: Systems and methods that enable removal of data from an endpoint, while not propagating such removal to other endpoints when synchronizing data sources associated therewith. A designation component can indicate items as forgotten items, wherein such items are being known to an endpoint and deleted therefrom—yet, reintroduced therein and reappearing (e.g., as a create) upon re-synchronizing with the replica over again. Moreover, the forgotten items can employ additional metadata such as in from of an additional bit that indicates whether an item is a forgotten item.

Abstract: The subject disclosure relates to an efficient multi-master synchronization infrastructure is provided enabling loosely coupled networked client and server devices, applications and services to efficiently convey and receive synchronization knowledge across interconnecting network(s). A set of synchronization methods and standardized interfaces are also provided that enable rich offline application experiences and collaboration among devices, applications and services predicated on the efficient synchronization infrastructure.

Abstract: Embodiments are directed to efficiently routing data requests from a plurality of tenants and to using smart routing to limit service denials. In an embodiment, a gateway node receives data requests from a tenant subscriber requesting data for an indicated service. The gateway node determines which server node the received data requests are to be routed to. The determination evaluates various criteria associated with the data request. The gateway node queries the determined server node to determine the health of the server nodes and receives a reply from the determined server node indicating the server node's current operating status. The gateway node also, based on the determined server node's reply, routes the received data requests to the determined server node, according to the evaluated criteria.

Abstract: Systems and methods that enable removal of data from an endpoint, while not propagating such removal to other endpoints when synchronizing data sources associated therewith. A designation component can indicate items as forgotten items, wherein such items are being known to an endpoint and deleted therefrom—yet, reintroduced therein and reappearing (e.g., as a create) upon re-synchronizing with the replica over again. Moreover, the forgotten items can employ additional metadata such as in from of an additional bit that indicates whether an item is a forgotten item.

Abstract: An efficient way and general mechanism is provided to represent and exchange knowledge and/or partial knowledge across nodes when synchronizing between any two nodes including custom or move filters where set membership can change over time at a device as data items come in and out of filter scope. A first node sends a second node its knowledge and/or partial knowledge, including objects and versions of those objects. The second node compares its knowledge and/or partial knowledge with the knowledge and/or partial knowledge of the first node, and then sends the first node any latest versions of objects of which the first node is unaware. In addition, the second node sends its knowledge and/or partial knowledge to the first node.

Abstract: Systems and methods that enable removal of data from an endpoint, while not propagating such removal to other endpoints when synchronizing data sources associated therewith. A designation component can indicate items as forgotten items, wherein such items are being known to an endpoint and deleted therefrom—yet, reintroduced therein and reappearing (e.g., as a create) upon re-synchronizing with the replica over again. Moreover, the forgotten items can employ additional metadata such as in from of an additional bit that indicates whether an item is a forgotten item.

Abstract: Embodiments are directed to efficiently routing data requests from a plurality of tenants and to using smart routing to limit service denials. In an embodiment, a gateway node receives data requests from a tenant subscriber requesting data for an indicated service. The gateway node determines which server node the received data requests are to be routed to. The determination evaluates various criteria associated with the data request. The gateway node queries the determined server node to determine the health of the server nodes and receives a reply from the determined server node indicating the server node's current operating status. The gateway node also, based on the determined server node's reply, routes the received data requests to the determined server node, according to the evaluated criteria.

Abstract: An efficient way and general mechanism is provided to represent and exchange knowledge and/or partial knowledge across nodes when synchronizing between any two nodes including custom or move filters where set membership can change over time at a device as data items come in and out of filter scope. A first node sends a second node its knowledge and/or partial knowledge, including objects and versions of those objects. The second node compares its knowledge and/or partial knowledge with the knowledge and/or partial knowledge of the first node, and then sends the first node any latest versions of objects of which the first node is unaware. In addition, the second node sends its knowledge and/or partial knowledge to the first node.

Abstract: A method of synchronizing data between multiple endpoints each storing a copy of the data in accordance with different underlying schemas. An application model that provides a logical representation of an underlying schema is extended with a synchronization model that provides a logical representation of changes made to the data. The synchronization model comprises functions that provide synchronization information on the changes in a common format. Using such synchronization information, changes in a copy of the data stored in a first underlying schema on a first endpoints are applied to another copy of the data stored in a second underlying schema on a second endpoint in synchronization relationship with the first endpoint.

Abstract: Systems and methods that enable removal of data from an endpoint, while not propagating such removal to other endpoints when synchronizing data sources associated therewith. A designation component can indicate items as forgotten items, wherein such items are being known to an endpoint and deleted therefrom—yet, reintroduced therein and reappearing (e.g., as a create) upon re-synchronizing with the replica over again. Moreover, the forgotten items can employ additional metadata such as in from of an additional bit that indicates whether an item is a forgotten item.

Abstract: The subject disclosure relates to an efficient multi-master synchronization infrastructure is provided enabling loosely coupled networked client and server devices, applications and services to efficiently convey and receive synchronization knowledge across interconnecting network(s). A set of synchronization methods and standardized interfaces are also provided that enable rich offline application experiences and collaboration among devices, applications and services predicated on the efficient synchronization infrastructure.