DR Testing

DR Testing

Overview

Acronis Disaster Recovery (DR) extends standard backup protection by allowing protected servers to be spun up as fully functional virtual machines in the Acronis cloud if the original server goes down. Instead of just restoring files, DR keeps a ready-to-launch replica (a "recovery server") so operations can fail over quickly during an outage, then fail back once the primary environment is restored.

This article covers enabling DR for the first time, adding servers into DR protection, configuring cloud replication, building and tuning recovery servers, choosing recovery points, and building/validating a full disaster recovery plan.

1. Performing a test failover

Though performing a test failover is optional, we recommend that you make it a regular process with a frequency that you find adequate in terms of cost and safety. A good practice is creating a runbook – a set of instructions describing how to spin up the production environment in the cloud.

You must create a recovery server in advance to protect your devices from a disaster.

You can perform failover only from recovery points (backups) that were created after the recovery server of the device was created.

At least one recovery point must be created before failing over to a recovery server. The maximum number of recovery points that is supported is 100.

To perform a test failover

  1. Select the original machine or select the recovery server that you want to test.

  2. Click Disaster Recovery.

    The description of the recovery server opens.

  3. Click Failover.
  4. Select the failover type Test failover.
  5. Select the recovery point (backup), and then click Start.

  6. If the backup that you selected is encrypted by using encryption as a machine property:

    1. Enter the encryption password for the backup set.

      The password will only be saved temporarily and will be used only for the current test failover operation. The password is automatically deleted from the credentials store if the test failover is stopped, or after the test failover completes.

    2. To save the password for the backup set and use it in subsequent failover operations, select the Store the password in a secure credentials store... check box and then, in the Credentials name field, enter a name for the credentials.

      The password will be stored in a secured credentials store and will be applied automatically in subsequent failover operations. However, saving passwords might conflict with your compliance obligations.

    3. Click Done.

    When the recovery server starts, its state changes to Testing failover.

  7. Test the recovery server by using any of the following methods:

    • In Disaster Recovery > Servers, select the recovery server, and then click Console.
    • Connect to the recovery server by using RDP or SSH, and the test IP address that you specified when creating the recovery server. Try the connection from both inside and outside the production network (as described in "Point-to-site connection").

    • Run a script within the recovery server.

      The script may check the login screen, whether applications are started, the Internet connection, and the ability of other machines to connect to the recovery server.

    • If the recovery server has access to the Internet and a public IP address, you may want to use TeamViewer.

  8. When the test is complete, click Stop testing.

    The recovery server is stopped. All changes made to the recovery server during the test failover are not preserved.

2. Start a Recovery Server in Test Mode

Procedure

  1. Open Disaster Recovery.
  2. Select the protected workload.
  3. Choose Run in Test Mode.
  4. Select the recovery point.
  5. Configure networking if required.
  6. Click Start.
  7. Wait for the server to boot.

Verification

  • Recovery server status is Running.
  • Operating system boots normally.
  • No startup errors are displayed.

Best Practices

  • Use isolated networking during testing.
  • Avoid connecting the test server to the production network.

3. Verify Applications during Test Failover

Procedure

  1. Log in to the recovery server.
  2. Launch each published application.
  3. Verify services are running.
  4. Confirm application data is available.
  5. Review application event logs.

Verification Checklist

  • Applications launch successfully.
  • Services start automatically.
  • No application errors occur.
  • Users can access required features.

4. Verify Database Connectivity

Procedure

  1. Start the database service.
  2. Verify database status.
  3. Test database connections.
  4. Run a sample query.
  5. Confirm application connectivity.

Verification Checklist

  • Database service is running.
  • Client connections succeed.
  • Data is accessible.
  • No database errors are reported.

5. Verify User Access

Procedure

  1. Sign in using a test user account.
  2. Launch required applications.
  3. Verify permissions.
  4. Test shared folders.
  5. Confirm remote access.

Verification Checklist

  • User authentication succeeds.
  • Applications are available.
  • File shares are accessible.
  • Network resources respond correctly.

6. Stop a Test Failover

Procedure

  1. Open Disaster Recovery.
  2. Select the running recovery server.
  3. Click Stop Test Failover.
  4. Confirm the operation.
  5. Wait until the server status changes to Stopped.

Verification

  • Recovery server stops successfully.
  • Test resources are released.
  • Production systems remain unaffected.

7. Prepare a DR Test Report

Test Information

  • Test date
  • Administrator
  • Protected server
  • Recovery point used

Recovery Metrics

  • Recovery Time Objective (RTO)
  • Recovery Point Objective (RPO)
  • Server startup time

Validation Results

  • Recovery server started successfully
  • Applications verified
  • Database connectivity verified
  • User authentication verified
  • Network connectivity verified
  • File access verified

Issues Identified

Document:

  • Errors encountered
  • Root cause
  • Corrective actions
  • Recommendations

Test Outcome

  • Pass – Recovery environment is ready.
  • Pass with Recommendations – Minor improvements required.
  • Fail – Additional remediation is required before the disaster recovery plan is considered production-ready.

    • Related Articles

    • Acronis Backup Recovery and Restore

      This document explains how to restore files, disks, and entire machines using Acronis Cyber Protect Cloud. It also covers bootable recovery media, Universal Restore, SQL database recovery, restore testing, and post-recovery validation. Platform: ...

    • How to Setup Virtual Printer with TSPlus?

      Here's a step-by-step guide to help you set up and use TSplus Virtual Printer effectively. ?️ TSplus Virtual Printer Setup Guide ✅ Purpose: To allow remote users to print from a TSplus server to their local printer seamlessly during an RDP or web ...

    • Understanding the Differences Between RDP, TSplus RemoteApp, and HTML5 Remote Access

      ? Summary Remote access technologies allow users to interact with desktop environments or applications hosted on remote servers. Among the most commonly used solutions are: Microsoft RDP (Remote Desktop Protocol) TSplus RemoteApp HTML5 Web Access ...