Skip to main content

​
Overview

Before creating protection plans, register both the primary and DR sites with the XDR controller and configure the replication link between them. This establishes the trust relationship and network path that all replication traffic flows through.
Prerequisites
  • XDR controller deployed and accessible from both sites
  • Network connectivity open between primary and DR sites on TCP 7000–7002
  • Administrator credentials on both sites
  • XDR agent deployed on both sites via XDeploy

​
Site Registration

Register the primary site

Log in to XDeploy (https://connect.<your-domain>) and navigate to Disaster Recovery → Sites → Register Site:

Register the DR site

Repeat the registration process for the DR site, selecting role DR. Provide the DR site’s XDR agent endpoint and its authentication token.
Both sites appear in the Sites list with status REGISTERED.

Create replication link

Navigate to Disaster Recovery → Sites → Replication Links → Create Link and select the primary site as source and DR site as destination.

Configure link settings

Verify connectivity

Click Test Connectivity to verify the link is functional in both directions.
Connectivity test returns CONNECTED with round-trip latency displayed.

​
Bandwidth Management

Replication bandwidth directly affects how quickly the initial sync completes and how tightly the replication lag tracks the configured RPO. Configure bandwidth policies to balance replication performance against production workload impact.
XDR supports per-link and per-plan bandwidth limits. Per-link limits cap total replication throughput on the network connection; per-plan limits allocate bandwidth among multiple plans sharing the same link.Navigate to Disaster Recovery → Sites → Replication Links → [Link] → Bandwidth:Configure these policies directly in the bandwidth settings panel for each replication link.
The initial sync transfers all protected data to the DR site. Estimate completion time before enabling a plan:
Schedule initial sync during off-peak hours or temporarily raise the bandwidth cap to accelerate it. Once initial sync completes, only incremental changes are replicated — bandwidth consumption drops significantly.

​
Replication Modes

Synchronous replication adds write latency equal to the round-trip time between sites on every write operation. For sites separated by more than 5ms RTT, synchronous replication will noticeably degrade application performance. Measure your inter-site latency before enabling synchronous mode.

​
Site Token Management

XDR agents authenticate between sites using site-specific tokens, not user credentials. Manage site tokens from Disaster Recovery → Sites → [Site] → Token Management:
  • View token status: The token expiry date and status are displayed for each registered site
  • Rotate token: Click Rotate Token to generate a new authentication token for the selected site
  • Update peer: After rotating a token, update the peer site with the new token in the peer’s site configuration panel
Rotate site tokens at least annually or immediately if a token is suspected compromised. Token rotation does not interrupt active replication — the old token remains valid for 15 minutes after rotation to allow the update to propagate.

​
Next Steps

Recovery Plans

Create ordered recovery groups and automation hooks

DR Automation

Configure automatic failover triggers and runbook scripts

Monitoring

Alert on replication lag and link throughput degradation

Troubleshooting

Diagnose initial sync failures and connectivity issues