IP Library › Granted Patent US 12,541,386
Granted Patent B2
US 12,541,386 · App. 17/507,672 · Granted Feb 3, 2026

Distributed data center

Inventors: Jehuda Shemer (Kfar Saba, IL); Valerie Lotosh (Ramat-Gan, IL); Erez Sharvit (Ramat-Gan, IL)
Assignee: EMC IP Holding Company LLC
G06F9/45558G06F2009/45579G06F2009/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,541,386
App. No.
17/507,672
Granted
Feb 3, 2026
Kind
B2
Abstract

A system can maintain a first data center in a first physical location that comprises first compute hardware, and a second data center in a second physical location that comprises second compute hardware. The system can establish an overlay network that spans the first data center and the second data center. The system can establish a group of virtualized volume identifiers that spans the first data center and the second data center, and that virtualizes physical storage volumes. The system can determine whether to process a customer virtualized workload on the first data center or on the second data center to produce a selected location, wherein the customer virtualized workload is configured to be processed on the first data center and to be processed on the second data center. The system can process the customer virtualized workload at the selected location.

Claims (42)

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 in a first physical location that comprises first compute hardware;

maintaining a second data center in a second physical location that comprises second compute hardware;

establishing an overlay network that spans the first data center and the second data center, and that virtualizes physical network resources of the first data center and the second data center;

establishing a group of virtualized volume identifiers that spans the first data center and the second data center, and that virtualizes physical storage volumes of the first data center and the second data center;

determining whether to process a first customer virtualized workload on the first data center or on the second data center to produce a selected location that identifies one of the first data center or the second data center, wherein the first customer virtualized workload is configured to be processed on one data center at a time of the first data center or on the second data center, wherein the first customer virtualized workload is configured to be processed on the first data center independently of the second data center, and wherein the first customer virtualized workload is configured to be processed on the second data center independently of the first data center;

processing the first customer virtualized workload at the selected location, wherein the first customer virtualized workload accesses physical storage volumes of the selected location by referencing the virtualized volume identifiers, and wherein respective virtualized volume identifiers of the virtualized volume identifiers differ from respective physical storage volume identifiers of the physical storage volumes; and

in response to determining that a first rate at which the first customer virtualized workload and a second customer virtualized workload call each other via application programming interface calls satisfies a first frequency criterion, or that a second rate at which the first customer virtualized workload and the second customer virtualized workload access a same database satisfies a second frequency criterion, running the second customer virtualized workload at the selected location.

2 . The system of claim 1 , wherein the first data center and the second data center are active concurrently.

3 . The system of claim 1 , wherein the first data center has a first group of processing capabilities, wherein the second data center has a second group of processing capabilities, and wherein the first group of processing capabilities differs from the second group of processing capabilities.

4 . The system of claim 1 , wherein the first data center comprises storage resources, and wherein the second data center omits the storage resources.

5 . The system of claim 1 , wherein the determining that the first rate at which the first customer virtualized workload and a second customer virtualized workload call each other via the application programming interface calls satisfies the first frequency criterion, or that the second rate at which the first customer virtualized workload and the second customer virtualized workload access the same database satisfies the second frequency criterion comprises determining that the second customer virtualized workload shares an affinity with the first customer virtualized workload, and wherein the operations further comprise:

obtaining, from a cloud management platform that is separate from the first data center and the second data center, information that indicates that the second customer virtualized workload shares the affinity with the first customer virtualized workload.

6 . The system of claim 5 , wherein the cloud management platform determined the affinity based on communicating with a virtualization management component operated by the first data center and the second data center.

7 . The system of claim 1 , wherein respective virtualized volume identifiers of the virtualized volume identifiers comprise respective worldwide names.

8 . The system of claim 1 , wherein the virtualized volume identifiers spoof the physical storage volume identifiers.

9 . A method, comprising:

maintaining, by a system comprising at least one processor, a first data center and a second data center;

facilitating, by the system, establishing an overlay network that spans the first data center and the second data center;

facilitating, by the system, establishing virtualized volume identifiers that span the first data center and the second data center, and that virtualize physical storage volumes of the first data center and the second data center;

determining, by the system, whether to execute a first customer virtualized workload on the first data center or on the second data center to produce a selected location that identifies one of the first data center or the second data center, wherein the first customer virtualized workload is configured to be executed on the first data center independently of the second data center, and wherein the customer virtualized workload is configured to be executed on the second data center independently of the first data center;

executing, by the system, the first customer virtualized workload at the selected location, wherein the first customer virtualized workload accesses selected physical storage volumes of the selected location by referencing the virtualized volume identifiers, and wherein respective virtualized volume identifiers of the virtualized volume identifiers differ from respective physical storage volume identifiers of the physical storage volumes; and

in response to determining that a first rate at which the first customer virtualized workload and a second customer virtualized workload call each other via application programming interface calls satisfies a first frequency criterion, or that a second rate at which the first customer virtualized workload and the second customer virtualized workload access a same database satisfies a second frequency criterion, executing, by the system, the second customer virtualized workload at the selected location.

10 . The method of claim 9 , wherein the first data center and the second data center are part of a group of data centers that comprises at least two data centers, and wherein the group of data centers are presented as a unified data center to a customer account.

11 . The method of claim 9 , wherein a cloud management platform is separate from the first data center and the second data center, and wherein the cloud management platform manages the first data center and the second data center.

12 . The method of claim 9 , wherein the first data center comprises primary storage and secondary storage.

13 . The method of claim 9 , wherein portions of respective computing resources of the first data center and the second data center are reserved for individual customers.

14 . The method of claim 9 , wherein the overlay network abstracts physical network resources of the first data center and the second data center.

15 . The method of claim 9 , wherein the determining that the first rate at which the first customer virtualized workload and the second customer virtualized workload call each other via application programming interface calls satisfies the first frequency criterion, or that the second rate at which the first customer virtualized workload and the second customer virtualized workload access the same database satisfies the second frequency criterion comprises determining that the second customer virtualized workload shares an affinity with the first customer virtualized workload, and further comprising:

obtaining, by the system and from a cloud management platform that is separate from the first data center and the second data center, information that indicates that the second customer virtualized workload shares the affinity with the first customer virtualized workload.

16 . 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:

creating an overlay network that spans a first data center and a second data center;

creating a group of virtualized volume identifiers that spans the first data center and the second data center, and that virtualize physical storage volumes of the first data center and the second data center;

determining whether to run a first customer virtualized workload on the first data center or on the second data center to produce a selected location that identifies one of the first data center or the second data center, wherein the first customer virtualized workload is configured to run on the first data center independently of the second data center, or wherein the first customer virtualized workload is configured to run on the second data center independently of the first data center;

running the first customer virtualized workload at the selected location, wherein the first customer virtualized workload accesses selected physical storage volumes of the selected location by referencing the virtualized volume identifiers, and wherein respective virtualized volume identifiers of the virtualized volume identifiers differ from respective physical storage volume identifiers of the physical storage volumes; and

in response to determining that a first rate at which the first customer virtualized workload and a second customer virtualized workload call each other via application programming interface calls satisfies a first frequency criterion, or that a second rate at which the first customer virtualized workload and the second customer virtualized workload access a same database satisfies a second frequency criterion, running the second customer virtualized workload at the selected location.

17 . The non-transitory computer-readable medium of claim 16 , wherein the overlay network provides an abstraction between respective virtualized network resources and respective physical network resources of the first data center and the second data center, and wherein the customer virtualized workload accesses the physical network resources by referencing the virtualized network resources.

18 . The non-transitory computer-readable medium of claim 16 , wherein the first data center has a first group of hardware capabilities, wherein the second data center has a second group of hardware capabilities, and wherein the first group of hardware capabilities differs from the second group of hardware capabilities.

19 . The non-transitory computer-readable medium of claim 16 , wherein the first data center, the second data center, and at least a third data center are part of a distributed data center, wherein the overlay network spans the distributed data center, and wherein the virtualized volume identifiers span the distributed data center.

20 . The non-transitory computer-readable medium of claim 16 , wherein a first system architecture of the first data center differs from a second system architecture of the second data center.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 13, 2025
From: SHEMER, JEHUDA; LOTOSH, VALERIE; SHARVIT, EREZ
To: EMC IP HOLDING COMPANY LLC
Reel/Frame 071101/0569 →
Continuity (1)
Related Publication 20230130897A1 · Apr 27, 2023
References Cited (35)
US 8966475B2 · Srinivasan · 2015 [cited by applicant]
US 10671431B1 · Dolan · 2020 [cited by examiner]
US 11875191B1 · Plenderleith · 2024 [cited by examiner]
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 et al. · 2018 [cited by applicant]
US 20190163763A1 · Pandey et al. · 2019 [cited by applicant]
US 20190243725A1 · Bade et al. · 2019 [cited by applicant]
US 20190332275A1 · Jin · 2019 [cited by examiner]
US 20200409803A1 · Naidu et al. · 2020 [cited by applicant]
US 20210034265A1 · Abouelwafa · 2021 [cited by examiner]
US 20210281642A1 · Padiyar · 2021 [cited by examiner]
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 20230127061A1 · Shemer et al. · 2023 [cited by applicant]
US 20230128370A1 · Shemer et al. · 2023 [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]
Office Action mailed Aug. 3, 2023 for U.S. Appl. No. 17/507,661, 52 pages. [cited by applicant]
Notice of Allowance mailed Feb. 11, 2025 for U.S. Appl. No. 17/507,664, 28 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 Sep. 27, 2024 for U.S. Appl. No. 17/507,664, 47 pages. [cited by applicant]