Requirements and Limits
Source conditions, compatibility, and limitations to keep in mind before activating a plan
Before activating a plan, it is worth reviewing these conditions to avoid surprises. Some we have confirmed with the current platform and are marked.
Source requirement
🚧 The source must be in a single zone
You can only protect a subscription whose resources are in a single availability zone.
If the subscription distributes resources across multiple zones, it will not appear in the list of possible sources.
Compatibility
Source type
Server and Remote Desktop subscriptions
Operating systems
Broad compatibility objective with Windows and Linux systems {/* TO BE VALIDATED exact scope and whether an agent is required */}
🚧 Agent on the machine
It remains to be confirmed whether the source needs a component inside the machine or not.
The product document proposes agentless replication, while an earlier tutorial mentioned updating an agent on old Windows machines. We'll clarify it before publishing.
Known limitations
SSH keys at the destination
After a failover evacuation, the SSH keys of the source might not appear in the Recovery site panel {/* TO BE VALIDATED with the current platform */}
IP failover
IP failover mode is not yet available (coming soon); today failover is via DNS
Where to follow
What is replicated from the environment: What is replicated.
How backup is activated: Failover and failback.
Last updated
Was this helpful?

