# US 2017/0286236 A1 · Systems and methods for disaster recovery using a cloud-based data center

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2017/0286236 A1
- Document ID: US20170286236A1
- Status: Published application
- Kind: A1
- Application number: 15/477,320
- Filed: 2017-04-03
- Published: 2017-10-05
- Earliest claimed: 2016-04-01
- Assignees: Acronis International GmbH
- Applicants: Acronis International GmbH
- Inventors: STANISLAV PROTASOV; SERGUEI M. BELOUSSOV; MARK SHMULEVICH; MIKHAIL KOCHEGAROV; ALEXEY DANILOV
- Web page: https://patentgrep.com/patent/US20170286236A1

## CPC

- H04L 41/08: Configuration management of networks or network elements (address allocation H04L61/50)
- G06F 11/1464: {for networked environments}
- G06F 16/184: {implemented as replicated file system}
- G06F 16/27: Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- H04L 12/4641: {Virtual LANs, VLANs, e.g. virtual private networks [VPN] (LAN interconnection over a bridge based backbone H04L12/462; encapsulation techniques H04L12/4633; routing of packets H04L45/00; packet switches H04L49/00; virtual private networks for security H04L63/0272)}
- H04L 41/0663: Performing the actions predefined by failover planning, e.g. switching to standby network elements
- H04L 41/0895: Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
- H04L 41/40: using virtualisation of network functions or resources, e.g. SDN or NFV entities
- H04L 63/0272: {Virtual private networks}
- H04L 67/1095: Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
- H04L 69/40: for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection (management of faults, events, alarms or notifications in data switching networks H04L41/06)
- G06F 2201/84: Using snapshots, i.e. a logical point-in-time copy of the data
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A cloud-based disaster recovery service solution is provided. The disaster recovery provides cloud-based backup services that maintain local and off-site backups that may be activated on demand for backup purposes, or for full-site disaster recovery. The cloud-based data center may be configured to perform this backup and recovery process in a secure way, while protecting individual client environments from each other, and protecting the backup and recovery operations environment from the individual client environments.

## Claims

### Claim 1

A method for replicating and restoring a client's network infrastructure, comprising:
determining a client's network configurations;
creating a backup of at least one of the client's databases;
identifying at least one physical or virtual server within the client's network infrastructure;
defining a recovery point objective (RPO) and a recovery time objective (RTO), wherein the RPO indicates a time-point of a latest backup and replication prior to a disaster and the RTO indicates a time-point when the client's infrastructure is to be restored from the client's personal cloud after the disaster;
allocating a client's personal cloud at a cloud-based data center;
backing up the client's databases to the client's personal cloud; and
replicating the previously identified physical or virtual servers, and the client's network configurations, on the client's personal cloud;
wherein the disaster comprises an event that results in the physical destruction or inoperability of at least a portion of the client's network infrastructure.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
a) in response to an occurrence of the disaster associated with the RPO and RTO, restoring the client's replicated infrastructure at the RTO time-point; or
b) restoring the client's replicated infrastructure prior to the RTO in response to a request from the client for a manual restoration.

### Claim 3 (depends on 1)

The method of claim 1, further comprising:
a) identifying client data on the identified at least one physical or virtual server; and
b) replicating the client data on the client's personal cloud.

### Claim 4 (depends on 1)

The method of claim 1, wherein the replication of the client's network configurations comprise replication of one or more of the following:
a) server connections of the one or more identified servers;
b) an order of activation of the one or more identified servers;
c) at least one router's configuration;
d) at least one spam filter; and
e) at least one hardware or virtual firewall.

### Claim 5 (depends on 4)

The method of claim 4, further comprising replicating an order of recovery of the one or more identified servers.

### Claim 6 (depends on 1)

The method of claim 1, further comprising: defining at least one additional pair of RPO and RTO parameters, wherein each pair of RPO and RTO parameters is associated with a different type of disaster.

### Claim 7 (depends on 1)

The method of claim 1, further comprising creating a virtual private network (VPN) between the client's network infrastructure and the client's personal cloud.

### Claim 8 (depends on 7)

The method of claim 7, further comprising using the VPN for the backup and replication of the client's network infrastructure, and optionally for backup and replication of client data on the one or more identified servers.

### Claim 9

A system for replicating and restoring a client's network infrastructure, comprising:
a cloud-based data center; and
a processor configured to:
determine a client's network configurations;
create a backup of at least one of the client's databases;
identify at least one physical or virtual server within the client's network infrastructure;
define a recovery point objective (RPO) and a recovery time objective (RTO), wherein the RPO indicates a time-point of a latest backup and replication prior to a disaster and the RTO indicates a time-point when the client's infrastructure is to be restored from the client's personal cloud after the disaster;
allocate a client's personal cloud at a cloud-based data center;
back up the client's databases to the client's personal cloud;
replicate the previously identified physical or virtual servers, and the client's network configurations, on the client's personal cloud; and
wherein the disaster comprises an event that results in the physical destruction or inoperability of at least a portion of the client's network infrastructure.

### Claim 10 (depends on 9)

The system for replicating and restoring a client's network infrastructure of claim 9, wherein the processor is further configured to:
a) in response to an occurrence of the disaster associated with the RPO and RTO, restore the client's replicated infrastructure at the RTO time-point; or
b) restore the client's replicated infrastructure prior to the RTO in response to a request from the client for a manual restoration.

### Claim 11 (depends on 9)

The system for replicating and restoring a client's network infrastructure of claim 9, wherein the processor is further configured to:
a) identify client data on the identified at least one physical or virtual server; and
b) replicate the client data on the client's personal cloud.

### Claim 12 (depends on 9)

The system for replicating and restoring a client's network infrastructure of claim 9, wherein the replication of the client's network
configurations comprise replication of one or more of the following:
a) server connections of the one or more identified servers;
b) an order of activation of the one or more identified servers;
c) at least one router's configuration;
d) at least one spam filter; and
e) at least one hardware or virtual firewall.

### Claim 13 (depends on 12)

The system for replicating and restoring a client's network infrastructure of claim 12, wherein the processor is further configured to: replicate an order of recovery of the one or more identified servers.

### Claim 14 (depends on 9)

The system for replicating and restoring a client's network infrastructure of claim 9, wherein the processor is further configured to: define at least one additional pair of RPO and RTO parameters, wherein each pair of RPO and RTO parameters is associated with a different type of disaster.

### Claim 15 (depends on 9)

The system for replicating and restoring a client's network infrastructure of claim 9, wherein the processor is further configured to: create a virtual private network (VPN) between the client's network infrastructure and the client's personal cloud.

### Claim 16 (depends on 15)

The system for replicating and restoring a client's network infrastructure of claim 15, wherein the processor is further configured to: use the VPN for the backup and replication of the client's network infrastructure, and optionally for backup and replication of client data on the one or more identified servers.

### Claim 17

A non-transitory computer readable medium is provided for replicating and restoring a client's network infrastructure that comprises computer-executable instructions for:
determining a client's network configurations;
creating a backup of at least one of the client's databases;
identifying at least one physical or virtual server within the client's network infrastructure;
defining a recovery point objective (RPO) and a recovery time objective (RTO), wherein the RPO indicates a time-point of a latest backup and replication prior to a disaster and the RTO indicates a time-point when the client's infrastructure is to be restored from the client's personal cloud after the disaster;
allocating a client's personal cloud at a cloud-based data center;
backing up the client's databases to the client's personal cloud;
replicating the previously identified physical or virtual servers, and the client's network configurations, on the client's personal cloud; and
wherein the disaster comprises an event that results in the physical destruction or inoperability of at least a portion of the client's network infrastructure.

### Claim 18 (depends on 17)

The non-transitory computer readable medium of claim 17, further comprising computer-executable instructions for:
a) in response to an occurrence of the disaster associated with the RPO and RTO, restoring the client's replicated infrastructure at the RTO time-point; or
b) restoring the client's replicated infrastructure prior to the RTO in response to a request from the client for a manual restoration.

### Claim 19 (depends on 17)

The non-transitory computer readable medium of claim 17, further comprising computer-executable instructions for:
a) identifying client data on the identified at least one physical or virtual server; and
b) replicating the client data on the client's personal cloud.

### Claim 20 (depends on 17)

The non-transitory computer readable medium of claim 17, wherein the replication of the client's network configurations comprise replication of one or more of the following:
a) server connections of the one or more identified servers;
b) an order of activation of the one or more identified servers;
c) at least one router's configuration;
d) at least one spam filter; and
e) at least one hardware or virtual firewall.