Systems and methods for disaster recovery using a cloud-based data center

Patent metadata

Field	Value
Publication number	US-10528433-B2
Application number	US-201715477320-A
Country	US
Kind code	B2
Filing date	Apr 3, 2017
Priority date	Apr 1, 2016
Publication date	Jan 7, 2020
Grant date	Jan 7, 2020

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.

First claim

What is claimed is:

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 at least one pair of a recovery point objective (RPO) and a recovery time objective (RTO) parameters, wherein, the pair of parameters is defined for a type of disaster, 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.

2. The method of claim 1 , further comprising:
a) in response to an occurrence of the disaster associated with the pair of RPO and RTO parameters, 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.

3. 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.

4. 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.

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

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

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

8. 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.

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 at least one pair of a recovery point objective (RPO) and a recovery time objective (RTO) parameters, wherein, the pair of parameters is defined for a type of disaster, 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; and
replicate 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.

10. 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 pair of RPO and RTO parameters, 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.

11. 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.

12. 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.

13. 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.

14. 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 additional pair of RPO and RTO parameters is associated with a different type of disaster.

15. 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.

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

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 at least one pair of a recovery point objective (RPO) and a recovery time objective (RTO) parameters, wherein, the pair of parameters is defined for a type of disaster, 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.

18. The non-transitory compu

Assignees

• Acronis Int Gmbh

Inventors

• Protasov Stanislav
• Beloussov Serguei M
• Shmulevich Mark
• Kochegarov Mikhail
• Danilov Alexey

Classifications

• G06F16/184

  implemented as replicated file system · CPC title

• H04L67/1095

  Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes · CPC title

• H04L41/0663

  Performing the actions predefined by failover planning, e.g. switching to standby network elements · CPC title

• H04L69/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) · CPC title

• G06F16/27

  Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor · CPC title