Abstract: In some examples, a first computing device may receive, from a second computing device, partition mapping information indicating partitions of a metadata database. The first computing device may be able to communicate with a plurality of metadata nodes, each metadata node maintaining a portion of the metadata database based on the partitioning of the metadata database to distribute the metadata database across the plurality of metadata nodes. The first computing device may determine to send a request to the metadata database based at least on key information. The first computing device may determine, based on the partition mapping information, a first metadata node of the plurality of metadata nodes indicated to maintain a partition of the metadata database corresponding to the key information. The first computing device, may send, to the first metadata node, based on the partition mapping information, a request to perform a database operation.

Abstract: In some examples, a system may receive, from a user device, a user request for a storage operation related to storage of data at a storage. An update may be added to an update queue to persist the storage operation prior to sending a response to the user device indicating performance of the storage operation. For instance, adding the update to the update queue may include sending a request to cause the update to be added to the update queue based on specifying a type of the storage operation and/or a state to be achieved by the storage operation. Additionally, information about the update may be sent to another processor for adding the update to another update queue managed by the other processor. Subsequently, the update may be obtained from the update queue and processed to perform the storage operation.

Abstract: In some examples, a first computing device may receive, from a second computing device, partition mapping information indicating partitions of a metadata database. The first computing device may be able to communicate with a plurality of metadata nodes, each metadata node maintaining a portion of the metadata database based on the partitioning of the metadata database to distribute the metadata database across the plurality of metadata nodes. The first computing device may determine to send a request to the metadata database based at least on key information. The first computing device may determine, based on the partition mapping information, a first metadata node of the plurality of metadata nodes indicated to maintain a partition of the metadata database corresponding to the key information. The first computing device, may send, to the first metadata node, based on the partition mapping information, a request to perform a database operation.

Abstract: In some examples, a first computing device associated with a first site may receive a certificate of a second computing device associated with a second site that is different from the first site. The first computing device may send, to the second computing device, a credential of a user associated with the second site. In addition, the first computing device may send to the second computing device, a certificate of the first computing device. Furthermore, based at least on authentication of the credential of the user by the second computing device, trusted communications may be established between the first computing device and the second computing device.

Abstract: In some examples, a computer system may receiving a request to allow a second user associated with a second user account to access at least one of a folder or a link associated with a first user account of a first user. The computer system may determine a first profile associated with the first user account, and may further determine whether sharing whitelisting is enabled for the first profile. Additionally, the computer system may determine a second profile associated with the second user account, and may determine whether the second profile is included in a sharing whitelist of the first profile. When sharing whitelisting is enabled for the first profile, the computer system may allow a client device associated with the second user account to access the folder and/or the link when the second profile is included in the sharing whitelist of the first profile.

Abstract: In some examples, a system may receive, from a first user, a request to create a team folder from a folder associated with the first user. The request may indicate a requested storage quota from a team folder storage pool to associate with the team folder. The system may determine whether the requested storage quota is below a threshold amount corresponding to a profile for team folder creation associated with the first user. If the requested storage quota is below the threshold amount, the system may automatically create a shared file system for the team folder and allocate a quantity of storage from the team folder storage pool to the shared file system based on the requested storage quota. Alternatively, if the requested storage quota exceeds the threshold amount, the system may generate a communication to an administrator to request approval for creation of the team folder.

Abstract: In some examples, a plurality of nodes may each host a respective logical database (LDB) that includes database data that references external resources stored in a storage system. Further, each node may maintain, for each external resource referenced by the respective LDB on that node, a reference count of a number of references in the respective LDB to each external resource and a timestamp associated with the reference count. In response to addition of a reference to a particular external resource in a particular LDB, a node that hosts the particular LDB may be programmed to increment the reference count and update the timestamp for the particular external resource. Similarly, in response to removal of the reference to the particular external resource in the particular LDB, the node hosting the particular LDB is programmed to decrement the reference count and update the timestamp for the particular external resource.

Abstract: In some examples, a computer system may receiving a request to allow a second user associated with a second user account to access at least one of a folder or a link associated with a first user account of a first user. The computer system may determine a first profile associated with the first user account, and may further determine whether sharing whitelisting is enabled for the first profile. Additionally, the computer system may determine a second profile associated with the second user account, and may determine whether the second profile is included in a sharing whitelist of the first profile. When sharing whitelisting is enabled for the first profile, the computer system may allow a client device associated with the second user account to access the folder and/or the link when the second profile is included in the sharing whitelist of the first profile.

Abstract: In some examples, a system may receive, from a first user, a request to create a team folder from a folder associated with the first user. The request may indicate a requested storage quota from a team folder storage pool to associate with the team folder. The system may determine whether the requested storage quota is below a threshold amount corresponding to a profile for team folder creation associated with the first user. If the requested storage quota is below the threshold amount, the system may automatically create a shared file system for the team folder and allocate a quantity of storage from the team folder storage pool to the shared file system based on the requested storage quota. Alternatively, if the requested storage quota exceeds the threshold amount, the system may generate a communication to an administrator to request approval for creation of the team folder.

Abstract: In some examples, a plurality of nodes may each host a respective logical database (LDB) that includes database data that references external resources stored in a storage system. Further, each node may maintain, for each external resource referenced by the respective LDB on that node, a reference count of a number of references in the respective LDB to each external resource and a timestamp associated with the reference count. In response to addition of a reference to a particular external resource in a particular LDB, a node that hosts the particular LDB may be programmed to increment the reference count and update the timestamp for the particular external resource. Similarly, in response to removal of the reference to the particular external resource in the particular LDB, the node hosting the particular LDB is programmed to decrement the reference count and update the timestamp for the particular external resource.