IP Library Granted Patent US 10,942,817
Granted Patent B1
US 10,942,817 · App. 16/416,387 · Granted Mar 9, 2021

Low cost, heterogeneous method of transforming replicated data for consumption in the cloud

Inventors: Pooja Sarda (Cupertino, CA); Anish A. Vaidya (San Jose, CA); Manjunath Mageswaran (Sunnyvale, CA)
Assignee: Veritas Technologies LLC
G06F11/1464G06F11/1451H04L67/1095
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,942,817
App. No.
16/416,387
Granted
Mar 9, 2021
Kind
B1
Abstract

Presented herein is functionality for using a recovery computing system to perform a failover where the recovery computing system is communicatively coupled to a homogeneous and/or heterogeneous primary computing system. In one embodiment, this functionality allows the recovery computing system to disconnect a first recovery application node from a contiguous storage volume after the contiguous storage volume had been created by the first recovery application node, and to then use a recovery gateway node to store replicated data on the continguous storage volume, where the recovery gateway node and the contiguous storage volume are both coupled to the recovery computing system. In response to detecting a failure on the primary computing system, performing a failover to the recovery computing system, where performing the failover comprises attaching the contiguous storage volume to a second recovery application node and bringing the second recovery application node online.

Claims (96)

1. A method comprising:

disconnecting a first recovery application node from a contiguous storage volume, wherein

the contiguous storage volume is created by the first recovery application node,

the first recovery application node is communicatively coupled to a recovery computing system, and

the recovery computing system comprises a recovery gateway node;

subsequent to the disconnecting of the first recovery application node from the contiguous storage volume, replicating data received from a primary computing system, wherein

the replicating is performed, at least in part, by the recovery gateway node, and

the replicating comprises storing the data in the contiguous storage volume;

detecting a failure of an application running on the primary computing system; and

in response to detecting the failure of the application, performing a failover of the application to the recovery computing system, wherein

performing the failover comprises

attaching the contiguous storage volume to a second recovery application node,

executing an instance of the application on the second recovery application node, and

bringing the second recovery application node online.

2. The method of claim 1 , wherein

the first recovery application node and the second recovery application node are the same node.

3. The method of claim 1 , further comprising:

prior to the disconnecting, creating the contiguous storage volume on a storage device, wherein

the creating the contiguous storage volume comprises

writing information regarding a starting location associated with the contiguous storage volume.

4. The method of claim 1 , wherein

the disconnecting comprises shutting down the first recovery application node, and

the shutting down is performed prior to the replicating of the data.

5. The method of claim 1 , further comprising:

prior to creating the contiguous storage volume, provisioning a storage device, wherein

the first recovery application node is used to provision the storage device, and

the storage device is communicatively coupled to the second recovery application node.

6. The method of claim 1 , wherein performing the failover further comprises:

prior to attaching the contiguous storage volume to the second recovery application node, detaching the contiguous storage volume from the recovery gateway node.

7. The method of claim 1 , wherein performing the failover further comprises:

prior to bringing the second recovery application node online, importing a volume group to the second recovery application node, wherein

the contiguous storage volume comprises the volume group.

8. A computer system comprising:

one or more processors; and

a memory coupled to at least one of the one or more processors and configured to store instructions executable by the one or more processors, the instructions configured to perform a method comprising

disconnecting a first recovery application node from a contiguous storage volume, wherein

the contiguous storage volume is created by the first recovery application node,

the first recovery application node is communicatively coupled to a recovery computing system, and

the recovery computing system comprises a recovery gateway node,

subsequent to the disconnecting of the first recovery application node from the contiguous storage volume, replicating data received from a primary computing system, wherein

the replicating is performed, at least in part, by the recovery gateway node, and

the replicating comprises storing the data in the contiguous storage volume,

detecting a failure of an application running on the primary computing system, and

in response to detecting the failure of the application, performing a failover of the application to the recovery computing system, wherein

performing the failover comprises

attaching the contiguous storage volume to a second recovery application node,

executing an instance of the application on the second recovery application node, and

bringing the second recovery application node online.

9. The computer system of claim 8 , wherein

the first recovery application node and the second recovery application node are the same node.

10. The computer system of claim 8 , wherein the method further comprises:

prior to the disconnecting, creating the contiguous storage volume on a storage device, wherein

the creating the contiguous storage volume comprises writing information regarding a starting location associated with the contiguous storage volume.

11. The computer system of claim 8 , wherein

the disconnecting comprises shutting down the first recovery application node, and

the shutting down is performed prior to the replicating of the data.

12. The computer system of claim 8 , wherein the method further comprises:

prior to creating the contiguous storage volume, provisioning a storage device, wherein

the first recovery application node is used to provision the storage device, and

the storage device is communicatively coupled to the second recovery application node.

13. The computer system of claim 8 , wherein performing the failover further comprises:

prior to attaching the contiguous storage volume to the second recovery application node, detaching the contiguous storage volume from the recovery gateway node.

14. The computer system of claim 8 , wherein performing the failover further comprises:

prior to bringing the second recovery application node online, importing a volume group to the second recovery application node, wherein

the contiguous storage volume comprises the volume group.

15. A non-transitory computer-readable storage medium configured to store program instructions that, when executed on a processor, are configured to cause the processor to perform a method comprising:

disconnecting a first recovery application node from a contiguous storage volume, wherein

the contiguous storage volume is created by the first recovery application node,

the first recovery application node is communicatively coupled to a recovery computing system, and

the recovery computing system comprises a recovery gateway node;

subsequent to the disconnecting of the first recovery application node from the contiguous storage volume, replicating data received from a primary computing system, wherein

the replicating is performed, at least in part, by the recovery gateway node, and

the replicating comprises storing the data in the contiguous storage volume;

detecting a failure of an application running on the primary computing system; and

in response to detecting the failure of the application, performing a failover of the application to the recovery computing system, wherein

performing the failover comprises

attaching the contiguous storage volume to a second recovery application node,

executing an instance of the application on the second recovery application node, and

bringing the second recovery application node online.

16. The non-transitory computer-readable storage medium of claim 15 , wherein

the first recovery application node and the second recovery application node are the same node.

17. The non-transitory computer-readable storage medium of claim 15 , wherein the method further comprises:

prior to the disconnecting

provisioning a storage device, wherein

the first recovery application node is used to provision the storage device, and

the storage device is communicatively coupled to the second recovery application node; and

creating the contiguous storage volume on a storage device, wherein

the creating the contiguous storage volume comprises writing information regarding a starting location associated with the contiguous storage volume.

18. The non-transitory computer-readable storage medium of claim 15 , wherein

the disconnecting comprises shutting down the first recovery application node, and

the shutting down is performed prior to the replicating of the data.

19. The non-transitory computer-readable storage medium of claim 15 , wherein performing the failover further comprises:

prior to attaching the contiguous storage volume to the second recovery application node, detaching the contiguous storage volume from the recovery gateway node.

20. The non-transitory computer-readable storage medium of claim 15 , wherein performing the failover further comprises:

prior to bringing the second recovery application node online, importing a volume group to the second recovery application node, wherein

the contiguous storage volume comprises the volume group.

Assignments (10)
AMENDMENT NO. 1 TO PATENT SECURITY AGREEMENT Recorded Apr 8, 2025
From: VERITAS TECHNOLOGIES LLC; COHESITY, INC.
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 070779/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 26, 2025
From: VERITAS TECHNOLOGIES LLC
To: COHESITY, INC.
Reel/Frame 070335/0013 →
RELEASE OF SECURITY INTEREST Recorded Dec 16, 2024
From: ACQUIOM AGENCY SERVICES LLC, AS COLLATERAL AGENT
To: VERITAS TECHNOLOGIES LLC
Reel/Frame 069697/0238 →
RELEASE OF SECURITY INTEREST Recorded Dec 13, 2024
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
To: VERITAS TECHNOLOGIES LLC
Reel/Frame 069634/0584 →
SECURITY INTEREST Recorded Dec 9, 2024
From: VERITAS TECHNOLOGIES LLC; COHESITY, INC.
To: JPMORGAN CHASE BANK. N.A.
Reel/Frame 069890/0001 →
ASSIGNMENT OF SECURITY INTEREST IN PATENT COLLATERAL Recorded Nov 25, 2024
From: BANK OF AMERICA, N.A., AS ASSIGNOR
To: ACQUIOM AGENCY SERVICES LLC, AS ASSIGNEE
Reel/Frame 069440/0084 →
TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS AT R/F 052426/0001 Recorded Nov 30, 2020
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
To: VERITAS TECHNOLOGIES LLC
Reel/Frame 054535/0565 →
SECURITY INTEREST Recorded Aug 20, 2020
From: VERITAS TECHNOLOGIES LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
Reel/Frame 054370/0134 →
PATENT SECURITY AGREEMENT SUPPLEMENT Recorded Apr 16, 2020
From: VERITAS TECHNOLOGIES, LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
Reel/Frame 052426/0001 →
PATENT SECURITY AGREEMENT SUPPLEMENT Recorded Mar 18, 2020
From: VERITAS TECHNOLOGIES LLC
To: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
Reel/Frame 052189/0311 →
Continuity (1)
Continuation 14611233 · Jan 31, 2015