IP Library Granted Patent US 10,284,437
Granted Patent B2
US 10,284,437 · App. 15/360,836 · Granted May 7, 2019

Cloud-based virtual machines and offices

Inventors: Todd Scallan (Los Gatos, CA); Shravya Yelisetti (Sunnyvale, CA); Saurabh Modh (San Jose, CA); Vlad Ananyev (Smolensk, RU); Leonid Kornilenko (Santa Clara, CA); William Scott Edwards (San Jose, CA)
Assignee: eFOLDER, INC.
H04L41/5051G06F11/1464G06F11/1484G06F11/203H04L41/5058H04L63/0272H04L67/10H04L69/40G06F11/2023G06F2009/4557G06F2009/45595G06F2201/84G06F2201/85H04L41/5096H04L61/1511H04L61/2015
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,284,437
App. No.
15/360,836
Granted
May 7, 2019
Kind
B2
Abstract

Cloud-based virtual machines and offices are provided herein. Methods may include establishing a cloud-based virtual office using a runbook that is pre-configured with computing resource settings for VMs as well as VM dependencies and sequences that create the virtual office or virtual private cloud. Multiple runbooks can be created to cover various scenarios such as disaster recovery and sandbox testing, by example.

Claims (50)

1. A method, comprising:

selecting one or more virtual machines for which configurations will be included in a runbook, the runbook being used to establish a virtual office;

selecting, for each of the one or more virtual machines, computing device configurations;

specifying a dependency between at least two of the one or more virtual machines, the dependency comprising a hierarchical relationship between the at least two of the one or more virtual machines that corresponds to an order in which to start the at least two of the one or more virtual machines;

generating the runbook that comprises the computing device configurations and the dependency;

storing the runbook in a replication system;

receiving a request to use the runbook, wherein the request comprises a selection of a recovery method from any of a data restore, an archive restore, a disaster recover test, a disaster recovery production failover, and a test and development environment;

instantiating the at least two of the one or more virtual machines by dedicating computing resources to the at least two of the one or more virtual machines using the computing device configurations and the dependency to create the virtual office; and

providing access to the virtual office to a user.

2. The method according to claim 1 , further comprising deleting the runbook when the virtual office is terminated by the user.

3. The method according to claim 1 , wherein the request is generated automatically upon occurrence of a failover event.

4. The method according to claim 1 , further comprising:

selecting the runbook;

instantiating the at least two of the one or more virtual machines by dedicating computing resources to the at least two of the one or more virtual machines using the computing device configurations and the dependency; and

providing access to the at least two of the one or more virtual machines to a user.

5. The method according to claim 1 , further comprising establishing any of:

a virtual private network selection;

port forwarding; and

a site-to-site virtual private network settings.

6. The method according to claim 5 , wherein the virtual private network selection comprises any of:

a split tunneling selection;

a site gateway Internet protocol address; and

a site netmask.

7. The method according to claim 5 , wherein the site-to-site virtual private network settings comprises any of:

an endpoint name;

a public Internet protocol address;

a gateway;

a netmask; and

endpoint Internet protocol address.

8. The method according to claim 1 , further comprising:

calculating the priority level; and

ranking the at least two of the one or more virtual machines based on calculated priority levels.

9. The method according to claim 1 , further comprising establishing a priority level for the at least two of the one or more virtual machines, wherein the runbook further comprises the priority level.

10. A method, comprising:

evaluating a network topology of a target network, the network topology defining:

dependencies of computing devices; and

computing device configurations of the computing devices;

generating a runbook from the network topology, the runbook comprising: a) an identification of the computing devices to be replicated as virtual machines of a virtual private cloud; b) one or more subnets, where each of the virtual machines is assigned to the one or more subnets; and c) computing device configurations for each of the virtual machines that comprise dependencies between the virtual machines that define an order in which to start the virtual machines, wherein the computing device configurations for each of the virtual machines comprise the computing device configurations of the computing devices and the dependencies between the virtual machines comprise the dependencies of the computing devices;

receiving a request to execute the runbook to establish the virtual private cloud;

executing the runbook to establish the virtual private cloud;

obtaining restore points the virtual machines, the restore points being associated with the computing devices;

preparing the virtual private cloud by establishing the virtual machines using the restore points and the computing device configurations in the runbook; and

providing access to the virtual private cloud to a user.

11. The method according to claim 10 , wherein a first portion of the virtual machines are assigned to a first subnet of the one or more subnets and a second portion of the virtual machines are assigned to a second subnet of the one or more subnets.

12. The method according to claim 10 , further comprising:

terminating the virtual private cloud; and

executing a second runbook to establish a second virtual private cloud, wherein the second virtual private comprises subnet configurations copied from prior execution of the runbook.

13. The method according to claim 10 , further comprising applying wait times for establishing one or more of the virtual machines.

14. The method according to claim 10 , wherein the one or more subnets each define a network boundary based on security attributes.

15. The method according to claim 10 , wherein the restore points are selected based on a user-selected date.

Assignments (14)
INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded Feb 19, 2025
From: SKYKICK, LLC; EFOLDER, INC.
To: BANK OF AMERICA, N.A.
Reel/Frame 070268/0489 →
RELEASE OF SECURITY INTEREST Recorded Sep 24, 2024
From: U.S. BANK NATIONAL ASSOCIATION FORMERLY MUFG UNION BANK, N.A.
To: EFOLDER, INC.
Reel/Frame 068680/0802 →
RELEASE OF SECURITY INTEREST Recorded Nov 2, 2022
From: WELLS FARGO BANK, NATIONAL ASSOCIATION
To: EFOLDER, INC.
Reel/Frame 061634/0623 →
SECURITY INTEREST Recorded Oct 27, 2022
From: EFOLDER, INC.
To: MUFG UNION BANK, N.A.
Reel/Frame 061559/0703 →
SECURITY INTEREST Recorded Jan 8, 2018
From: EFOLDER, INC.
To: WELLS FARGO BANK, NATIONAL ASSOCIATION, AS AGENT
Reel/Frame 044563/0633 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 12, 2017
From: AXCI (AN ABC) LLC
To: AXCIENT HOLDINGS, LLC
Reel/Frame 044368/0556 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 12, 2017
From: AXCIENT HOLDINGS, LLC
To: EFOLDER, INC.
Reel/Frame 044370/0412 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 12, 2017
From: AXCIENT, INC.
To: AXCI (AN ABC) LLC
Reel/Frame 044367/0507 →
RELEASE OF SECURITY INTEREST Recorded Oct 11, 2017
From: STRUCTURED ALPHA LP
To: AXCIENT, INC.
Reel/Frame 043840/0227 →
RELEASE OF SECURITY INTEREST Recorded Jul 26, 2017
From: SILVER LAKE WATERMAN FUND, L.P.
To: AXCIENT, INC.
Reel/Frame 043106/0389 →
SECURITY INTEREST Recorded Jun 2, 2017
From: AXCIENT, INC.
To: SILVER LAKE WATERMAN FUND, L.P.
Reel/Frame 042577/0901 →
SECURITY INTEREST Recorded May 31, 2017
From: AXCIENT, INC.
To: STRUCTURED ALPHA LP
Reel/Frame 042542/0364 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 21, 2017
From: EDWARDS, WILLIAM SCOTT
To: AXCIENT, INC.
Reel/Frame 041669/0171 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 7, 2016
From: SCALLAN, TODD; YELISETTI, SHRAVYA; MODH, SAURABH; ANANYEV, VLAD; KORNILENKO, LEONID
To: AXCIENT, INC.
Reel/Frame 040594/0218 →
Continuity (4)
Continuation In Part 14971832 · Dec 16, 2015
Continuation 14564082 · Dec 8, 2014
Continuation 13570161 · Aug 8, 2012
Related Publication 20170075719A1 · Mar 16, 2017
Cited By (2)
US 12,271,287 US 12,530,645