Reference
Unsupported configurations
Known product limitations — point-in-time checkpoint reverse restrictions, AWS Dedicated Host constraints, playbook gaps, and upgrade GUI reverts.
- Product
- Easy Hybrid DR
- Version
- v2.0.3
- Last updated
- Updated
- Reading time
- 1 min read
These configurations are not supported in solution version 2.0.3. Review them when designing protection plans — several affect failback behavior and AWS Dedicated Host recovery.
Point-in-time checkpoints
When point-in-time is configured for a protection plan:
- A workload recovered from a PIT copy cannot be reversed differentially — full data is replicated back.
- With VMware as the target platform, PIT-configured workloads also cannot reverse differentially.
Reverse differential support by platform pair:
| Source | Recovered from | To VMware | To AWS | To Azure |
|---|---|---|---|---|
| VMware | Latest | Data disks only | Yes | Yes |
| VMware | PIT | Not supported | Not supported | Not supported |
| AWS | Latest | Data disks only | Yes | Yes |
| AWS | PIT | Not supported | Not supported | Not supported |
| Azure | Latest | Data disks only | Yes | Yes |
| Azure | PIT | Not supported | Not supported | Not supported |
AWS Dedicated Host
When a workload is configured to recover onto an AWS Dedicated Host, the following are not supported for replication, recovery, and reverse recovery:
- Recovery using an auto-detected AMI — create an AMI matching the source guest OS version, add it to the target site, and set it in the workload's recovery configuration.
- Recovery onto ARM-based Dedicated Hosts.
- Recovery of EFI Linux VMs.
- Auto-discovery and listing of Dedicated Hosts and Host Resource Groups — specify the Dedicated Host ID or Host Resource Group ARN manually in the protection plan.
- License consumption monitoring — ensure required licenses exist in the infrastructure.
Playbooks
Not supported through playbooks:
- Point-in-time configuration settings
- AWS Dedicated Host configuration
- Advanced replication settings: Quiesce Guest OS, and replication priority for AWS as source or target
Configure these by editing the plan after playbook-based creation.
System upgrade GUI
- Reverting node system packages is a manual procedure, documented separately.
- Reverting the database is a manual procedure, documented separately.
Contact support@datamotive.io for either procedure.
Related docs
Was this page helpful?