In some embodiments, a computer system may buffer, in a local storage buffer, data to be stored at the cloud and upload the data to the cloud storage from the local storage buffer. Upon receipt of an acknowledgement, from the cloud storage, that the data was successfully uploaded, the computer system may delete the data from the local storage buffer. The computer system may provide a ghost file representation of the uploaded data through the computer system, through which the data uploaded to the cloud storage may be accessed. In some embodiments, the computer system may access multiple cloud storage accounts, each corresponding to a file folder on the computer system, allowing the user to easily access different cloud storage accounts. The computer system may recover data that was deleted from either local persistent storage or the cloud storage.

In some embodiments, a computer system may buffer, in a local storage buffer, data to be stored at the cloud and upload the data to the cloud storage from the local storage buffer. Upon receipt of an acknowledgement, from the cloud storage, that the data was successfully uploaded, the computer system may delete the data from the local storage buffer. The computer system may provide a ghost file representation of the uploaded data through the computer system, through which the data uploaded to the cloud storage may be accessed. In some embodiments, the computer system may access multiple cloud storage accounts, each corresponding to a file folder on the computer system, allowing the user to easily access different cloud storage accounts. The computer system may recover data that was deleted from either local persistent storage or the cloud storage.

The present invention provides systems and methods for data storage. A hierarchical storage management architecture is presented to facilitate data management. The disclosed system provides methods for evaluating the state of stored data relative to enterprise needs by using weighted parameters that may be user defined. Also disclosed are systems and methods evaluating costing and risk management associated with stored data.

A method includes determining a length of a file and storing the length of the file in a first memory location. An endpoint of a last complete record within the file is determined and the endpoint is stored in a second memory location. The length of the file stored in the first memory location is compared to a current length of the file, and a data structure associated with the file is updated beginning at the endpoint if the current length of the file exceeds the length of the file stored in the first memory location.

A method and system for executing database queries in parallel using a shared metadata store. The metadata store may reside on a master node, where the master node is the root node in a tree. The master node may distribute query plans and query metadata to other nodes in the cluster. These additional nodes may request additional metadata from each other or the master nodes as necessary.

The present disclosure provides a file delivery method. The file delivery method includes receiving a task request for a file delivery task sent by a target node to request a file; determining according to the task request whether there are completed nodes, the completed nodes being other target nodes that have completed a file delivery task delivering the file; designating, if there are completed nodes, a node from the completed nodes as a source station corresponding to the task request; designating, if there are no completed nodes, a source server as the source station corresponding to the task request; and delivering the file to the target node through the designated source station.

A data management services architecture includes architectural components that run in both a storage and compute domains. The architectural components redirect storage requests from the storage domain to the compute domain, manage resources allocated from the compute domain, ensure compliance with a policy that governs resource consumption, deploy program code for data management services, dispatch service requests to deployed services, and monitor deployed services. The architectural components also include a service map to locate program code for data management services, and service instance information for monitoring deployed services and dispatching requests to deployed services. Since deployed services can be stateless or stateful, the services architecture also includes state data for the stateful services, with supporting resources that can expand or contract based on policy and/or service demand. The architectural components also include containers for the deployed services.

A data management services architecture includes architectural components that run in both a storage and compute domains. The architectural components redirect storage requests from the storage domain to the compute domain, manage resources allocated from the compute domain, ensure compliance with a policy that governs resource consumption, deploy program code for data management services, dispatch service requests to deployed services, and monitor deployed services. The architectural components also include a service map to locate program code for data management services, and service instance information for monitoring deployed services and dispatching requests to deployed services. Since deployed services can be stateless or stateful, the services architecture also includes state data for the stateful services, with supporting resources that can expand or contract based on policy and/or service demand. The architectural components also include containers for the deployed services.

A server system, based on content of a first file stored on a first client device being modified, automatically receives a copy of the modified first file from a first transfer client, implemented on the first client device, the copy of the modified first file being an updated version of the first file generated from content of the first file being modified. The server system receives, from the first transfer client, first metadata associated with the updated version of the first file, the first metadata being assigned a first priority greater than a second priority assigned to the copy of the modified first file. The server system automatically transfers the first metadata to a second transfer client, implemented on a second client device, before the copy of the modified first file is transferred to the second transfer client to be stored on the second client device.

A server system, based on content of a first file stored on a first client device being modified, automatically receives a copy of the modified first file from a first transfer client, implemented on the first client device, the copy of the modified first file being an updated version of the first file generated from content of the first file being modified. The server system receives, from the first transfer client, first metadata associated with the updated version of the first file, the first metadata being assigned a first priority greater than a second priority assigned to the copy of the modified first file. The server system automatically transfers the first metadata to a second transfer client, implemented on a second client device, before the copy of the modified first file is transferred to the second transfer client to be stored on the second client device.