Crash recovery of vRPA cluster protection engine
One example method includes, in response to a crash event, obtaining data protection system credentials, accessing a target storage of the data protection system, obtaining, from the target storage, a configuration file including configuration information for a data protection cluster, and using, by the data protection cluster, the configuration information to self-configure. The method further includes creating a consistency group (CG) of a group of volume, and restoring a journal volume to append backup indexes.
1. A method, comprising:
performing, by a data protection cluster that includes a plurality of nodes, a self-recovery process, and the self-recovery process comprises:
detecting, by the data protection cluster, a crash of the data protection cluster, and in response to the detecting, obtaining, by the data protection cluster, data protection system credentials that were created during an initial data protection cluster node deployment;
after obtaining the data protection system credentials, using, by the data protection cluster, the data protection system credentials to access a target storage of the data protection system;
based on an IP address of the data protection cluster, obtaining, by the data protection cluster from the target storage, a configuration file that includes configuration information about a configuration of the data protection cluster;
using, by the data protection cluster, the configuration information to self-configure the data protection cluster so that, once self-configured, the data protection cluster is restored from a crashed state to a fully operational state, and the configuration information used by the data protection cluster to self-configure itself comprises an IP (Internet Protocol) address of the data protection cluster, a cluster name of the data protection cluster, and a cluster ID of the data protection cluster;
creating, by the data protection cluster, a consistency group (CG) of a plurality of volumes; and
restoring, by the data protection cluster, a journal volume to append backup indexes.
2. The method as recited in claim 1 , wherein backups of data from one or more nodes of the data protection cluster reside in the target storage.
3. The method as recited in claim 1 , wherein the plurality of volumes in the CG are crash-consistent copies.
4. The method as recited in claim 1 , wherein obtaining the configuration information comprises iterating through a plurality of configuration files that reside in the target storage and selecting a configuration file that includes an Internet Protocol (IP) address that matches an IP address of the data protection cluster.
5. The method as recited in claim 1 , wherein the volumes in the CG each correspond to a respective virtual machine (VM) backup that resides in the target storage, and the VM backups are in a consistent state at the time of the crash.
6. The method as recited in claim 1 , wherein the method is performed automatically upon detection of the crash event.
7. The method as recited in claim 1 , wherein creating a consistency group (CG) of a plurality of volumes comprises retrieving a CG name and CG ID from another configuration file.
8. The method as recited in claim 1 , wherein the configuration file and backups of data from one or more nodes of the data protection cluster are stored in the same Mtree.
9. A non-transitory storage medium having stored therein computer-executable instructions which, when executed by one or more hardware processors, perform the following operations:
performing, by a data protection cluster that includes a plurality of nodes, a self-recovery process, and the self-recovery process comprises:
detecting, by the data protection cluster, a crash of the data protection cluster, and in response to the detecting, obtaining, by the data protection cluster, data protection system credentials that were created during an initial data protection cluster node deployment;
after obtaining the data protection system credentials, using, by the data protection cluster, the data protection system credentials to access a target storage of the data protection system;
based on an IP address of the data protection cluster, obtaining, by the data protection cluster from the target storage, a configuration file that includes configuration information about a configuration of the data protection cluster;
using, by the data protection cluster, the configuration information to self-configure itself the data protection cluster so that, once self-configured, the data protection cluster is restored from a crashed state to a fully operational state, and the configuration information used by the data protection cluster to self-configure itself comprises an IP (Internet Protocol) address of the data protection cluster, a cluster name of the data protection cluster, and a cluster ID of the data protection cluster;
creating, by the data protection cluster, a consistency group (CG) of a plurality of volumes; and
restoring, by the data protection cluster, a journal volume to append backup indexes.
10. The non-transitory storage medium as recited in claim 9 , wherein backups of data from one or more nodes of the data protection cluster reside in the target storage.
11. The non-transitory storage medium as recited in claim 9 , wherein the plurality of volumes in the CG are crash-consistent copies.
12. The non-transitory storage medium as recited in claim 9 , wherein obtaining the configuration information comprises iterating through a plurality of configuration files that reside in the target storage and selecting a configuration file that includes an Internet Protocol (IP) address that matches an IP address of the data protection cluster.
13. The non-transitory storage medium as recited in claim 9 , wherein the volumes in the CG each correspond to a respective virtual machine (VM) backup that resides in the target storage, and the VM backups are in a consistent state at the time of the crash.
14. The non-transitory storage medium as recited in claim 9 , wherein the method is performed automatically upon detection of the crash event.
15. The non-transitory storage medium as recited in claim 9 , wherein creating a consistency group (CG) of a plurality of volumes comprises retrieving a CG name and CG ID from another configuration file.
16. The non-transitory storage medium as recited in claim 9 , wherein the configuration file and backups of data from one or more nodes of the data protection cluster are stored in the same Mtree.