Abstract: A computer-implemented method for efficiently backing up large datasets may include (i) identifying data on an application server to be deduplicated by a deduplication server and then stored on a backup server, (ii) dividing the data into subsets, and (iii) for each subset of data subsequent to an initial subset of data, (a) transferring the subset of data to the deduplication server in response to detecting that a previous subset of data has completed transfer to the deduplication server, (b) deduplicating the subset of data in response to detecting that the previous subset of data has completed deduplication, and (c) transferring a deduplicated version of the subset of data to the backup server in response to detecting that the subset of data has completed deduplication and the previous subset of data has completed transfer to the backup server. Various other methods, systems, and computer-readable media are also disclosed.

Abstract: Methods, computer program products, computer systems, and the like for improved performance, when backing up objects, are disclosed, which can include assigning a top-level entity to a backup host of a number of backup hosts and performing a backup operation on a number of objects. The objects are associated with the top-level entity. The backup operation is performed by the backup host. The backup operation includes determining whether one of the objects includes at least one new data segment or at least one modified data segment, and, in response to a determination that the object includes at least one new data segment or at least one modified data segment, writing information regarding the at least one new data segment or at least one modified data segment in a tracklog dedicated to the top-level entity.

Abstract: The disclosed computer-implemented method for backing-up an eventually-consistent database in a production cluster may include (1) forming, on a production node, a stable copy of production data, (2) provisioning storage on a backup node based on an amount of data in the stable copy and a replication factor, (3) transferring information from the stable copy to a backup copy on the backup node, (4) performing record synthesis on the backup copy to merge record updates into complete backup records, (5) identifying and discarding any stale records and any redundant records in the complete backup records, and (6) transferring the complete backup records from the backup node to a cloud storage device. Various other methods, systems, and computer-readable media are also disclosed.

Abstract: Disclosed are techniques that provide for eventually-complete backups, and restoration thereof. For example, such methods, computer program products, and computer systems can include initiating a backup operation (where the backup operation is configured back up a dataset), detecting termination of the backup operation, detecting termination of the backup operation, and determining whether the backup operation backed up the dataset completely. In response to a determination that the backup operation did not backup the dataset completely, generating an indication that the backup is not complete. In response to a determination that the backup operation did not backup the dataset completely, generating an indication that the backup is complete.

Abstract: Disclosed are techniques that provide for eventually-complete backups, and restoration thereof. For example, such methods, computer program products, and computer systems can include initiating a backup operation (where the backup operation is configured back up a dataset), detecting termination of the backup operation, detecting termination of the backup operation, and determining whether the backup operation backed up the dataset completely. In response to a determination that the backup operation did not backup the dataset completely, generating an indication that the backup is not complete. In response to a determination that the backup operation did not backup the dataset completely, generating an indication that the backup is complete.

Abstract: Disclosed herein are systems, methods, and processes to optimize the storage of pre-allocated units of storage during a backup operation. Null units of storage are identified in pre-allocated units of storage prior to the backup operation. Upon being identified, the null units of storage are inhibited from being written to a backup image during the backup operation.

Abstract: The disclosed computer-implemented method for agentless and accelerated backup of a database may include, receiving, by a data backup device from a data server, blocks of data that provide a full backup of data of the data server. The method additionally includes receiving, by the data backup device from the data server, one or more native logs indicating one or more transactions performed by the data server. The method also includes determining, by the data backup device and based on the native logs, one or more changed blocks of the blocks of data. The method further includes providing, by the data backup device, a point in time restore of the data server by creating a synthetic full backup that overlays one or more of the blocks of data with the one or more changed blocks, and that shares remaining blocks of the blocks of data with the full backup.

Abstract: The disclosed computer-implemented method for marking application-consistent points-in-time may include intercepting, by an I/O filter, a write request from a guest virtual machine to a virtual machine disk and queueing the write request in an I/O filter queue. The method may include sending the write request to the virtual machine disk and receiving a write completion message from the virtual machine disk. The method may also include sending, in response to the write completion message, the write request to an I/O daemon, and queueing the write request in an I/O daemon queue. The method may further include sending the write completion message to the guest virtual machine, and sending the write request to a backup gateway such that the backup gateway mimics writes to the virtual machine disk. Various other methods, systems, and computer-readable media are also disclosed.

Abstract: Various systems, methods, and processes for optimizing access to production data in application development and testing environments are disclosed. If an input/output (I/O) operation is a read operation, a storage location on a virtual storage unit at which the read operation is to be performed is determined. Also determined is whether an earlier write operation was performed at the storage location. If an earlier write operation was performed at the storage location, the read operation is performed on one or more virtual data files. However, if the earlier write operation was not performed at the storage location, the read operation is performed on allocated storage space.

Abstract: The disclosed computer-implemented method for agentless and accelerated backup of a database may include, receiving, by a data backup device from a data server, blocks of data that provide a full backup of data of the data server. The method additionally includes receiving, by the data backup device from the data server, one or more native logs indicating one or more transactions performed by the data server. The method also includes determining, by the data backup device and based on the native logs, one or more changed blocks of the blocks of data. The method further includes providing, by the data backup device, a point in time restore of the data server by creating a synthetic full backup that overlays one or more of the blocks of data with the one or more changed blocks, and that shares remaining blocks of the blocks of data with the full backup.

Abstract: A computer-implemented method for efficiently backing up large datasets may include (i) identifying data on an application server to be deduplicated by a deduplication server and then stored on a backup server, (ii) dividing the data into subsets, and (iii) for each subset of data subsequent to an initial subset of data, (a) transferring the subset of data to the deduplication server in response to detecting that a previous subset of data has completed transfer to the deduplication server, (b) deduplicating the subset of data in response to detecting that the previous subset of data has completed deduplication, and (c) transferring a deduplicated version of the subset of data to the backup server in response to detecting that the subset of data has completed deduplication and the previous subset of data has completed transfer to the backup server. Various other methods, systems, and computer-readable media are also disclosed.

Abstract: The disclosed computer-implemented method for marking application-consistent points-in-time may include intercepting, by an I/O filter, a write request from a guest virtual machine to a virtual machine disk and queueing the write request in an I/O filter queue. The method may include sending the write request to the virtual machine disk and receiving a write completion message from the virtual machine disk. The method may also include sending, in response to the write completion message, the write request to an I/O daemon, and queueing the write request in an I/O daemon queue. The method may further include sending the write completion message to the guest virtual machine, and sending the write request to a backup gateway such that the backup gateway mimics writes to the virtual machine disk. Various other methods, systems, and computer-readable media are also disclosed.

Abstract: The disclosed computer-implemented method for performing a database backup for repairless restore may include (1) receiving replica data records representing copies of a database from each of a group of data storage nodes in a production cluster, (2) processing the replica data records in parallel without inter-node communication between the data storage nodes, (3) merging updates to the replica data records, (4) identifying stale or redundant data records in the updated replica data records, (5) discarding the stale or redundant data records from the updated replica data records to create a single copy of updated data records, and (6) restoring the copy of the updated data records to the production cluster by replicating the updated data records to the data storage nodes such that each of the updated data records is consistent thereby obviating subsequent repair. Various other methods, systems, and computer-readable media are also disclosed.

Abstract: The disclosed computer-implemented method for backing-up an eventually-consistent database in a production cluster may include (1) forming, on a production node, a stable copy of production data, (2) provisioning storage on a backup node based on an amount of data in the stable copy and a replication factor, (3) transferring information from the stable copy to a backup copy on the backup node, (4) performing record synthesis on the backup copy to merge record updates into complete backup records, (5) identifying and discarding any stale records and any redundant records in the complete backup records, and (6) transferring the complete backup records from the backup node to a cloud storage device. Various other methods, systems, and computer-readable media are also disclosed.

Abstract: Various systems, methods, and processes for optimizing access to production data in application development and testing environments are disclosed. If an input/output (I/O) operation is a read operation, a storage location on a virtual storage unit at which the read operation is to be performed is determined. Also determined is whether an earlier write operation was performed at the storage location. If an earlier write operation was performed at the storage location, the read operation is performed on one or more virtual data files. However, if the earlier write operation was not performed at the storage location, the read operation is performed on allocated storage space.

Abstract: Various systems, methods, and processes for optimizing access to production data in application development and testing environments are disclosed. If an input/output (I/O) operation is a read operation, a storage location on a virtual storage unit at which the read operation is to be performed is determined. Also determined is whether an earlier write operation was performed at the storage location. If an earlier write operation was performed at the storage location, the read operation is performed on one or more virtual data files. However, if the earlier write operation was not performed at the storage location, the read operation is performed on allocated storage space.

Abstract: A system and method having accelerated data recovery in a clustered storage system is provided. The method may include generating an extent map of data having an original order, wherein the extent map associates the original order with a stored order of the data in a plurality of storage units coupled to a server node. After receipt of a request for data recovery of a subset of data, the method may further include optimizing data retrieval of the data to a minimum recovery time using the extent map. For static optimization, the server node can generate a second map indicating the stored order of each fragment of data to be sent prior to the data. Alternatively in dynamic optimization, the server node can send a qualifying identifier with each fragment indicating the storage location. Thereby, the client node is enabled to rearrange the data upon receipt to its original order.

Abstract: Various systems, methods, and processes for accelerating data access in application and testing environments are disclosed. A production dataset is received from a storage system, and cached in a consolidated cache. The consolidated cache is implemented by an accelerator virtual machine. A file system client intercepts a request for the production dataset from one or more application virtual machines, and transmits the request to the accelerator virtual machine. The accelerator virtual machine serves the production dataset to the one or more application virtual machines from the consolidated cache.

Abstract: The disclosed computer-implemented method for backing-up an eventually-consistent database in a production cluster may include (1) forming, on a production node, a stable copy of production data, (2) provisioning storage on a backup node based on an amount of data in the stable copy and a replication factor, (3) transferring information from the stable copy to a backup copy on the backup node, (4) performing record synthesis on the backup copy to merge record updates into complete backup records, (5) identifying and discarding any stale records and any redundant records in the complete backup records, and (6) transferring the complete backup records from the backup node to a cloud storage device. Various other methods, systems, and computer-readable media are also disclosed.

Abstract: The disclosed computer-implemented method for performing a database backup for repairless restore may include (1) receiving replica data records representing copies of a database from each of a group of data storage nodes in a production cluster, (2) processing the replica data records in parallel without inter-node communication between the data storage nodes, (3) merging updates to the replica data records, (4) identifying stale or redundant data records in the updated replica data records, (5) discarding the stale or redundant data records from the updated replica data records to create a single copy of updated data records, and (6) restoring the copy of the updated data records to the production cluster by replicating the updated data records to the data storage nodes such that each of the updated data records is consistent thereby obviating subsequent repair. Various other methods, systems, and computer-readable media are also disclosed.