True zero rto: planned failover

Patent metadata

Field	Value
Publication number	US-2021406139-A1
Application number	US-202016910694-A
Country	US
Kind code	A1
Filing date	Jun 24, 2020
Priority date	Jun 24, 2020
Publication date	Dec 30, 2021
Grant date	—

Abstract

One example method includes performing, as part a planned failover procedure, operations that include connecting a replica OS disk to a replica VM, powering up the replica VM, booting an OS of the replica VM, disconnecting a source VM from a network, and connecting replica data disks to the replica VM. IOs issued by an application at the source VM continue to be processed by the source VM while the replica OS disk is connected, the replica VM is powered up, and the OS of the replica VM is booted.

First claim

What is claimed is:

1 . A method, comprising:
as part of a planned failover procedure, performing operations comprising:
connecting a replica OS disk to a replica VM;
powering up the replica VM;
booting an OS of the replica VM;
disconnecting a source VM from a network; and
connecting replica data disks to the replica VM,
wherein IOs issued by an application at the source VM continue to be processed by the source VM while the replica OS disk is connected, the replica VM is powered up, and the OS of the replica VM is booted.

2 . The method as recited in claim 1 , wherein processing of the IOs at the source VM stops when the source VM is disconnected from the network.

3 . The method as recited in claim 1 , wherein the operations further comprise, after booting the OS and before disconnecting the source VM, setting a new IP address and/or network configuration for the replica VM.

4 . The method as recited in claim 1 , wherein the operations further comprise, after disconnection of the source VM, flushing a buffer of the source VM and transferring leftover data from a volume of the source VM to a volume of the replica VM.

5 . The method as recited in claim 1 , wherein the operations further comprise, after disconnection of the source VM and before connecting the replica data disks to the replica VM, connecting the replica VM to the network.

6 . The method as recited in claim 1 , wherein the operations further comprise running the application at the replica VM after the replica data disks are connected to the replica VM.

7 . The method as recited in claim 1 , further comprising configuring VM hardware of the replica VM after the replica OS disk is connected to the replica VM.

8 . A non-transitory storage medium having stored therein instructions that are executable by one or more hardware processors to perform operations comprising:
connecting a replica OS disk to a replica VM; powering up the replica VM; booting an OS of the replica VM; disconnecting a source VM from a network; and connecting replica data disks to the replica VM, wherein IOs issued by an application at the source VM continue to be processed by the source VM while the replica OS disk is connected, the replica VM is powered up, and the OS of the replica VM is booted, and wherein the operations are performed as part of a planned failover procedure.

9 . The non-transitory storage medium as recited in claim 8 , wherein processing of the IOs at the source VM stops when the source VM is disconnected from the network.

10 . The non-transitory storage medium as recited in claim 8 , wherein the operations further comprise, after booting the OS and before disconnecting the source VM, setting a new IP address and/or network configuration for the replica VM.

11 . The non-transitory storage medium as recited in claim 8 , wherein the operations further comprise, after disconnection of the source VM, flushing a buffer of the source VM and transferring leftover data from a volume of the source VM to a volume of the replica VM.

12 . The non-transitory storage medium as recited in claim 8 , wherein the operations further comprise, after disconnection of the source VM and before connecting the replica data disks to the replica VM, connecting the replica VM to the network.

13 . The non-transitory storage medium as recited in claim 8 , wherein the operations further comprise running the application at the replica VM after the replica data disks are connected to the replica VM.

14 . The non-transitory storage medium as recited in claim 8 , further comprising configuring VM hardware of the replica VM after the replica OS disk is connected to the replica VM.

15 . A system, comprising:
one or more hardware processors; and a non-transitory storage medium having stored therein instructions that are executable by the one or more hardware processors to perform operations comprising:
connecting a replica OS disk to a replica VM;
powering up the replica VM;
booting an OS of the replica VM;
disconnecting a source VM from a network; and
connecting replica data disks to the replica VM,
wherein IOs issued by an application at the source VM continue to be processed by the source VM while the replica OS disk is connected, the replica VM is powered up, and the OS of the replica VM is booted, and wherein the operations are performed as part of a planned failover procedure.

16 . The system as recited in claim 15 , wherein processing of the IOs at the source VM stops when the source VM is disconnected from the network.

17 . The system as recited in claim 15 , wherein the operations further comprise, after booting the OS and before disconnecting the source VM, setting a new IP address and/or network configuration for the replica VM.

18 . The system as recited in claim 15 , wherein the operations further comprise, after disconnection of the source VM, flushing a buffer of the source VM and transferring leftover data from a volume of the source VM to a volume of the replica VM.

19 . The system as recited in claim 15 , wherein the operations further comprise, after disconnection of the source VM and before connecting the replica data disks to the replica VM, connecting the replica VM to the network.

20 . The system as recited in claim 15 , wherein the operations further comprise running the application at the replica VM after the replica data disks are connected to the replica VM.

Assignees

• Emc Ip Holding Co Llc

Inventors

• Said Jawad
• Wolfson Kfir
• Shemer Jehuda

Classifications

• G06F2009/45575

  Starting, stopping, suspending or resuming virtual machine instances · CPC title

• G06F2009/45562

  Creating, deleting, cloning virtual machine instances · CPC title

• G06F11/2097

  maintaining the standby controller/processing unit updated (initialisation or re-synchronisation thereof G06F11/1658 and subgroups) · CPC title

• G06F11/2094

  Redundant storage or storage space (G06F11/2056 takes precedence) · CPC title

• G06F11/1484

  involving virtual machines · CPC title