Computer data is vital to today's organizations and a significant part of protection against disasters is focused on data protection. A data protection system may offer various types of data protection, such as synchronous replication, asynchronous replication, and periodic backups. Moreover, there may be many different configuration options available for each type of data protection.
In data protection systems having a vast number of machines (physical or virtual), one problem is configuring appropriate data protection for each machine. Existing solutions include policy-based configurations, whereby a user can attach a data protection policy to a VM, and the replication and backups are configured accordingly. Such solutions (sometimes referred to as “single-click” configuration) can help reduce configuration costs. For organizations managing a large number of machines (e.g., thousands or tens of thousands of machines), even single-click configuration is complex and error prone.
Described herein are embodiments of systems and methods for data protection configuration that reduce complexity, errors, and cost by automatically selecting configuration profiles for VMs. In some embodiments, the described systems and methods can be scaled up to an arbitrary number of VMs, meeting the demands of large organizations.
According to one aspect of the disclosure, a method comprises: determining a set of available data protection plans; determining one or more parameters associated with a customer, a host, or a data protection system; generating a recommended host protection configuration for the host using the parameters, wherein the recommended host protection configuration includes one or more of the available data protection plans; and assigning the recommended host protection configuration to the host.
In various embodiments, determining the one or more parameters associated with the customer includes at least one of: a number of employees for the customer, an annual revenue for the customer, an industry to which the customer belongs, a data protection budget for the customer, and customer preferences. In one embodiment, determining the one or more parameters associated with the host includes at least one of: a set of applications installed on the host, a set of applications running on the host, a number of open network connections on the host, CPU usage on the host, storage usage on the host, network usage on the host, and a role for the host. In some embodiments, determining the one or more parameters associated with the data protection system includes at least one of: a number of sites associated with the data protection system, connectivity between sites associated with the data protection system, connectivity between hosts within the data protection system, and connectivity between the data protection system and an external backup site.
In certain embodiments, the set of available data protection plan comprises one or more data replication plans and one or more data backup plans. In various embodiments, the method further comprises determining a confidence level for the recommended host protection configuration; and determining a minimum confidence level for the customer, wherein assigning the recommended host protection configuration to the host comprises assigning the recommended host protection configuration to the host only if the confidence level for the recommended host protection configuration is greater than or equal to the minimum confidence level for the customer. In one embodiment, the method further comprises prompting a user to accept the recommended host protection configuration, wherein assigning the recommended host protection configuration to the host comprises assigning the recommended host protection configuration to the host only if the user accepts the recommended host protection configuration.
In some embodiments, generating the recommended host protection configuration comprises using a machine learning (ML) model. In various embodiments, the method further comprises receiving feedback information from a user regarding the recommended host protection configuration, and updating the ML model based on the feedback information.
The foregoing features may be more fully understood from the following description of the drawings in which:
The drawings are not necessarily to scale, or inclusive of all elements of a system, emphasis instead generally being placed upon illustrating the concepts, structures, and techniques sought to be protected herein.
Before describing embodiments of the concepts, structures, and techniques sought to be protected herein, some terms are explained. In some embodiments, the term “I/O request” or simply “I/O” may be used to refer to an input or output request. In some embodiments, an I/O request may refer to a data read or write request.
Referring to the embodiment of
In certain embodiments, Site I and Site II may be remote from one another. In other embodiments, the two sites may be local to one another. In particular embodiments, Site I and Site II may be connected via a local area network (LAN). In other embodiments, the two sites may be connected via a wide area network (WAN), such as the Internet.
In particular embodiments, the data protection system may include a failover mode of operation, wherein the direction of replicated data flow is reversed. In such embodiments, Site I may behave as a target side and Site II may behave as the source side. In some embodiments, failover may be triggered manually (e.g., by a user) or automatically. In many embodiments, failover may be performed in the event of a disaster at Site I. In some embodiments, both Site I and Site II may behave as source side for some stored data and may behave simultaneously as a target site for other stored data. In certain embodiments, a portion of stored data may be replicated from one site to the other, and another portion may not be replicated.
In some embodiments, Site I corresponds to a production site (e.g., a facility where one or more hosts run data processing applications that write data to a storage system and read data from the storage system) and Site II corresponds to a backup or replica site (e.g., a facility where replicated production site data is stored). In such embodiments, Site II may be responsible for replicating production site data and may enable rollback of Site I data to an earlier point in time. In many embodiments, rollback may be used in the event of data corruption of a disaster, or alternatively in order to view or to access data from an earlier point in time.
Referring again to
Referring back to
Referring again to
In the embodiment of
Referring back to
Referring again to
Referring back to
In some embodiments, a DPA may be a cluster of such computers. In many embodiments, a cluster may ensure that if a DPA computer is down, then the DPA functionality switches over to another computer. In some embodiments, computers within a DPA cluster may communicate with one another using at least one communication link suitable for data transfer via fiber channel or IP based protocols, or such other transfer protocol. In certain embodiments, one computer from the DPA cluster may serve as the DPA leader that coordinates other computers in the cluster, and may also perform other tasks that require coordination between the computers, such as load balancing.
In certain embodiments, a DPA may be a standalone device integrated within a SAN. In other embodiments, a DPA may be integrated into a storage system. In some embodiments, the DPAs communicate with their respective hosts through communication lines such as fiber channels using, for example, SCSI commands or any other protocol.
In various embodiments, the DPAs may be configured to act as initiators in the SAN. For example, the DPAs may issue I/O requests using to access LUs on their respective storage systems. In some embodiments, each DPA may also be configured with the necessary functionality to act as targets, e.g., to reply to I/O requests, such as SCSI commands, issued by other initiators in the SAN, including their respective hosts. In certain embodiments, the DPAs, acting as target nodes, may dynamically expose or remove one or more LUs.
Referring again to
In the embodiment of
In various embodiments, a protection agent may change its behavior for handling SCSI commands, for example as a result of an instruction received from the DPA. In certain embodiments, the behavior of a protection agent for a certain host device may depend on the behavior of its associated DPA with respect to the LU of the host device. In some embodiments, when a DPA behaves as a source site DPA for a certain LU, then during normal course of operation, the associated protection agent may split I/O requests issued by a host to the host device corresponding to that LU. In particular embodiments, when a DPA behaves as a target device for a certain LU, then during normal course of operation, the associated protection agent fails I/O requests issued by the host to the host device corresponding to that LU.
Referring back to
In certain embodiments, protection agents may be drivers located in their respective hosts. In other embodiments, a protection agent may be located in a fiber channel switch or in any other device situated in a data path between a host and a storage system or on the storage system itself. In a virtualized environment, the protection agent may run at the hypervisor layer or in a virtual machine providing a virtualization layer.
Referring again to
In the embodiment of
In one embodiment, the journal processor 180 is configured to perform processing described in the patent titled “METHODS AND APPARATUS FOR OPTIMAL JOURNALING FOR CONTINUOUS DATA REPLICATION” and with U.S. Pat. No. 7,516,287, issued Apr. 7, 2009, which is hereby incorporated by reference.
Embodiments of the data replication system may be provided as physical systems for the replication of physical LUs, or as virtual systems for the replication of virtual LUs. In one embodiment, a hypervisor may consume LUs and may generate a distributed file system on the logical units such as VMFS, for example, generates files in the file system and exposes the files as LUs to the virtual machines (each virtual machine disk is seen as a SCSI device by virtual hosts). In another embodiment, a hypervisor may consume a network based file system and exposes files in the NFS as SCSI devices to virtual hosts.
Referring back to
When source DPA 112 receives a replicated I/O request from protection agent 144, source DPA 112 may transmit certain I/O information characterizing the write request, packaged as a “write transaction”, over WAN 128 to the target DPA 124 for journaling and for incorporation within target storage system 120. When applying write operations to storage system 120, the target DPA 124 may act as an initiator, and may send SCSI commands to LU 156 (“LU B”).
The source DPA 112 may send its write transactions to target DPA 124 using a variety of modes of transmission, including inter alia (i) a synchronous mode, (ii) an asynchronous mode, and (iii) a batch mode. In synchronous mode, the source DPA 112 may send each write transaction to the target DPA 124, may receive back an acknowledgement from the target DPA 124, and in turns may send an acknowledgement back to protection agent 144.
In synchronous mode, protection agent 144 may wait until receipt of such acknowledgement before sending the I/O request to LU 136. In asynchronous mode, the source DPA 112 may send an acknowledgement to protection agent 144 upon receipt of each I/O request, before receiving an acknowledgement back from target DPA 124.
In batch mode, the source DPA 112 may receive several I/O requests and combines them into an aggregate “batch” of write activity performed in the multiple I/O requests, and may send the batch to the target DPA 124, for journaling and for incorporation in target storage system 120. In batch mode, the source DPA 112 may send an acknowledgement to protection agent 144 upon receipt of each I/O request, before receiving an acknowledgement back from the target DPA 124.
As discussed above, in normal operation, LU B 156 may be used as a backup of LU A 136. As such, while data written to LU A by host 104 is replicated from LU A to LU B, the target host 116 should not send I/O requests to LU B. To prevent such I/O requests from being sent, protection agent 164 may act as a target side protection agent for host device B 160 and may fail I/O requests sent from host 116 to LU B 156 through host device B 160.
Still referring to
In many embodiments, the data protection system provides various types of data protection, such as synchronous replication, asynchronous replication, and periodic backups.
Referring to the embodiment of
In the embodiment of
In some embodiments, one or more of the hosts may correspond to a non-virtualized host having an OS that runs directly accesses physical hardware. In certain embodiments, a non-virtualized host may be the same as or similar to host 104 or 116 in
In some embodiments, the hosts may be collocated within a single site (e.g., a single data center). In other embodiments, the hosts may be distributed across multiple sites.
Referring again to
One available data protection plan is data replication. The associated parameters may include: (1) replication type, e.g., synchronous continuous replication, asynchronous continuous replication, and asynchronous snapshot-based replication; and (2) journal retention time.
Another available data protection plan is data backups. The associated parameters may include: (1) how often backups are performed, e.g., every six hours, every twenty-four hours, etc.); (2) whether full or incremental backups are performed; (3) how long backups are retained for; (4) which backup copies are retained; (5) location(s) where backups are stored, e.g., local, remote, or in a cloud backup system; and (6) a backup restore policy, i.e., where to push the backups in order to guarantee a maximum time-to-restore.
In certain embodiments, the set of available protection plans may be shared across data protection systems and/or customers. In some embodiments, the customer may generate proprietary protection plans that can be added to the set of available plans (e.g., they may be stored within the available plan database 216). In one embodiment, the customer may download protection plans from an external repository into the set of available plans. In the embodiment of
In some embodiments, the databases 216 and 218 are provided as separate logical databases stored within the same physical database. In other embodiments, the databases 216 and 218 may be provided as separate physical databases. In certain embodiments, one or both databases 216 and 218 may be stored within a storage array (e.g., storage array 108 in
Referring back to
Referring back to the example embodiment of
In some embodiments, host configuration agent input parameters may include parameters associated with the customer (“customer parameters”). Non-limiting examples of customer parameters include: the number of employees the customer has, the customer's annual revenue, the industry the customer belongs to, the customer's data protection budget, and customer preferences. Non-limiting examples of customer preferences include a minimum acceptable confidence level and an automatic confidence level. In certain embodiments, a minimum acceptable confidence level is a confidence level above which a recommendation made by the host configuration agent must exceed in order for that recommendation to be presented to the customer for approval. In some embodiments, an automatic confidence level is a confidence level above which a recommendation made by the host configuration agent is automatically applied to a host without requiring user approval. In many embodiments, some or all of the aforementioned customer information may be stored within a system database (e.g., database 216 or database 218), or may be retrieved from an external source. Referring to
In certain embodiments, host configuration agent input parameters may include information about the VM (“host-level parameters”). In some embodiments, host-level parameters include the VM's role as determined by its app detection component (e.g., app detection component 210 in
In various embodiments, host configuration agent input parameters include parameters associated with the data protection system topology (“system-level parameters”). For example, system-level parameters may include the number of sites (e.g., data centers) across which the system is distributed. As another example, system-level parameters may include the type of network connectivity between hosts and/or sites. As yet another example, the system-level parameters may include network connectivity to external backup storage (e.g., connectivity to an external cloud-based backup system).
Referring back to
Referring back to
Referring again to
Referring back to
In some embodiments, the system may prompt the customer (e.g., via the customer management interface 220) to approve or reject a recommended host protection. If a customer approves, the recommended protection configuration may be assigned to the host and used to provide data protection thereto. In some embodiments, the host protection configuration is stored within the host protection configuration database (e.g., database 218 in
In certain embodiments, the host configuration agent can re-evaluate the existing host protection configuration for one or more VMs. In some embodiments, host protection configuration may be re-evaluated periodically. In certain embodiments, host protection configuration may be re-evaluated in response to a user request (e.g., via the customer management interface 220). In particular embodiments, host protection configuration may be re-evaluated in response to changes within the system, e.g., new information about a VM, changes in system or VM configuration, changes to the customer's budget, changes or updates to the ML model, and/or improvements within an external analytics platform. Previous decisions by the customer to accept or reject recommendations may be to train the ML model.
As shown in the embodiment of
Alternatively, the processing and decision blocks may represent steps performed by functionally equivalent circuits such as a digital signal processor (DSP) circuit or an application specific integrated circuit (ASIC). The flow diagrams do not depict the syntax of any particular programming language but rather illustrate the functional information one of ordinary skill in the art requires to fabricate circuits or to generate computer software to perform the processing required of the particular apparatus. It should be noted that many routine program elements, such as initialization of loops and variables and the use of temporary variables may be omitted for clarity. The particular sequence of blocks described is illustrative only and can be varied without departing from the spirit of the concepts, structures, and techniques sought to be protected herein. Thus, unless otherwise stated, the blocks described below are unordered meaning that, when possible, the functions represented by the blocks can be performed in any convenient or desirable order.
Referring to the example embodiment of
Referring back to
Referring again to
If the confidence level is below the customer's automatic confidence level but greater than or equal to the customer's minimum confidence level, then the customer may be promoted to approve or reject the recommended host protection plan (block 312). If the customer approves (block 314), then the recommended protection configuration may be assigned to the host (block 316). Otherwise, processing may proceed to block 311, as described above.
In some embodiments, the host protection configuration is stored within the host protection configuration database. In certain embodiments, the approved host protection configuration may be applied to the host. In some embodiments, if a customer rejects the recommended configuration, an alternate configuration may be generated, as shown. In certain embodiments, customer feedback information is used to update a ML model.
Processing may be implemented in hardware, software, or a combination of the two. In various embodiments, processing is provided by computer programs executing on programmable computers/machines that each includes a processor, a storage medium or other article of manufacture that is readable by the processor (including volatile and non-volatile memory and/or storage elements), at least one input device, and one or more output devices. Program code may be applied to data entered using an input device to perform processing and to generate output information.
The system can perform processing, at least in part, via a computer program product, (e.g., in a machine-readable storage device), for execution by, or to control the operation of, data processing apparatus (e.g., a programmable processor, a computer, or multiple computers). Each such program may be implemented in a high level procedural or object-oriented programming language to communicate with a computer system. However, the programs may be implemented in assembly or machine language. The language may be a compiled or an interpreted language and it may be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program may be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network. A computer program may be stored on a storage medium or device (e.g., CD-ROM, hard disk, or magnetic diskette) that is readable by a general or special purpose programmable computer for configuring and operating the computer when the storage medium or device is read by the computer. Processing may also be implemented as a machine-readable storage medium, configured with a computer program, where upon execution, instructions in the computer program cause the computer to operate. The program logic may be run on a physical or virtual processor. The program logic may be run across one or more physical or virtual processors.
Processing may be performed by one or more programmable processors executing one or more computer programs to perform the functions of the system. All or part of the system may be implemented as special purpose logic circuitry (e.g., an FPGA (field programmable gate array) and/or an ASIC (application-specific integrated circuit)).
All references cited herein are hereby incorporated herein by reference in their entirety.
Having described certain embodiments, which serve to illustrate various concepts, structures, and techniques sought to be protected herein, it will be apparent to those of ordinary skill in the art that other embodiments incorporating these concepts, structures, and techniques may be used. Elements of different embodiments described hereinabove may be combined to form other embodiments not specifically set forth above and, further, elements described in the context of a single embodiment may be provided separately or in any suitable sub-combination. Accordingly, it is submitted that the scope of protection sought herein should not be limited to the described embodiments but rather should be limited only by the spirit and scope of the following claims.
Number | Name | Date | Kind |
---|---|---|---|
7203741 | Marco et al. | Apr 2007 | B2 |
7719443 | Natanzon | May 2010 | B1 |
7840536 | Ahal et al. | Nov 2010 | B1 |
7840662 | Natanzon | Nov 2010 | B1 |
7844856 | Ahal | Nov 2010 | B1 |
7860836 | Natanzon et al. | Dec 2010 | B1 |
7882286 | Natanzon et al. | Feb 2011 | B1 |
7934262 | Natanzon et al. | Apr 2011 | B1 |
7958372 | Natanzon | Jun 2011 | B1 |
8037162 | Marco et al. | Oct 2011 | B2 |
8041940 | Natanzon et al. | Oct 2011 | B1 |
8060713 | Natanzon | Nov 2011 | B1 |
8060714 | Natanzon | Nov 2011 | B1 |
8103937 | Natanzon et al. | Jan 2012 | B1 |
8108634 | Natanzon et al. | Jan 2012 | B1 |
8214612 | Natanzon | Jul 2012 | B1 |
8250149 | Marco et al. | Aug 2012 | B2 |
8271441 | Natanzon et al. | Sep 2012 | B1 |
8271447 | Natanzon et al. | Sep 2012 | B1 |
8285850 | Jones | Oct 2012 | B1 |
8332687 | Natanzon et al. | Dec 2012 | B1 |
8335761 | Natanzon | Dec 2012 | B1 |
8335771 | Natanzon et al. | Dec 2012 | B1 |
8341115 | Natanzon et al. | Dec 2012 | B1 |
8370648 | Natanzon | Feb 2013 | B1 |
8380885 | Natanzon | Feb 2013 | B1 |
8392680 | Natanzon et al. | Mar 2013 | B1 |
8429362 | Natanzon et al. | Apr 2013 | B1 |
8433869 | Natanzon et al. | Apr 2013 | B1 |
8438135 | Natanzon et al. | May 2013 | B1 |
8464101 | Natanzon et al. | Jun 2013 | B1 |
8478955 | Natanzon et al. | Jul 2013 | B1 |
8495304 | Natanzon et al. | Jul 2013 | B1 |
8510279 | Natanzon et al. | Aug 2013 | B1 |
8521691 | Natanzon | Aug 2013 | B1 |
8521694 | Natanzon | Aug 2013 | B1 |
8543609 | Natanzon | Sep 2013 | B1 |
8583885 | Natanzon | Nov 2013 | B1 |
8600945 | Natanzon et al. | Dec 2013 | B1 |
8601085 | Ives et al. | Dec 2013 | B1 |
8627012 | Derbeko et al. | Jan 2014 | B1 |
8683592 | Dotan et al. | Mar 2014 | B1 |
8694700 | Natanzon et al. | Apr 2014 | B1 |
8706700 | Natanzon et al. | Apr 2014 | B1 |
8712962 | Natanzon et al. | Apr 2014 | B1 |
8719497 | Don et al. | May 2014 | B1 |
8725691 | Natanzon | May 2014 | B1 |
8725692 | Natanzon et al. | May 2014 | B1 |
8726066 | Natanzon et al. | May 2014 | B1 |
8738813 | Natanzon et al. | May 2014 | B1 |
8745004 | Natanzon et al. | Jun 2014 | B1 |
8751828 | Raizen et al. | Jun 2014 | B1 |
8769336 | Natanzon et al. | Jul 2014 | B1 |
8805786 | Natanzon | Aug 2014 | B1 |
8806161 | Natanzon | Aug 2014 | B1 |
8825848 | Dotan et al. | Sep 2014 | B1 |
8832399 | Natanzon et al. | Sep 2014 | B1 |
8850143 | Natanzon | Sep 2014 | B1 |
8850144 | Natanzon et al. | Sep 2014 | B1 |
8862546 | Natanzon et al. | Oct 2014 | B1 |
8892835 | Natanzon et al. | Nov 2014 | B1 |
8898112 | Natanzon et al. | Nov 2014 | B1 |
8898409 | Natanzon et al. | Nov 2014 | B1 |
8898515 | Natanzon | Nov 2014 | B1 |
8898519 | Natanzon et al. | Nov 2014 | B1 |
8914595 | Natanzon | Dec 2014 | B1 |
8924668 | Natanzon | Dec 2014 | B1 |
8930500 | Marco et al. | Jan 2015 | B2 |
8930947 | Derbeko et al. | Jan 2015 | B1 |
8935498 | Natanzon | Jan 2015 | B1 |
8949180 | Natanzon et al. | Feb 2015 | B1 |
8954673 | Natanzon et al. | Feb 2015 | B1 |
8954796 | Cohen et al. | Feb 2015 | B1 |
8959054 | Natanzon | Feb 2015 | B1 |
8977593 | Natanzon et al. | Mar 2015 | B1 |
8977826 | Meiri et al. | Mar 2015 | B1 |
8996460 | Frank et al. | Mar 2015 | B1 |
8996461 | Natanzon et al. | Mar 2015 | B1 |
8996827 | Natanzon | Mar 2015 | B1 |
9003138 | Natanzon et al. | Apr 2015 | B1 |
9026696 | Natanzon et al. | May 2015 | B1 |
9031913 | Natanzon | May 2015 | B1 |
9032160 | Natanzon et al. | May 2015 | B1 |
9037818 | Natanzon et al. | May 2015 | B1 |
9063994 | Natanzon et al. | Jun 2015 | B1 |
9069479 | Natanzon | Jun 2015 | B1 |
9069709 | Natanzon et al. | Jun 2015 | B1 |
9081754 | Natanzon et al. | Jul 2015 | B1 |
9081842 | Natanzon et al. | Jul 2015 | B1 |
9087008 | Natanzon | Jul 2015 | B1 |
9087112 | Natanzon et al. | Jul 2015 | B1 |
9104529 | Derbeko et al. | Aug 2015 | B1 |
9110914 | Frank et al. | Aug 2015 | B1 |
9116811 | Derbeko et al. | Aug 2015 | B1 |
9128628 | Natanzon et al. | Sep 2015 | B1 |
9128855 | Natanzon et al. | Sep 2015 | B1 |
9134914 | Derbeko et al. | Sep 2015 | B1 |
9135119 | Natanzon et al. | Sep 2015 | B1 |
9135120 | Natanzon | Sep 2015 | B1 |
9146878 | Cohen et al. | Sep 2015 | B1 |
9152339 | Cohen et al. | Oct 2015 | B1 |
9152578 | Saad et al. | Oct 2015 | B1 |
9152814 | Natanzon | Oct 2015 | B1 |
9158578 | Derbeko et al. | Oct 2015 | B1 |
9158630 | Natanzon | Oct 2015 | B1 |
9160526 | Raizen et al. | Oct 2015 | B1 |
9177670 | Derbeko et al. | Nov 2015 | B1 |
9189339 | Cohen et al. | Nov 2015 | B1 |
9189341 | Natanzon et al. | Nov 2015 | B1 |
9201736 | Moore et al. | Dec 2015 | B1 |
9223659 | Natanzon et al. | Dec 2015 | B1 |
9225529 | Natanzon et al. | Dec 2015 | B1 |
9235481 | Natanzon et al. | Jan 2016 | B1 |
9235524 | Derbeko et al. | Jan 2016 | B1 |
9235632 | Natanzon | Jan 2016 | B1 |
9244997 | Natanzon et al. | Jan 2016 | B1 |
9256605 | Natanzon | Feb 2016 | B1 |
9274718 | Natanzon et al. | Mar 2016 | B1 |
9275063 | Natanzon | Mar 2016 | B1 |
9286052 | Solan et al. | Mar 2016 | B1 |
9304796 | Douglas | Apr 2016 | B1 |
9305009 | Bono et al. | Apr 2016 | B1 |
9323750 | Natanzon et al. | Apr 2016 | B2 |
9330155 | Bono et al. | May 2016 | B1 |
9336094 | Wolfson et al. | May 2016 | B1 |
9336230 | Natanzon | May 2016 | B1 |
9367260 | Natanzon | Jun 2016 | B1 |
9378096 | Erel et al. | Jun 2016 | B1 |
9378219 | Bono et al. | Jun 2016 | B1 |
9378261 | Bono et al. | Jun 2016 | B1 |
9383937 | Frank et al. | Jul 2016 | B1 |
9389800 | Natanzon et al. | Jul 2016 | B1 |
9405481 | Cohen et al. | Aug 2016 | B1 |
9405684 | Derbeko et al. | Aug 2016 | B1 |
9405765 | Natanzon | Aug 2016 | B1 |
9411535 | Shemer et al. | Aug 2016 | B1 |
9459804 | Natanzon et al. | Oct 2016 | B1 |
9460028 | Raizen et al. | Oct 2016 | B1 |
9471579 | Natanzon | Oct 2016 | B1 |
9477407 | Maranak et al. | Oct 2016 | B1 |
9501542 | Natanzon | Nov 2016 | B1 |
9507732 | Natanzon et al. | Nov 2016 | B1 |
9507845 | Natanzon et al. | Nov 2016 | B1 |
9514138 | Natanzon et al. | Dec 2016 | B1 |
9524218 | Veprinsky et al. | Dec 2016 | B1 |
9529885 | Natanzon et al. | Dec 2016 | B1 |
9535800 | Natanzon et al. | Jan 2017 | B1 |
9535801 | Natanzon et al. | Jan 2017 | B1 |
9547459 | BenHanokh et al. | Jan 2017 | B1 |
9547591 | Natanzon et al. | Jan 2017 | B1 |
9552405 | Moore et al. | Jan 2017 | B1 |
9557921 | Cohen et al. | Jan 2017 | B1 |
9557925 | Natanzon | Jan 2017 | B1 |
9563517 | Natanzon et al. | Feb 2017 | B1 |
9563684 | Natanzon et al. | Feb 2017 | B1 |
9575851 | Natanzon et al. | Feb 2017 | B1 |
9575857 | Natanzon | Feb 2017 | B1 |
9575894 | Natanzon et al. | Feb 2017 | B1 |
9582382 | Natanzon et al. | Feb 2017 | B1 |
9588703 | Natanzon et al. | Mar 2017 | B1 |
9588847 | Natanzon et al. | Mar 2017 | B1 |
9594822 | Natanzon et al. | Mar 2017 | B1 |
9600377 | Cohen et al. | Mar 2017 | B1 |
9619543 | Natanzon et al. | Apr 2017 | B1 |
9632881 | Natanzon | Apr 2017 | B1 |
9665305 | Natanzon et al. | May 2017 | B1 |
9710177 | Natanzon | Jul 2017 | B1 |
9720618 | Panidis et al. | Aug 2017 | B1 |
9722788 | Natanzon et al. | Aug 2017 | B1 |
9727429 | Moore et al. | Aug 2017 | B1 |
9733969 | Derbeko et al. | Aug 2017 | B2 |
9737111 | Lustik | Aug 2017 | B2 |
9740572 | Natanzon et al. | Aug 2017 | B1 |
9740573 | Natanzon | Aug 2017 | B1 |
9740880 | Natanzon et al. | Aug 2017 | B1 |
9749300 | Cale et al. | Aug 2017 | B1 |
9772789 | Natanzon et al. | Sep 2017 | B1 |
9798472 | Natanzon et al. | Oct 2017 | B1 |
9798490 | Natanzon | Oct 2017 | B1 |
9804934 | Natanzon et al. | Oct 2017 | B1 |
9811431 | Natanzon et al. | Nov 2017 | B1 |
9823865 | Natanzon et al. | Nov 2017 | B1 |
9823973 | Natanzon | Nov 2017 | B1 |
9832261 | Don et al. | Nov 2017 | B2 |
9846698 | Panidis et al. | Dec 2017 | B1 |
9875042 | Natanzon et al. | Jan 2018 | B1 |
9875162 | Panidis et al. | Jan 2018 | B1 |
9880777 | Bono et al. | Jan 2018 | B1 |
9881014 | Bono et al. | Jan 2018 | B1 |
9910620 | Veprinsky et al. | Mar 2018 | B1 |
9910621 | Golan et al. | Mar 2018 | B1 |
9910735 | Natanzon | Mar 2018 | B1 |
9910739 | Natanzon et al. | Mar 2018 | B1 |
9916551 | Bandopadhyay | Mar 2018 | B1 |
9917854 | Natanzon et al. | Mar 2018 | B2 |
9921955 | Derbeko et al. | Mar 2018 | B1 |
9933957 | Cohen et al. | Apr 2018 | B1 |
9934302 | Cohen et al. | Apr 2018 | B1 |
9940205 | Natanzon | Apr 2018 | B2 |
9940460 | Derbeko et al. | Apr 2018 | B1 |
9946649 | Natanzon et al. | Apr 2018 | B1 |
9959061 | Natanzon et al. | May 2018 | B1 |
9965306 | Natanzon et al. | May 2018 | B1 |
9990256 | Natanzon | Jun 2018 | B1 |
9996539 | Natanzon | Jun 2018 | B1 |
10007626 | Saad et al. | Jun 2018 | B1 |
10019194 | Baruch et al. | Jul 2018 | B1 |
10025931 | Natanzon et al. | Jul 2018 | B1 |
10031675 | Veprinsky et al. | Jul 2018 | B1 |
10031690 | Panidis et al. | Jul 2018 | B1 |
10031692 | Elron et al. | Jul 2018 | B2 |
10031703 | Natanzon et al. | Jul 2018 | B1 |
10037251 | Bono et al. | Jul 2018 | B1 |
10042579 | Natanzon | Aug 2018 | B1 |
10042751 | Veprinsky et al. | Aug 2018 | B1 |
10055146 | Natanzon et al. | Aug 2018 | B1 |
10055148 | Natanzon et al. | Aug 2018 | B1 |
10061666 | Natanzon et al. | Aug 2018 | B1 |
10067694 | Natanzon et al. | Sep 2018 | B1 |
10067837 | Natanzon et al. | Sep 2018 | B1 |
10078459 | Natanzon et al. | Sep 2018 | B1 |
10082980 | Cohen et al. | Sep 2018 | B1 |
10083093 | Natanzon et al. | Sep 2018 | B1 |
10095489 | Liberman et al. | Oct 2018 | B1 |
10101943 | Ayzenberg et al. | Oct 2018 | B1 |
10108356 | Natanzon et al. | Oct 2018 | B1 |
10108507 | Natanzon | Oct 2018 | B1 |
10108645 | Bigman et al. | Oct 2018 | B1 |
10114581 | Natanzon et al. | Oct 2018 | B1 |
10120787 | Shemer et al. | Nov 2018 | B1 |
10120925 | Natanzon et al. | Nov 2018 | B1 |
10126946 | Natanzon et al. | Nov 2018 | B1 |
10133874 | Natanzon et al. | Nov 2018 | B1 |
10140039 | Baruch et al. | Nov 2018 | B1 |
10146436 | Natanzon et al. | Dec 2018 | B1 |
10146639 | Natanzon et al. | Dec 2018 | B1 |
10146675 | Shemer et al. | Dec 2018 | B1 |
10146961 | Baruch et al. | Dec 2018 | B1 |
10148751 | Natanzon | Dec 2018 | B1 |
10152246 | Lieberman et al. | Dec 2018 | B1 |
10152267 | Ayzenberg et al. | Dec 2018 | B1 |
10152384 | Amit et al. | Dec 2018 | B1 |
10157014 | Panidis et al. | Dec 2018 | B1 |
10185583 | Natanzon et al. | Jan 2019 | B1 |
10191677 | Natanzon et al. | Jan 2019 | B1 |
10191687 | Baruch et al. | Jan 2019 | B1 |
10191755 | Natanzon et al. | Jan 2019 | B1 |
10203904 | Natanzon et al. | Feb 2019 | B1 |
10210073 | Baruch et al. | Feb 2019 | B1 |
10223007 | Natanzon et al. | Mar 2019 | B1 |
10223023 | Natanzon et al. | Mar 2019 | B1 |
10223131 | Lieberman et al. | Mar 2019 | B1 |
10229006 | Natanzon et al. | Mar 2019 | B1 |
10229056 | Panidis et al. | Mar 2019 | B1 |
10235055 | Saad et al. | Mar 2019 | B1 |
10235060 | Baruch et al. | Mar 2019 | B1 |
10235061 | Natanzon et al. | Mar 2019 | B1 |
10235064 | Natanzon et al. | Mar 2019 | B1 |
10235087 | Baruch et al. | Mar 2019 | B1 |
10235088 | Baruch et al. | Mar 2019 | B1 |
10235090 | Baruch et al. | Mar 2019 | B1 |
10235091 | Ayzenberg et al. | Mar 2019 | B1 |
10235092 | Natanzon et al. | Mar 2019 | B1 |
10235145 | Natanzon et al. | Mar 2019 | B1 |
10235196 | Natanzon et al. | Mar 2019 | B1 |
10235247 | Natanzon et al. | Mar 2019 | B1 |
10235249 | Natanzon et al. | Mar 2019 | B1 |
10235252 | Lieberman et al. | Mar 2019 | B1 |
10250679 | Natanzon et al. | Apr 2019 | B1 |
10255137 | Panidis et al. | Apr 2019 | B1 |
10255291 | Natanzon et al. | Apr 2019 | B1 |
20070220320 | Sen | Sep 2007 | A1 |
20080147821 | Dietrich | Jun 2008 | A1 |
20090254593 | Halim | Oct 2009 | A1 |
20090254971 | Herz | Oct 2009 | A1 |
20100262796 | Camborde | Oct 2010 | A1 |
20130054518 | Anglin | Feb 2013 | A1 |
20140189680 | Kripalani | Jul 2014 | A1 |
20140250070 | Odenheimer | Sep 2014 | A1 |
20170063887 | Muddu | Mar 2017 | A1 |
Entry |
---|
EMC Corporation, “EMC Recoverpoint/Ex;” Applied Technology; White Paper; Apr. 2012; 17 Pages. |
U.S. Appl. No. 14/496,783, filed Sep. 25, 2014, Natanzon et al. |
U.S. Appl. No. 14/496,790, filed Sep. 25, 2014, Cohen et al. |
U.S. Appl. No. 14/559,036, filed Dec. 3, 2014, Natanzon et al. |
U.S. Appl. No. 14/753,389, filed Jun. 29, 2015, Nir et al. |
U.S. Appl. No. 14/976,719, filed Dec. 21, 2015, Natanzon. |
U.S. Appl. No. 14/978,378, filed Dec. 22, 2015, Bigman et al. |
U.S. Appl. No. 15/085,148, filed Mar. 30, 2016, Baruch et al. |
U.S. Appl. No. 15/274,362, filed Sep. 23, 2016, Baruch et al. |
U.S. Appl. No. 15/275,768, filed Sep. 26, 2016, Natanzon et al. |
U.S. Appl. No. 15/275,756, filed Sep. 26, 2016, Natanzon et al. |
U.S. Appl. No. 15/379,940, filed Dec. 15, 2016, Baruch et al. |
U.S. Appl. No. 15/386,754, filed Dec. 21, 2016, Shemer et al. |
U.S. Appl. No. 15/380,013, filed Dec. 15, 2016, Baruch et al. |
U.S. Appl. No. 15/390,996, filed Dec. 27, 2016, Natanzon et al. |
U.S. Appl. No. 15/391,030, filed Dec. 27, 2016, Shemer et al. |
U.S. Appl. No. 15/970,243, filed May 3, 2018, Schneider et al. |
U.S. Appl. No. 16/052,037, filed Aug. 1, 2018, Schneider et al. |
U.S. Appl. No. 16/048,763, filed Jul. 30, 2018, Schneider et al. |
U.S. Appl. No. 16/050,400, filed Jul. 31, 2018, Alkalay et al. |
U.S. Appl. No. 16/179,295, filed Nov. 2, 2018, Natanzon et al. |
U.S. Appl. No. 16/261,174, filed Jan. 29, 2019, Natanzon et al. |
U.S. Appl. No. 16/368,008, filed Mar. 28, 2019, Natanzon et al. |