Cloud IBR Expands Disaster Recovery for MSPs — Scalable, on-demand recovery without idle infrastructure

READ PRESS RELEASE
Try It For Free
Book A Demo

Redirecting Internal Workstations to a Recovered Cloud Server

Overview

When a Windows server is recovered to Cloud IBR, internal workstations may still attempt to reach the original on-premises IP address (e.g., 192.168.1.254). This article explains the available methods to redirect or resolve workstation traffic to the recovered cloud server.

Scenario 1: Workstations on the Same Subnet (192.168.1.x)

Example:

  • Original Server: 192.168.1.254
  • Workstations: 192.168.1.x
  • Server recovered in cloud

Recommended Solution: OpenVPN with DNS Configuration

If the workstations are on the same subnet as the original server:

  1. Configure the appropriate DNS settings in the VPN tab within Cloud IBR.
  2. Install and configure the OpenVPN client on each workstation.
  3. Users connect to the VPN.
  4. Workstations resolve the server using its FQDN, such as: server1.yourdomain.com

Once connected, DNS will resolve the FQDN to the recovered server in the cloud.

Scenario 2: Workstations on a Different Subnet Behind a Firewall

Example:

  • Original Server Network: 192.168.1.x
  • Workstations: 192.168.2.x
  • Firewall in place

Recommended Solution: IPSEC Site-to-Site Tunnel

In this case:

  1. Configure an IPSEC tunnel between:
    • Your Firewall
    • The Cloud IBR Linux firewall
  2. Disable the 192.168.1.x network locally on the Firewall.
  3. Route all traffic destined for 192.168.1.x through the VPN tunnel.

DNS Requirements

  • No additional DNS configuration is required if the Active Directory server was successfully recovered in Cloud IBR.
  • Active Directory will continue handling name resolution as before.

Scenario 3: Same Subnet on Both Ends (Layer 2 Bridging Required)

Example:

  • Workstations: 192.168.1.x
  • Recovered servers: 192.168.1.x
  • Same subnet exists at both locations

In this case, simple routing will not work due to subnet overlap.

Advanced Solution: Layer 2 Bridged IPSEC Tunnel

  1. Log into the Cloud IBR Linux firewall.
  2. Configure a Layer 2 Bridged IPSEC tunnel.
  3. Use the strongSwan VPN software installed on the firewall.

This setup allows devices on the local 192.168.1.x network to communicate with devices on the remote 192.168.1.x network as if they were on the same Layer 2 segment.

Note: Layer 2 IPSEC bridging is less commonly requested but can be prioritized for Platinum+ customers upon request.