Abstract: In some embodiments, a method stores domain name system (DNS) resolution mappings from a domain name to an address in a first table. The DNS resolution mappings are intercepted from DNS responses being sent by a DNS server. The first table is sent to a manager for validation of the DNS resolution mappings. Then, a second table is received from the manager that contains validated DNS resolution mappings. The method intercepts a DNS response that includes a domain name to address resolution mapping from the DNS server and validates the domain name to address resolution mapping using a validated DNS resolution mapping in the second table.

Abstract: Methods, computer program products, computer systems, and the like are disclosed that provide for scalable deduplication in an efficient and effective manner. For example, such methods, computer program products, and computer systems can include determining whether a source data store and a replicated data store are unsynchronized and, in response to a determination that the source data store and the replicated data store are unsynchronized, performing a resynchronization operation. The source data stored in the source data store is replicated to replicated data in the replicated data store. The resynchronization operation resynchronizes the source data and the replicated data.

Abstract: The disclosed computer-implemented method for replicating information with information retention systems may include (1) queueing information communicated between a virtual machine and a source storage device, (2) initiating creating a clone of the virtual machine, (3) sending update information sets, (4) inserting a flush marker into a network queue, (5) stopping the queueing of the information communicated between the virtual machine and the source storage device, (6) sending, after sending the update information sets, the flush marker via a source replication gateway to the target server computing device, (7) pausing replication of the source storage device, (8) resuming replication of the source storage device responsive to completing creating the clone of the virtual machine, and (9) sending, to the target server computing device, additional information communicated between the virtual machine and the source storage device after stopping the queueing.

Abstract: An in-guest agent in a virtual machine (VM) operates in conjunction with a replication module. The replication module performs continuous data protection (CDP) by saving images of the VM as checkpoints at a disaster recovery site over time. Concurrently, the in-guest agent monitors for behavior in the VM that may be indicative of the presence of malicious code. If the in-guest agent identifies behavior (at a particular point in time) at the VM that may be indicative of the presence of malicious code, the replication module can tag a checkpoint that corresponds to the same particular point in time as a security risk. One or more checkpoints generated prior to the particular time may be determined to be secure checkpoints that are usable for restoration of the VM.

Abstract: Disclosed herein are methods, systems, and processes for migration between storage tiers. Such a method, for example, can include extracting one or more characteristics of a replication workload, determining one or more storage costs of each storage tier of a plurality of storage tiers (where the one or more storage costs are determined for the replication workload and the one or more storage costs are determined based, at least in part, on the one or more characteristics), identifying one or more storage tiers of the plurality of storage tiers (where the identifying is based, at least in part, on the one or more storage costs), and migrating at least a portion of the replication workload from a target storage unit in an initial storage tier to a storage unit in the one or more storage tiers.

Abstract: A system and method for automatically adjusting a learning mode duration on a virtual computing instance for an application security system extends a minimum duration of time for the learning mode duration for a guest agent running in the virtual computing instance based on a condition with respect to suspicious activities and deviations from normal behaviors detected during a fixed time interval. The guest agent is switched to a protected mode when the condition with respect to the suspicious activities and the deviations from the normal behaviors is satisfied for any fixed time interval after the minimum duration of time.

Abstract: Disclosed herein are methods, systems, and processes to select storage tiers for data replication and data recovery. A replication stream is received from a replication appliance that is configured to replicate data to a storage tier of multiple storage tiers. Each storage tier differs from at least one other storage tier in at least one storage characteristic. Portions of the replication stream are identified based on input/output (I/O) characteristics. The portions are stored in one storage tier other than the storage tier based on the I/O characteristics, and a storage cost associated with each storage tier, where the storage cost associated with each storage tier is based on storage characteristics of each storage tier.

Abstract: Disclosed herein are methods, systems, and processes to provide and maintain data consistency during reverse replication. It is determined that a migrate operation or a reverse replication operation has been requested. Upon determining that the migrate operation or the reverse replication operation has been requested, a resynchronization identifier is set in a dirty region log (DRL) associated with a computing device that is subject to the migrate operation or the reverse replication operation. In response to the operation being the reverse replication operation, a master boot record (MBR) sector of a boot disk associated with the computing device is overwritten.

Abstract: The disclosed computer-implemented method for recovery of computing environments via a replication solution may include (1) dynamically maintaining a replica of data associated with a protected computing device via a data replication device, (2) obtaining, from a preboot execution environment (PXE) server, a PXE that includes a bootable replication environment for the protected computing device, (3) directing the protected computing device to boot using the bootable replication environment, (4) exposing at least one data storage device associated with the protected computing device to the data replication device via a secure data connection, and (5) replicating the replica of data associated with the protected computing device to the data storage device associated with the protected computing device via the bootable replication environment and the secure data connection. Various other methods, systems, and computer-readable media are also disclosed.

Abstract: The disclosed computer-implemented method for replicating information with information retention systems may include (1) queueing information communicated between a virtual machine and a source storage device, (2) initiating creating a clone of the virtual machine, (3) sending update information sets, (4) inserting a flush marker into a network queue, (5) stopping the queueing of the information communicated between the virtual machine and the source storage device, (6) sending, after sending the update information sets, the flush marker via a source replication gateway to the target server computing device, (7) pausing replication of the source storage device, (8) resuming replication of the source storage device responsive to completing creating the clone of the virtual machine, and (9) sending, to the target server computing device, additional information communicated between the virtual machine and the source storage device after stopping the queueing.

Abstract: Disclosed herein are methods, systems, and processes to provide and maintain data consistency during reverse replication. It is determined that a migrate operation or a reverse replication operation has been requested. Upon determining that the migrate operation or the reverse replication operation has been requested, a resynchronization identifier is set in a dirty region log (DRL) associated with a computing device that is subject to the migrate operation or the reverse replication operation. In response to the operation being the reverse replication operation, a master boot record (MBR) sector of a boot disk associated with the computing device is overwritten.

Abstract: The disclosed computer-implemented method for recovering data may include (i) accumulating a list of changed blocks that have changed in a replicated source volume over a continuous-data-protection window of time, (ii) receiving a request to recover data in a replication target volume of the replicated source volume, (iii) converting the changed blocks to a changed-block volume that is paired with the replication target volume, (iv) launching a virtual machine from the replication target volume and the paired changed-block volume, (v) determining that an intercepted read request is directed to a changed block stored within the changed-block volume, and (vi) redirecting the intercepted read request from the replication target volume to the changed-block volume to fulfill the intercepted read request. Various other methods, systems, and computer-readable media are also disclosed.

Abstract: The disclosed computer-implemented method for managing replication of data to a remote storage device may include (1) maintaining a first bitmap and a second bitmap storing data acknowledging persistence of target data, respectively, at source and target gateways, where the target gateway serves the remote storage device, (2) sending replication data from a computing device to the source gateway, (3) setting a bit in the first bitmap, where the set bit corresponds to the replication data sent to the source gateway, (4) receiving a first acknowledgement indicating the source gateway received the replication data, (5) copying, in response to the first acknowledgement, the bit to the second bitmap, (6) clearing, in response to the first acknowledgement, the bit in the first bitmap, and (7) receiving a second acknowledgement indicating the target gateway received the replication data. Various other methods, systems, and computer-readable media are also disclosed.

Abstract: The disclosed computer-implemented method for monitoring data synchronization progress in a multi-hop data recovery system may include (i) calculating a number of data blocks to be synchronized, (ii) setting each element of a synchronization data structure to dirty, (iii) determining a dirty bytes counter, (iv) transmitting a portion of the data blocks to be synchronized, (v) receiving an acknowledgement corresponding to the transmitted portion of the data blocks, (vi) setting a set of elements within the synchronization data structure corresponding to the transmitted portion of the data blocks to clean, (vii) determining a pending dirty bytes counter that indicates a current number of elements within the synchronization data structure that are set to dirty, and (viii) transmitting the dirty bytes counter and the pending dirty bytes counter. Various other methods, systems, and computer-readable media are also disclosed.

Abstract: The disclosed computer-implemented method for managing replication of data to a remote storage device may include (1) maintaining a first bitmap and a second bitmap storing data acknowledging persistence of target data, respectively, at source and target gateways, where the target gateway serves the remote storage device, (2) sending replication data from a computing device to the source gateway, (3) setting a bit in the first bitmap, where the set bit corresponds to the replication data sent to the source gateway, (4) receiving a first acknowledgement indicating the source gateway received the replication data, (5) copying, in response to the first acknowledgement, the bit to the second bitmap, (6) clearing, in response to the first acknowledgement, the bit in the first bitmap, and (7) receiving a second acknowledgement indicating the target gateway received the replication data. Various other methods, systems, and computer-readable media are also disclosed.

Abstract: Disclosed herein are methods, systems, and processes to select storage tiers for data replication and data recovery. A replication stream is received from a replication appliance that is configured to replicate data to a storage tier of multiple storage tiers. Each storage tier differs from at least one other storage tier in at least one storage characteristic. Portions of the replication stream are identified based on input/output (I/O) characteristics. The portions are stored in one storage tier other than the storage tier based on the I/O characteristics, and a storage cost associated with each storage tier, where the storage cost associated with each storage tier is based on storage characteristics of each storage tier.

Abstract: A DR site is maintained containing multiple VMs distributed across multiple hosts to which a multi-tiered application can be failed over from a production site. A network bubble is created in which the multi-tiered application can be fire drill tested without conflicting with the production instance. Each VM is cloned, and cloned VMs communicate using private IP addresses. A virtual switch is created on each host, and configured for cloned VM communication. On each host, a virtual router is configured with both a public virtual adapter and a private virtual adapter. The source VMs communicate using public IP addresses over the physical channel, via the external virtual switches on the hosts, and are available for failover from the production site. The cloned VMs communicate using private IP addresses via the virtual switches and private virtual adapters of the virtual routers, thereby forming the network bubble.

Abstract: A computer-implemented method may include (1) identifying at least one computer cluster configured to (a) facilitate substantially continuous availability of at least one multi-tier application that includes a plurality of discrete architectural layers and (b) provide a plurality of virtual machines configured to execute the discrete architectural layers within the multi-tier application, (2) detecting a failure that prevents at least one node within the computer cluster from providing at least one virtual machine configured to execute at least one discrete architectural layer within the multi-tier application, (3) identifying a different node capable of providing the virtual machine within the computer cluster, and then (4) directing the different node within the computer cluster to provide the virtual machine in order to facilitate substantially continuous availability of all of the discrete architectural layers within the multi-tier application despite the detected failure.