IP Library › Granted Patent US 12,327,147
Granted Patent B2
US 12,327,147 · App. 17/507,664 · Granted Jun 10, 2025

Standby data center as a service

Inventors: Jehuda Shemer (Kfar Saba, IL); Valerie Lotosh (Ramat-Gan, IL); Erez Sharvit (Ramat-Gan, IL)
Assignee: EMC IP HOLDING COMPANY LLC
G06F9/5088G06F9/45558G06F2009/45595
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 12,327,147
App. No.
17/507,664
Granted
Jun 10, 2025
Kind
B2
Abstract

A system can maintain a first data center that comprises a virtualized overlay network and virtualized volume identifiers, and store data comprising virtualized workloads. The system can determine a service level agreement associated with providing a second data center as a backup to the first data center. The system can, based on the service level agreement, divide, into a first portion of tasks and a second portion of tasks deploying the data to a secondary storage of the second data center, deploying the data to a primary storage of the second data center, and configuring the second data center with the virtualized overlay network and the virtualized volume identifiers. The system can perform the first portion of tasks before determining to restore the first data center to the second data center. The system can perform the second portion of tasks in response to determining to restore the first data center.

Claims (61)

1. A system, comprising:

at least one processor; and

at least one memory that stores executable instructions that, when executed by the at least one processor, facilitate performance of operations, comprising:

maintaining a first data center that comprises a first instance of a virtualized overlay network that virtualizes physical network resources and a first instance of a group of virtualized volume identifiers that virtualize physical storage volumes, the first data center storing data comprising first instances of a group of virtualized workloads that operate on the first data center;

determining a service level agreement associated with providing a second data center as a backup to the first data center;

based on the service level agreement, dividing tasks into a first portion of tasks to complete before determining to restore the first data center to the second data center, and a second portion of tasks to perform after determining to restore the first data center and the second data center, wherein the tasks comprise,

deploying the data to a secondary storage of the second data center,

deploying the data to a primary storage of the second data center, and

configuring the second data center with a second instance of the virtualized overlay network and a second instance of the group of virtualized volume identifiers;

assigning the deploying of the data to the primary storage of the second data center to the first portion of tasks;

assigning the configuring of the second data center with the second instance of the virtualized overlay network and the second instance of the group of virtualized volume identifiers to the second portion of tasks;

performing the first portion of tasks before determining to restore the first data center to the second data center; and

performing the second portion of tasks in response to determining to restore the first data center to the second data center.

2. The system of claim 1 , wherein the dividing of the tasks into the first portion of tasks and the second portion of tasks comprises:

assigning the deploying of the data to the secondary storage of the second data center to the first portion of tasks.

3. The system of claim 1 , wherein the second data center comprises compute components, and wherein the operations further comprise:

powering on the compute components in response to determining to restore the first data center to the second data center.

4. The system of claim 3 , wherein a first charge is associated with maintaining the compute components as powered off, wherein a second charge is associated with maintaining the compute components as powered on, and wherein the first charge is less than the second charge.

5. The system of claim 1 , wherein the operations further comprise:

repeatedly populating the primary storage or the secondary storage with updated data from the first data center before determining to restore the first data center to the second data center.

6. The system of claim 1 , wherein the operations further comprise:

in response to determining to restore the first data center to the second data center, determining to provision a first amount of resources for the second data center that corresponds to a used amount of resources of the first data center, wherein the used amount of resources is less than an ordered amount of resources of the first data center.

7. A method, comprising:

maintaining, by a system comprising at least one processor, a first data center that comprises a first instance of a virtualized overlay network that abstracts physical network resources and a first instance of a group of virtualized volume identifiers that abstract physical storage volumes, the first data center storing data comprising first instances of a group of virtualized workloads that operate on the first data center;

determining, by the system, a service level agreement associated with providing a second data center as a backup to the first data center;

based on the service level agreement, dividing, by the system, tasks into a first portion of tasks to complete before determining to restore the first data center to the second data center, and a second portion of tasks to perform after determining to restore the first data center and the second data center, wherein the tasks comprise,

deploying the data to a secondary storage of the second data center, wherein the deploying of the data to a secondary storage is assigned to the first portion of tasks,

deploying the data to a primary storage of the second data center, and

configuring the second data center with a second instance of the virtualized overlay network and a second instance of the group of virtualized volume identifiers, wherein the configuring is assigned to the second portion of tasks;

performing the first portion of tasks before determining to restore the first data center to the second data center; and

performing the second portion of tasks in response to determining to restore the first data center to the second data center.

8. The method of claim 7 , wherein deploying the data to the storage of the second data center comprises:

deploying, by the system, the data to a primary storage of the second data center in response to determining to restore the first data center to the second data center.

9. The method of claim 7 , wherein the operations further comprise:

in response to determining that a configuration of the first data center has changed, updating, by the system, the configuring of the second data center.

10. The method of claim 7 , wherein the operations further comprise:

in response to determining that a first amount of resources deployed at the first data center has changed by a first amount, changing, by the system, a second amount of resources deployed at the second data center by a second amount that corresponds to the first amount.

11. The method of claim 7 , further comprising:

activating, by the system, the second instance of the virtualized overlay network and the second instance of the group of virtualized volume identifiers in response to determining to restore the first data center to the second data center.

12. The method of claim 11 , wherein a first charge is associated with maintaining the second instance of the virtualized overlay network and the second instance of the group of virtualized volume identifiers as inactive, wherein a second charge is associated with maintaining the second instance of the virtualized overlay network and the second instance of the group of virtualized volume identifiers as active, wherein the first charge is less than the second charge, and wherein a cost value of a cost data structure is determined as a function of a first measure of inactivity of the second instance of the virtualized overlay network and the second instance of the group of virtualized volume identifiers, and a second measure of activity of the second instance of the virtualized overlay network and the second instance of the group of virtualized volume identifiers.

13. The method of claim 7 , wherein the service level agreement indicates a recovery time objective of restoring the first data center to the second data center.

14. A non-transitory computer-readable medium comprising instructions that, in response to execution, cause a system comprising at least one processor to perform operations, comprising:

determining a service level agreement associated with providing a second data center as a backup to a first data center, wherein the first data center comprises a first instance of a virtualized overlay and a first instance of a group of virtualized volume identifiers that abstract physical storage volumes;

based on the service level agreement, dividing, by the system, tasks into a first portion of tasks to complete before determining to restore the first data center to the second data center, and a second portion of tasks to perform after determining to restore the first data center and the second data center, wherein the dividing comprises,

assigning deploying the data to a secondary storage of the second data center to the first portion of tasks, and

assigning configuring the second data center with a second instance of the virtualized overlay network and a second instance of the group of virtualized volume identifiers to the second portion of tasks;

performing the first portion of tasks before determining to restore the first data center to the second data center; and

performing the second portion of tasks in response to determining to restore the first data center to the second data center.

15. The non-transitory computer-readable medium of claim 14 , wherein pre-deploying the second data center comprises:

over-provisioning hardware resources of the second data center.

16. The non-transitory computer-readable medium of claim 15 , wherein the over-provisioning comprises:

maintaining a group of hardware for restorations of multiple data centers that comprises the first data center; and

allocating at least a portion of the group of hardware to the first data center in response to determining to restore the first data center to the second data center.

17. The non-transitory computer-readable medium of claim 15 , wherein the over-provisioning comprises:

over-provisioning a first storage resource that is not pre-filled; and

determining to omit over-provisioning a second storage resource that is pre-filled.

18. The non-transitory computer-readable medium of claim 14 , wherein the dividing of the tasks into the first portion of tasks and the second portion of tasks comprises:

assigning the deploying of the data to the secondary storage of the second data center to the first portion of tasks.

19. The non-transitory computer-readable medium of claim 14 , wherein the second data center comprises compute components, and wherein the operations further comprise:

powering on the compute components in response to determining to restore the first data center to the second data center.

20. The non-transitory computer-readable medium of claim 19 , wherein a first charge is associated with maintaining the compute components as powered off, wherein a second charge is associated with maintaining the compute components as powered on, and wherein the first charge is less than the second charge.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 10, 2025
From: SHEMER, JEHUDA; LOTOSH, VALERIE; SHARVIT, EREZ
To: EMC IP HOLDING COMPANY LLC
Reel/Frame 070170/0411 →
Continuity (1)
Related Publication 20230127061A1 · Apr 27, 2023
References Cited (31)
US 8966475B2 · Srinivasan · 2015 [cited by applicant]
US 11875191B1 · Plenderleith et al. · 2024 [cited by applicant]
US 20030028729A1 · Yamamoto et al. · 2003 [cited by applicant]
US 20030126327A1 · Pesola et al. · 2003 [cited by applicant]
US 20050193245A1 · Hayden et al. · 2005 [cited by applicant]
US 20090172816A1 · Maino et al. · 2009 [cited by applicant]
US 20100049823A1 · Saigo et al. · 2010 [cited by applicant]
US 20120192006A1 · Qi et al. · 2012 [cited by applicant]
US 20140215272A1 · Bauer et al. · 2014 [cited by applicant]
US 20150074447A1 · Park et al. · 2015 [cited by applicant]
US 20150169417A1 · Brandwine et al. · 2015 [cited by applicant]
US 20150331753A1 · Nakajima et al. · 2015 [cited by applicant]
US 20150347221A1 · Anderson et al. · 2015 [cited by applicant]
US 20160062858A1 · Gallagher et al. · 2016 [cited by applicant]
US 20160119202A1 · Iyer et al. · 2016 [cited by applicant]
US 20170242758A1 · Chou et al. · 2017 [cited by applicant]
US 20180365117A1 · Basham · 2018 [cited by examiner]
US 20190163763A1 · Pandey et al. · 2019 [cited by applicant]
US 20190243725A1 · Bade et al. · 2019 [cited by applicant]
US 20200409803A1 · Naidu · 2020 [cited by examiner]
US 20210281642A1 · Padiyar et al. · 2021 [cited by applicant]
US 20210342237A1 · Polimera et al. · 2021 [cited by applicant]
US 20220229685A1 · Helvey et al. · 2022 [cited by applicant]
US 20230125085A1 · Shemer et al. · 2023 [cited by applicant]
US 20230128370A1 · Shemer et al. · 2023 [cited by applicant]
US 20230130897A1 · Shemer et al. · 2023 [cited by applicant]
Office Action mailed Aug. 3, 2023 for U.S. Appl. No. 17/507,661, 52 pages. [cited by applicant]
Notice of Allowance mailed Feb. 8, 2024 for U.S. Appl. No. 17/507,661, 46 pages. [cited by applicant]
Office Action mailed Jun. 4, 2024 for U.S. Appl. No. 17/507,656, 25 pages. [cited by applicant]
Notice of Allowance mailed Sep. 12, 2024 for U.S. Appl. No. 17/507,656, 25 pages. [cited by applicant]
Office Action mailed Dec. 4, 2024 for U.S. Appl. No. 17/507,672, 37 pages. [cited by applicant]