# Patent

## Title
Cloud agnostic replication

## Abstract

A computer implemented method, computer program product, and system comprising setting a configuration of a virtual machine to boot into a replication virtual machine or a production virtual machine, booting the virtual machine to the set configuration, and upon a failover, rebooting the virtual machine into the other configuration.

## Background
A portion of the disclosure of this patent document may contain command formats and other computer language listings, all of which are subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.
TECHNICAL FIELD
This invention relates to data replication.
BACKGROUND
Computer data is vital to today's organizations, and a significant part of protection against disasters is focused on data protection. As solid-state memory has advanced to the point where cost of memory has become a relatively insignificant factor, organizations can afford to operate with systems that store and process terabytes of data.
Conventional data protection systems include tape backup drives, for storing organizational production site data on a periodic basis. Such systems suffer from several drawbacks. First, they require a system shutdown during backup, since the data being backed up cannot be used during the backup operation. Second, they limit the points in time to which the production site can recover. For example, if data is backed up on a daily basis, there may be several hours of lost data in the event of a disaster. Third, the data recovery process itself takes a long time.
Another conventional data protection system uses data replication, by creating a copy of the organization's production site data on a secondary backup storage system, and updating the backup with changes. The backup storage system may be situated in the same physical location as the production storage system, or in a physically remote location. Data replication systems generally operate either at the application level, at the file system level, at the hypervisor level or at the data block level.
Current data protection systems try to provide continuous data protection, which enable the organization to roll back to any specified point in time within a recent history. Continuous data protection systems aim to satisfy two conflicting objectives, as best as possible; namely, (i) minimize the down time, in which the organization production site data is unavailable, during a recovery, and (ii) enable recovery as close as possible to any specified point in time within a recent history.
Continuous data protection typically uses a technology referred to as “journaling,” whereby a log is kept of changes made to the backup storage. During a recovery, the journal entries serve as successive “undo” information, enabling rollback of the backup storage to previous points in time. Journaling was first implemented in database systems, and was later extended to broader data protection.
One challenge to continuous data protection is the ability of a backup site to keep pace with the data transactions of a production site, without slowing down the production site. The overhead of journaling inherently requires several data transactions at the backup site for each data transaction at the production site. As such, when data transactions occur at a high rate at the production site, the backup site may not be able to finish backing up one data transaction before the next production site data transaction occurs. If the production site is not forced to slow down, then necessarily a backlog of un-logged data transactions may build up at the backup site. Without being able to satisfactorily adapt dynamically to changing data transaction rates, a continuous data protection system chokes and eventually forces the production site to shut down.
SUMMARY
A computer implemented method, computer program product, and system comprising setting a configuration of a virtual machine to boot into a replication virtual machine or a production virtual machine, booting the virtual machine to the set configuration, and upon a failover, rebooting the virtual machine into the other configuration.



BRIEF DESCRIPTION OF THE DRAWINGS
Objects, features, and advantages of embodiments disclosed herein may be better understood by referring to the following description in conjunction with the accompanying drawings. The drawings are not meant to limit the scope of the claims included herewith. For clarity, not every element may be labeled in every Figure. The drawings are not necessarily to scale, emphasis instead being placed upon illustrating embodiments, principles, and concepts. Thus, features and advantages of the present disclosure will become more apparent from the following detailed description of exemplary embodiments thereof taken in conjunction with the accompanying drawings in which:
FIG. 1 is a simplified illustration of a data protection system, in accordance with an embodiment of the present disclosure;
FIG. 2 is a simplified illustration of a write transaction for a journal, in accordance with an embodiment of the present disclosure;
FIG. 3 is a simplified illustration of a hypervisor environment, in accordance with an embodiment of the present disclosure;
FIG. 4 is a simplified illustration of a virtual machine configured to have a dual boot capability including a production boot and a replication boot, in accordance with an embodiment of the present disclosure;
FIG. 5 is a simplified illustration of a replication environment with a production site replicating IO to a virtual machine in a cloud, in accordance with an embodiment of the present disclosure;
FIG. 6 is a simplified example of a method of replicating IO in a hypervisor environment, in accordance with an embodiment of the present disclosure;
FIG. 7 is an alternative simplified illustration of a replication environment with a production site replicating IO to a virtual machine in a cloud, in accordance with an embodiment of the present disclosure;
FIG. 8 is a simplified example of a method of a failover in a hypervisor environment, in accordance with an embodiment of the present disclosure;
FIG. 9 is a simplified illustration of a replication environment with a production virtual machine in a cloud replicating IO to a virtual machine in a cloud, in accordance with an embodiment of the present disclosure;
FIG. 10 is a simplified illustration of a replication environment with a production virtual machine in a cloud replicating IO to a virtual machine in a cloud, in accordance with an embodiment of the present disclosure;
FIG. 11 is an example of an embodiment of an apparatus that may utilize the techniques described herein, in accordance with an embodiment of the present disclosure; and
FIG. 12 is an example of an embodiment of a method embodied on a computer readable storage medium that may utilize the techniques described herein, in accordance with an embodiment of the present disclosure.



DETAILED DESCRIPTION
In certain embodiments, the current disclosure may enable cloud agnostic replication. In some embodiments, the current disclosure may enable a splitter to be placed in different places in a data path to replicate data from a production site to replication site. In many embodiments, in virtual environments, a splitter may be placed in a hypervisor. In certain embodiments, if a splitter is placed in a hypervisor, replication may be transparent to a virtual machine being replicated. In most embodiments, use of a splitter in a hypervisor in a cloud may require access to the cloud hypervisor and permissions from the cloud provider. In certain embodiments, integrating a splitter into cloud environment may be problematic. In many embodiments, in a cloud environment one may not be able to change the environment beyond changing a virtual machine deployed in that environment.
In other embodiments, a splitter may be placed in a virtual machine. In certain embodiments, this may enable a virtual machine to be shipped to a cloud environment and may have replication enabled without a splitter in the hypervisor environment of the cloud. In some embodiments, a virtual machine may have a dual boot capability. In many embodiments a dual boot capability of a virtual machine may enable it to boot into a replication virtual machine or a production virtual machine.
In many embodiments, a virtual machine may not be able to access its associated virtual machine disks if it is not running as the disks may be abstracted away via the cloud environment. In further embodiments a replication appliance may not be able to directly access a production or replication virtual machine's associated disks as this may be a violation of a cloud environment policy. In many embodiments, a splitter in a virtual machine may provide access for a replication appliance to the virtual machine's disks. In some embodiments, a replication appliance may have access to a splitter in a virtual machine, which may have access to the virtual machine's disk.
In an embodiment, a production virtual machine may have a splitter running and splitting virtual machines to a replication appliance or anther virtual machine configured to receive split data from the production site. In many embodiments, on a replication virtual machine, an operating system may not be in use if the virtual machine is being used as a replica VM. In certain embodiments, a VM may not run at the replica site, as a running virtual machine may be changing its local disks. In many embodiments, a dual boot may enable the state of a virtual machine to be changed without the virtual machine changing a state of disks of the virtual machine.
In these embodiments, it may be useful to have a machine that may be configured to be a production virtual machine and a replication virtual machine. In most embodiments, it may be useful to be able to toggle a virtual machine between being a production virtual machine and a replication virtual machine. In some embodiments, a virtual machine may be switched between a production virtual machine and a replication virtual machine through a boot process.
In some embodiments, a virtual machine may have a boot disk capable of loading an operating system with a splitter. In certain embodiments, an operating system with a splitter may be used to access the virtual machine volume. In some embodiments, virtual machine volumes may have previously served as replica volumes. In certain embodiments, an additional boot volume may be placed by the replication system on the target VM (in addition to the other VM devices). In other embodiments, a dual boot partition may be placed on an existing device. In certain embodiments, a replication system may need to be aware of this to replicate the production system disk correctly.
In other embodiments, an external boot mechanism (CD/DVD, virtual USB, PXE boot) may be used to boot the virtual machine into another mode. In most embodiments, a replication system may need to manipulate a target VM configuration in order to add and remove the boot devices during replication, DR test, and failover.
In some embodiments, for a replication appliance to access a journal volume of a virtual machine there may be direct access to journals by the vRPA or using iSCSI exposed by a journal VM. In many embodiments, the current disclosure may allow for automatic configuration of a production and a replica VMs so that splitter installation and dual boot may be installed automatically. In certain embodiments, a virtual machine may be switched between a production and replication virtual machine using a cloud API.
In certain embodiments, a virtual machine may be booted into replication mode. In many embodiments, a virtual machine in replication mode may have a splitter installed. In most embodiments, a virtual machine in replication mode may not be actively accessing the virtual machine's disks. In some embodiments, a virtual machine in replication mode may be able to replicate received IO using the splitter to write the IO to virtual machine disks. In at least some embodiments, a replication virtual machine may be rebooted to become a production virtual machine. In certain embodiments, rebooting a virtual machine from a production mode to a replication mode may include rolling disks previously used to replicate IO to a point in time and starting the virtual machine with the disk at that point in time. In at least some embodiments, a virtual machine may be rebooted by a hypervisor.
The following may be helpful in understanding the specification and claims:
BACKUP SITE—may be a facility where replicated production site data is stored; the backup site may be located in a remote site or at the same location as the production site; a backup site may be a virtual or physical site; a backup site may be referred to alternatively as a replica site or a replication site;
CLONE—a clone may be a copy or clone of the image or images, drive or drives of a first location at a second location;
DELTA MARKING STREAM—may mean the tracking of the delta between the production and replication site, which may contain the meta data of changed locations, the delta marking stream may be kept persistently on the journal at the production site of the replication, based on the delta marking data the DPA knows which locations are different between the production and the replica and transfers them to the replica to make both sites identical.
DPA—may be Data Protection Appliance a computer or a cluster of computers, or a set of processes that serve as a data protection appliance, responsible for data protection services including inter alia data replication of a storage system, and journaling of I/O requests issued by a host computer to the storage system; The DPA may be a physical device, a virtual device running, or may be a combination of a virtual and physical device.
RPA—may be replication protection appliance, is another name for DPA. An RPA may be a virtual DPA or a physical DPA.
HOST—may be at least one computer or networks of computers that runs at least one data processing application that issues I/O requests to one or more storage systems; a host is an initiator with a SAN; a host may be a virtual machine
HOST DEVICE—may be an internal interface in a host, to a logical storage unit;
IMAGE—may be a copy of a logical storage unit at a specific point in time;
INITIATOR—may be a node in a SAN that issues I/O requests;
JOURNAL—may be a record of write transactions issued to a storage system; used to maintain a duplicate storage system, and to rollback the duplicate storage system to a previous point in time;
LOGICAL UNIT—may be a logical entity provided by a storage system for accessing data from the storage system;
LUN—may be a logical unit number for identifying a logical unit; may also refer to one or more virtual disks or virtual LUNs, which may correspond to one or more Virtual Machines. As used herein, LUN and LU may be used interchangeably to refer to a LU.
Management and deployment tools—may provide the means to deploy, control and manage the RP solution through the virtual environment management tools
PHYSICAL STORAGE UNIT—may be a physical entity, such as a disk or an array of disks, for storing data in storage locations that can be accessed by address;
PRODUCTION SITE—may be a facility where one or more host computers run data processing applications that write data to a storage system and read data from the storage system; may be a virtual or physical site.
SAN—may be a storage area network of nodes that send and receive I/O and other requests, each node in the network being an initiator or a target, or both an initiator and a target;
SOURCE SIDE—may be a transmitter of data within a data replication workflow, during normal operation a production site is the source side; and during data recovery a backup site is the source side; may be a virtual or physical site
SNAPSHOT—a Snapshot may refer to differential representations of an image, i.e. the snapshot may have pointers to the original volume, and may point to log volumes for changed locations. Snapshots may be combined into a snapshot array, which may represent different images over a time period.
STORAGE SYSTEM—may be a SAN entity that provides multiple logical units for access by multiple SAN initiators
TARGET—may be a node in a SAN that replies to I/O requests;
TARGET SIDE—may be a receiver of data within a data replication workflow; during normal operation a back site is the target side, and during data recovery a production site is the target side; may be a virtual or physical site
WAN—may be a wide area network that connects local networks and enables them to communicate with one another, such as the Internet.
SPLITTER/PROTECTION AGENT: may be an agent running either on a production host a switch or a storage array which can intercept IO and split them to a DPA and to the storage array, fail IO redirect IO or do any other manipulation to the IO; the splitter or protection agent may be used in both physical and virtual systems. The splitter may be in the IO stack of a system and may be located in the hypervisor for virtual machines. May be referred to herein as an Open Replicator Splitter (ORS).
VIRTUAL VOLUME: may be a volume which is exposed to host by a virtualization layer, the virtual volume may be spanned across more than one site and or volumes
VASA: may be a set of vCenter providers that allow an administrator to manage storage
VMFS: may be a virtual machine file system, a file system provided by VMware for storing a virtual machine
VMDK: may be a virtual machine disk file containing a disk data in a VMFS. Analog to a LUN in a block storage array
Virtual RPA (vRPA)/Virtual DPA (vDPA): may be a DPA running in a VM.
VASA may be vSphere Storage application program interfaces (APIs) for Storage Awareness.
MARKING ON SPLITTER: may be a mode in a splitter where intercepted IOs are not split to an appliance and the storage, but changes (meta data) are tracked in a list and/or a bitmap and I/O is immediately sent to down the IO stack.
FAIL ALL MODE: may be a mode of a volume in the splitter where all write and read IOs intercepted by the splitter are failed to the host, but other SCSI commands like read capacity are served.
LOGGED ACCESS: may be an access method provided by the appliance and the splitter, in which the appliance rolls the volumes of the consistency group to the point in time the user requested and let the host access the volumes in a copy on first write base.
VIRTUAL ACCESS: may be an access method provided by the appliance and the splitter, in which the appliance exposes a virtual volume from a specific point in time to the host, the data for the virtual volume is partially stored on the remote copy and partially stored on the journal.
CDP: Continuous Data Protection, may refer to a full replica of a volume or a set of volumes along with a journal which allows any point in time access, the CDP copy is at the same site, and maybe the same storage array of the production site
CRR: Continuous Remote Replica may refer to a full replica of a volume or a set of volumes along with a journal which allows any point in time access at a site remote to the production volume and on a separate storage array.
A description of journaling and some techniques associated with journaling may be described in the patent titled METHODS AND APPARATUS FOR OPTIMAL JOURNALING FOR CONTINUOUS DATA REPLICATION and with U.S. Pat. No. 7,516,287, and METHODS AND APPARATUS FOR OPTIMAL JOURNALING FOR CONTINUOUS DATA REPLICATION and with U.S. Pat. No. 8,332,687, which are hereby incorporated by reference. A description of synchronous and asynchronous replication may be described in the patent titled DYNAMICALLY SWITCHING BETWEEN SYNCHRONOUS AND ASYNCHRONOUS REPLICATION and with U.S. Pat. No. 8,341,115, which is hereby incorporated by reference.
A discussion of image access may be found in U.S. patent application Ser. No. 12/969,903 entitled “DYNAMIC LUN RESIZING IN A REPLICATION ENVIRONMENT” filed on Dec. 16, 2010 assigned to EMC Corp., which is hereby incorporated by reference.
Description of Embodiments Using of a Five State Journaling Process
Reference is now made to FIG. 1, which is a simplified illustration of a data protection system 100, in accordance with an embodiment of the present invention. Shown in FIG. 1 are two sites; Site I, which is a production site, on the right, and Site II, which is a backup site, on the left. Under normal operation the production site is the source side of system 100, and the backup site is the target side of the system. The backup site is responsible for replicating production site data. Additionally, the backup site enables rollback of Site I data to an earlier pointing time, which 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.
During normal operations, the direction of replicate data flow goes from source side to target side. It is possible, however, for a user to reverse the direction of replicate data flow, in which case Site I starts to behave as a target backup site, and Site II starts to behave as a source production site. Such change of replication direction is referred to as a “failover”. A failover may be performed in the event of a disaster at the production site, or for other reasons. In some data architectures, Site I or Site II behaves as a production site for a portion of stored data, and behaves simultaneously as a backup site for another portion of stored data. In some data architectures, a portion of stored data is replicated to a backup site, and another portion is not.
The production site and the backup site may be remote from one another, or they may both be situated at a common site, local to one another. Local data protection has the advantage of minimizing data lag between target and source, and remote data protection has the advantage is being robust in the event that a disaster occurs at the source side.
The source and target sides communicate via a wide area network (WAN) 128, although other types of networks are also adaptable for use with the present invention.
In accordance with an embodiment of the present invention, each side of system 100 includes three major components coupled via a storage area network (SAN); namely, (i) a storage system, (ii) a host computer, and (iii) a data protection appliance (DPA). Specifically with reference to FIG. 1, the source side SAN includes a source host computer 104, a source storage system 108, and a source DPA 112. Similarly, the target side SAN includes a target host computer 116, a target storage system 120, and a target DPA 124.
Generally, a SAN includes one or more devices, referred to as “nodes”. A node in a SAN may be an “initiator” or a “target”, or both. An initiator node is a device that is able to initiate requests to one or more other devices; and a target node is a device that is able to reply to requests, such as SCSI commands, sent by an initiator node. A SAN may also include network switches, such as fiber channel switches. The communication links between each host computer and its corresponding storage system may be any appropriate medium suitable for data transfer, such as fiber communication channel links.
In an embodiment of the present invention, the host communicates with its corresponding storage system using small computer system interface (SCSI) commands.
System 100 includes source storage system 108 and target storage system 120. Each storage system includes physical storage units for storing data, such as disks or arrays of disks. Typically, storage systems 108 and 120 are target nodes. In order to enable initiators to send requests to storage system 108, storage system 108 exposes one or more logical units (LU) to which commands are issued. Thus, storage systems 108 and 120 are SAN entities that provide multiple logical units for access by multiple SAN initiators.
Logical units are a logical entity provided by a storage system, for accessing data stored in the storage system. A logical unit is identified by a unique logical unit number (LUN). In an embodiment of the present invention, storage system 108 exposes a logical unit 136, designated as LU A, and storage system 120 exposes a logical unit 156, designated as LU B.
In an embodiment of the present invention, LU B is used for replicating LU A. As such, LU B is generated as a copy of LU A. In one embodiment, LU B is configured so that its size is identical to the size of LU A. Thus for LU A, storage system 120 serves as a backup for source side storage system 108. Alternatively, as mentioned hereinabove, some logical units of storage system 120 may be used to back up logical units of storage system 108, and other logical units of storage system 120 may be used for other purposes. Moreover, in certain embodiments of the present invention, there is symmetric replication whereby some logical units of storage system 108 are used for replicating logical units of storage system 120, and other logical units of storage system 120 are used for replicating other logical units of storage system 108.
System 100 includes a source side host computer 104 and a target side host computer 116. A host computer may be one computer, or a plurality of computers, or a network of distributed computers, each computer may include inter alia a conventional CPU, volatile and non-volatile memory, a data bus, an I/O interface, a display interface and a network interface. Generally a host computer runs at least one data processing application, such as a database application and an e-mail server.
Generally, an operating system of a host computer creates a host device for each logical unit exposed by a storage system in the host computer SAN. A host device is a logical entity in a host computer, through which a host computer may access a logical unit. In an embodiment of the present invention, host device 104 identifies LU A and generates a corresponding host device 140, designated as Device A, through which it can access LU A. Similarly, host computer 116 identifies LU B and generates a corresponding device 160, designated as Device B.
In an embodiment of the present invention, in the course of continuous operation, host computer 104 is a SAN initiator that issues I/O requests (write/read operations) through host device 140 to LU A using, for example, SCSI commands. Such requests are generally transmitted to LU A with an address that includes a specific device identifier, an offset within the device, and a data size. Offsets are generally aligned to 512 byte blocks. The average size of a write operation issued by host computer 104 may be, for example, 10 kilobytes (KB); i.e., 20 blocks. For an I/O rate of 50 megabytes (MB) per second, this corresponds to approximately 5,000 write transactions per second.
System 100 includes two data protection appliances, a source side DPA 112 and a target side DPA 124. A DPA performs various data protection services, such as data replication of a storage system, and journaling of I/O requests issued by a host computer to source side storage system data. As explained in detail hereinbelow, when acting as a target side DPA, a DPA may also enable rollback of data to an earlier point in time, and processing of rolled back data at the target site. Each DPA 112 and 124 is a computer that includes inter alia one or more conventional CPUs and internal memory.
For additional safety precaution, each DPA is a cluster of such computers. Use of a cluster ensures that if a DPA computer is down, then the DPA functionality switches over to another computer. The DPA computers within a DPA cluster 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. One computer from the DPA cluster serves as the DPA leader. The DPA cluster leader coordinates between the computers in the cluster, and may also perform other tasks that require coordination between the computers, such as load balancing.
In the architecture illustrated in FIG. 1, DPA 112 and DPA 124 are standalone devices integrated within a SAN. Alternatively, each of DPA 112 and DPA 124 may be integrated into storage system 108 and storage system 120, respectively, or integrated into host computer 104 and host computer 116, respectively. Both DPAs communicate with their respective host computers through communication lines such as fiber channels using, for example, SCSI commands.
In accordance with an embodiment of the present invention, DPAs 112 and 124 are configured to act as initiators in the SAN; i.e., they can issue I/O requests using, for example, SCSI commands, to access logical units on their respective storage systems. DPA 112 and DPA 124 are also configured with the necessary functionality to act as targets; i.e., to reply to I/O requests, such as SCSI commands, issued by other initiators in the SAN, including inter alia their respective host computers 104 and 116. Being target nodes, DPA 112 and DPA 124 may dynamically expose or remove one or more logical units.
As described hereinabove, Site I and Site II may each behave simultaneously as a production site and a backup site for different logical units. As such, DPA 112 and DPA 124 may each behave as a source DPA for some logical units and as a target DPA for other logical units, at the same time.
In accordance with an embodiment of the present invention, host computer 104 and host computer 116 include protection agents 144 and 164, respectively. Protection agents 144 and 164 intercept SCSI commands issued by their respective host computers, via host devices to logical units that are accessible to the host computers. In accordance with an embodiment of the present invention, a data protection agent may act on an intercepted SCSI commands issued to a logical unit, in one of the following ways:
Send the SCSI commands to its intended logical unit.
Redirect the SCSI command to another logical unit.
Split the SCSI command by sending it first to the respective DPA. After the DPA returns an acknowledgement, send the SCSI command to its intended logical unit.
Fail a SCSI command by returning an error return code.
Delay a SCSI command by not returning an acknowledgement to the respective host computer.
A protection agent may handle different SCSI commands, differently, according to the type of the command. For example, a SCSI command inquiring about the size of a certain logical unit may be sent directly to that logical unit, while a SCSI write command may be split and sent first to a DPA associated with the agent. A protection agent may also change its behavior for handling SCSI commands, for example as a result of an instruction received from the DPA.
Specifically, the behavior of a protection agent for a certain host device generally corresponds to the behavior of its associated DPA with respect to the logical unit of the host device. When a DPA behaves as a source site DPA for a certain logical unit, then during normal course of operation, the associated protection agent splits I/O requests issued by a host computer to the host device corresponding to that logical unit. Similarly, when a DPA behaves as a target device for a certain logical unit, then during normal course of operation, the associated protection agent fails I/O requests issued by host computer to the host device corresponding to that logical unit.
Communication between protection agents and their respective DPAs may use any protocol suitable for data transfer within a SAN, such as fiber channel, or SCSI over fiber channel. The communication may be direct, or via a logical unit exposed by the DPA. In an embodiment of the present invention, protection agents communicate with their respective DPAs by sending SCSI commands over fiber channel.
In an embodiment of the present invention, protection agents 144 and 164 are drivers located in their respective host computers 104 and 116. Alternatively, a protection agent may also be located in a fiber channel switch, or in any other device situated in a data path between a host computer and a storage system.
What follows is a detailed description of system behavior under normal production mode, and under recovery mode.
In accordance with an embodiment of the present invention, in production mode DPA 112 acts as a source site DPA for LU A. Thus, protection agent 144 is configured to act as a source side protection agent; i.e., as a splitter for host device A. Specifically, protection agent 144 replicates SCSI I/O requests. A replicated SCSI I/O request is sent to DPA 112. After receiving an acknowledgement from DPA 124, protection agent 144 then sends the SCSI I/O request to LU A. Only after receiving a second acknowledgement from storage system 108 may host computer 104 initiate another I/O request.
When DPA 112 receives a replicated SCSI write request from data protection agent 144, DPA 112 transmits certain I/O information characterizing the write request, packaged as a “write transaction”, over WAN 128 to DPA 124 on the target side, for journaling and for incorporation within target storage system 120.
DPA 112 may send its write transactions to DPA 124 using a variety of modes of transmission, including inter alia (i) a synchronous mode, (ii) an asynchronous mode, and (iii) a snapshot mode. In synchronous mode, DPA 112 sends each write transaction to DPA 124, receives back an acknowledgement from DPA 124, and in turns sends an acknowledgement back to protection agent 144. Protection agent 144 waits until receipt of such acknowledgement before sending the SCSI write request to LU A.
In asynchronous mode, DPA 112 sends an acknowledgement to protection agent 144 upon receipt of each I/O request, before receiving an acknowledgement back from DPA 124.
In snapshot mode, DPA 112 receives several I/O requests and combines them into an aggregate “snapshot” of all write activity performed in the multiple I/O requests, and sends the snapshot to DPA 124, for journaling and for incorporation in target storage system 120. In snapshot mode DPA 112 also sends an acknowledgement to protection agent 144 upon receipt of each I/O request, before receiving an acknowledgement back from DPA 124.
For the sake of clarity, the ensuing discussion assumes that information is transmitted at write-by-write granularity.
While in production mode, DPA 124 receives replicated data of LU A from DPA 112, and performs journaling and writing to storage system 120. When applying write operations to storage system 120, DPA 124 acts as an initiator, and sends SCSI commands to LU B.
During a recovery mode, DPA 124 undoes the write transactions in the journal, so as to restore storage system 120 to the state it was at, at an earlier time.
As described hereinabove, in accordance with an embodiment of the present invention, LU B is used as a backup of LU A. As such, during normal production mode, while data written to LU A by host computer 104 is replicated from LU A to LU B, host computer 116 should not be sending I/O requests to LU B. To prevent such I/O requests from being sent, protection agent 164 acts as a target site protection agent for host Device B and fails I/O requests sent from host computer 116 to LU B through host Device B.
In accordance with an embodiment of the present invention, target storage system 120 exposes a logical unit 176, referred to as a “journal LU”, for maintaining a history of write transactions made to LU B, referred to as a “journal”. Alternatively, journal LU 176 may be striped over several logical units, or may reside within all of or a portion of another logical unit. DPA 124 includes a journal processor 180 for managing the journal.
Journal processor 180 functions generally to manage the journal entries of LU B. Specifically, journal processor 180 (i) enters write transactions received by DPA 124 from DPA 112 into the journal, by writing them into the journal LU, (ii) applies the journal transactions to LU B, and (iii) updates the journal entries in the journal LU with undo information and removes already-applied transactions from the journal. As described below, with reference to FIGS. 2 and 3A-3D, journal entries include four streams, two of which are written when write transaction are entered into the journal, and two of which are written when write transaction are applied and removed from the journal.
Reference is now made to FIG. 2, which is a simplified illustration of a write transaction 200 for a journal, in accordance with an embodiment of the present invention. The journal may be used to provide an adaptor for access to storage 120 at the state it was in at any specified point in time. Since the journal contains the “undo” information necessary to rollback storage system 120, data that was stored in specific memory locations at the specified point in time may be obtained by undoing write transactions that occurred subsequent to such point in time.
Write transaction 200 generally includes the following fields:
one or more identifiers;
a time stamp, which is the date & time at which the transaction was received by source side DPA 112;
a write size, which is the size of the data block;
a location in journal LU 176 where the data is entered;
a location in LU B where the data is to be written; and
the data itself.
Write transaction 200 is transmitted from source side DPA 112 to target side DPA 124. As shown in FIG. 2, DPA 124 records the write transaction 200 in four streams. A first stream, referred to as a DO stream, includes new data for writing in LU B. A second stream, referred to as an DO METADATA stream, includes metadata for the write transaction, such as an identifier, a date & time, a write size, a beginning address in LU B for writing the new data in, and a pointer to the offset in the do stream where the corresponding data is located. Similarly, a third stream, referred to as an UNDO stream, includes old data that was overwritten in LU B; and a fourth stream, referred to as an UNDO METADATA, include an identifier, a date & time, a write size, a beginning address in LU B where data was to be overwritten, and a pointer to the offset in the undo stream where the corresponding old data is located.
In practice each of the four streams holds a plurality of write transaction data. As write transactions are received dynamically by target DPA 124, they are recorded at the end of the DO stream and the end of the DO METADATA stream, prior to committing the transaction. During transaction application, when the various write transactions are applied to LU B, prior to writing the new DO data into addresses within the storage system, the older data currently located in such addresses is recorded into the UNDO stream.
By recording old data, a journal entry can be used to “undo” a write transaction. To undo a transaction, old data is read from the UNDO stream in a reverse order, from the most recent data to the oldest data, for writing into addresses within LU B. Prior to writing the UNDO data into these addresses, the newer data residing in such addresses is recorded in the DO stream.
The journal LU is partitioned into segments with a pre-defined size, such as 1 MB segments, with each segment identified by a counter. The collection of such segments forms a segment pool for the four journaling streams described hereinabove. Each such stream is structured as an ordered list of segments, into which the stream data is written, and includes two pointers—a beginning pointer that points to the first segment in the list and an end pointer that points to the last segment in the list.
According to a write direction for each stream, write transaction data is appended to the stream either at the end, for a forward direction, or at the beginning, for a backward direction. As each write transaction is received by DPA 124, its size is checked to determine if it can fit within available segments. If not, then one or more segments are chosen from the segment pool and appended to the stream's ordered list of segments.
Thereafter the DO data is written into the DO stream, and the pointer to the appropriate first or last segment is updated. Freeing of segments in the ordered list is performed by simply changing the beginning or the end pointer. Freed segments are returned to the segment pool for re-use.
A journal may be made of any number of streams including less than or more than 5 streams. Often, based on the speed of the journaling and whether the back-up is synchronous or a synchronous a fewer or greater number of streams may be used.
Virtual Machines
Refer now to the example embodiment of FIG. 3, which illustrates a production site and cloud environment. In the example embodiment of FIG. 3, hypervisor 310 runs virtual machine 330 and has splitter 335. Hypervisor 310 is also in communication with storage 341 which has access to volume 321. Refer as well to hypervisor cloud 311, which illustrates a hypervisor running in a cloud environment. Hypervisor cloud 311 is running cloud virtual machine 331. Hypervisor cloud 311 has permissions that allow cloud virtual machine 331 to be deployed into hypervisor cloud 311. Hypervisor cloud 311 limits the actions that may be taken in the cloud. In this embodiment, hypervisor cloud has permissions that do not allow splitter 336 to be deployed into hypervisor cloud 311. In hypervisor cloud 311, only virtual machines are allowed to be deployed in the cloud. Thus, in this embodiment, it is not possible to replication IO send to a virtual machine at a hypervisor cloud level such as that of hypervisor cloud 311.
Refer now to the example embodiment of FIG. 4, which illustrates a cloud virtual machine with dual boot capability. In this example embodiment, cloud virtual machine 431 has dual boot 432 that enables cloud virtual machine 431 to be booted to either production virtual machine 433 or replication virtual machine 434. In this embodiment, when cloud virtual machine 431 is running in production mode 433, cloud virtual machine 431 is running the same OS as a production VM. In this embodiment, when running in production mode, cloud virtual machine 431 has splitter 435 installed which splits the IO to a vRPA running in a public cloud to enable replication from the public cloud to a another site. In this embodiment, when cloud virtual machine 431 is booted to replication mode 434, VM 431 is booted to serve as a disk machine allowing the virtual machine to replicate IOs from a production site by writing IOs arriving from a production site to replica volumes. In this embodiment, when cloud virtual machine 431 is in production mode, the disks of the cloud virtual machine may only be accessed by virtual machine 431, as internal devices of the machine. In replication mode, the machine is booted with a proprietary OS (typically a version of Linux), where the internal disks are exposed to the vRPA.
In some embodiments, a cloud virtual machine may have dual boot capability from a boot disk. In many embodiments, a cloud virtual machine may have dual boot capability from a network drive. In other embodiments, a cloud virtual machine may have dual boot capability from another type of boot device.
Refer now to the example embodiment of FIG. 5 which illustrates a deployment of a dual boot virtual machines. In the example embodiment of FIG. 5, hypervisor 510 has virtual machine 530 and RPA 512. Virtual machine 530 has and splitter 535. Splitter 535 runs inside virtual machine 530 and allows replication of the virtual machine. Splitter 535 splits IO to virtual replication protection appliance 512. Hypervisor 510 is also in communication with storage 541, which stores volume 1 521 and volume 2 522 for hypervisor 510, which correspond to volumes for virtual machine 530. In this embodiment, volumes 1 and 521 and volume 2 522 may be virtual machine disks stored on a virtual machine file system, however this abstraction is not shown for simplicity.
vRPA 512 is communicatively coupled to hypervisor cloud 511. vRPA 512 is enabled to send split IO to Hypervisor cloud 511. Hypervisor Cloud 511 has vRPA 513 and cloud virtual machine 531. Cloud virtual machine 531 is configured to have dual boot capability 532. Dual boot 532 includes the ability to boot to a production VM 533 and a replication VM 534. Cloud virtual machine 531 also has splitter 536 deployed in production mode. In this embodiment, splitter 536 is a piece of software and present depending on whether the virtual machine is booted into production mode or replication mode. In this embodiment, there is no splitter when in replication mode, In this embodiment there is a splitter in production mode, in order to have a splitter. In production mode, the splitter is installed on the production virtual machine 530. vRPA 513 has journal 526. In other embodiments, a journal may be another disk of a cloud virtual machine exposed in replication mode.
Returning to FIG. 5, hypervisor cloud 511 also is communicatively coupled to storage 542 which stored the virtual machines for cloud virtual machine 531. Volume 551 and volume 2 552 are replicas of volumes 521 and 522 respectively. Volume 553, includes a dual boot system for virtual machine 531 allowing it to either boot as a replication VM or as a copy of VM 530 booting from the replica disk of machine 530. The volumes may be virtual machine disks stored in a virtual machine file system accessed by hypervisor cloud, but in this embodiment for simplicity are represented as volumes.
In this example embodiment, cloud virtual machine 531 is configured to be a replica virtual machine 530. Virtual machine 530 has its IO intercepted at splitter 535. Splitter 535 sends IOs to vRPA 512 which send them to vRPA 513. vRPA 513 in hypervisor cloud 511. vRPA 513 sends the IOs to splitter 536 of cloud virtual machine 531. Cloud virtual machine 531 writes the IOs to volume 1 1 551 on storage 541.
In certain embodiments, when a virtual machine is booted to replication mode, there may be no splitter running, rather the splitter is configured for the production mode and in replication mode the volumes of the replica VMs may be internal disks of the cloud machine.
Refer to the example embodiments of FIG. 5 and FIG. 6, which illustrate a deployment of a cloud virtual machine. Cloud virtual machine 531 is created (step 600). Cloud virtual machine 531 is configured to dual boot (step 610). Cloud virtual machine 531 is deployed to hypervisor cloud 511.
Refer now to the example embodiments of FIGS. 7 and 8, which illustrate switching a virtual machine from replication mode to production mode. Volume 1 751 of cloud virtual machine 731 is rolled to a point in time (step 800). Cloud virtual machine 731 is brought down (step 810). Cloud virtual machine 731 is rebooted into a production virtual machine (step 815). Cloud virtual machine 731 is now a production virtual machine and IO from cloud virtual machine 731 is split to vRPA 713 and replicated to vRPA 712 and to virtual machine 730 on hypervisor 710.
Refer now to the example embodiment of FIG. 9, which illustrates virtual machines with dual boot in a hypervisor cloud. In this example embodiment, Hypervisor cloud 911 has vRPA 912 and cloud virtual machine 920. Hypervisor cloud 911 has vRPA 913 and cloud virtual machine 931. Cloud virtual machines 920 and 931 are dual boot virtual machines each having dual boot 926 and 932 respectively. In this embodiment, each cloud virtual machine 920 and 931 may be booted into either production mode or replication mode. In this embodiment, cloud virtual machine 920 is booted into production mode 923 and cloud virtual machine 931 is booted into replication mode 934. Cloud virtual machine 920 is configured in production mode where splitter 925 splits IO sent to Cloud virtual machine 920's disks to vRPA 912 which sends IO to vRPA 913. vRPA 913 sends the split IO to splitter 936 in cloud virtual machine 931.
Refer as well to the example embodiment of FIG. 6, which illustrates deployment of virtual machines in hypervisor cloud. Cloud virtual machines 920 and 931 are created (step 600). Cloud virtual machines 920 and 931 are configured (step 610). Cloud virtual machines 920 and 931 are created (step 620).
Refer now to the example embodiments of FIGS. 9 and 10 which illustrate a failover of a production and replication virtual machine. Volume 1 1051 of cloud virtual machine 1031 is rolled to a point in time (step 800). Cloud virtual machine 1031 is brought down (step 810). Cloud virtual machine 1031 is rebooted into a production virtual machine (step 815). Cloud virtual machine 1020 is brought down (step 810). Cloud virtual machine 1020 is rebooted (step 815). Cloud virtual machine 1031 is now a production virtual machine and IO from cloud virtual machine 1031 is split to vRPA 1013, which sends IO to vRPA 912 and the IO replicated to virtual machine 1020.
The methods and apparatus of this invention may take the form, at least partially, of program code (i.e., instructions) embodied in tangible media, such as floppy diskettes, CD-ROMs, hard drives, random access or read only-memory, or any other machine-readable storage medium. When the program code is loaded into and executed by a machine, such as the computer of FIG. 11, the machine becomes an apparatus for practicing the invention. When implemented on one or more general-purpose processors, the program code combines with such a processor 1103 to provide a unique apparatus that operates analogously to specific logic circuits. As such a general purpose digital machine can be transformed into a special purpose digital machine. FIG. 12 shows Program Logic 1210 embodied on a computer-readable medium 1220 as shown, and wherein the Logic is encoded in computer-executable code configured for carrying out the reservation service process of this invention and thereby forming a Computer Program Product 1200. The logic 1210 may be the same logic 1140 on memory 1104 loaded on processor 1103. The program logic may also be embodied in software modules, as modules, or as hardware modules.
The logic for carrying out the method may be embodied as part of the system described below, which is useful for carrying out a method described with reference to embodiments shown in, for example, FIGS. 6 and 8. For purposes of illustrating the present invention, the invention is described as embodied in a specific configuration and using special logical arrangements, but one skilled in the art will appreciate that the device is not limited to the specific configuration but rather only by the claims included with this specification. A processor may be a physical or virtual processor.
Although the foregoing invention has been described in some detail for purposes of clarity of understanding, it will be apparent that certain changes and modifications may be practiced within the scope of the appended claims. Accordingly, the present implementations are to be considered as illustrative and not restrictive, and the invention is not to be limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.

## Claims

1. A system comprising:
a virtual machine with a splitter and a configuration to enable the virtual machine to switch between modes including a replication virtual machine mode and a production virtual machine mode;
computer-executable logic operating in memory, wherein the computer-executable program logic is configured to enable execution across one or more processors of:
setting the configuration of the virtual machine to boot into a replication virtual machine or a production virtual machine; and
booting the virtual machine to the set configuration; and
upon a failover, rebooting the virtual machine into the other configuration; wherein the replication virtual machine mode enables a virtual replication appliance to access the virtual disks of the replication virtual machine; wherein the replication virtual machine boots to a separate boot disk and has access to disks corresponding to a production virtual machine as disks internal to the replication virtual machine.

2. The system of claim 1 wherein the production virtual machine mode loads a splitter upon booting into production virtual machine.

3. The system of claim 1 wherein a production splitter sends IO to a virtual replication protection appliance (vRPA), the vRPA communicating the IO to a second vRPA, which communicates with the virtual machine replicating the IO to create a copy of a virtual machine disk.

4. The system of claim 1 the logic further enabling:
creating the virtual machine by configuring the virtual machine to have one more virtual machine disk than a production virtual machine the virtual machine is to replicate.

5. The method of claim 1 wherein the separate boot disk has an operating system that enables it to be booted from the additional disk when replicating IO and booted from the production virtual machines primary disk when running as a production virtual machine.

6. The method of claim 1 wherein the separate boot disk is configured with a dual boot option.

7. A computer implemented method comprising:
setting a configuration of a virtual machine to boot into a replication virtual machine or a production virtual machine; wherein in the virtual machine has a splitter and a configuration to enable the virtual machine to switch between modes including a replication virtual machine mode and a production virtual machine mode; and
booting the virtual machine to the set configuration; and
upon a failover, rebooting the virtual machine into the other configuration; wherein the replication virtual machine mode enables a virtual replication appliance to access the virtual disks of the replication virtual machine; wherein the replication virtual machine boots to a separate boot disk and has access to disks corresponding to a production virtual machine as disks internal to the replication virtual machine.

8. The method of claim 7 wherein the production virtual machine mode loads a splitter upon booting into production virtual machine.

9. The system of claim 7 wherein a production splitter sends IO to a virtual replication protection appliance (vRPA), the vRPA communicating the IO to a second vRPA, which communicates with the virtual machine replicating the IO to create a copy of a virtual machine disk.

10. The system of claim 7 further comprising:
creating the virtual machine by configuring the virtual machine to have one more virtual machine disk than a production virtual machine the virtual machine is to replicate.

11. The system of claim 7 wherein the separate boot disk has an operating system that enables it to be booted from the additional disk when replicating IO and booted from the production virtual machines primary disk when running as a production virtual machine.

12. The system of claim 7 wherein the separate boot disk is configured with a dual boot option.

13. A computer program product comprising:
a non-transitory computer readable medium encoded with computer executable program code, wherein the code enables execution across one or more processors of:
setting a configuration of a virtual machine to boot into a replication virtual machine or a production virtual machine; wherein in the virtual machine has a splitter and a configuration to enable the virtual machine to switch between modes including a replication virtual machine mode and a production virtual machine mode; and
booting the virtual machine to the set configuration; and

upon a failover, rebooting the virtual machine into the other configuration; wherein the replication virtual machine mode enables a virtual replication appliance to access the virtual disks of the replication virtual machine; wherein the replication virtual machine boots to a separate boot disk and has access to disks corresponding to a production virtual machine as disks internal to the replication virtual machine.

14. The computer program product of claim 13 wherein the production virtual machine mode loads a splitter upon booting into production virtual machine.

15. The computer program product of claim 13 wherein a production splitter sends IO to a virtual replication protection appliance (vRPA), the vRPA communicating the IO to a second vRPA, which communicates with the virtual machine replicating the IO to create a copy of a virtual machine disk.

16. The computer program product of claim 13 the logic further enabling:
creating the virtual machine by configuring the virtual machine to have one more virtual machine disk than a production virtual machine the virtual machine is to replicate.

17. The computer program product of claim 13 wherein the separate boot disk has an operating system that enables it to be booted from the additional disk when replicating IO and booted from the production virtual machines primary disk when running as a production virtual machine.

18. The computer program product of claim 13 wherein the separate boot disk is configured with a dual boot option.