Home > Infrastructure Resilience > Test Failover and Run Failover > Test Failover and Reset Test Resources
Export to PDFRefer to the following sections on steps to test failover and reset the test results.
To run test failover jobs, complete the following steps:
On the Infrastructure resilience page, select your target resilience policy.
Click Test failover.
In the confirmation window, click OK. A test failover job will start based on the latest recovery point. You can go to Job monitor to check the job details, including the failed over resources and the error details. For details on checking jobs, refer to Job Monitor.
*Note: Test failover jobs do not trigger the failover details reported to the resilience policy’s configured Webhook URL.
Refer to the following table for the details of test failover for each resource type.
| Cloud Service Type | Resource | Test Failover Details |
|---|---|---|
| Microsoft Azure | Azure Kubernetes Service | Create Kubernetes clusters and disk storage in the policy’s target environment. |
| Microsoft Azure | My SQL flexible service | Apply metadata of the latest recovery point to the database replicated in the policy’s target environment. |
| Microsoft Azure | PostgreSQL flexible server | Apply metadata of the latest recovery point to the database replicated in the policy’s target environment. |
| Microsoft Azure | SQL database | Apply metadata of the latest recovery point to the database replicated in the policy’s target environment. |
| Microsoft Azure | Storage account | Apply metadata of the latest recovery point to the storage account replicated in the policy’s target environment. |
| Microsoft Azure | Web app | Create web app and related resources in the policy’s target environment. |
| Microsoft Azure | Virtual machine | Create virtual machine in the policy’s target environment. |
| Microsoft Azure | Virtual machine scale set | Create scale set and related resources in the policy’s target environment. |
| Amazon Web Services | Aurora and RDS database | Apply metadata of the latest recovery point to the database replicated in the policy’s target environment. |
| Amazon Web Services | DynamoDB | Apply metadata of the latest recovery point to the database replicated in the policy’s target environment. |
| Amazon Web Services | EC2 instance | Create EC2 instances and policies in the policy’s target environment and apply the saved settings. |
| Amazon Web Services | Elastic Beanstalk | Create the resources in the policy’s target environment. |
| Amazon Web Services | Elastic Kubernetes Service | Create Kubernetes cluster, disk storage, IAM role, and IAM policy related to the cluster in the target environment.*Note: If there are IAM role and policy with the same names, new ones will not be created. |
| Amazon Web Services | S3 bucket | Apply metadata of the latest recovery point to the S3 bucket replicated in the policy’s target environment. |
| Google Cloud | Cloud storage | Apply metadata of the latest recovery point to the bucket replicated in the policy’s target environment. |
| Google Cloud | Kubernetes engine | Create Kubernetes cluster, disk storage, IAM role, and IAM principle and role of related instance.*Note: If there are IAM role and policy with the same names, new ones will not be created. |
| Google Cloud | SQL instance | Apply metadata of the latest recovery point to the instance replicated in the policy’s target environment. |
| Google Cloud | Virtual Machine (VM) instance | Create VM instance, IAM roles, and IAM principles related to the instance.*Note: If there are IAM role and policy with the same names, new ones will not be created. |
After running test failover jobs, you can reset the test failover data to save your cloud service usage or reset the target resource to avoid unexpected data loss caused by the failover tests.
*Note: Only resources created by the test failover jobs can be reset.
Refer to the table below for details on how each resource type is reset during test operations..
| Cloud Service Type | Resource | Reset Details |
|---|---|---|
| Microsoft Azure | Azure Kubernetes Service | Delete the Kubernetes clusters and disk storage created in the policy’s target environment. |
| Microsoft Azure | MySQL flexible server | No action will be done to the replicated database. The applied settings will not be reverted. |
| Microsoft Azure | PostgreSQL flexible server | No action will be done to the replicated database. The applied settings will not be reverted. |
| Microsoft Azure | SQL database | No action will be done to the replicated database. The applied settings will not be reverted. |
| Microsoft Azure | Storage account | No action will be done to the replicated storage account. The applied settings will not be reverted. |
| Microsoft Azure | Web app | Delete the created web app and related resources created in the policy’s target environment. |
| Microsoft Azure | Virtual machine | Delete the virtual machine created in the policy’s target environment. |
| Microsoft Azure | Virtual machine scale set | Delete the scale set and related resources created in the policy’s target environment |
| Amazon Web Services | DynamoDB | No action will be done to the replicated storage account. The applied settings will not be reverted. |
| Amazon Web Services | EC2 instance | Delete the EC2 instances and policies created in the policy’s target environment. |
| Amazon Web Services | Elastic Beanstalk | Delete the created resources created I the target environment. |
| Amazon Web Services | Elastic Kubernetes Service | Delete the Kubernetes cluster and disk storage. The disk snapshot will be kept in the target resource group until the retention period ends. IAM role and policy created will not be deleted. |
| Amazon Web Services | Aurora and RDS database | No action will be done to the replicated database. The applied settings will not be reverted. |
| Amazon Web Services | S3 bucket | No action will be done to the replicated bucket. The applied settings will not be reverted. |
| Google Cloud | Cloud storage | No action will be done to the replicated bucket. The applied settings will not be reverted. |
| Google Cloud | Kubernetes engine | Delete Kubernetes clusters and disk storage. Snapshot will remain until the retention period ends.IAM role and policy created will not be deleted. |
| Google Cloud | SQL instance | No action will be done to the replicated instance. The applied settings will not be reverted. |
| Google Cloud | VM instance | Delete VM instance created.IAM role and policy will not be deleted. |
To reset the test failover data of a resilience policy, complete the following steps:
On the Infrastructure resilience page, select the target policy that has run the test failover job.
Click Reset test resources.
In the confirmation window, click OK. A reset job will start to run. You can go to Job monitor to check the job details, including the failed over resources and the error details. For details on checking jobs, refer to Job Monitor.