Druva Inc.

A system and a method for client-side deduplication system for a plurality of backup streams, generated by a backup and recovery client from a client database, is presented. The system includes a stream handler configured to generate a unique file name for an underlying file of each backup stream of the plurality of backup streams based on one or more data blocks in each backup stream. The system further includes a file creator configured to create a data file corresponding to each backup stream of the plurality of backup streams in a local cache of a client database server, wherein each data file has a file name corresponding to the unique file name generated by the stream handler. The client-system furthermore includes a dedupe module configured to dedupe subsequent backup streams based on the data files in the local cache.

A cloud-based (CRM) data storage system with query support is provided. The system includes a memory storing processor-executable routines and a processor configured to execute routines to initiate a data backup operation for customers of the system. The processor is configured to receive source data having at least one of data schema, records/CRM data, and blob data and to transform the source data into a columnar storage format to generate converted source data and corresponding index files. Further, versioning data for the source data, converted source data and corresponding index files for each customer are stored. The processor is configured to receive a data query having query parameters from customers and to identify index files and/or data files to be scanned from the converted source data, and to scan the identified index files and/or data files to generate data query results.

A data backup system configured to enable point in time recovery is presented. The data backup system is configured to enable point in time recovery using a full backup storage space and a unique log backup storage space thereby enabling parallel full backups and archive log backups. A related method is also presented.

An incremental backup agent performs backup operations that synchronize database on client side to a server database. In one embodiment, such backup operations are incremental backups, where the agent may identify differences between the current directory with the latest backed up version. The agent may issue a direct RPC using SMB protocols or NFS protocols to fetch all entries of directories with metadata in a single RPC call, instead of issuing one call to fetch metadata for each directory entry. The agent may identify changes with efficiency by performing checksum changes in a DFS manner. Starting from a root directory, the agent may generate a checksum for each directory and compare the checksums on the client side with the retrieved fingerprints, and if the backup agent identifies that the fingerprints match, the backup agent may then go to a deeper level and compare the fingerprints for child directories.

A system for performing root-cause analysis of cost and/or usage anomalies in a shared data protection environment is presented. The shared backup environment includes a backup/restore system configured to backup data in a storage server and/or restore data from the storage server. The system is configured to perform the root-cause analysis based on storage server data and backup/restore system telemetry data.

A system includes a data management server and a data store. The data store uses an external file system to store the data of a client virtual machine (VM) which uses an internal file system. The server comprises an agent VM. Responsive to receiving a request to retrieve a file from a filesystem snapshot, the agent VM determines a path of the internal files system of the client VM and mounts a virtual file system at the agent VM based on the determined path. The virtual file system represents the internal file system of the client virtual machine. The agent VM uses a block device protocol to translate the internal file address to an external file address of the external file system. The agent VM retrieves the file stored in the data store based on the external file address and provides the retrieved file to the target device.

The invention provides a dynamic data-backup scheduling system. The system includes a memory storing one or more processor-executable routines and a processor communicatively coupled to the memory. The processor is configured to execute one or more processor-executable routines to determine a dynamic backup schedule for one or more computing machines based upon data change patterns of the respective computing machines. The processor is further configured to access user inputs corresponding to data backup for the one or more computing machines. The user inputs comprise at least one of a tolerable data loss threshold, critical data type, file sensitivity data, and exceptions data time period information. The processor is further configured to create one or more service level agreement (SLA) configurations for data backup based on the user inputs. The processor is further configured to access historical data corresponding to one or more data backup cycles of the one or more computing machines. The historical data comprises one or more of time series changes, the addition and/or change of data information for pre-determined data sets, and corresponding file metadata of the data sets. The processor is further configured to implement one of the active and passive modes of data backup using the user inputs and the historical data. The processor is further configured to trigger a backup job for one or more computing machines based on a comparison between the SLA configurations and dynamic information received about data addition and/or data change of the computing machines in the active mode. The processor is further configured to trigger a backup job for one or more computing machines based on a comparison between the SLA configurations and historical time series change and/or addition of data of the computing machines in the passive mode.

The invention provides a dynamic data-backup scheduling system. The system includes a memory storing one or more processor-executable routines and a processor communicatively coupled to the memory. The processor is configured to execute one or more processor-executable routines to determine a dynamic backup schedule for one or more computing machines based upon data change patterns of the respective computing machines. The processor is further configured to access user inputs corresponding to data backup for the one or more computing machines. The user inputs comprise at least one of a tolerable data loss threshold, critical data type, file sensitivity data, and exceptions data time period information. The processor is further configured to create one or more service level agreement (SLA) configurations for data backup based on the user inputs. The processor is further configured to access historical data corresponding to one or more data backup cycles of the one or more computing machines. The historical data comprises one or more of time series changes, the addition and/or change of data information for pre-determined data sets, and corresponding file metadata of the data sets. The processor is further configured to implement one of the active and passive modes of data backup using the user inputs and the historical data. The processor is further configured to trigger a backup job for one or more computing machines based on a comparison between the SLA configurations and dynamic information received about data addition and/or data change of the computing machines in the active mode. The processor is further configured to trigger a backup job for one or more computing machines based on a comparison between the SLA configurations and historical time series change and/or addition of data of the computing machines in the passive mode.

A system includes a duplicative data store different from a cloud storage. The data store stores duplicative copies of data that are used by one or more virtual machines. The system receives a request to retrieve from the cloud storage data associated with a VM. The cloud storage is configured to store data in a first chunk granularity larger than a second chunk granularity of the duplicative data store. The system determines whether a duplicative copy of the requested data is stored in the data store, and responsive to determining the duplicative copy of the requested data is stored in the data store, the system retrieves the duplicative copy of requested data from the data store. The system bypasses a retrieval of the chunk from the cloud storage, and provides the duplicative copy as a response to the request.

The present invention discloses a file storage system including an object storage for storing data blocks for a client, a merge index database to store metadata corresponding to the stored data blocks using a merge index, a cloudcache located on a premise of the client, and a cloudcache implementation module communicatively coupled to the object storage, the cloudcache and the merge index database. The cloudcache implementation module facilitates data backup and restore operations for the client in accordance with a data retention policy, where one or more data blocks are stored on the cloudcache and a sync operation is performed between the cloudcache and the object storage. A backup of the data blocks is performed to the cloudcache in a backup operation, data blocks are compacted, and a restore operation for data blocks stored on the cloudcache are performed in accordance with the data retention policy.