Home > Replication (Private Preview) > 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 Replication page, select your target replication 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.
Test failover jobs do not trigger the failover details reported to the replication policy’s configured Webhook URL.
Refer to the following tables for the details of test failover for each resource type.
| Resource | Test Failover Details |
|---|---|
| Azure Kubernetes Service | Create Kubernetes clusters and disk storage in the policy's target environment. |
| My SQL flexible service | Apply metadata of the latest recovery point to the database replicated in the policy's target environment. |
| PostgreSQL flexible server | Apply metadata of the latest recovery point to the database replicated in the policy's target environment. |
| SQL database | Apply metadata of the latest recovery point to the database replicated in the policy's target environment. |
| Storage account | Apply metadata of the latest recovery point to the storage account replicated in the policy's target environment. |
| Web app | Create web app and related resources in the policy's target environment. |
| Virtual machine | Create virtual machine in the policy's target environment. |
| Virtual machine scale set | Create scale set and related resources in the policy's target environment. |
| Resource | Test Failover Details |
|---|---|
| Aurora and RDS database | Apply metadata of the latest recovery point to the database replicated in the policy's target environment. |
| DynamoDB | Apply metadata of the latest recovery point to the database replicated in the policy's target environment. |
| EC2 instance | Create EC2 instances and policies in the policy's target environment and apply the saved settings. |
| Elastic Beanstalk | Create the resources in the policy's target environment. |
| 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. |
| S3 bucket | Apply metadata of the latest recovery point to the S3 bucket replicated in the policy's target environment. |
| Resource | Test Failover Details |
|---|---|
| Cloud storage | Apply metadata of the latest recovery point to the bucket replicated in the policy's target environment. |
| 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. |
| SQL instance | Apply metadata of the latest recovery point to the instance replicated in the policy's target environment. |
| 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 caused by the failover tests.
Only resources created by the test failover jobs can be reset.
Refer to the tables below for details on how each resource type is reset during test operations.
| Resource | Reset Details |
|---|---|
| Azure Kubernetes Service | Delete the Kubernetes clusters and disk storage created in the policy's target environment. |
| MySQL flexible server | No action will be done to the replicated database. The applied settings will not be reverted. |
| PostgreSQL flexible server | No action will be done to the replicated database. The applied settings will not be reverted. |
| SQL database | No action will be done to the replicated database. The applied settings will not be reverted. |
| Storage account | No action will be done to the replicated storage account. The applied settings will not be reverted. |
| Web app | Delete the created web app and related resources created in the policy's target environment. |
| Virtual machine | Delete the virtual machine created in the policy's target environment. |
| Virtual machine scale set | Delete the scale set and related resources created in the policy's target environment |
| Resource | Reset Details |
|---|---|
| DynamoDB | No action will be done to the replicated storage account. The applied settings will not be reverted. |
| EC2 instance | Delete the EC2 instances and policies created in the policy's target environment. |
| Elastic Beanstalk | Delete the created resources created I the target environment. |
| 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. |
| Aurora and RDS database | No action will be done to the replicated database. The applied settings will not be reverted. |
| S3 bucket | No action will be done to the replicated bucket. The applied settings will not be reverted. |
| Resource | Reset Details |
|---|---|
| Cloud storage | No action will be done to the replicated bucket. The applied settings will not be reverted. |
| 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. |
| SQL instance | No action will be done to the replicated instance. The applied settings will not be reverted. |
| VM instance | Delete VM instance created. IAM role and policy will not be deleted. |
To reset the test failover data of a replication policy, complete the following steps:
On the Replication 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.