Backup Verification
As what we have discussed in Restoring Backup user guide, one importance of restoring a backup is to verify the backup. Does it comply with standards or comply with your data protection and business continuity? Does it meet with regulatory frameworks (such as GDPR, HIPAA, or US – SOX)? How ready are you when disaster strikes? Are your backups consistent and reliable once the backup is created and ready for restoration? For organizations and companies that has strict compliance and disaster recovery planning, backup verification feature of ClusterControl is helpful.
Backup verification is one of the very important process when managing backups. A successful backup might sound important and useful, but the big question that database administrators cannot determine is, how reliable the backup can be? Is it useful and reliable or is it corrupted? You won’t truly be prepared for a disaster until you can successfully verify and restore the backup on a single node that is completely isolated from your production or pre-production environments, such as UAT or staging — especially when restoring your data becomes imperative.
Verifying backups isn’t just about the data itself — it also involves ensuring that the configuration settings in your backup verification environment align with those in production. This helps confirm that any changes in configuration won’t impact the ability to successfully restore the backup.
This page will help you guide on how to verify and restore your backup to provide you and your organization the sense of actual readiness and true sense of security.
Overview of Backup Verification
ClusterControl's Backup Verification is only available for Enterprise license. It allows you to choose your desired standalone environment that is setup for ClusterControl to communicate and access the server to perform necessary steps for the planned process of verifying backup.
Backup verification in ClusterControl is critical to avoid a false sense of security. In that regard, there are two ways you can achieve to verify your backup:
- You can manually verify existing backups. This is ideal when you want to do the following:
- Restore data to a target node to recover loss data.
- Restore data to a target node to verify the integrity of your data.
- Test and verify if using the data you have can work on a particular server and configuration changes does not damage or put your database server in havoc.
- You can schedula a backup, then automate verifying your backup data either immediately after the backup is done or set an hour-basis up to not less than 24 hours. This is helpful especially if your systems rely heavily on the availability and integrity of data. Usually, this is the preferred method when creating a backup in order to determine that your backup is reliable and useful in the future whenever disaster happens and you need to restore your data immediately.
Support Matrix
Most database clusters supported by ClusterControl include the backup verification feature. For the complete list, checkout below:
Database | Vendor | Topology |
---|---|---|
MySQL | Percona, Oracle | Standalone, replication |
MariaDB | MariaDB | Standalone, replication |
Galera Cluster | MariaDB, Percona | Galera certification-based replication |
PostgreSQL | PostgreSQL, EnterpriseDB | Standalone, streaming replication |
TimescaleDB | TimescaleDB | Standalone, streaming replication |
Redis | Redis | Sentinel |
Elasticsearch | Elastic | Single-node cluster, high availability cluster |
Prerequisites
- Backup should be created using ClusterControl and from an existing cluster.
- Target Backup Verification Server (BVS) should be accessible by ClusterControl controller, same access per OS user on how your database nodes are setup.
- You have sufficient storage space for the target environment. Make sure that the new environment or target nodes has enough disk space to copy and restore the backup. This also includes the BVS.
- Network interoperability between ClusterControl controller and the source cluster where backup was taken.
- Ensure that you have appropriate user permissions and privileges on the target environment. If security kernel modules such as AppArmor or SELinux must be enabled, make sure you have appropriate configuration to allow the operation successful.
- Requires to have a successful backup creation prior to verifying the backup.
- To ensure compatibility, it is recommended that the target BVS environment matches the operating system and version of the source database server where the backup was originally created.
MySQL Replication
The following vendors and versions are supported for backup verification:
- Oracle MySQL - 8.0.
- Percona Server for MySQL - 8.0.
- Percona Server for MySQL Pro - 8.0.
- MariaDB Server - 10.4, 10.5, 10.6 (LTS), 10.11 (LTS) and 11.4 (LTS).
Default Configuration
- Restores backup on a standalone host.
- Backups created using ClusterControl's supported backup method shall be available for restore and backup verification.
- Only successful backups can be listed and can be attempted for restore and backup verification.
- ClusterControl will configure the target Backup Verification Server (BVS) and that covers the database configuration, package repositories, and required package dependencies.
- Install software shall be set to On.
- Disable firewall is enabled.
- Disable SELinux/AppArmor is enabled.
- When Shutdown the server after the backup is restored is checked, the BVS will be terminated when the Verify Backup job finishes. The
datadir
and configuration files will be removed. This also means that Install Software must be specified for the next Verify Backup job to set up thedatadir
and configuration files.
Steps to restore a backup (Backup method: mysqldump)
-
Go to the Clusters dashboard. Choose your target source cluster then click.
-
Go to the Backups tab and make sure you click or set the view to All Backups (default).
-
Choose a backup you would like to restore and click the ellipsis button (...).
-
Select and click Restore option.
-
First step is Configuration.
- Backup: This is selected backup to be restored to the cluster
- Restore this backup from: This is the path or storage location of the backup
- Method: This is a panel view just displays information of the backup information such as backup method, size, when it was created, and host where backup was taken
-
Click Continue.
-
Second step is How to restore.
- Choose Restore and verify on standalone host
-
Click Continue.
-
Third step is Settings.
- Restore backup on: Enter a valid Fully Qualified Domain Name (FQDN) or valid IP-address of your target Backup Verification Server (BVS).
- Temporary directory: The tmpdir is used as temporary storage area for the backup files during restore. Make sure it has enough space or assure you have a bit larger disk space than your datadir total size."
- Install software: Toogle on (default) will instruct ClusterControl to install the database software from the package repository during deployment. Toggling off will skip the database installation part. In some cases, where you have a custom database build or in an offline environment without a proper offline repository set up, you may install the database server packages manually beforehand and set this option to off. ClusterControl will then skip the installation part and proceed to the database configuration part.
- Disable firewall is enabled. Leave check if you need to Disable firewall (default). Otherwise uncheck if you have filtered entry for your firewall.
- Disable SELinux/AppArmor is enabled. Leave check if you need to Disable SELinux/AppArmor. If you have uncheck Disable SELinux/AppArmor, make sure that you have configured properly to allow creating files and opening sockets for the database to run properly.
- Shutdown the server after the backup is restored is set to Off (recommended). When Off, this assures that the database server is accessible and state is online. Its data directory and config files are also intact and packages are retained and not removed/uninstalled. When On, the BVS will be terminated and when the verify backup job finishes, the
datadir
and configuration files will be removed. This means that Install Software must be enabled for the next Verify Backup job to set up thedatadir
and configuration files.
-
Click Continueto proceed the last step Summary.
-
The last step is Summary. This summarizes the action to be taken when restoring the backup to your cluster. This gives you the time to review your actions before executing the restore process.
-
Click Finish button to execute the job.
To be added soon
Steps to restore a backup (Backup method: xtrabackup and mariabackup)
-
Go to the Clusters dashboard. Choose your target source cluster then click.
-
Go to the Backups tab and make sure you click or set the view to All Backups (default).
-
Choose a backup you would like to restore and click the ellipsis button (...).
-
Select and click Restore option.
-
First step is Configuration.
- Backup: This is selected backup to be restored to the cluster
- Incremental backups: Shows up only when there are incremental backups linked to a
mariabackupfull
orxtrabackupfull
backup. This is a drop down element that lists down the incremental backups link to the full backup (xtrabackup
ormariabackup
) - Restore this backup from: This is the path or storage location of the backup
- Method: This is a panel view just displays information of the backup information such as backup method, size, when it was created, and host where backup was taken
-
Click Continue.
-
Second step is How to restore.
- Choose Restore and verify on standalone host
-
Click Continue.
-
Third step is Settings.
- Restore backup on: Enter a valid Fully Qualified Domain Name (FQDN) or valid IP-address of your target Backup Verification Server (BVS).
- Temporary directory: The tmpdir is used as temporary storage area for the backup files during restore. Make sure it has enough space or assure you have a bit larger disk space than your datadir total size."
- Install software: Toogle on (default) will instruct ClusterControl to install the database software from the package repository during deployment. Toggling off will skip the database installation part. In some cases, where you have a custom database build or in an offline environment without a proper offline repository set up, you may install the database server packages manually beforehand and set this option to off. ClusterControl will then skip the installation part and proceed to the database configuration part.
- Disable firewall is enabled. Leave check if you need to Disable firewall (default). Otherwise uncheck if you have filtered entry for your firewall.
- Disable SELinux/AppArmor is enabled. Leave check if you need to Disable SELinux/AppArmor. If you have uncheck Disable SELinux/AppArmor, make sure that you have configured properly to allow creating files and opening sockets for the database to run properly.
- Shutdown the server after the backup is restored is set to Off (recommended). When Off, this assures that the database server is accessible and state is online. Its data directory and config files are also intact and packages are retained and not removed/uninstalled. When On, the BVS will be terminated and when the verify backup job finishes, the
datadir
and configuration files will be removed. This means that Install Software must be enabled for the next Verify Backup job to set up thedatadir
and configuration files.
-
Click Continueto proceed the last step Summary.
-
The last step is Summary. This summarizes the action to be taken when restoring the backup to your cluster. This gives you the time to review your actions before executing the restore process.
-
Click Finish button to execute the job.
To be added soon
MySQL Galera
The following vendors and versions are supported for backup verification:
- Percona XtraDB Cluster - 8.0.
- MariaDB Cluster - 10.4, 10.5, 10.6 (LTS), 10.11 (LTS) and 11.4 (LTS).
Default Configuration
- Restores backup on a standalone host.
- Backups created using ClusterControl's supported backup method shall be available for restore and backup verification
- Only successful backups can be listed and can be attempted for restore and backup verification.
- ClusterControl will configure the target Backup Verification Server (BVS) and that covers the database configuration, package repositories, and required package dependencies.
- Install software shall be set to On.
- Disable firewall is enabled.
- Disable SELinux/AppArmor is enabled.
- When Shutdown the server after the backup is restored is checked, the BVS will be terminated when the Verify Backup job finishes. The
datadir
and configuration files will be removed. This also means that Install Software must be specified for the next Verify Backup job to set up thedatadir
and configuration files.
Steps to restore a backup (Backup method: mysqldump)
-
Go to the Clusters dashboard. Choose your target source cluster then click.
-
Go to the Backups tab and make sure you click or set the view to All Backups (default).
-
Choose a backup you would like to restore and click the ellipsis button (...).
-
Select and click Restore option.
-
First step is Configuration.
- Backup: This is selected backup to be restored to the cluster
- Restore this backup from: This is the path or storage location of the backup
- Method: This is a panel view just displays information of the backup information such as backup method, size, when it was created, and host where backup was taken
-
Click Continue.
-
Second step is How to restore.
- Choose Restore and verify on standalone host
-
Click Continue.
-
Third step is Settings.
- Restore backup on: Enter a valid Fully Qualified Domain Name (FQDN) or valid IP-address of your target Backup Verification Server (BVS).
- Temporary directory: The tmpdir is used as temporary storage area for the backup files during restore. Make sure it has enough space or assure you have a bit larger disk space than your datadir total size."
- Install software: Toogle on (default) will instruct ClusterControl to install the database software from the package repository during deployment. Toggling off will skip the database installation part. In some cases, where you have a custom database build or in an offline environment without a proper offline repository set up, you may install the database server packages manually beforehand and set this option to off. ClusterControl will then skip the installation part and proceed to the database configuration part.
- Disable firewall is enabled. Leave check if you need to Disable firewall (default). Otherwise uncheck if you have filtered entry for your firewall.
- Disable SELinux/AppArmor is enabled. Leave check if you need to Disable SELinux/AppArmor. If you have uncheck Disable SELinux/AppArmor, make sure that you have configured properly to allow creating files and opening sockets for the database to run properly.
- Shutdown the server after the backup is restored is set to Off (recommended). When Off, this assures that the database server is accessible and state is online. Its data directory and config files are also intact and packages are retained and not removed/uninstalled. When On, the BVS will be terminated and when the verify backup job finishes, the
datadir
and configuration files will be removed. This means that Install Software must be enabled for the next Verify Backup job to set up thedatadir
and configuration files.
-
Click Continueto proceed the last step Summary.
-
The last step is Summary. This summarizes the action to be taken when restoring the backup to your cluster. This gives you the time to review your actions before executing the restore process.
-
Click Finish button to execute the job.
To be added soon
Steps to restore a backup (Backup method: xtrabackup and mariabackup)
-
Go to the Clusters dashboard. Choose your target source cluster then click.
-
Go to the Backups tab and make sure you click or set the view to All Backups (default).
-
Choose a backup you would like to restore and click the ellipsis button (...).
-
Select and click Restore option.
-
First step is Configuration.
- Backup: This is selected backup to be restored to the cluster
- Incremental backups: Shows up only when there are incremental backups linked to a
mariabackupfull
orxtrabackupfull
backup. This is a drop down element that lists down the incremental backups link to the full backup (xtrabackup
ormariabackup
) - Restore this backup from: This is the path or storage location of the backup
- Method: This is a panel view just displays information of the backup information such as backup method, size, when it was created, and host where backup was taken
-
Click Continue.
-
Second step is How to restore.
- Choose Restore and verify on standalone host
-
Click Continue.
-
Third step is Settings.
- Restore backup on: Enter a valid Fully Qualified Domain Name (FQDN) or valid IP-address of your target Backup Verification Server (BVS).
- Temporary directory: The tmpdir is used as temporary storage area for the backup files during restore. Make sure it has enough space or assure you have a bit larger disk space than your datadir total size."
- Install software: Toogle on (default) will instruct ClusterControl to install the database software from the package repository during deployment. Toggling off will skip the database installation part. In some cases, where you have a custom database build or in an offline environment without a proper offline repository set up, you may install the database server packages manually beforehand and set this option to off. ClusterControl will then skip the installation part and proceed to the database configuration part.
- Disable firewall is enabled. Leave check if you need to Disable firewall (default). Otherwise uncheck if you have filtered entry for your firewall.
- Disable SELinux/AppArmor is enabled. Leave check if you need to Disable SELinux/AppArmor. If you have uncheck Disable SELinux/AppArmor, make sure that you have configured properly to allow creating files and opening sockets for the database to run properly.
- Shutdown the server after the backup is restored is set to Off (recommended). When Off, this assures that the database server is accessible and state is online. Its data directory and config files are also intact and packages are retained and not removed/uninstalled. When On, the BVS will be terminated and when the verify backup job finishes, the
datadir
and configuration files will be removed. This means that Install Software must be enabled for the next Verify Backup job to set up thedatadir
and configuration files.
-
Click Continueto proceed the last step Summary.
-
The last step is Summary. This summarizes the action to be taken when restoring the backup to your cluster. This gives you the time to review your actions before executing the restore process.
-
Click Finish button to execute the job.
To be added soon
PostgreSQL/TimescaleDB
The following vendors and versions are supported for backup verification:
- PostgreSQL from postgresql.org repository - 12, 13, 14, 15, and 16.
- PostgreSQL from EDB repository - 12, 13, 14, 15, and 16 (requires a valid EDB repository token).
Default Configuration
- Restores backup on a standalone host
- Backups created using ClusterControl's supported backup method shall be available for restore and backup verification
- Only successful backups can be listed and can be attempted for restore and backup verification
- ClusterControl will configure the target Backup Verification Server (BVS) and that covers the database configuration, package repositories, and required package dependencies
- Install software shall be set to On
- Disable firewall is enabled
- Disable SELinux/AppArmor is enabled
- When Shutdown the server after the backup is restored is checked, the BVS will be terminated when the Verify Backup job finishes. The
datadir
and configuration files will be removed. This also means that Install Software must be specified for the next Verify Backup job to set up thedatadir
and configuration files.
Steps to restore a backup (Backup method: pgdumpall and pg_basebackup)
-
Go to the Clusters dashboard. Choose your target source cluster then click.
-
Go to the Backups tab and make sure you click or set the view to All Backups (default).
-
Choose a backup you would like to restore and click the ellipsis button (...).
-
Select and click Restore option.
-
First step is Configuration.
- Backup: This is selected backup to be restored to the cluster
- Restore this backup from: This is the path or storage location of the backup
- Method: This is a panel view just displays information of the backup information such as backup method, size, when it was created, and host where backup was taken
-
Click Continue.
-
Second step is How to restore.
- Choose Restore and verify on standalone host
-
Click Continue.
-
Third step is Settings.
- Restore backup on: Enter a valid Fully Qualified Domain Name (FQDN) or valid IP-address of your target Backup Verification Server (BVS).
- Temporary directory: The tmpdir is used as temporary storage area for the backup files during restore. Make sure it has enough space or assure you have a bit larger disk space than your datadir total size."
- Install software: Toogle on (default) will instruct ClusterControl to install the database software from the package repository during deployment. Toggling off will skip the database installation part. In some cases, where you have a custom database build or in an offline environment without a proper offline repository set up, you may install the database server packages manually beforehand and set this option to off. ClusterControl will then skip the installation part and proceed to the database configuration part.
- Disable firewall is enabled. Leave check if you need to Disable firewall (default). Otherwise uncheck if you have filtered entry for your firewall.
- Disable SELinux/AppArmor is enabled. Leave check if you need to Disable SELinux/AppArmor. If you have uncheck Disable SELinux/AppArmor, make sure that you have configured properly to allow creating files and opening sockets for the database to run properly.
- Shutdown the server after the backup is restored is set to Off (recommended). When Off, this assures that the database server is accessible and state is online. Its data directory and config files are also intact and packages are retained and not removed/uninstalled. When On, the BVS will be terminated and when the verify backup job finishes, the
datadir
and configuration files will be removed. This means that Install Software must be enabled for the next Verify Backup job to set up thedatadir
and configuration files.
-
Click Continueto proceed the last step Summary.
-
The last step is Summary. This summarizes the action to be taken when restoring the backup to your cluster. This gives you the time to review your actions before executing the restore process.
-
Click Finish button to execute the job.
To be added soon
Steps to restore a backup (Backup method: pgbackrest)
-
Go to the Clusters dashboard. Choose your target source cluster then click.
-
Go to the Backups tab and make sure you click or set the view to All Backups (default).
-
Choose a backup you would like to restore and click the ellipsis button (...).
-
Select and click Restore option.
-
First step is Configuration.
- Backup: This is selected backup to be restored to the cluster
- Incremental backups: Shows up only when there are incremental backups linked to a
pgbackrestfull
backup. This is a drop down element that lists down the incremental backups link to the full backup created usingpgbackrest
. - Restore this backup from: This is the path or storage location of the backup
- Method: This is a panel view just displays information of the backup information such as backup method, size, when it was created, and host where backup was taken
-
Click Continue.
-
Second step is How to restore.
- Choose Restore and verify on standalone host
-
Click Continue.
-
Third step is Settings.
- Restore backup on: Enter a valid Fully Qualified Domain Name (FQDN) or valid IP-address of your target Backup Verification Server (BVS).
- Temporary directory: The tmpdir is used as temporary storage area for the backup files during restore. Make sure it has enough space or assure you have a bit larger disk space than your datadir total size."
- Install software: Toogle on (default) will instruct ClusterControl to install the database software from the package repository during deployment. Toggling off will skip the database installation part. In some cases, where you have a custom database build or in an offline environment without a proper offline repository set up, you may install the database server packages manually beforehand and set this option to off. ClusterControl will then skip the installation part and proceed to the database configuration part.
- Disable firewall is enabled. Leave check if you need to Disable firewall (default). Otherwise uncheck if you have filtered entry for your firewall.
- Disable SELinux/AppArmor is enabled. Leave check if you need to Disable SELinux/AppArmor. If you have uncheck Disable SELinux/AppArmor, make sure that you have configured properly to allow creating files and opening sockets for the database to run properly.
- Shutdown the server after the backup is restored is set to Off (recommended). When Off, this assures that the database server is accessible and state is online. Its data directory and config files are also intact and packages are retained and not removed/uninstalled. When On, the BVS will be terminated and when the verify backup job finishes, the
datadir
and configuration files will be removed. This means that Install Software must be enabled for the next Verify Backup job to set up thedatadir
and configuration files.
-
Click Continueto proceed the last step Summary.
-
The last step is Summary. This summarizes the action to be taken when restoring the backup to your cluster. This gives you the time to review your actions before executing the restore process.
-
Click Finish button to execute the job.
To be added soon
Redis Sentinel Cluster
The following vendors and versions are supported for backup verification:
- Redis Sentinel - 6 and 7
Default Configuration
- Restores backup on a standalone host.
- Backups created using ClusterControl's supported backup method shall be available for restore and backup verification.
- Only successful backups can be listed and can be attempted for restore and backup verification.
- ClusterControl will configure the target Backup Verification Server (BVS) and that covers the database configuration, package repositories, and required package dependencies.
- Install software shall be set to On.
- Disable firewall is enabled.
- Disable SELinux/AppArmor is enabled.
- When Shutdown the server after the backup is restored is checked, the BVS will be terminated when the Verify Backup job finishes. The
datadir
and configuration files will be removed. This also means that Install Software must be specified for the next Verify Backup job to set up thedatadir
and configuration files.
Steps to restore a backup
-
Go to the Clusters dashboard. Choose your target source cluster then click.
-
Go to the Backups tab and make sure you click or set the view to All Backups (default).
-
Choose a backup you would like to restore and click the ellipsis button (...).
-
Select and click Restore option.
-
First step is Configuration.
- Backup: This is selected backup to be restored to the cluster
- Restore this backup from: This is the path or storage location of the backup
- Method: This is a panel view just displays information of the backup information such as backup method, size, when it was created, and host where backup was taken
-
Click Continue.
-
Second step is How to restore.
- Choose Restore and verify on standalone host
-
Click Continue.
-
Third step is Settings.
- Restore backup on: Enter a valid Fully Qualified Domain Name (FQDN) or valid IP-address of your target Backup Verification Server (BVS).
- Temporary directory: The tmpdir is used as temporary storage area for the backup files during restore. Make sure it has enough space or assure you have a bit larger disk space than your datadir total size."
- Install software: Toogle on (default) will instruct ClusterControl to install the database software from the package repository during deployment. Toggling off will skip the database installation part. In some cases, where you have a custom database build or in an offline environment without a proper offline repository set up, you may install the database server packages manually beforehand and set this option to off. ClusterControl will then skip the installation part and proceed to the database configuration part.
- Disable firewall is enabled. Leave check if you need to Disable firewall (default). Otherwise uncheck if you have filtered entry for your firewall.
- Disable SELinux/AppArmor is enabled. Leave check if you need to Disable SELinux/AppArmor. If you have uncheck Disable SELinux/AppArmor, make sure that you have configured properly to allow creating files and opening sockets for the database to run properly.
- Shutdown the server after the backup is restored is set to Off (recommended). When Off, this assures that the database server is accessible and state is online. Its data directory and config files are also intact and packages are retained and not removed/uninstalled. When On, the BVS will be terminated and when the verify backup job finishes, the
datadir
and configuration files will be removed. This means that Install Software must be enabled for the next Verify Backup job to set up thedatadir
and configuration files.
-
Click Continueto proceed the last step Summary.
-
The last step is Summary. This summarizes the action to be taken when restoring the backup to your cluster. This gives you the time to review your actions before executing the restore process.
-
Click Finish button to execute the job.
To be added soon
ElasticSearch
In Elasticsearch, verifying a backup has a different approach compared to the other supported database clusters for verifying a backup. Elasticsearch do not need a standalone server or host to verify the backup. Instead, it just run a HTTP request _snapshot/_verify
to verify if the snapshot is healthy or not. Although it does not verify the backup/snapshot by restoring it, but it does the following:
- Access the repository (e.g., a shared filesystem, S3 bucket, etc.),
- Read and write to the repository
- Ensure all nodes in the cluster can access it (if it's a shared location)
- Confirm the repository is usable for snapshot and restore operations.
The reason that it does not verify the content of a specific snapshot (that is the backup you made is intact or restorable), Elasticsearch are used to have humungous amount of data and that could be complicated to determine and restore a backup to identify its ability if its restorable or not.
The following vendors and versions are supported for backup verification:
- Elasticsearch by Elastic versions 7.17, 8.3, 8.15
Default Configuration
- Backups created using ClusterControl's supported backup method shall be available for restore.
- Only successful backups can be listed and can be stored.
- Only elasticsearch-snapshot backups can be verified.
- Sends a HTTP request
_snapshot/_verify
to verify the state of the snapshot or backup.
Steps to restore a backup
-
Go to the Clusters dashboard. Choose your target source cluster then click.
-
Go to the Backups tab and make sure you click or set the view to All Backups (default).
-
Choose a backup you would like to restore and click the ellipsis button (...).
-
Select and click Restore option.
-
First step is Configuration.
- Backup: This is selected backup to be restored to the cluster
- Restore this backup from: This is the path or storage location of the backup
- Method: This is a panel view just displays information of the backup information such as backup method, size, when it was created, and host where backup was taken
-
Click Continue.
-
Second step is How to restore.
- Choose Verify snapshot. This does a snapshot checksum to be validated
-
Click Continueto proceed the last step Summary.
-
The last step is Summary. This summarizes the action to be taken when restoring the backup to your cluster. This gives you the time to review your actions before executing the restore process.
-
Click Finish button to execute the job.
To be added soon